axstack 0.25.3 → 0.25.5

package/skills/axstack/references/autopilot.md

@@ -35,9 +35,9 @@ human approval)` as a decision hold eligible under the Notification policy.
 
 ## Phase sequence
 
-- Small: Align read-back, small-change intent, implement, watch in maintain
-  mode, merge under the watch §5 predicate. An opted-in Align refinement is part
-  of read-back.
+- Small: small-change intent read-back, with Align only when unclear, then
+  implement, watch in maintain mode, merge under the watch §5 predicate.
+  An opted-in Align refinement is part of read-back.
 - Substantial: Align, spec draft with advisers and diligence, human spec
   approval at gate 1, tickets with diligence, implement, watch in maintain mode,
   merge-ready, merge under the watch §5 predicate. An opted-in Align refinement
@@ -96,10 +96,11 @@ noted. Install hosts come only from explicit targets; an absent host list is a
 decision hold, not permission to infer hosts. A missing install host list at
 Align or spec time is a decision hold before release authority is presented.
 
-Show the `Release:` line in the spec for human approval at gate 1, or the small
-work Align read-back. Copy that decision to `Authority:` in the run record.
+Show the `Release:` line in the spec for human approval at gate 1, or the
+small-change intent read-back. Copy that decision to `Authority:` in the run
+record.
 This authority is per run and never carries over to another run or repository.
-The small-work Align read-back names the existing Release and host-mutation
+The small-change intent read-back names the existing Release and host-mutation
 authority and explicit hosts; silence cannot fill a missing authority or target.
 
 After all required feature PRs merge, open one release PR. Default to a patch

package/skills/axstack/references/review-manager-prompt.md

@@ -9,10 +9,13 @@ which loads `../axstack/references/automations.md` relatively. Read that contrac
 and [T3 runtime](t3-runtime.md). Reconcile lane ownership and duplicate status,
 then follow [Provider bindings](t3-runtime.md#preflight-and-binding) for shared schedule
 recreation and recorded instance update before verifying the recorded `axstack-owner`
-binding before admission. Discover all eligible peer-review events and admit within measured host capacity.
+binding before admission. At pass start, every pass, including a duplicate,
+settles finished predecessor and duplicate pass threads under the Finite-session
+teardown guards before admission. Discover all eligible peer-review events and admit within measured host capacity.
 Use host-clone detached per-PR checkouts; preserve exact ownership and receipts.
-Retire settled predecessors, report retained worktree count, and disable the
-schedule and hold past its authorized limit. Save and read back continuity at
+Report retained worktree count and disable the schedule and hold past its
+authorized limit. Only the owner retires settled predecessors and saves and
+reads back continuity at
 `~/.local/share/axstack/runs/review-manager/progress.md` using
 `run-record.md#review-manager-continuity-template`; settle descendants and end
 the finite turn. Stay quiet when unchanged. Never check out a PR branch here.

package/skills/axstack/references/routing.md

@@ -5,10 +5,12 @@ Driver entry sweep follows [Workspace hygiene](workspace-hygiene.md).
 
 ## Role routing
 
-Presets: `mixed`, `codex-only`, `claude-only`. For new runs, use
-`profiles.preset` from `.axstack-manifest.json` at the actually loaded
-skills root, or an explicit user selection in the run record. Missing or contradictory sources are
-a setup gap: hold. Never infer from live profiles, harness,
+Presets: `mixed`, `codex-only`, `claude-only`. For new runs, read the `preset`
+from installed `skills/axstack/roles.json` at the actually loaded skills root,
+or use an explicit user selection in the run record. The legacy manifest
+`profiles.preset` is inert and ignored, including stale values. A stale
+manifest value does not create a contradiction. Missing or contradictory installed
+preset / explicit user selection: setup gap, hold. Never infer from live profiles, harness,
 tools, credentials, quota, subscription, or default to `mixed`.
 Only same-provider, same-model account selection among instances of one driver
 may use headroom under [Provider bindings](t3-runtime.md#preflight-and-binding);
@@ -23,7 +25,7 @@ For each role record class, resolved exact ID, source (`capabilities`), and time
 Read the [T3 runtime boundary](t3-runtime.md) before dispatch, receipt consumption
 or recovery; use its permitted-write role split, completion checks and run watch.
 Resolve Codex and Claude classes with
-`skills/axstack/scripts/resolve-models.js --provider <provider> --capabilities <path>`
+`skills/axstack/scripts/resolve-models.js --provider <provider> --capabilities <path> (--class <class> | --model <model>) --effort <effort>`
 using saved T3 capabilities JSON; missing or malformed capabilities holds.
 Claude exact IDs come from capabilities, replacing transcript read-back.
 Use an explicit model as given; for `model:null` without a class, grok uses the
@@ -118,7 +120,8 @@ reason in the run record, or in the brief for tiny direct work.
   Own PRs default to automatic merge under watch §5 predicate.
 - **Unclear:** clarify via `axstack-align` or a bounded question, then
   classify small or substantial; it does not force substantial-work paperwork.
-  [Design lens](design-lens.md) Rung 1 is Unclear; use `axstack-align`.
+  Only an unsettled material Rung 1 design question is Unclear; use `axstack-align`
+  ([Design lens](design-lens.md)).
 
 Reassess size when growth adds an additional PR, a new execution dependency
 that materially expands scope, an unsettled material design question, or a

package/skills/axstack/references/run-record.md

@@ -139,9 +139,9 @@ Record the reason for each driver-elected repair in `Decisions`.
 ## Privacy
 
 Record concise IDs, SHAs, URLs, status, timestamps, next actions, and evidence
-references. Include no tokens, transcripts, full worker output, credentials,
-private prompts, or machine-specific paths beyond the private record's own
-resolved location. Publication of a sanitized summary needs separate
+references. Private records include the checkout, evidence and worktree paths
+that the schema requires. Include no tokens, transcripts, full worker output,
+credentials or private prompts. Publication of a sanitized summary needs separate
 authority.
 
 ## Review-manager continuity template
@@ -181,7 +181,7 @@ Routing: <preset + source + snapshot ref>
 Notification policy: <none | transport/target label/host/instructions path>
 Autopilot: on | paused (<hold>; resume: <condition>) | off (cancelled <ts>)
 Next: <owner; last receipt time; next action; hold or none>
-PR digest watermarks: <repo -> absolute path inside this private run record> | none
+PR digest watermarks: <repo -> absolute path of its per-repository JSON file inside the private run directory> | none
 Release: <AGENTS.md file:line + tag-triggered workflow path + named install hosts> | not applicable (<reason>)
 Source base: <exact revision or source identity>
 IDs: <projectId + driver threadId/runId + dispatch identity receipt pointers>

package/skills/axstack/references/t3-runtime.md

@@ -84,7 +84,8 @@ A preset model must be used as given.
 
 `modelClass` must resolve to the newest matching catalog ID for that provider:
 codex `gpt-<N>-<class>`, claude `claude-<class>-<N>-<N>`. Use
-`scripts/resolve-models.js --provider` with the saved capabilities JSON path;
+`scripts/resolve-models.js --provider <provider> --capabilities <path> (--class <class> | --model <model>) --effort <effort>`
+with the saved capabilities JSON path;
 a missing or malformed catalog holds resolution.
 Model catalog resolution retains the canonical instance IDs above.
 
@@ -130,7 +131,7 @@ configuration; unrelated configurations remain eligible.
 |---|---|---|
 | Advisers, research, read-only explorers, explainers, diligence, checker, auditor, monitor, arena prose candidates and judges, escalation | Must use async `delegate_task` in the driver worktree, title = dispatch key; tracked and untracked files stay untouched; writes only `<run>/evidence/<key>/` | Native notification followed by persisted `task_status` |
 | Reviewers (peer/authored), release checks, debug investigators, execution investigators (`axstack-explore-execution`), UI verifier (`axstack-ui-verifier`) | Must use async `delegate_task`, title = dispatch key; driver makes a disposable detached checkout of candidate SHA and pinned base with `git worktree add --detach <run>/checkouts/<key> <sha>` (plus pinned debug patch); brief requires `cd` into it; only disposable probes write there, outputs go to `<run>/evidence/<key>/` | Same delegated terminal checks |
-| Author and repairs, code-arena writers | Must use `t3_thread_launch` with `{type:worktree, baseRef:<SHA>, branch:<encoded branch>, startFromOrigin:false}` in their own worktree, kept until PR merges or closes | Writer sends a receipt to the driver; driver verifies terminal run and candidate |
+| Author and repairs | Must use `t3_thread_launch` with `{type:worktree, baseRef:<SHA>, branch:<encoded branch>, startFromOrigin:false}` in their own worktree, kept until PR merges or closes | Writer sends a receipt to the driver; driver verifies terminal run and candidate |
 | Owner | Driver thread in Driver worktree; never writes tracked candidate source or tests; planning artifacts allowed only for repository Markdown; scope, integration, forge mutations and record | No worker launch |
 
 The driver must be the sole run-record writer and enforce one writer per

package/skills/axstack/references/test-audit-weekly.md

@@ -53,6 +53,8 @@ or edit line-caps. Report test-only production seams without changing them.
 After restoring mutations, verify every non-test path byte-identical to the base;
 coverage, where reported, is a per-file guard and never deletion proof alone.
 Keep one writer and private revision-bound receipts; workers never push.
+The weekly test audit is a named exception to Implement's publish-then-review
+order: it requires review-before-publication.
 Obtain independent review using Implement's configured authored-review roles and
 verify the exact candidate's checks before publication. The driver uses
 `gh stack` and opens at most one test-audit PR per week after independent review;

package/skills/axstack/references/workspace-hygiene.md

@@ -32,7 +32,12 @@ Cleanup order is: settled descendants -> evidence readback -> salvage dirty or i
 Require terminal run evidence before `t3_thread_organize` settle or archive.
 These metadata actions do not remove worktrees. Accept matching delegated task
 or launched run completion under the runtime contract before settlement.
-Keep the author worktree and thread until the PR merges or closes.
+After the driver accepts a launched writer's or delegated task's completion from terminal run evidence plus a verified receipt or candidate check, it settles the matching thread with `t3_thread_organize` as metadata only.
+Settling never removes, archives or abandons the thread or worktree.
+Retain the author worktree and thread unarchived until the PR merges or closes, with repairs returning to the same author.
+A repair turn automatically un-settles the thread, making it visible while working.
+The driver settles the thread again after the next accepted repair completion.
+Threads with unaccepted completion, FAILED or QUESTION markers, held, failed or interrupted runs, or anything needing the user stay unsettled and visible.
 Retain a user-taken-over T3 thread and never send cleanup commands to it, including `t3_thread_organize` settle or archive.
 Never remove the current driver, current pass, an active or unknown thread, an unsettled descendant, or a resource with ambiguous ownership.
 At final settlement, no eligible non-driver thread or worktree remains.

package/skills/axstack-audit/references/record.md

@@ -14,6 +14,7 @@ Decisions: <escalation trigger + evidence pointers + outcome changed yes/no, or
 Debug: <rung reached + loop command + fix attempts + adviser and investigator receipts + isolation evidence | n/a>
 TDD: <applicable evidence path: normal real red-green | accepted structure-preserving old revision green before edits + same checks new revision green | F-repair base-green/removal-inversion-red/rewording-green evidence; absent proof: noncompliance | unavailable records: UNKNOWN with reason>
 Review: <exact-rev independent review status + unresolved findings>
+Simplification: <applicability determinations evidenced / total candidate diffs, complete simplification receipts / total candidates, applied, not-applicable, or UNKNOWN with reason + evidence>
 Rework: <cycles + causes>
 Interventions: <avoidable user interventions, or unsupported by records>
 Parallelism: <identified vs dispatched + dependency/writer isolation>

package/skills/axstack-explain/SKILL.md

@@ -91,7 +91,7 @@ Diagram never calls explain.
    for other artifacts, use it when warranted. Bind it to the exact artifact identity.
    Any byte change invalidates
    that review and requires a fresh check. In `claude-only`, separate Sonnet
-   author xhigh and reviewer high sessions are allowed for explanations as
+   author high and reviewer high sessions are allowed for explanations as
    session independence only. This exception never permits same-model code
    review or a cross-provider-independence claim.
 3. Report source, tests, rendered observations, independent review, and

package/skills/axstack-watch/references/watch-runtime.md

@@ -55,7 +55,9 @@ add no daemon and no polling model between wakes.
 At the start of each driver wake, follow [Provider bindings](../../axstack/references/t3-runtime.md#preflight-and-binding)
 for driver account re-selection, then run the digest once per repository
 from the installed `axstack` skill directory:
-`bun scripts/pr-digest.js --repo <owner/name> --prs <comma-separated numbers of every watched member in that repo> --watermark <that repository's private run-record path>`.
+`bun scripts/pr-digest.js --repo <owner/name> --prs <comma-separated numbers of every watched member in that repo> --watermark <that repository's per-repository JSON watermark file path>`.
+Use a per-repository JSON file in the private run directory for the watermark,
+separate from `progress.md` (for example, `pr-digest-owner-repo.json`).
 Exit 0 means unchanged: when no pending local action remains in `Next:` or unsettled runs,
 end the turn with no text or notification. Exit 10 supplies deltas
 to reconcile with current PR and local state; the driver saves only the printed