Updated 2026-09-14; item 3 amended 2026-09-24. This is the current execution order; the older inventory in docs/app/MVP_PASS_2026_09_07.md retains the broader scope and history.
Develop a bounded Super change inside Super: select a saved task and repository, prepare source files, send the assigned bot a request, observe progress or recover from a failure, review the proposed bytes, run checks, explicitly accept, and restore the same work after restart.
Continue work chooses one task and guides preparation, reply, review, checks and completion.
Editor and retained reviews link to exact task revisions and source snapshots.
Schematics fills the workspace, with automatic routing, zoom, pan and floating panels.
Idle worker status checks no longer create a self-triggering refusal/refresh loop.
User confirmed the desktop is responsive after that repair.
Hardware track: Two-machine fleet MVP. Both hosts have machine and guest detail pages, a compact Machines directory, and consistent schematic naming. Separate Proxmox and bhyve Linux guests have passed restricted task-bound checks and interrupted-receiver recovery. Wifibox remains separate. Physical network-outage and whole-host reboot drills remain open.
Task activity across work surfaces — implemented and tested. Show actual request lifecycle, bounded assistant-text preview and request events in Continue work and Schematics. Match bot, task revision and runtime session. Keep graph nodes stable while text arrives. Older saved replies remain history after reload.
Connection and interruption recovery — current increment. Continue work, task status and schematic activity distinguish capacity limits, expired sign-in, cancellation, timeout and unavailable-provider replies. Restored task attachments no longer hide failure guidance behind a Send action. Recovery opens the assigned conversation, preserves drafts and requires an explicit retry. Live recovery observations remain session-only; saved conversation history remains separate. Controlled native provider checks cover connection failure, capacity failure, restored files and successful explicit retry. A real provider reply remains a separate gate.
Repeat the full Super-on-Super cycle. Repeat the full Super-on-Super cycle using the assigned bot, bt_0034, with a working provider connection. Record the producing model and provider configuration for each proposal-producing turn. Produce and inspect a real change, run required checks, explicitly accept it, and verify restart recovery. Provider fixture tests do not satisfy this gate.
Amended 2026-09-24 (ProjectAmp2 `REVISION_REGISTER.md` R98). The original wording was "Use the assigned Fable bot with a working provider connection." When it was written, bt_0034 was both named "Super · Fable 5.1" and configured for claude-fable-5-1; it was later renamed and moved to Opus. The gate now names the bot by identity and records its model per turn instead of requiring one. Under this wording the r2 run (Opus 5.5, accepted as da_0131) is eligible on the model condition. That does not complete the gate: inspection of the accepted diff and of the acceptance and restart evidence remains open.
Mobile observation gate — Android browser regression implemented. The read-only web companion passes grouped pairing, exact task identity, observation withdrawal, interrupted-connection recovery, background/resume, world replacement, failed logout and code-renewal checks on Android 15 / Chrome 124 with controlled records. The existing private Tailscale HTTPS route now serves the current companion at /mobile. A same-node client with certificate verification paired with the actual saved workspace and matched all 14 task identities; one-use codes, renewal, logout and read-only refusals passed. The user confirmed physical-phone pairing on 2026-09-14. The separate native/Expo client remains open. Before/after PNG attachments now belong to a task revision and can be read by paired mobile devices; Android browser image rendering and withdrawal checks pass. Physical-phone screenshot viewing has not yet been confirmed.
Expand internal diagrams and observed execution. Add remaining screen internals, evidence-linked events and follow-active behavior. Per-edge execution and WRL integration require corresponding runtime observations.
Each increment saves test output, native checks, inspected screenshots and saved-world installation verification in the development workspace's outputs/. The task-activity increment uses outputs/task-activity/. The detailed graph plan remains in SCHEMATICS.md.
Task-activity validation: 175 behavior tests and 42 native app checks passed. Native provider fixtures cover pending, complete, failure, task isolation and reload; a real Fable request remains a separate gate.
Continue work, plan details and Schematics now have task-bound remote-check controls and device-local history. Execution is enabled through the approved restricted Proxmox check key and fixed VM-100 bridge. Three real task-bound checks passed; an interrupted local result receiver recovered the original receipt without resubmission. See FLEET_MVP.md. The separate bhyve guest is now enrolled with destination-bound receipts and a restricted SSH bridge. Next: a physical network-outage drill. Actual app screenshots and recovery evidence are in outputs/fleet-active/. Earlier simulation screenshots remain labeled separately.
Bot selection now opens its conversations in the sidebar: pinned first, then recent across providers. Existing local histories migrate in place. Titles are requested as metadata in the first successful reply using the selected provider, without a second naming request, with a readable fallback on failure; manual edits are retained. Bot settings and Work are separate panels, with an independently scrolling chat transcript and composer. Starting a new conversation, typing or navigating cancels an older pending history open so delayed provider setup cannot replace a newer draft.
Development task details accept Before and After PNG attachments (2 MB, up to 4096 pixels each), scoped to world and task revision. Mobile can read the current revision through its existing paired session. These are user-attached visual evidence, not an automated acceptance signal or a captured build provenance claim. Storage retains up to 100 task revisions; managing old screenshot revisions and automatic capture are follow-up work.
Before/after attachments now have explicit removal with an immediate Undo action while the panel stays open. Removing the final image releases its storage slot. Controls show the task revision and PNG limits, preserve keyboard focus, announce save/removal outcomes, and recheck task identity after file reading. Native interaction and storage tests cover removal, restoration, retention of the other image, and updated mobile observations. Historical revision management and automatic capture remain open.
Task screenshots now support an explicit AI review against each acceptance-criteria line. Findings distinguish visually met, missing and needs-verification, with reasons and possible regressions. A reviewer can link a recorded test snapshot or retained accepted build, inspect the checks and exact source/executable identity, and record that the findings were inspected. This does not accept the task or bypass required checks. Images remain manually attached with unverified capture origin; automatic capture from a known preview remains open.
The review freezes criteria, both image digests, and selected evidence. Changed evidence makes older findings stale. Mobile shows findings read-only and withdraws loaded images/findings when desktop evidence changes. Model and effort choices are separate from bot conversation preferences. Claude uses real image blocks over stream-json; API adapters support their image formats. The Codex connection explicitly refuses visual review until image support is added.
Controlled native, storage and Android checks pass. The attempted real Claude Opus 5 / medium image check reached an expired OAuth session; a new sign-in is needed to complete real-provider validation. This is separate from the full Super-on-Super acceptance gate.