docs: synchronize R1/R2/R3 delivery plan (#66) - #70
Conversation
Map the maintainer-accepted three-release sequencing onto the existing issue inventory without changing G01's recovery Goal, native parent edges, or historical M0-M5/Agent records.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b76e54c1f1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ### R2 — Everyday operations | ||
|
|
||
| Practical install/start/stop/status, restart recovery, bounded scaling and repeated operational use. Full original acceptance of #4, #5, #6, #7, #9, #10, #12, #13, #14, #15, #20 and completed #40. Original G04 blockers (#1/#2/#3) and G13 blockers, including native-macOS #11, remain in force. |
There was a problem hiding this comment.
Under the declared authoritative R1→R2→R3 sequencing, this R2 exit cannot be completed: #4 remains blocked by #2 (assigned R3), #13 by #11 (R3), and #20 by #17/#18 (R3, explicitly reiterated below). Consequently, satisfying the “full original acceptance” promised here requires completing major R3 work first, so the release map cannot drive the advertised sequence. Move the prerequisites into R2, move the dependents to R3, or create bounded R2 children while preserving the native gates.
AGENTS.md reference: AGENTS.md:L5-L6
Useful? React with 👍 / 👎.
| "agent": "Grok 4.6 xhigh", | ||
| "review_agent": "Luna max", | ||
| "dependencies": [ | ||
| "#60", |
There was a problem hiding this comment.
This is the only dependencies entry in the machine-readable backlog that does not resolve to another record's key: the active #60/G01g node is omitted, while this edge uses the raw string #60 and the other two edges use keys. A graph or readiness consumer therefore cannot consistently resolve #68's blocker and must either reject or misinterpret the dependency. Add a keyed G01g record or model external issue references consistently.
AGENTS.md reference: AGENTS.md:L5-L5
Useful? React with 👍 / 👎.
| - set the Project Agent field to `Luna max` when no override exists, otherwise set | ||
| it to the explicitly requested routing; | ||
| it to the explicitly requested routing when that option exists; |
There was a problem hiding this comment.
For the newly exempted #67/#68/#69 path, Grok has no Project Agent option, yet the executable workflow below still initializes AGENT_OPTION_ID to Luna and unconditionally writes it. Limiting this instruction to cases where an override option exists therefore makes dispatching #67 record Luna in the Project despite its issue contract requiring Grok, which can route implementation to the wrong model. Explicitly skip the Agent edit or preserve an unset value for issue-body-only overrides while retaining Luna as the reviewer.
AGENTS.md reference: AGENTS.md:L6-L6
Useful? React with 👍 / 👎.
| | [#67](https://github.com/1XP-AI/gh-runnerd/issues/67) | R1 subset of [#2](https://github.com/1XP-AI/gh-runnerd/issues/2): manual single-organization credentials. Ready; no live App/Keychain/launchd authorization. Parent #2 stays In progress on R3. | | ||
| | [#60](https://github.com/1XP-AI/gh-runnerd/issues/60) G01g | Bounded broker handoff for the paired Linux-container path. In progress in a separate worktree. | | ||
| | [#66](https://github.com/1XP-AI/gh-runnerd/issues/66) | Planning and documentation synchronization. | | ||
| | [#68](https://github.com/1XP-AI/gh-runnerd/issues/68) | R1 subset of [#13](https://github.com/1XP-AI/gh-runnerd/issues/13), coordinated slice of #4–#15: one foreground command, capacity one. Blocked by #60, #66 and #67. Freeze the minimal contract before implementation. Completing #68 does not complete #4–#15. | |
There was a problem hiding this comment.
Once #60/#66/#67 finish, this makes #68 dispatchable even though full G01 #1 remains unresolved until the later #69 qualification and full G02 #2 is deferred to R3. Because #68 explicitly implements a production slice of #4–#15, this schedules dependent implementation before the repository's G01/G02 evidence gates are resolved; completing child subsets does not satisfy those parent gates. Make #68 depend on full #1/#2, or restrict it to non-production contract/evidence work until those gates pass.
AGENTS.md reference: AGENTS.md:L11-L11
Useful? React with 👍 / 👎.
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee4d47b68e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| The maintainer-authorized override for [#66](https://github.com/1XP-AI/gh-runnerd/issues/66) | ||
| and R1 children [#67](https://github.com/1XP-AI/gh-runnerd/issues/67)/[#68](https://github.com/1XP-AI/gh-runnerd/issues/68)/[#69](https://github.com/1XP-AI/gh-runnerd/issues/69) | ||
| is main author Grok 4.6 xhigh with independent Luna max review. Do not create a |
There was a problem hiding this comment.
For #66/#67/#68/#69, this establishes Grok as implementer and Luna as the required independent reviewer, but the reusable handoff prompt and final checklist still instruct agents to obtain independent review using the current user-selected model/effort—Grok for these issues. An agent following that operational handoff can therefore use the wrong reviewer and proceed without the mandated independent Luna gate; update those downstream instructions to distinguish implementer selection from reviewer selection.
AGENTS.md reference: AGENTS.md:L6-L6
Useful? React with 👍 / 👎.
Distinguish implementer selection from reviewer selection in the handoff prompt, dispatch text and verification checklist.
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dbd20b1c2c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "title": "Wire paired terminal execution through a bounded broker handoff", | ||
| "stage": "M0 - Evidence gates", | ||
| "agent": "Luna max", | ||
| "dependencies": [], |
There was a problem hiding this comment.
The newly added keyed G01g record fixes #68's reference to #60 but models G01g as a root node, even though the synchronized maps explicitly record #60 as blockedBy #54 (docs/ISSUES.md lines 73 and 89; docs/BACKLOG.md line 17). Any readiness or dependency consumer of backlog.json therefore loses this native gate; add a keyed record for #54 and list it here, or represent the external issue edge consistently.
AGENTS.md reference: AGENTS.md:L5-L5
Useful? React with 👍 / 👎.
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 29f54e9c67
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | [#67](https://github.com/1XP-AI/gh-runnerd/issues/67) | R1 subset of [#2](https://github.com/1XP-AI/gh-runnerd/issues/2): manual single-organization credentials. Ready; no live App/Keychain/launchd authorization. Parent #2 stays In progress on R3. | | ||
| | [#60](https://github.com/1XP-AI/gh-runnerd/issues/60) G01g | Bounded broker handoff for the paired Linux-container path. In progress in a separate worktree. | | ||
| | [#66](https://github.com/1XP-AI/gh-runnerd/issues/66) | Planning and documentation synchronization. | | ||
| | [#68](https://github.com/1XP-AI/gh-runnerd/issues/68) | R1 subset of [#13](https://github.com/1XP-AI/gh-runnerd/issues/13), coordinated slice of #4–#15. Native blockers remain #60, #66 and #67; do not add #1/#2 without an explicit ask. **First authorized work is a reviewed minimal contract**, not `cmd/gh-runnerd` production behavior and not a G04/G13 bypass. Implementation after that contract still reuses the reviewed G01 paired Linux-container path (#54/#60) and R1 credentials (#67). It must not claim G01 or G02 complete. Completing #68 does not complete #4–#15. | |
There was a problem hiding this comment.
Fresh evidence in the final revision keeps the earlier gate finding applicable: after only #60/#66/#67 and a contract review finish, this row expressly authorizes implementation while full G01 #1 and G02 #2 remain in progress. Because #68 is a production vertical slice of #4–#15, building it atop the experimental G01g path and credential subset starts dependent implementation before the required evidence gates resolve; leaving the parent issues open does not preserve that start gate. Add #1/#2 as dependencies or restrict #68 to contract/evidence work until both gates pass.
AGENTS.md reference: AGENTS.md:L11-L11
Useful? React with 👍 / 👎.
1 participant
Change
Synchronize repository planning docs with the maintainer-accepted three-release sequencing in #66. Release classification is now the user-visible sequence; historical M0–M5 Stage/milestones, original Goal text, Agent history and native parent/
blockedByedges are retained.This is documentation only. It does not implement the daemon/CLI, authorize live App/Keychain/launchd/runner/Docker/Lima operations, or mark G01 complete.
Fixes #66
Delivery map
#1 exact Goal is unchanged and remains In progress. #2 remains In progress on R3. #68 stays Blocked by #60/#66/#67 until the minimal foreground contract is reviewed; daemon/install are not implemented. Relabeling does not bypass native dependencies (including G20 still blocked by #17/#18).
Main author Grok 4.6 xhigh; independent review Luna max. Historical Astra/Luna records and live #1/#2/#60 Agent values are unchanged.
Native relations audit (no further edge edits)
Verified live Project #2 = 36 items.
blockedByOriginal G04 blockers (#1/#2/#3) and G13 blockers (#6/#9/#10/#11/#12) are unchanged. Ask before adding more children or changing #60's missing native parent.
Validation
Prose-only change; no synthetic application tests.
jq empty docs/backlog.jsongit diff --checkblockedByAGENTS.md,README.md,docs/{PLAN,BACKLOG,EXECUTION,HANDOFF,ISSUES,backlog.json}Gaps
Rollback
Revert this PR / delete branch
orca/release-reframe. Do not remove the already-applied Release field,release:*labels, or #67/#68/#69 native relations unless the maintainer explicitly reverses that mapping. Original issue bodies, statuses and historical edges remain in GitHub.Review / merge
Do not merge until independent Luna max review is recorded and the exact current head has a clean Codex verdict plus required CI. After merge, #68 is still blocked by #60 and #67.