greprag 5.74.7 → 5.74.8

package/dist/codex-chip-hooks.js

@@ -64,9 +64,9 @@ function context(input) {
         `Worktree: ${(0, model_1.chipExecutionPath)(chip)}`,
         `Branch: ${chip.worktree.branch}`,
         `Parent session: ${chip.parent.sessionId || 'not recorded'}`,
-        `Finish by committing the durable result and reporting the commit artifact to the parent, including checks, caveats, and a Cleanup line naming archive/task, worktree, and branch actions. The optional host command is ${cli} codex chip report ${chip.id}.`,
+        `Finish by committing the durable result, then send the parent the commit artifact, checks, caveats, Cleanup line, and Archive: yes|no in the actual native task message. After delivery, Archive: yes means archive this child task yourself. The optional host command is ${cli} codex chip report ${chip.id}.`,
         // adr: adr/codex-landing-doctrine.md — one delivery owner, including FIX missions.
-        'Landing: the parent is the delivery owner for merge, archive, cleanup, and any profile-declared push/deploy/release — do not edit the parent checkout or independently cross those boundaries. A mission whose first line begins `FIX:` (emitted by `greprag fix spawn`) is writable in its isolated checkout/worktree and hands its verified checkpoint to that owner without a human approval gate. If no live parent exists and the chip carries the full-goal mission, it becomes delivery owner. `greprag fix spawn` only prints the mission; visible Codex task dispatch creates the isolated checkout/worktree.',
+        'Landing: the parent is the delivery owner for merge, post-merge branch/manifest bookkeeping, and any profile-declared push/deploy/release; the child owns routine archival of its own task after the terminal message is delivered. Do not edit the parent checkout or independently cross delivery boundaries. A mission whose first line begins `FIX:` (emitted by `greprag fix spawn`) is writable in its isolated checkout/worktree and hands its verified checkpoint to that owner without a human approval gate. If no live parent exists and the chip carries the full-goal mission, it becomes delivery owner. `greprag fix spawn` only prints the mission; visible Codex task dispatch creates the isolated checkout/worktree.',
     ];
     if ((0, model_1.chipMissionKind)(chip) === 'fix') {
         lines.push('Harness: Codex. Mission: visible native FIX chip with ordinary writable authority, not an internal subagent.', 'Scope: repair GrepRAG-owned harness surfaces in this checkout: load entries, skill templates, docs, hook context, CLI messages, and tests. Codex owns native task creation, worktrees, permissions, Git, and task lifecycle.', 'Own diagnosis, implementation, tests, commit, and parent report. Inspect Codex behavior only far enough to correct GrepRAG guidance or report a precise external blocker.', 'FIX peer handoff: if a peer offers to coordinate, integrate, rework, or take over a harness repair, hand off branch/commit, dirty files, checks, blockers, and caveats. Do not defend patch ownership; peers may take ownership within their assigned GrepRAG harness scope.', 'Visible delegation route: load `codex-chip-spawn` and create the child with `codex_app__create_thread` using the current project worktree target; load `chip-leader` for multi-chip seams. Never use `multi_agent_v1__spawn_agent` for a visible chip.');

package/dist/commands/codex-chip/help.js

@@ -21,11 +21,12 @@ quick chips, an explicit LEAD for multi-chip orchestration, and Chip A/B/C with
 optional ADVISOR orientation. FIX missions are visible one-friction tasks from
 \`greprag fix spawn\`: they select \`chip.fix\` and load mechanic doctrine.
 Every role is an ordinary writable session; roles only orient the work. Native Codex chips commit their durable
-result, then reply to the LEAD in the native task thread with status, commit
-hash, checks, caveats, cleanup parameters, and archive clearance. Include a
-\`Cleanup:\` line naming archive/task, worktree, and branch actions. Use
-\`Clearance: safe to archive\` or \`Clearance: keep open because ...\`. The
-parent integrates, archives when safe, and cleans up the task. Peer review is a
-separate explicit review chip/session when needed. The
+result, then use the native task-message channel to send the LEAD status,
+commit hash, checks, caveats, cleanup parameters, and
+\`Archive: yes\` or \`Archive: no — <reason>\`. The archive decision must be in
+that sent message, not only the child's final response. After delivery,
+\`Archive: yes\` means the child archives its own task; the parent integrates
+the commit and handles post-merge branch bookkeeping. Peer review is a separate
+explicit review chip/session when needed. The
 \`greprag codex chip report\` command remains host bookkeeping for explicit
 CLI-managed chips, not mandatory native Codex completion ceremony.`;

package/dist/commands/codex-chip/prompt.js

@@ -20,7 +20,7 @@ function chipPrompt(manifest, _cliCommand = 'greprag') {
         ? `- After setup and bootstrap succeed, reply to the LEAD in the native Codex task thread: \`IN-FLIGHT: ${(0, model_1.chipTitle)(manifest)} — setup complete; work started\`. If setup fails, reply \`BLOCKED\` with the exact failure instead.\n`
         : '';
     const reportInstruction = native
-        ? '- Commit the durable result, then reply to the LEAD in the native Codex task thread with `DONE` or `BLOCKED`, commit hash if any, checks, material caveats, cleanup parameters, and archive clearance.'
+        ? '- Commit the durable result, then use the native Codex task-message tool to send the LEAD `DONE` or `BLOCKED`, commit hash if any, checks, material caveats, cleanup parameters, and `Archive: yes` or `Archive: no — <reason>`. Do not substitute a final response in your own task.'
         : '- Commit the completed durable result, including report-only artifacts, then run `greprag codex chip report <id> --summary "<result>" --check "<check>"`. The report must carry the commit artifact back to the parent.';
     return `${(0, model_1.chipTitle)(manifest)}
 
@@ -37,7 +37,7 @@ ${manifest.task}
 
 Report when done:
 ${reportInstruction}
-- Include a \`Cleanup:\` line naming the archive/task action, worktree action, and branch action. Use \`Cleanup: archive task; Codex may prune managed worktree; parent may delete branch after merge\` when done, or \`Cleanup: keep task/worktree/branch because ...\` when anything must remain open.
-- Include \`Clearance: safe to archive\` when no follow-up is needed, or \`Clearance: keep open because ...\` when the lead should not archive yet.
-- Landing: do not independently merge, push, deploy, or delete the worktree — the parent is the delivery owner and integrates the result, follows the repo profile, and cleans up the task. If this task begins \`FIX:\` (a fix-spawn mission), hand the verified checkpoint to that owner without a human approval gate. If no live parent exists and this task carries the full-goal mission, become delivery owner. \`greprag fix spawn\` only prints the mission; visible Codex task dispatch creates the isolated checkout/worktree.`;
+- Include a \`Cleanup:\` line naming the task, worktree, and branch actions. When done use \`Cleanup: child archives own task; Codex may prune managed worktree; parent may delete branch after merge\`; when anything must remain open use \`Cleanup: keep task/worktree/branch because ...\`.
+- Put the archive decision in the actual message sent to the LEAD: \`Archive: yes\` or \`Archive: no — <reason>\`. After that message is delivered, \`Archive: yes\` means call \`set_thread_archived\` for your own task; \`Archive: no\` means leave it open. Never make the parent perform routine child-task archival.
+- Landing: do not independently merge, push, deploy, or manually delete the worktree — the parent is the delivery owner and integrates the result, follows the repo profile, and deletes the branch after merge. If this task begins \`FIX:\` (a fix-spawn mission), hand the verified checkpoint to that owner without a human approval gate. If no live parent exists and this task carries the full-goal mission, become delivery owner. \`greprag fix spawn\` only prints the mission; visible Codex task dispatch creates the isolated checkout/worktree.`;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "greprag",
-  "version": "5.74.7",
+  "version": "5.74.8",
   "description": "GrepRAG — agent memory for Claude Code, Codex, and OpenCode.",
   "main": "dist/index.js",
   "bin": {

package/skill/greprag/docs/codex-chip.md

@@ -20,13 +20,13 @@ child sends the native parent-task reply
 `IN-FLIGHT: <exact title> — setup complete; work started`; setup failure sends
 `BLOCKED` with the exact failure. It has no lease, read-only, mandatory
 nested-goal, or nonce/ACK requirement. Completion is another native
-parent-child task reply: commit the durable result, then reply to the LEAD with
-`DONE` or `BLOCKED`, commit hash if any, checks, caveats, and
-cleanup parameters (`Cleanup: archive task; Codex may prune managed worktree;
-parent may delete branch after merge` or `Cleanup: keep task/worktree/branch
-because ...`) plus archive clearance (`Clearance: safe to archive` or
-`Clearance: keep open because ...`). The lead remains responsible for
-integrating, archiving, and cleanup.
+parent-child task message: commit the durable result, then send the LEAD
+`DONE` or `BLOCKED`, commit hash if any, checks, caveats, cleanup parameters,
+and `Archive: yes` or `Archive: no — <reason>` in the actual sent message, not
+only the child's final response. After successful delivery, `Archive: yes`
+means the child archives its own Codex task; `Archive: no` leaves it open. The
+lead remains responsible for integration and post-merge branch bookkeeping,
+not routine child-task archival.
 Review is a separate explicit review chip/session when the lead asks for it.
 FIX landing (adr/codex-landing-doctrine.md): a mission whose first line
 begins `FIX:` (from `greprag fix spawn`) uses the handoff's detected

package/skill/templates/codex-chip-spawn.md

@@ -133,27 +133,32 @@ Paste this at the end of the child prompt.
 
 ```text
 ## Report when done
-Commit the durable result first. Then reply to the LEAD in the native Codex task
-thread with `DONE` or `BLOCKED`, commit hash if any, concise result, checks,
-caveats, cleanup parameters, and archive clearance.
+Commit the durable result first. Then use the native Codex task-message tool to
+send the LEAD `DONE` or `BLOCKED`, commit hash if any, concise result, checks,
+material caveats, cleanup parameters, and the archive decision. Do not
+substitute a final response in your own task: the lifecycle report must be the
+actual message sent to the LEAD.
 
 Include one cleanup line:
-`Cleanup: archive task; Codex may prune managed worktree; parent may delete branch after merge`
+`Cleanup: child archives own task; Codex may prune managed worktree; parent may delete branch after merge`
 or
-`Cleanup: archive task; local mode has no worktree or branch to prune`
+`Cleanup: child archives own task; local mode has no worktree or branch to prune`
 or
 `Cleanup: keep task/worktree/branch because ...`
 
-Include one clearance line:
-`Clearance: safe to archive`
+Include one archive line in that same sent message:
+`Archive: yes`
 or
-`Clearance: keep open because ...`
+`Archive: no — <reason>`
 
-In worktree mode, do not merge, push, deploy, or delete the worktree. In local
-mode, do not archive the task or perform unrelated project cleanup. The parent
-decides whether to archive and cleans up from the child's cleanup parameters.
-If review is needed, the parent spawns a fresh review chip/session with an
-explicit review brief.
+After the message is delivered, `Archive: yes` means call
+`set_thread_archived` for your own task; `Archive: no` means leave it open. Do
+not make the parent perform routine child-task archival.
+
+Do not merge, push, deploy, or manually delete the worktree. The parent
+integrates the commit and may delete the branch after merge; Codex owns managed
+worktree pruning. If review is needed, the parent creates a fresh review
+chip/session.
 ```
 
 ## FIX contract
@@ -188,12 +193,13 @@ require a writable task.
 
 ## Parent cleanup
 
-After the parent integrates/reviews and archives a completed worktree task, it
-may run:
+After integration, the parent may clear remaining GrepRAG manifest/branch
+bookkeeping with:
 
 ```bash
 greprag codex chip cleanup <id> --native-archived
 ```
 
-Codex owns the managed-worktree lifecycle. The child does not prune it.
-Local-mode FIX tasks have no worktree or branch to prune; archive the task only.
+The child archives its own task after sending `Archive: yes`; the parent does
+not perform routine child-task archival. Codex owns managed-worktree pruning.
+Local-mode FIX tasks have no worktree or branch to prune.