[Plan] Reframe delivery into MVP, operations and distribution releases

[jjangg96]

Goal

Reorganize delivery into an internal single-host MVP, an everyday operations release, and a general-distribution release without weakening the existing Scale Set recovery objective or safety/review gates.

Authorization

The maintainer explicitly accepted the three-stage proposal in the coordinator conversation. This is delivery sequencing, not permission for new live operations or for declaring partial evidence complete.

Approved delivery stages

1. Internal MVP: this Mac, one organization, one private test repository, one execution backend, concurrency one, manual App setup. Demonstrate real job execution and owned cleanup plus recovery/quarantine at ACK, acquisition and JIT boundaries.
2. Everyday operations: practical install/start/stop/status, restart recovery, bounded scaling and repeated operational use.
3. General distribution: multi-organization support, additional Linux/macOS execution modes, automated onboarding, signing/update/diagnostics and broad qualification.

Scope

• Update PLAN, BACKLOG, EXECUTION, HANDOFF and issue mapping coherently. Preserve G01 issue [G01] Prove Scale Set delivery, acquisition and drain contracts #1 exact Goal and acceptance evidence. Keep current active goal; this planning task must not create another native goal.
• Map every existing issue to a release stage, separating experimental evidence from shipped capabilities. Where an existing issue mixes MVP and later acceptance, propose explicit child issues and dependencies rather than marking the original Done or silently dropping criteria.
• Clarify one MVP backend from existing reviewed implementation/evidence; do not expand into a second backend by default.
• Keep independent review, exact-head clean Codex review and CI, TDD, credential/ownership/busy-drain safeguards, and concrete maintainer authorization for live operations.
• Main implementation/document author Grok 4.6 xhigh; independent review Luna max. Preserve historical authorship and existing active Project ownership.
• Existing [G01g] Wire paired terminal execution through a bounded broker handoff #60 runtime correction and [G02] Prove local App enrollment and launchd credential access #2 readiness review continue without conflicting writes. No production implementation of dependency-blocked issues is authorized by this planning issue alone.

Acceptance

• Three release stages and concrete user-visible exit criteria documented.
• All current issues mapped, with native dependency updates only where justified and no false Done states.
• Minimum executable MVP critical path identified, with unimplemented CLI/daemon/install work explicit.
• Existing G01 full objective preserved; no live evidence represented as complete.
• Focused independently reviewed PR, exact-head clean Codex verdict and CI before merge.

Dependencies

No prerequisite for this planning-only change. Production work retains its existing evidence dependencies.

[jjangg96]

Maintainer-approved release reorganization (preserving history)

The Project now has an additive Release field and all 33 items have matching release:* issue labels. Original M0–M5 Stage/milestones, Goal, issue bodies, assignees, Agent, statuses, closed states and native dependency edges are retained. No issue/PR was deleted, archived, closed or reopened for this reclassification.

Release	Full-acceptance issue placement
R1 — Internal MVP	#1 #3 #30 #44 #46 #47 #50 #52 #54 #60 #61 #64 #66
R2 — Everyday operations	#4 #5 #6 #7 #9 #10 #12 #13 #14 #15 #20 #40
R3 — General distribution	#2 #8 #11 #16 #17 #18 #19
Future research	#21

Placement means the release that needs the complete original scope; it is not a claim that none of its safe subset is required earlier. In particular #2 remains In progress: manual single-organization credential evidence is needed for R1, but its full automated/two-organization qualification belongs to R3. Minimum R1 contract, authority, recovery, worker and execution-command slices must be explicitly split/linked rather than bypassing #4–#15 dependencies. Existing #1 exact recovery Goal remains unchanged.

Next planning deliverable in this issue: explicitly scoped R1 child issues, native dependency mapping, and a reviewed documentation PR synchronizing PLAN/BACKLOG/HANDOFF/EXECUTION. Until those edges are reviewed and justified, existing production dependency gates stay in force; release relabeling does not make blocked implementation Ready.

Rollback: remove only the newly added release:* labels and Release values/field if the maintainer reverses this plan; original planning records remain available unchanged. Main authoring Grok 4.6 xhigh, independent review Luna max; historical model attribution unchanged.

[jjangg96]

R1 vertical-slice issues created and native relations verified

• [R1] Prove manual single-organization credentials for the foreground MVP #67 (child of [G02] Prove local App enrollment and launchd credential access #2): manual single-organization foreground credential evidence. Ready, no dependency on broader automated/multi-org/launchd qualification; no implicit live authorization.
• [R1] Deliver one foreground command for a bounded single-worker lifecycle #68 (child of [G13] Integrate reconciliation, drain and safe restart #13; coordinated subset of [G04] Freeze CLI configuration, provider and scaling contracts #4–[G15] Implement startup, shutdown and safe configuration updates #15): one foreground command for the existing paired Linux-container backend on this Mac, concurrency one. Blocked by [G01g] Wire paired terminal execution through a bounded broker handoff #60, [Plan] Reframe delivery into MVP, operations and distribution releases #66, [R1] Prove manual single-organization credentials for the foreground MVP #67. No second backend/native jobs added; minimal contract must be reviewed before implementation.
• [R1] Qualify the internal MVP with an authorized real job and recovery evidence #69 (child of [G16] Build repeatable two-organization runtime qualification #16): actual private job plus complete ACK/acquisition/JIT recovery qualification. Blocked by [G01] Prove Scale Set delivery, acquisition and drain contracts #1 and [R1] Deliver one foreground command for a bounded single-worker lifecycle #68; a happy-path run is insufficient.

All three are in Project2 Release R1 with actual native parent and blockedBy relations, exact Goal text and dependency fields. The original #4 blockers (#1/#2/#3) remain unchanged; original full-scope parents are not closed or weakened. Existing active #1/#2/#60 status and Agent remain unchanged. There are now 36 Project items. Further R1 details and the supporting documentation PR remain tracked here; no implementation permission inferred while #68 is blocked.

Rollback is additive: remove these new child/dependency relations and R1 metadata only if explicitly requested, retaining issue history. No original issue body, original dependency, or closed state was removed.

[jjangg96]

Project/issue release classification and native R1 child relations are applied and verified. Remaining documentation PR is currently blocked by an Orca cross-project coordinator-binding collision, not a product dependency: the dedicated planning worktree exists, but a conflict-free Grok author dispatch could not be established. Project status is Blocked to reflect this; no original issue status, dependency or acceptance was changed. Resume documentation authoring after coordinator identity is repaired; do not treat this planning-only infrastructure blocker as evidence that runtime work is complete.

[jjangg96]

Coordinator connection restored after the unrelated run tasks completed, without stopping or replacing any worker. A dedicated Grok 4.6/xhigh documentation task is now assigned in the separate release-reframe worktree, reading the already-applied 36-item mapping and #67/#68/#69 native relations rather than recreating them. Project #66 returns to In progress; original #1/#2/#60 ownership and statuses remain unchanged. Runtime authority-path correction continues in its own worktree. No live authorization or merge gate changed.