axstack 0.20.1 → 0.20.3

package/README.md

@@ -1,141 +1,124 @@
 # Axstack
 
-Axstack is a standalone toolkit for finishing agreed engineering work with less
-supervision while retaining independent review. Chat drives execution; a Bun
-CLI installs owned skills and role data and checks capabilities. Axstack has no
-daemon, scheduler, runtime database, or workflow state machine.
-
-Orca is the only supported active runtime. Its installed, version-matched
-`orchestration` and `orca-cli` guides own worktrees, sessions, supervised
-dispatch, messages, settlement, and handoff mechanics. Axstack owns scope,
-role choices, evidence, review policy, and one private derived run record.
-
-## How a run works
-
-Invoke the needed phase directly: `axstack-align`, `axstack-spec`,
-`axstack-tickets`, `axstack-implement`, `axstack-review`, and `axstack-watch`.
-Direct `axstack-research`, `axstack-explain`,
-`axstack-improve`, and `axstack-debug` routes need no spec ceremony. `axstack-relay` remains an
-optional inline route for explicit messages and authorized notifications; an
-unavailable or legacy-runtime-only relay falls back to the current conversation
-without changing authority.
-
-1. Classify new engineering work as substantial, small, or unclear with a brief
-   reason. Small, bounded one-PR work uses the current request or selected issue
-   as a snapshotted small-change intent;
-   substantial or stacked work needs an approved spec and matching ticket map.
-   Substantial work uses Linear by default, or explicitly selected GitHub Issues
-   or repository Markdown, as its authoritative spec and capability tracker.
-2. The current chat drives on whatever model runs it; there is no driver
-   profile. Bind each ready task to the selected role snapshot and an authoritative Orca
-   Run, Task, and Dispatch. Exactly one writer owns a candidate at a time. All
-   subagent and delegated worker dispatches go through Orca orchestration rather than
-   harness-native subagent tools.
-3. Peer PRs receive both configured independent reviewer roles. Authored PRs
-   receive one eligible reviewer from the selected preset's explicit mapping
-   and actual author provenance. Every review binds the exact head and base.
-   Stable IDs are `axstack-reviewer-primary` and `axstack-reviewer-secondary`.
-4. Accepted repairs return to the same author where its session and evidence
-   remain valid. The human merges by default, bottom-up for a stack.
-5. Full handoff requires explicit recipient acceptance of the exact scope and
-   authority before ownership changes. Ordinary resume reconciles the current
-   owner instead of replacing it.
-
-Active PR fanout is dependency- and capacity-driven; there is no fixed count.
-Each PR has one theme and a measured size under the shared
-[PR-shape policy](skills/axstack/references/pr-shape.md). Routine shape and
-fanout choices remain autonomous inside approved scope. Material scope,
-serious-risk, unavailable-model, and human-merge holds remain explicit.
-The autonomous driver records the rationale band's cohesion rationale; the exception band needs a
-reasonable split attempt and full exception record. Size alone never requires
-user approval.
-
-## Install from source
-
-Requirements: Bun >=1.3.14, Git, `gh`, the `gh stack` extension, and a running
-Orca with its runtime-owned guides. Filesystem access uses Bun's implementation
-of `node:fs` and `node:fs/promises`; there are no runtime dependencies.
+Engineering workflows for AI agents, from an idea to a reviewed pull request.
+
+Axstack is a set of skills for engineers who want agents to carry work forward
+with less supervision, without giving up clear scope, independent review, or
+control over what ships. Use it to plan a feature, implement an agreed task,
+review a teammate's PR, or maintain your own PRs as feedback arrives.
+
+Your chat stays in charge. Orca provides the worktrees, agent sessions, and
+coordination; Axstack supplies the workflow and review rules. A small Bun CLI
+installs the skills and checks prerequisites. There is no Axstack daemon,
+scheduler, or runtime database to operate. Orca is the only supported runtime.
+
+## What you can do
+
+| Need | Skill |
+| --- | --- |
+| Explore an idea and settle scope | `axstack-align` |
+| Turn agreed scope into a specification | `axstack-spec` |
+| Break a specification into executable tickets | `axstack-tickets` |
+| Build an approved task with tests and independent review | `axstack-implement` |
+| Review a pull request | `axstack-review` |
+| Monitor or maintain an existing PR | `axstack-watch` |
+| Diagnose a bug and establish a failing check | `axstack-debug` |
+| Answer a bounded question with sources | `axstack-research` |
+| Explain a system or identify improvements | `axstack-explain`, `axstack-improve` |
+| Measure a run's outcomes and gaps | `axstack-audit` |
+| Send an explicit message or authorized notification | `axstack-relay` |
+
+Start at the phase you need. Small, bounded changes can begin with your request
+or an existing issue; substantial work needs an approved spec and matching
+tickets before implementation. Research, explanation, and peer review do not
+require a new specification.
+
+For a larger feature, the usual path is:
+
+```text
+align → spec → tickets → implement → review → watch
+```
+
+The implementation workflow includes the author–review–repair loop. You do not
+need to manually coordinate every agent or repeat an approval that is still valid.
+
+## Quick start
+
+You need Bun >=1.3.14, Git, the GitHub CLI (`gh`), the `gh stack` extension,
+and a running Orca with its `orca-cli` and `orchestration` guides available.
+The agents selected by your preset must also be available in Orca.
+
+Install the CLI and skills for your harness. For example, for Codex:
 
 ```sh
-bun bin/axstack.js check --bundle . [--harness claude|codex|opencode|antigravity]
-bun bin/axstack.js install --bundle . --skills-dir <dir> --instructions <file> --preset mixed [--yes]
-bun bin/axstack.js install --bundle . --skills-dir <dir> --preset mixed
-bun bin/axstack.js uninstall --skills-dir <dir> --instructions <file>
+bun add --global axstack
+axstack check --harness codex
+axstack install --harness codex --preset mixed --yes
+```
+
+Then open an Orca chat and ask for the relevant skill:
+
+```text
+$axstack-align Help me scope account recovery.
+$axstack-implement Build the task we agreed on.
+$axstack-review Review this pull request: <PR URL>
+$axstack-watch Monitor this PR without making changes: <PR URL>
 ```
 
-Use `--harness claude|codex|opencode|antigravity` only for a verified default
-skill directory and rules file. `--claude-settings` and `--no-claude-settings` manage the existing
-Claude Code subagent default transaction; they do not configure Orca roles.
-See [installation details](docs/installation.md).
-
-`--instructions` manages one versioned Axstack block in `AGENTS.md`,
-`CLAUDE.md`, or `GEMINI.md`. Harness defaults resolve those files automatically. The block
-requires direct matching phase-skill invocation and requires every subagent, delegated
-worker, reviewer, and cross-harness dispatch to use visible Orca orchestration via the `orca` CLI
-rather than a harness-native subagent tool (e.g. Claude/Codex native subagents). OpenCode
-and Antigravity subagents run as Orca-supervised workers. Text and file
-mode outside the markers are preserved; edited, malformed, unowned, or unsafe
-targets are reported without normal-path adoption. Install exits nonzero when
-an instruction conflict is preserved, while clean and idempotent installs exit
-successfully.
-
-The public bundle preserves three canonical 24-role inputs:
+Use `--harness claude`, `opencode`, or `antigravity` for another supported
+installation target, or provide explicit skill and instruction paths.
+Installation adds an owned instruction block and preserves unrelated content;
+it does not enable automations or prove that every configured model is available.
+See [installation](docs/installation.md) for source installs, custom paths,
+upgrades, conflicts, and uninstalling.
+
+## How work stays controlled
+
+- **One accountable driver, one writer per candidate.** Your current chat
+  coordinates work; separate worktrees keep PR jobs isolated.
+- **Independent review.** Peer PRs receive two independent reviews; authored
+  changes receive a reviewer selected from the actual author's configured
+  pairing. Reviews apply to an exact revision, not just a branch name.
+- **Visible agent work.** Delegation uses visible Orca orchestration via the `orca` CLI,
+  not harness-native subagent tools.
+- **Explicit boundaries.** Agents work within agreed scope. Missing authority,
+  unavailable models, and serious risks are surfaced rather than silently
+  bypassed. The human merges by default.
+- **Resumable progress.** Work retains ownership, decisions, and evidence so a
+  later session can reconcile what happened before continuing.
+
+Choose an explicit role preset:
 [mixed](profiles/presets/mixed.json),
-[codex-only](profiles/presets/codex-only.json), and
-[claude-only](profiles/presets/claude-only.json). Each is exactly
-`{ "version": 1, "roles": [...] }`. Installation writes the selected snapshot
-to `<skills-dir>/axstack/roles.json` as
-`{ "version": 1, "preset": "<name>", "roles": [...] }` under normal ownership
-hashes. An edited installed role file is preserved.
-
-Mixed configures independent Astra and Fable advisers at high. Single-provider
-presets preserve both adviser IDs and mark the unavailable one with `model:
-null` inside that preset's provider bounds; installation remains ready, while
-Align and Spec hold because both receipts are required. The mixed
-`axstack-checker` and `axstack-research-web-google` roles launch Antigravity by
-agent ID with explicit `model: null`; the run records the model reported by the
-TUI. The single-provider presets configure the checker and record the Google
-research branch as intentionally absent. Preset changes affect new runs only. Stored model, effort, and permission
-fields are declared intent until actual Orca launch receipts establish effective
-behavior; installation never proves provider availability or permission parity.
-Subscription availability and quota never select a fallback model.
-End-to-end compatibility remains unverified without matching runtime receipts.
-
-## Runtime evidence and holds
-
-Native Orca exercises have returned Codex, Claude, and OpenCode Muse Spark
-worker completions, same-terminal follow-up, separate worktree placement, settlement
-cleanup, `user_takeover` retention, and recovery from `consumer_fenced`. These are
-bounded runtime facts, not proof that every role or harness is compatible.
-
-Input acceptance is not agent readiness. A trust prompt was observed after an
-accepted launch, so startup recovery must inspect the existing attempt, never
-answer trust or permission prompts on the worker's behalf, and never create a
-duplicate writer. A `worker_done` advances work only when its Task and Dispatch
-match the active attempt and its revision evidence verifies.
-
-Two logical native PR-manager lanes run on staggered 15-minute schedules. Each
-pass uses a fresh finite session in its persistent dedicated workspace. Review
-and watch each admit at most five bounded PR jobs;
-waiting PRs stay covered without reserving slots. Axstack adds no custom
-scheduler, queue engine, or decision interpreter. Sessions reconcile before
-admission, save durable continuity and decisions, clean only positively
-identified owned unused setup shells, and self-close as their final action.
-Native fresh-session, overlapping-pass, recovery, and VPS resource behavior
-require a canary before activation.
-
-Mobile completion/reply behavior remains unverified. Structural checks and
-qualitative scenario evaluation are not live runtime proof.
-
-## Historical migration boundary
-
-Older releases used Paseo for orchestration and could leave profile ownership
-provenance or retired skills behind. That state is historical and inert in the
-Orca runtime. Migration preserves user-edited and unknown assets and records
-legacy ownership without reading, writing, or deleting live host configuration.
-Use the explicit migration guidance in [installation](docs/installation.md);
-release installation, host cutover, and old-timer cleanup need separate
-authorization.
+[codex-only](profiles/presets/codex-only.json), or
+[claude-only](profiles/presets/claude-only.json).
+Mixed supports the cross-provider implementation workflow. Single-provider
+presets have workflow limitations; they are not automatic fallbacks when a
+model is unavailable. See [workflow and routing details](docs/workflows.md).
+
+## Optional PR automation
+
+Manual review and watch work independently of scheduled automation.
+For recurring use, Axstack defines two native Orca manager lanes: one discovers
+eligible peer-review requests, and the other monitors your open PRs and handles
+authorized repair events.
+
+The lanes use staggered 15-minute schedules. Each pass uses a fresh finite
+session in an isolated workspace and admits at most five executing PR jobs per
+lane, fewer under resource pressure. Waiting PRs remain tracked without consuming
+execution slots, so a large open-PR backlog does not require an idle agent per PR.
+Completed passes save continuity and retire their own verified resources.
+
+Scheduling is opt-in and requires host-specific runtime validation before
+activation. Installing Axstack does not turn it on. Repairs are limited to
+explicitly allowed repositories; automation never merges for you.
+See [PR-manager setup and safety](skills/axstack/references/automations.md).
+
+## Documentation
+
+- [Installation and configuration](docs/installation.md)
+- [Workflows, review policy, and model routing](docs/workflows.md)
+- [PR scope and sizing](skills/axstack/references/pr-shape.md)
+- [Releases](https://github.com/axatbhardwaj/axstack/releases)
 
 ## License
 

package/docs/workflows.md

@@ -184,19 +184,21 @@ read-only observer for standalone watches and never sends.
 
 The accepted contract has exactly two logical native manager lanes: review at
 minutes `0,15,30,45` and watch at `7,22,37,52`. Each scheduled pass uses a
-fresh finite session in a persistent dedicated workspace, scans complete
+fresh finite session in a new isolated workspace, scans complete
 discovery pages, and admits at most five executing
 PR jobs. Waiting PRs stay covered and consume no slot after owned descendants
 settle. Each job uses one repository-parented worktree; managers never check out
 PR branches in their own workspaces.
 
-Every pass reconciles saved, GitHub, and native Orca state before admission. A
+Every pass reconciles saved, GitHub, and native Orca state across all same-lane
+workspaces before admission. A
 confirmed same-lane manager makes the new duplicate do no work or shared-record
 write and close only itself. Normal teardown settles descendants, saves durable
-continuity and decisions, closes only positively identified owned unused setup
-shell terminals, then self-closes as the final action. It never blanket-closes
-the workspace or cleans preserved candidates, evidence, user sessions, unknown
-liveness, `user_takeover`, or ambiguous publication state.
+continuity and decisions outside disposable workspaces, then retires its own
+verified isolated pass workspace as the final action. It never bulk-closes a
+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.
 
 Requested reviews cover any accessible repository; automatic repairs retain
 their `defi-com/monorepo` and `defi-com/mobile` scope. Orca owns schedules,
@@ -226,6 +228,8 @@ Predeclared scenario evaluation is qualitative behavior evidence, not determinis
 compatibility requires actual guide discovery, role/session evidence, worktree
 and Dispatch receipts, completion delivery, and cleanup as applicable. Mobile
 completion and reply behavior remain unverified.
+End-to-end compatibility remains unverified for any route without matching
+runtime receipts; evidence from one route does not establish support for all roles.
 
 ## Historical migration
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.20.1",
+  "version": "0.20.3",
   "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

@@ -13,13 +13,22 @@ There are exactly two logical manager lanes:
   [axstack-watch](../../axstack-watch/SKILL.md) for eligible own-PR watch or
   repair events.
 
-Each scheduled pass starts a fresh finite manager session in its persistent
-dedicated workspace; the workspace and saved continuity persist, but the
-manager chat does not. A manager never checks out a PR branch in that
-workspace. Missed slots do not replay a backlog; the next ordinary pass
+Use a new isolated workspace for every scheduled pass, with one fresh finite
+manager session. Configure native repo-created worktree mode against the
+designated manager repository; never target an existing shared workspace.
+Do not use `--reuse-session`. The scheduler creates the pass workspace before
+launch; the manager must not move itself from a shared launch workspace.
+Keep lane continuity and evidence outside disposable manager workspaces at
+the configured durable absolute paths. A manager never checks out a PR branch
+in its pass workspace. Missed slots do not replay a backlog; the next ordinary pass
 discovers current state. The two short packaged prompts sit beside this file
 and discover these rules by relative link instead of copying them.
 
+Provision one explicit absolute continuity path per automation ID in the
+scheduled prompt. Follow [Run record](run-record.md) for its contents; the
+repository's absolute Git common directory is a valid durable root, but a pass
+worktree is not. Missing or non-durable continuity configuration holds admission.
+
 This is prompt policy, not proof that Orca starts a fresh session or prevents
 overlapping passes. Before activation a native canary must prove fresh-session
 launch, overlapping-pass behavior, recovery after session loss, nested
@@ -29,14 +38,43 @@ effects. A firing timestamp proves neither delivery nor useful completion.
 ## Session admission
 
 Reconcile saved state, current GitHub state, and native Orca Tasks, Dispatches,
-sessions, and liveness in the dedicated workspace before discovery or
-admission. A confirmed live manager for the same lane remains authoritative.
+sessions, and liveness across all workspaces belonging to the same automation
+before discovery or admission; never infer lane ownership from an empty local
+workspace. Bind the lane to the automation ID and pass to its native run ID,
+workspace ID, and terminal identity, not a title or directory-name guess.
+A confirmed live manager for the same lane remains authoritative.
 The new duplicate does no PR work, makes no shared-record write, touches
-nothing owned by the live manager, and closes only itself as its final action.
+nothing owned by the live manager, and closes only itself as its final action
+by the same guarded isolated-workspace retirement below, not a tab-only close.
 Unknown liveness blocks admission and shared-record writes; it does not
 authorize takeover, cleanup, or a duplicate manager. Preserve `user_takeover`
 and other user-owned sessions.
 
+When two new passes overlap, reconcile native run ordering before either admits
+work; the earlier unsettled pass retains the lane. Missing ordering or ownership
+evidence holds admission, never guesses a winner. This is not an atomic lock:
+activation requires an overlap canary proving only one pass admits work. Count
+all unsettled PR jobs and descendants across the lane, not just this workspace.
+Read every page of native runs, workers, and workspace inventory; truncated or
+failed inventory holds admission and cleanup rather than implying absence.
+
+A prior manager does not retain the lane merely because its automation run
+status says failed or dispatched. Require confirmed native process exit for its
+exact terminal incarnation, saved continuity, and settlement of all owned jobs
+and descendants before releasing its lane ownership. Absence or saved retirement
+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.
+
+Before PR admission, reconcile old pass resources. If three or more unreclaimed
+earlier pass workspaces remain, disable only this automation through the native
+CLI, verify the disabled setting, save/report the cleanup hold, and admit no new
+PR jobs. Also pause on a confirmed cleanup failure or unresolved lane ownership.
+Already-dispatched passes still reconcile and retire only their own safe resources;
+this threshold is a stop condition, not an atomic hard cap on in-flight creations.
+An uncertain disable is a reported failure, not proof scheduling stopped. Resume
+only after ownership/cleanup is verified and explicit activation authority exists.
+
 ## Discovery and coverage
 
 Resolve self on every tick with `gh api user --jq .login`; never hardcode the
@@ -176,13 +214,35 @@ and must be reconciled rather than trusted from saved status. Then save durable
 continuity, evidence locations, pending receipts, and user decisions before
 self-close. Waiting PRs still occupy zero slots once their owned trees settle.
 
-Cleanup is scoped to positively identified owned unused setup shells: use the
-version-matched native exact-terminal close operation for each such terminal only.
-Never blanket-close a workspace. Preserve dirty worktrees, unpushed candidates,
-review evidence, user-owned terminals, unknown liveness, `user_takeover`, and
-ambiguous publication state. Close the finite manager's own exact terminal
-through the native guide. Self-close is the final action; perform no record
-write, cleanup, or other work afterward.
+Cleanup of PR-job setup shells stays scoped to positively identified owned unused
+setup shells: use the native exact-terminal close operation for each only.
+Preserve dirty worktrees, unpushed candidates, review evidence, user-owned
+terminals, unknown liveness, `user_takeover`, and ambiguous publication state.
+
+For the manager pass only, verify native run/workspace identity, exclusive
+automation ownership, no unsettled descendants, and a fresh terminal inventory
+containing only this manager and its proven unused setup shells. No other pass
+may target this workspace. If an unexpected terminal or user takeover is present,
+do not bulk-close; preserve the workspace and report the hold at its durable
+decision location. Never bulk-close a shared manager workspace or a PR-job worktree.
+
+After saving continuity, use the version-matched native workspace retirement:
+`terminal close --worktree id:<exact-native-workspace-id> --all --json`.
+Copy the complete ID from the run/workspace receipt; never use a name, branch,
+path-only selector, or `active` for this destructive operation.
+Self-close is the final action; perform no record write or cleanup afterward.
+A failed or uncertain close is not proof of retirement. The next admitted pass
+reconciles prior retirement from native state before trusting saved intent.
+Retire only positively identified completed pass resources; do not kill another
+live or unknown manager. Remove an old pass worktree only with native cleanup
+after terminal retirement is confirmed and its Git state is clean, with no
+unpushed commits, retained evidence, children, or user-owned work. Never use
+recursive shell deletion. Failed cleanup remains recorded, not silently forgotten.
+
+The activation canary must additionally prove distinct workspace IDs per pass,
+cross-workspace lane admission, self-retirement and absence after client reconnect,
+and bounded retained worktrees over repeated passes. A shell-only close test does
+not prove agent resume-record retirement. Do not activate on source checks alone.
 
 ## Recovery and limits
 

package/skills/axstack/references/lifecycle.md

@@ -110,7 +110,7 @@ differs from merged; human merges.
 
 ## Watch health
 
-Native review and watch lanes use fresh finite sessions in persistent dedicated
+Native review and watch lanes use fresh finite sessions in isolated per-pass
 workspaces on staggered 15-minute schedules. Each admits at most five executing PR jobs;
 waiting PRs remain covered without reserving slots. Bounded PR jobs own their
 events, use per-PR worktrees, and settle after descendants settle. Build no

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

@@ -1,10 +1,12 @@
 # Review manager prompt
 
-You are a fresh finite review-manager session in its persistent dedicated Orca workspace. Enter
+You are a fresh finite review-manager session in its isolated per-pass Orca workspace. Enter
 through the installed `axstack-review` skill; that skill loads its packaged
 `../axstack/references/automations.md` contract by relative reference. Discover
 every eligible peer-review event and invoke the skill through Orca for each
 admitted bounded PR job. Keep complete coverage separate from the five-job
 execution cap, preserve exact ownership and receipts, settle completed trees,
 and stay quiet when nothing changed. Reconcile before admission, save durable
-continuity, then self-close as the final action. Never check out a PR branch here.
+continuity outside this workspace, then retire only this pass workspace as the
+final action under the contract's ownership guards. Reconcile the whole lane,
+not just this workspace. Never check out a PR branch here.

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

@@ -1,11 +1,12 @@
 # Watch manager prompt
 
-You are a fresh finite watch-manager session in its persistent dedicated Orca workspace. Enter
+You are a fresh finite watch-manager session in its isolated per-pass Orca workspace. Enter
 through the installed `axstack-watch` skill; that skill loads its packaged
 `../axstack/references/automations.md` contract by relative reference. Discover
 every eligible own-PR event and invoke the skill through Orca for each admitted
 bounded PR job. Keep complete coverage separate from the five-job execution
 cap, preserve exact ownership, candidates, holds, and receipts, settle
 completed trees, and stay quiet when nothing changed. Reconcile before
-admission, save durable continuity, then self-close as the final action. Never
-check out a PR branch here.
+admission, save durable continuity outside this workspace, then retire only this
+pass workspace as the final action under the contract's ownership guards.
+Reconcile the whole lane, not just this workspace. Never check out a PR branch here.

package/skills/axstack-review/SKILL.md

@@ -5,6 +5,8 @@ description: When a candidate PR needs final review, use axstack-review for conf
 
 # Review
 
+Manual invocation does not enter the scheduled manager lifecycle; never close the user’s chat or workspace.
+
 Produce one evidence-bound verdict for an exact candidate revision using the
 review count and model routing required by its mode. Report within the
 requested authority; the human merges unless separately authorized otherwise.

package/skills/axstack-watch/SKILL.md

@@ -5,6 +5,8 @@ description: When babysitting an existing PR, use axstack-watch to monitor or ma
 
 # Watch
 
+Manual invocation does not enter the scheduled manager lifecycle; never close the user’s chat or workspace.
+
 Leave each adopted PR with one accountable owner, current readiness evidence,
 and user-facing updates that name its current milestone and next wake or
 condition.
@@ -71,8 +73,8 @@ Read-only checks and updates to the already-owned local record need no runtime
 load. When the watch needs a new owner or automated observation, first read
 [Watch runtime](references/watch-runtime.md) and then
 [Orca runtime](../axstack/references/orca-runtime.md). Reconcile before creating
-anything. Each native watch-manager pass starts a fresh finite session in one
-persistent dedicated workspace on its staggered 15-minute schedule, covers
+anything. Each native watch-manager pass starts a fresh finite session in an
+isolated per-pass workspace on its staggered 15-minute schedule, covers
 every eligible own PR, and starts only bounded actionable-event jobs. Waiting PRs reserve no execution slots and
 there is no watch deadline for manager automation. `axstack-monitor` stays an
 optional read-only observer that never sends. One read-only PR observation

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

@@ -14,9 +14,10 @@ stop task-owned registrations at completion, cancellation, or expiry.
 ## Native watch manager
 
 The separate native watch manager lane follows the
-[native PR-manager contract](../../axstack/references/automations.md). It reuses
-one persistent dedicated workspace while each scheduled pass uses a fresh
-finite session at minutes `7,22,37,52`. It scans every eligible own PR and
+[native PR-manager contract](../../axstack/references/automations.md). Each pass
+uses a new isolated workspace and fresh finite session at minutes `7,22,37,52`.
+Continuity survives outside disposable workspaces; admission reconciles the
+whole lane across workspaces. It scans every eligible own PR and
 admits at most five bounded actionable-event jobs. Waiting PRs stay covered
 without reserving slots. Each job uses its own repository-parented worktree and
 settles with all descendants; no model, per-PR timer, or polling loop waits for