Axstack v0.20.12

What's Changed

• fix(cleanup): retire settled reviewer worktrees after archival by @axatbhardwaj in #144
• chore(release): v0.20.12 by @axatbhardwaj in #145

Full Changelog: v0.20.11...v0.20.12

v0.20.5

What's Changed

• feat(audit): report learning candidates by @axatbhardwaj in #125
• chore(release): v0.20.5 by @axatbhardwaj in #126

Full Changelog: v0.20.4...v0.20.5

v0.20.4

Changes

• Codex skill installs now default to ~/.agents/skills, with guarded migration of unchanged Axstack-owned copies from the legacy Codex root.
• Migration preserves customized files and instruction ownership, and supports retry after partial retirement failures.
• Finished automation-owned PR worktrees gain private evidence archival and verification instructions before native retirement.
• Finished manager passes are reclaimed before retention limits are checked.

Verification

394 tests pass. PR #124 passed all eight Linux/macOS CI checks and independent configured review.

The tag-triggered publish workflow stages the npm package for maintainer approval. Host installation and live automation cleanup are separate from this release.

v0.20.3

Rewrite the README as a product introduction: what Axstack does, a skill guide, a runnable quick start, control boundaries, and optional PR automation. Operational details remain in linked documentation. Includes v0.20.2 manager-isolation changes. npm publication awaits staged-release approval; schedules are not enabled by this release.

v0.20.2

PR #122: isolate scheduled manager passes in native per-run workspaces, preserve durable lane continuity, and bound retired-workspace accumulation. Manual review/watch remain unchanged. Runtime activation validation is still in progress; this release does not enable schedules. npm publication requires staged-release approval.

v0.20.1

Packages finite PR-manager sessions and scoped unused setup-shell cleanup from #121. Managers preserve durable continuity and decisions, settle descendants, and self-close. Separate five-job review/watch ceilings and zero-slot waiting remain unchanged.

Verification: 367 tests pass; Linux/macOS CI passes; independent authored review approved and eight-scenario decision evaluation completed. Prompt tests do not prove native runtime behavior; no desktop/VPS reinstall is included.

Npm staging workflow: https://github.com/axatbhardwaj/axstack/actions/runs/35562249225 — final registry publication requires maintainer approval.

Attached archive is Bun-packed from release f46f33b. SHA256: a47f374749e4d18474495a0b29e58eacd5f78c70bd6f654868725fd79689f632. The npm stage is independently packed by npm in CI.

v0.20.0

Replaces the PR automation harness with two reusable native managers. Each lane permits five executing PR jobs without limiting monitored PR coverage. Waiting jobs release capacity after settlement. Preserves reviewed fast-forward repairs and human merge. Native runtime canary required before activation. PR #120.

v0.10.1

Specification revision 5.1: every pair C review is a binding verdict, one per
tick, and the pair C precheck ships with a working busy guard.

Pair C precheck. The defi-com driver precheck is now versioned beside pair
A's (docs/plans/orca-automations-precheck-c.sh). Two defects are fixed: the
terminal-hygiene/busy block never ran (its guard compared the automation id to
itself), which let a scheduled run launch over a still-working attended run;
and due-work read a cursor shape the driver never writes, so an expired repair
cap could not wake the driver. The hygiene behaviour tests now run over both
drivers and pin the driver-written cursor shape.

Binding verdicts everywhere for C. Automation C has no COMMENT path: a
peer PR reached through the qualifying mention trigger takes a verdict exactly
as an officially-requested one does; an incidental mention stays discovery
data. Pair A/B is unchanged and keeps COMMENT-only.

One verdict per tick. A per-tick review budget of one binding verdict,
oldest updatedAt first, is the brake that replaces the COMMENT-for-mentions
rule. The user may lift it for an attended session; the override is recorded in
the run record. Three caps now: one repair per PR per 24h, six pushes per tick,
one verdict per tick.

Installed skills and the repository match again after this release.

v0.10.0

Specification revision 5: per-repo scope for the defi-com pair, and binding
review verdicts for Automation C.

Two scopes, not one. Pair C/D reviews across defi-com/monorepo,
defi-com/mobile and defi-com/azure-next-hybrid, and repairs only the first
two. azure-next-hybrid is review-only: its own PRs are recorded and never
repaired or pushed to.

Binding verdicts. Automation C submits a real APPROVE or
REQUEST_CHANGES on a peer PR where the account is officially review-requested,
replacing the COMMENT-only automation exception. Pair A/B is unchanged and
keeps COMMENT-only, and a mention-triggered peer review still publishes
COMMENT — a casual "take a look" is not a request for a merge-blocking review.

Blocking obligations. Submitting a review removes the account from GitHub's
review-requested results, so a blocked PR would otherwise leave discovery and
the block would stand forever. C records each unresolved blocking review as a
durable obligation, wakes on it every scheduled tick, polls it directly by URL,
and carries an inherited authority — following the obligation chain across a
teammate's later pushes — to submit the clearing APPROVE without a fresh
request. Supersession is capped at one verdict per head SHA.

Also: ~/defi and ~/dev workspace paths, a green gate that uses the unit-level
command plus CI, inherited-failure holds, and the local review-PR-<num>.html
written alongside every review C publishes.

Suite: 363 pass / 0 fail. Five adviser passes, both advisers AGREE, plus a
four-pass authored review.

This ships the contract. Automations C and D are not created and nothing is
enabled.

v0.9.0

Adds the defi-com automation pair to the shipped contract.

Specification revision 4 — a second, independent Orca automation pair
(C driver, D watchdog) covering defi-com/monorepo, defi-com/mobile and
defi-com/azure-next-hybrid, with its own allowlist, hourly cadence, run id
and sidecars. The axstack pair (A/B) is unchanged apart from a named amendment
correcting its recorded cadence to */30.

Pair-aware session contract — skills/axstack/references/automations.md
now carries: per-automation mutation allowlist; stack-aware repair sequencing
(lowest open failing PR, descendants take a pending restack hold rather than
a duplicate fix); bot review feedback with dedup by review ID plus body digest
under explicit caps; per-pair watch windows (rolling for C/D, 24h retained for
A/B); C/D PR eligibility; and a branch-name-agnostic deploy-on-push hold.

gh stack restack authority remains withheld for every automation.

This ships the contract. The defi-com automations are not live — the spec holds
activation behind its 13 acceptance checks.

Suite: 356 pass / 0 fail.