A job can reach `shipped` via autoship PATCH, the `ship` operator action, or a terminal lease release, but the run-level `result` was left at whatever the factory last reported (e.g. `review`), so the dashboard showed a shipped job with a non-terminal run result. - Add markLatestRunShipped(): on any transition to `shipped`, set the latest run result to `shipped` (+ endedAt if unset). Idempotent, best-effort. - Wire it into patchJobFenced (ungated; budget accrual stays flag-gated) and the `ship` operator action. - Document the testing->shipped paths (factory autoship vs `ship` operator action) and the run-mirroring in docs/GIGAFACTORY/FLEET_CONTROL_PLANE.md. Tests: +2 (patchJobFenced->shipped and operator ship both set run.result=shipped). Fleet suite 180 pass; tsc clean. Generated with [Devin](https://cli.devin.ai/docs) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| FLEET_CONTROL_PLANE.md | ||
| gigafactory-phase3-progress.md | ||
| README.md | ||
| ROADMAP_COMPLETION_AUDIT.md | ||
| TASKS_TO_COMPLETE.md | ||
Gigafactory — Platform Docs
Planning, status, and operational docs for the Agent Gigafactory fleet
backend that lives in this repo (services/platform-service fleet module +
the dashboards/tracker-web UI).
Contents
| Doc | What it is |
|---|---|
ROADMAP_COMPLETION_AUDIT.md |
Audit of the current build state against the roadmap: completed / partial / missing features, risks, and prioritized remaining work. |
TASKS_TO_COMPLETE.md |
The actionable, priority-ordered completion checklist that companions the audit. |
gigafactory-phase3-progress.md |
Phase-3 progress log: per-slice end-state. |
FLEET_CONTROL_PLANE.md |
Operational guide for running and using the fleet control plane. |
Source of truth
The canonical spec and system overview live in the runner repo,
learning_ai_devops_tools, under
agent-queue/docs/GIGAFACTORY/ (GIGAFACTORY_ROADMAP.md,
GIGAFACTORY_SYSTEM_OVERVIEW.md).