axstack 0.20.6 → 0.20.7

package/docs/workflows.md

@@ -200,6 +200,17 @@ shared manager workspace or a PR-job worktree, or cleans preserved candidates,
 evidence, user sessions, unknown liveness, `user_takeover`, or ambiguous
 publication state. Manual review/watch remains outside this scheduled lifecycle.
 
+One natively ordered successor may recover an exact positively completed
+predecessor whose terminal survived, but only after matching its automation,
+run, workspace, and terminal incarnation and proving zero unsettled descendants.
+It saves and reads back the cleanup claim before exact native close, then proves
+the full process tree exited before ownership release or guarded worktree removal.
+Age, status, or idle state alone never authorizes cleanup. Conflicting successors,
+identity mismatch, unknown or protected state, `user_takeover`, unexpected
+terminals, dirty or unpushed work, and unarchived evidence hold cleanup; an
+unchanged failure is deduplicated. Native ordering is not an atomic lock, so the
+overlap canary remains an activation requirement.
+
 Each bounded job uses a private `0700` temporary directory inside its own
 worktree. Cleanup targets only the validated owned path: no `TMPDIR` globs,
 shared-root sweeps, or general cache wipes, and uncertain files remain for

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.20.6",
+  "version": "0.20.7",
   "description": "Axstack installer and setup CLI: installs owned chat skills and role data, configures supported harness settings, and checks Orca capabilities.",
   "keywords": [
     "claude-code",

package/skills/axstack/references/automations.md

@@ -66,6 +66,38 @@ intent alone is insufficient. Conversely a completed run row does not prove exit
 If these facts remain unknown, report the hold at the durable decision location;
 do not silently stand down forever or replace a potentially live owner.
 
+### Guarded completed-predecessor recovery
+
+A successor may retire a positively completed predecessor whose manager terminal
+survived only through this narrow recovery path. Eligibility requires an exact
+automation ID, run ID, workspace ID, and terminal incarnation match, a positive
+completion receipt bound to that incarnation, zero active or unsettled descendants,
+and every owned Task and Dispatch settled. A completed row or saved retirement
+intent alone is not positive completion. Age, status, and idle state are never
+cleanup authority. Active, unknown, protected, identity-mismatched,
+`user_takeover`, unexpected-terminal, permission-held, or otherwise unverifiable
+state preserves the predecessor and pauses admission; this path never takes over
+its PR work.
+
+Exactly one successor, selected by native run ordering, may write the cleanup
+claim. Immediately before writing, re-read the complete lane inventory and
+ordering; then save and read back claimant identity, predecessor identity,
+completion, and zero-descendant continuity before the exact native workspace
+close. A later successor reconciles that claim and performs no cleanup mutation.
+Missing ordering or a conflicting claim holds both cleanup and admission. This
+ordering is not an atomic lock; activation still depends on the overlap canary
+proving that two successors cannot both mutate one predecessor.
+
+Use the version-matched native workspace close against the receipt's complete
+workspace ID, never an individually guessed terminal or broad selector. After
+close, re-list native runs, workspaces, terminals, Tasks, and Dispatches and prove
+the full predecessor process tree exited before ownership release. Save and read
+back the exit and release receipts, then use native worktree cleanup only when the
+workspace has no children, dirty or unknown files, unpushed commits, unarchived
+evidence, or user-owned work. Preserve every failed or uncertain close, exit,
+release, or removal with its exact resume condition and pause the lane. An
+unchanged cleanup failure gets no destructive retry or duplicate notification.
+
 Before PR admission, reconcile old pass resources and reclaim every safely
 removable earlier pass workspace under the retirement guards below. This is
 routine cleanup on every admitted pass; do not wait for the three-workspace