Files
browser/platform/dto
npc0-hue a822e9250a Store SCUM facts in typed platform tables
Run pushes typed SCUM facts through POST /api/v1/run/scum/facts, but the
production router rejected that path before the signature middleware because
runServiceRequest listed individual Run channel prefixes, and MySQL kept SCUM
rows inside the whole metadata snapshot instead of platform tables.

- /api/v1/run/ is now the signed machine channel space while
  /api/v1/run/endpoints keeps normal bearer/admin authorization.
- MySQL gets real scum_user, scum_user_trajectory, scum_vehicle,
  scum_vehicle_trajectory and scum_vehicle_lock tables with parameterized
  per-row repositories instead of full snapshot rewrites. Snapshot-shaped
  tables from the unreleased interim build are replaced, and SCUM rows still
  inside a metadata snapshot are migrated once.
- Facts ingest verifies the target server plugin type and converges stale
  online users to offline after SCUMUserOfflineAfter.
- The plugin page and browser read one bounded /scum/surface response instead
  of five list calls per refresh.

Call-count budget for one server: per 5s facts batch, one SELECT plus one
INSERT/UPDATE per reported user and vehicle, one INSERT per moved trajectory
sample or new lock row, one bounded stale-user SELECT, and a trajectory
retention DELETE at most once per hour. One browser refresh issues one surface
request every 15s instead of five list requests.
2026-09-15 12:12:11 +08:00
..
2026-07-20 16:42:33 +08:00
2026-07-11 14:56:10 +08:00
2026-08-26 23:06:06 +08:00
2026-07-11 14:56:10 +08:00
2026-07-11 14:56:10 +08:00
2026-09-07 20:26:20 +08:00
2026-08-20 17:58:36 +08:00

platform/dto

Request and response DTOs live here. Do not define API request or response structs inside handlers.

Initial DTO groups:

  • auth: login/session payloads.
  • users: user and role management payloads.
  • game_plugins: game management plugin marketplace and installation payloads.
  • server_instances: create server, update config, lifecycle, and detail payloads.
  • ai_providers: AI provider create/update/test/invoke payloads.
  • run: run registration, capability, and status payloads.
  • jobs: job claim, ack, progress, result, cancel, and reconcile payloads.
  • artifacts: chunk upload/download and metadata payloads.
  • logs: ingest, query, tail, and analysis-window payloads.