greprag 5.62.0 → 5.64.0

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

@@ -128,6 +128,29 @@ The child never silently changes the orchestration shape. If the work grows
 from quick to Leader-scale, tell the parent and let the parent create the
 dedicated `LEAD: <Mission>` task.
 
+## FIX missions — the one landing exception
+
+Landing authority follows the MISSION SHAPE, not the harness
+(adr/codex-landing-doctrine.md). Every chip shape above (`Chip A/B/C`, `LEAD`,
+`ADVISOR`, `MECHANIC`) keeps the parent-owned landing: commit, native reply
+with archive clearance, and the parent reviews, integrates, archives, and
+cleans up.
+
+A mission whose first line begins `FIX:` — emitted by `greprag fix spawn`
+(grepragOS law 4) — is the ONE exception: it carries its own Phase 3
+self-landing contract, which supersedes the "Do not merge, push, deploy, or
+delete the worktree" line for that task only. The fix chip confers with live
+peers (`greprag inbox watchers`), merges its branch to main itself, and
+re-verifies on merged main; its native reply to the parent is an FYI, not a
+review gate — a fix chip's repair must never strand on its branch waiting for
+a review no one owns.
+
+Even a FIX chip keeps two Codex-native boundaries: cleanup stays native (never
+remove the Codex-managed checkout or delete its branch — reply `Clearance:
+safe to archive` and let Codex archive and prune), and sensitive landings
+(`git push`, releases, `npm publish`, migrations) stay operator-gated — report
+READY-TO-PUSH instead.
+
 ## Selection rule
 
 ```text