axstack 0.34.4 → 0.36.0

package/README.md

@@ -22,7 +22,7 @@ coordination. You can start at the phase you need.
 ## Prerequisites
 
 Axstack supports only Linux hosts. You need Bun >=1.3.14, Git, the GitHub
-CLI (`gh`) with `gh stack`, and T3 Code `0.0.46-nightly.20261003.2610` or newer
+CLI (`gh`), and T3 Code `0.0.46-nightly.20261003.2610` or newer
 on PATH. The providers selected by your preset must be available inside T3.
 
 Choose one explicit preset (each contains all role IDs): [mixed](profiles/presets/mixed.json)
@@ -66,7 +66,7 @@ You make decisions at holds and substantial-spec approval.
 Follow [getting started](docs/getting-started.md) for the full first-task journey
 and [guides](docs/guides.md) for features, reviews, watches, debugging and releases.
 
-## What you can do
+## What you can do (19 skills)
 
 | Layer | Skill | What it does |
 | --- | --- | --- |
@@ -86,6 +86,7 @@ and [guides](docs/guides.md) for features, reviews, watches, debugging and relea
 | Operate | [axstack-cleanup](skills/axstack-cleanup/SKILL.md) | Retire eligible completed agent resources. |
 | Operate | [axstack-relay](skills/axstack-relay/SKILL.md) | Send an explicit message or authorized notification. |
 | Understand | [axstack-research](skills/axstack-research/SKILL.md) | Answer one bounded question with sources. |
+| Understand | [axstack-scout](skills/axstack-scout/SKILL.md) | Gather codebase evidence for an agent across several areas. |
 | Understand | [axstack-explain](skills/axstack-explain/SKILL.md) | Explain a system and separate known behavior from gaps. |
 | Understand | [axstack-diagram](skills/axstack-diagram/SKILL.md) | Draw SVG/CSS in inline pages, Mermaid for chat/GitHub/docs, or requested archify viewers. |
 

package/bin/axstack.js

@@ -51,7 +51,7 @@ Usage:
 Commands:
   install    Validate a skill bundle, then copy owned skills and selected role
              data and record ownership hashes.
-  check      Probe Bun, Git, gh stack, and the T3 Code version floor.
+  check      Probe Bun, Git, gh, and the T3 Code version floor.
              Driver preflight verifies MCP readiness inside a T3 thread.
   uninstall  Remove only unchanged Axstack-owned assets. User edits survive.
 

package/docs/getting-started.md

@@ -8,7 +8,7 @@ For the mental model, read [concepts](concepts.md); for other journeys, use
 
 ## Prepare your host
 
-You need Bun >=1.3.14, Git, the GitHub CLI with its `gh stack` extension, and
+You need Bun >=1.3.14, Git, the GitHub CLI, and
 T3 Code `0.0.46-nightly.20261003.2610` or newer. These executables must be on PATH.
 The providers required by your chosen preset must be available inside T3.
 See [installation](installation.md) for harness paths and
@@ -30,17 +30,17 @@ and fetches the pinned archify tool for explicit viewer requests. Reload the
 harness's skills in T3 after installation. Use the [installation reference](installation.md) for other
 harnesses, source installs or conflicts.
 
-A successful check exits 0. Its five capability rows mean:
+A successful check exits 0. Its four capability rows mean:
 
 | Row | Meaning |
 | --- | --- |
 | `bun` | The running Bun version meets the floor. |
 | `git` | Git's version command succeeds. |
 | `gh` | The GitHub CLI's version command succeeds. |
-| `gh stack` | The extension's actual help command succeeds. |
 | `t3` | T3's version command succeeds and meets the floor. |
 
-With this harness target, check also validates the archify record/copy/SHA and
+The `gh stack` extension is needed only for preexisting native stacks; ordinary
+PRs/chains use Git and `gh pr`. With this harness target, check also validates the archify record/copy/SHA and
 reports the owned instruction binding. Missing Chrome is a warning. Any reported
 gap exits 1; follow [troubleshooting](installation.md#exit-codes-and-troubleshooting) before
 starting a task.

package/docs/guides.md

@@ -12,7 +12,7 @@ Invoke `$axstack-spec Write the agreed specification.` to record observable
 acceptance, exclusions and a revision for your approval. After approval,
 `$axstack-tickets Map the approved work into tasks.` prepares the dependency map.
 `$axstack-implement Build the approved tasks.` carries it through authors,
-exact-revision review and repairs. The driver publishes through `gh stack`
+exact-revision review and repairs. The driver publishes through scoped Git push and `gh pr create/edit`
 and records each candidate and its evidence.
 
 ## Small fix

package/docs/installation.md

@@ -7,7 +7,7 @@ checks host capabilities. T3 Code is the only supported active runtime. The CLI
 does not dispatch agents, edit T3 settings, run a scheduler, or maintain a
 workflow database.
 
-Requirements: Bun >=1.3.14, Git, `gh`, the `gh stack` extension, and a running
+Requirements: Bun >=1.3.14, Git, `gh`, and a running
 T3 Code `0.0.46-nightly.20261003.2610` or newer. The driver is a T3 thread
 with the `t3-code` MCP. See the [T3 runtime boundary](../skills/axstack/references/t3-runtime.md).
 Axstack has no runtime package dependencies. Filesystem access uses Bun-backed
@@ -123,14 +123,14 @@ role store and no T3 configuration merge.
 axstack check [--bundle <dir>] [--instructions <file>] [--skills-dir <dir>|--harness <name>]
 ```
 
-The capability report has five rows:
+The capability report has four rows; `gh stack` is required only for preexisting
+legacy native-stack operations, which probe `gh stack --help` separately:
 
 | Row | What it checks |
 | --- | --- |
 | `bun` | The `bun` row reports the already-validated running version, because Bun below 1.3.14 exits 1 before any row is printed. |
 | `git` | `git --version` succeeds. |
 | `gh` | `gh --version` succeeds. |
-| `gh stack` | `gh stack --help` succeeds, rather than merely finding an extension name. |
 | `t3` | `t3 --version` succeeds and its output meets the T3 version floor. |
 
 `--bundle` additionally validates the bundle and reports its skill-file count
@@ -307,6 +307,11 @@ The `mixed` and `claude-only` presets assign `axstack-auditor`,
 Activation requires that exact ID and high effort in saved T3 capabilities;
 missing either holds these roles without substitution, including Haiku 4.5.
 The `codex-only` assignments for these roles are unchanged.
+Scout adds `axstack-explore-codebase-luna` at Codex Luna xhigh in `mixed` and
+`codex-only`. The optional `axstack-explore-codebase-flash` seat uses
+Antigravity `gemini-3.8-flash-medium` at medium effort in `mixed`.
+The missing Scout seats have explicit null models: Luna and Flash in
+`claude-only`, and Flash in `codex-only`.
 The three `-sol` pair seats for auditor, research-code, and explore-execution
 use Sol high in `mixed` and `codex-only`; `claude-only` records intentional
 absences. The paired seats run independently on one brief and the driver

package/docs/workflows.md

@@ -29,6 +29,8 @@ Direct routes need no spec ceremony:
 - [axstack-perf](../skills/axstack-perf/SKILL.md) routes performance work to
   Debug, Improve, or Implement through the shared performance loop.
 - `axstack-research` answers one bounded source-backed question.
+- `axstack-scout` gathers cited codebase evidence for broad or unfamiliar
+  questions using independent, read-only seats.
 - `axstack-correct` reports repeated mistakes and proposes stronger checks.
   Only the user invokes it.
 - `axstack-explain` separates implemented, intended, tested, live, and unknown
@@ -129,8 +131,11 @@ use the Claude Sonnet class at high effort. `axstack-explore-codebase` and
 `axstack-monitor` adopt Haiku 5.5 high, with class `haiku` and exact pin
 `claude-haiku-5-5`. Missing that ID or high effort in saved T3 capabilities
 holds those roles without substitution. `codex-only` keeps its Codex
-assignments for those roles. Mixed web-google and X retain their source-specific
-Antigravity and Grok routes.
+assignments for those roles. Scout adds a Luna xhigh codebase seat in `mixed`
+and `codex-only`, and an optional Antigravity Flash medium seat in `mixed`.
+In `claude-only`, Luna and Flash are intentionally absent; Flash is also
+intentionally absent in `codex-only`. Mixed web-google and X retain their
+source-specific Antigravity and Grok routes.
 The mixed `axstack-auditor` uses Haiku 5.5 xhigh, pinned to `claude-haiku-5-5`;
 missing that ID or xhigh effort holds without substitution. The mixed
 `axstack-explainer-review` uses Sol medium; `axstack-explainer` stays Sonnet high.
@@ -234,7 +239,7 @@ for explicit ownership transfer.
 - `axstack-implement` uses strict behavioral RED, GREEN, then refactor. The
   narrow accepted structure-preserving route uses old-green and the same check
   new-green. One author writes and returns a local receipt without pushing. The
-  owner reconciles it, publishes the unchanged commits through `gh stack`, and
+  owner reconciles it, publishes the unchanged commits through scoped Git push and `gh pr create/edit`, and
   confirms the remote SHA before review. Local green and CI green remain
   separate evidence. Authors apply the shared
   [test-value gate](../skills/axstack/references/test-value.md) to each new or
@@ -250,7 +255,7 @@ for explicit ownership transfer.
   authorized-maintenance scope. A changed head or comment is an event, not
   repair authority. Within an implementation run, fixes return to the original
   author and follow its publish-before-review loop. Manual adopted-PR repair
-  reviews the exact local SHA and reply bodies before `gh stack` publication
+  reviews the exact local SHA and reply bodies before scoped Git push and `gh pr create/edit` publication
   and remote readback.
 - `axstack-audit` separates execution outcome, procedure, and measurement
   coverage with evidenced denominators; it proposes but never self-edits.
@@ -393,7 +398,8 @@ that authored or repaired `merge-base..head` commits. Team approval also needs a
 counted non-author collaborator review at the current head. Axstack automation
 votes never count. Unknown or mixed provenance and manually authored PRs need a
 merge card. New heads need fresh authored review, diligence, and CI. A collaborator
-approval carries over only across an unchanged stable patch-id rebase, recorded
+approval carries over only across an unchanged stable patch-id rebase, base-update
+merge or base-only retarget, recorded
 for both heads, while the forge still counts it.
 
 Base classification uses repository docs and workflows, never the branch name
@@ -417,6 +423,9 @@ Proven verification is required for every own PR. Use the authored receipt:
   Earlier-head red-to-green evidence in the PR's patch lineage counts only when
   the reviewer records that it still applies to the final change.
   An applicable `verify-<app>` passing result is required for the changed behavior.
+  The passing result must come from the reviewer's or `axstack-ui-verifier`'s local drive at that head.
+  The author's log alone never satisfies this requirement.
+  A preview URL never satisfies this requirement.
 - Verification requires no limitation tagged `changed-behavior: unproven`.
   The reviewer tags every limitation leaving changed behavior unexercised or
   unverified, in whatever words, `changed-behavior: unproven`.
@@ -483,12 +492,35 @@ Personal and work PRs remain eligible whatever files they change, including
 branch-protection or ruleset config, `CODEOWNERS`, `AGENTS.md`, and non-clean
 revert lines such as `Revert: steps`.
 
-For a `gh stack`, only the bottom member's base must be eligible.
+For a legacy native `gh stack`, only the bottom member's base must be eligible.
 Each other member's base must be the next-lower member's branch at its reviewed head.
 Every member must meet every other term.
-A stack holds until every member of its approved plan (the ticket map or the
+A legacy native stack holds until every member of its approved plan (the ticket map or the
 adopted stack's recorded members) is published.
-Reviewed members are never retargeted to become eligible.
+Reviewed legacy native-stack members are never retargeted to become eligible.
+
+New work uses ordinary PRs/chains under [PR chains](../skills/axstack/references/pr-chain.md).
+Record chain/native identity and direct dependencies; unknown or mixed routing
+holds affected operations. Children start from reviewed parents and merge
+parent/base updates without rewriting existing commits. Immediately invalidate
+affected child readiness, then refresh next ready children as needed, batching
+ancestor changes. A ready parent with independently deliverable approved scope
+can integrate before its children are published or ready. Only ready roots
+merge into integration targets; children never merge into open parent branches.
+
+Each root uses `gh pr merge <n> --merge --match-head-commit <sha>` under the full
+watch predicate, with merge commits enabled, no merge queue and auto-delete off.
+After confirmed parent merge, prove actual head equals reviewed head and is an
+ancestor of the integration result; reread direct child head/old base, change
+only base and read back unchanged head/new base. Unknown outcomes require lookup
+before retry; rewritten, squash/rebase or closed-unmerged parents hold dependents.
+The latest integration tip must enter child history before its merge. Retargeting
+or a base update requires fresh applicable review, diligence, shape, CI and
+approval evaluation bound to PR/head/base branch/base SHA. Branch retirement
+checks unpublished dependencies, active authors and complete open-PR inventory;
+unknown consumers hold deletion, not independent parent integration. Existing
+native stacks retain their full-stack, linear-history and no-retarget path.
+Singleton eligibility and user-only categories are unchanged.
 
 Never auto-merge PRs authored by anyone other than the user or the user's agents.
 Test sources stay eligible.

package/package.json

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

package/profiles/presets/claude-only.json

@@ -173,6 +173,24 @@
       "modelClass": "haiku",
       "model": "claude-haiku-5-5"
     },
+    {
+      "id": "axstack-explore-codebase-luna",
+      "name": "Axstack codebase explorer Luna (unavailable)",
+      "provider": "claude",
+      "model": null,
+      "modeId": "bypassPermissions",
+      "thinkingOptionId": "xhigh",
+      "notes": "Intentional single-provider absence: Luna Scout seat is unavailable in claude-only."
+    },
+    {
+      "id": "axstack-explore-codebase-flash",
+      "name": "Axstack codebase explorer Flash (unavailable)",
+      "provider": "claude",
+      "model": null,
+      "modeId": "bypassPermissions",
+      "thinkingOptionId": "medium",
+      "notes": "Intentional single-provider absence: Flash Scout seat is unavailable in claude-only."
+    },
     {
       "id": "axstack-explore-execution",
       "name": "Axstack execution explorer",

package/profiles/presets/codex-only.json

@@ -172,6 +172,24 @@
       "notes": "Codebase mapper: explores repository structure and interfaces for research and handoff context. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
       "modelClass": "sol"
     },
+    {
+      "id": "axstack-explore-codebase-luna",
+      "name": "Axstack codebase explorer Luna",
+      "provider": "codex",
+      "modeId": "full-access",
+      "thinkingOptionId": "xhigh",
+      "notes": "Independent read-only Luna Scout facet explorer. Searches the whole repository on the same brief without cross-reading; reports evidence for driver reconciliation. Unavailable model or effort holds without substitution.",
+      "modelClass": "luna"
+    },
+    {
+      "id": "axstack-explore-codebase-flash",
+      "name": "Axstack codebase explorer Flash (unavailable)",
+      "provider": "codex",
+      "model": null,
+      "modeId": "full-access",
+      "thinkingOptionId": "medium",
+      "notes": "Intentional single-provider absence: Flash Scout seat is unavailable in codex-only."
+    },
     {
       "id": "axstack-explore-execution",
       "name": "Axstack execution explorer",

package/profiles/presets/mixed.json

@@ -173,6 +173,24 @@
       "modelClass": "haiku",
       "model": "claude-haiku-5-5"
     },
+    {
+      "id": "axstack-explore-codebase-luna",
+      "name": "Axstack codebase explorer Luna",
+      "provider": "codex",
+      "modeId": "full-access",
+      "thinkingOptionId": "xhigh",
+      "notes": "Independent read-only Luna Scout facet explorer. Searches the whole repository on the same brief without cross-reading; reports evidence for driver reconciliation. Unavailable model or effort holds without substitution.",
+      "modelClass": "luna"
+    },
+    {
+      "id": "axstack-explore-codebase-flash",
+      "name": "Axstack codebase explorer Flash",
+      "provider": "antigravity",
+      "model": "gemini-3.8-flash-medium",
+      "modeId": "full-access",
+      "thinkingOptionId": "medium",
+      "notes": "Optional read-only Scout breadth seat: searches the whole repository for missed boundaries and counterexamples. Reports evidence for driver reconciliation without cross-reading."
+    },
     {
       "id": "axstack-explore-execution",
       "name": "Axstack execution explorer",

package/skills/axstack/references/automations.md

@@ -210,10 +210,12 @@ through a broad `TMPDIR` glob, sweep a shared temporary root, or wipe a general
 cache. Preserve evidence and any temporary path with uncertain ownership or
 containment.
 
-An unchanged exact head and unchanged event identity creates no job; an
+An unchanged exact head, base branch identity, base SHA and event identity
+creates no job; an
 unchanged exact head with a new event identity remains actionable. Event
 identity includes the applicable review ID and body digest, request identity, or other current GitHub event
-receipt. Dedupe from current GitHub state,
+receipt. A base-only retarget or base update is a new evidence identity under
+[PR chains](pr-chain.md). Dedupe from current GitHub state,
 native T3 task and thread/run state, and the existing compact run record; do
 not create machine cursor files or a queue engine. Record enough to resume: PR,
 head, base, event identity, mode, owner and worker receipts, verdict,

package/skills/axstack/references/autopilot.md

@@ -97,7 +97,8 @@ cadence conditions before ending the turn.
 An explicitly adopted PR joins only with its maintenance snapshot.
 The original driver alone routes work; one author writes each
 candidate. Until a PR is merge-ready, wakes feed implement §6 step 4. After
-merge-ready, watch §5 maintenance repairs feedback, rebases when the base moves,
+merge-ready, watch §5 maintenance repairs feedback, updates the base under
+[PR chains](pr-chain.md),
 keeps CI green, and checks approvals without re-requesting human review.
 
 Maintain is the default mode for run-created PRs.
@@ -168,20 +169,9 @@ instructions, always win.
 
 Follow [Provider bindings](t3-runtime.md#preflight-and-binding) for driver account re-selection on start, resume and run-watch wakes.
 
-Use the run's recorded Notification policy through `axstack-relay`.
-Decision holds, including spec and npm approval, are always eligible.
-Relay eligibility is limited to user-decision holds, serious-risk holds, the
-60-minute blocked ping, unresolved-rating notice and capped peer PR milestones
-under the Notification policy.
-Under the recorded Notification policy, `verification not proven` is a
-user-decision hold. The 60-minute blocked ping is a notification-only category
-under the Notification policy. The unresolved-rating notice is a notification-only
-category under the Notification policy, deduplicated per comment and head.
-The unresolved-rating notice grants no reply authority.
-The unresolved-rating notice never clears the hold.
-Never send routine merge-ready or merged relays
-for own PRs. Notifications for peer PRs are unchanged, including at most two
-merge-ready/merged milestones per run, deduplicated across implementation and release.
+Follow [Watch notifications](../../axstack-watch/SKILL.md#4-route-each-wake)
+under the recorded Notification policy. Decision holds, including spec and npm
+approval, are always eligible.
 Across implementation and release, peer PR merge-ready and merged notifications
 together are capped at two per run; deduplicate by purpose and revision. Healthy ticks stay
 quiet. A failed or uncertain delivery preserves the underlying hold. A relay

package/skills/axstack/references/candidate-publication.md

@@ -1,25 +1,27 @@
 # Candidate publication
 
-This is the author-to-review boundary for an owned candidate. The author stops
-after returning its revision-bound implementation receipt and does not push.
-Within recorded PR-scoped publication authority, the owner reconciles that
-receipt against the actual local candidate SHA and base. The owner does not edit
-the author's candidate; required code changes return to the author.
+For an owned candidate, the author returns its revision-bound implementation
+receipt and stops without pushing. Under recorded PR-scoped publication authority,
+the owner reconciles author receipt with actual local candidate SHA/base. The owner
+does not edit the candidate; code changes return to its author.
 
 Before publication, dispatch `axstack-diligence` under
 [Diligence](diligence.md) to check the author receipt against its evidence
 folder: red/green logs exist, and counts, SHAs, and paths match. Resolve
 `FINDINGS` with the same author before publishing.
 
-Publish the existing commits through `gh stack`. Prefer a fast-forward push.
-Before a history rewrite, confirm the expected-old remote SHA and use lease
-protection; a mismatch holds publication. If the push outcome is ambiguous,
+Follow [PR chains](pr-chain.md) for recorded membership and base-bound evidence.
+For ordinary PRs, use `git push origin HEAD:refs/heads/<owned branch>` and
+`gh pr create` or `gh pr edit` with the actual parent or integration base.
+Never use routine force push for ordinary PRs. For legacy native `gh stack`,
+prefer a fast-forward push of existing commits, preserving unrelated entries.
+Before a history rewrite, confirm expected-old remote SHA and use a narrowly
+justified lease; a mismatch holds publication. If push outcome is ambiguous,
 inspect remote state before retrying.
 
-Before reviewer dispatch, read the remote ref back and confirm that it resolves
-to the candidate SHA; also pin the current base.
-Before reviewer dispatch, refresh the PR body counts and base from the confirmed
-candidate SHA and current base under [PR shape](pr-shape.md).
+Before reviewer dispatch, read the remote ref back, confirm its SHA equals candidate SHA, pin
+current base and refresh PR body counts and base from confirmed candidate SHA
+and that base under [PR shape](pr-shape.md).
 After every push, before post-push diligence or merge-ready, compare the PR body's
 stated head SHA with `Confirmed remote SHA` and record `PR body head SHA: <sha or none>`.
 Accept `none` for a PR body without a stated head SHA.
@@ -32,6 +34,7 @@ Record:
 
 ```text
 Candidate: <sha>
+Base branch: <branch>
 Base: <sha>
 Remote ref: <branch>
 Expected-old remote SHA: <sha | absent>
@@ -41,11 +44,8 @@ PR: <url>
 CI: <run ID or URL and triggered/pending/completed status>
 ```
 
-Local green is not CI green: immediately after publication CI is pending until
-its required checks complete. Review may run in parallel with CI only after the
-remote confirmation. Reviewers inspect a detached immutable checkout of the
-confirmed candidate SHA and pinned base, never only the movable branch name.
-Any author repair creates a new revision and repeats this boundary.
+Local green is not CI green: CI is pending after publication until required checks complete. Review may run alongside CI only after remote confirmation. Follow [Immutable checkout shape](#immutable-checkout-shape) for review.
+Author repairs create new revisions and repeat this boundary.
 After verified publication readback, follow
 [Native PR links and watches](t3-runtime.md#native-pr-links-and-watches).
 
@@ -67,18 +67,17 @@ step, subject to recorded release authority and human npm stage approval.
 ## Immutable checkout shape
 
 The driver creates the immutable review checkout with `git worktree add --detach <run>/checkouts/<key> <sha>` at the confirmed candidate SHA and pinned base.
-Follow [T3 runtime](t3-runtime.md) for async `delegate_task` and exact attempt
-identity. The checkout is disposable, made from the existing repository; never
-register a duplicate repository or replace it with a movable branch checkout.
+Follow [T3 runtime](t3-runtime.md) for async `delegate_task`.
+Bind disposable checkout to exact attempt identity.
+Use the existing repository; never register a duplicate or use a movable branch.
 Delegated reviewers must `cd` into their separate detached checkout; tracked candidate files remain read-only and outputs go to their private evidence folder.
-Snapshot driver HEAD and full status, including untracked entries, before dispatch.
+Snapshot driver HEAD and full status (including untracked) before dispatch.
 After each delegated completion, compare the driver HEAD and `git status --porcelain` with their pre-dispatch values; any change holds advancement.
-Each peer reviewer has a separate checkout and evidence folder with no first-pass
-cross-read. Later review gets a fresh checkout.
+Peer reviewers have separate checkouts/evidence without first-pass cross-read.
+Later review gets a fresh checkout.
 Before removing a reviewer checkout, read back its report and supporting evidence, then use exact `git worktree remove <run>/checkouts/<key>` without force.
-Verify Git worktree absence under [Workspace hygiene](workspace-hygiene.md);
-reviewer retirement preserves the separate author candidate until merge or closure.
-Release checks use the same driver-made SHA-pinned detached-checkout procedure.
+Verify absence under [Workspace hygiene](workspace-hygiene.md); retain the author
+candidate until merge/closure. Release checks use same driver-made SHA-pinned detached-checkout procedure.
 
 For a release PR, dispatch `axstack-diligence` under
 [Diligence](diligence.md) to check the release PR body

package/skills/axstack/references/contracts.md

@@ -125,12 +125,11 @@ remain a serious-risk hold.
 - One T3 host/server owns a run. No fixed active-PR count; fanout is dependency-
   and capacity-driven within host resource and spending limits. Reduce fanout for
   recorded rework, review backlog, or resource pressure. Queue conflicts and
-  dependencies; use `gh stack` for dependent PRs. Routine shape, split, fanout, and
+  dependencies; follow [PR chains](pr-chain.md). Routine shape, split, fanout, and
   exception choices within approved scope are autonomous driver decisions; size alone never
   requires user approval.
 - Exactly one writer per candidate; one persistent accountable PR owner. Each PR has one theme and measured size under [PR shape](pr-shape.md). Report unknown capacity
-  metrics; never a telemetry prerequisite or blocker. Parent changes invalidate
-  affected child evidence; refresh it against the new parent.
+  metrics; never a telemetry prerequisite or blocker. PR chains owns child evidence invalidation and refresh.
 - Own PRs default to automatic merge under [watch §5](../../axstack-watch/SKILL.md).
   Review approval and reviewer votes alone never grant mutation or merge authority.
   User merges are bottom-up for a stack.

package/skills/axstack/references/lifecycle.md

@@ -24,7 +24,7 @@ binding state and receipts to exact revisions.
 
 Prefer parallel independent bounded work; no redundant workers. Fanout is dependency- and
 capacity-driven within host/spending limits. [PR shape](pr-shape.md) covers
-theme/size; queue dependencies through `gh stack`.
+theme/size; queue dependencies under [PR chains](pr-chain.md).
 
 ## Ownership
 
@@ -70,7 +70,7 @@ Store receipt references, not raw output, in the [Run record](run-record.md).
   role; reuse on resume.
 - Acceptance receipt: sender/recipient, accepted scope/authority, timestamp,
   and ownership session receipt.
-- Review receipt: mode, provenance, reviewer, SHA/base,
+- Review receipt: mode, provenance, reviewer, PR/head/base branch/base SHA,
   verdict (`APPROVE | REQUEST_CHANGES | INCOMPLETE`), coverage, limitations and
   findings. Changed code needs a new receipt. Codebase: revision/scope,
   `COMPLETE | INCOMPLETE` coverage, no PR verdict.

package/skills/axstack/references/pr-chain.md

@@ -0,0 +1,51 @@
+# Ordinary PR chains
+
+Record ordinary-chain or legacy-native-stack identity and direct dependencies.
+Ordinary PRs/chains are default. Unknown/mixed identity holds
+affected operations. Use `gh stack` only for legacy-native-stack operations,
+probe `gh stack --help` first. Preserve publication, linear-history, full-stack
+merge, pinning and no-retarget rules under
+[watch §5](../../axstack-watch/SKILL.md#5-state-readiness-precisely).
+No automatic live unstacking. Singleton eligibility unchanged.
+
+Children start from reviewed parent. For ordinary chains, merge parent
+or base into owned child preserving existing commits. Immediately
+invalidate affected child readiness. Refresh next ready children and direct
+dependencies as needed, batching ancestor changes. Re-run affected checks and
+remeasure shape against new base; size growth alone is not an automatic hold.
+Legacy children retain reviewed-parent rebasing and revalidation.
+Ordinary chains/legacy stacks: repair lowest affected ancestor first,
+then refresh/revalidate children as needed.
+
+## Integration
+
+Only ready chain roots merge into integration targets. Never merge a child into
+an open parent branch. Ready parent can merge before child publication or
+readiness for independently deliverable approved scope. Apply watch §5, including
+personal/work eligibility and user-only categories. Latest integration tip
+must enter child history before merge.
+
+After confirmed parent merge, verify reviewed head equals actual head and
+is reachable from integration result. Mismatch: serious-risk hold.
+Direct children: reread old head and base, change only base, read back
+unchanged head and new base. Use `gh pr edit <child> --base <integration>` only
+after confirming old base is parent branch and recorded head matches.
+Retarget direct children only; prove forge auto-retargeting likewise.
+Unknown retarget outcome: lookup before retry. Closed without merge,
+rewritten parents, external squash or rebase, and missing ancestry hold dependents.
+
+Bind evidence to PR, head, base branch identity and base SHA. Base-only retarget
+or base update needs fresh applicable review, diligence, shape, CI and
+approval evaluation. Check new-base workflow coverage at unchanged heads;
+never reuse old-base receipts. Carryover compares stable patch-id at both recorded
+head/base
+identities and requires a forge-counted human approval under watch §5. Never
+automatically request human rereview.
+
+## Retirement
+
+Branch retirement checks published and unpublished dependencies, active authors
+and complete open-PR inventory. Unknown consumers hold deletion, never safe
+independent parent integration. Resolve/read back all consumers before deletion.
+Keep auto-delete off; omit
+merge-time deletion for present/uncertain consumers.

package/skills/axstack/references/role-roster.md

@@ -41,6 +41,10 @@
   or high effort holds these roles without substitution.
   `axstack-monitor`: standalone watch never sends; chat-run watch: bounded
   internal reports to its Run and original driver.
+- Scout requires `axstack-explore-codebase` and
+  `axstack-explore-codebase-luna` per facet in mixed (Haiku high + Luna
+  xhigh) and codex-only (Sol high + Luna xhigh). Claude-only requires
+  the Haiku high base seat per facet.
 - Sol pairs `axstack-auditor-sol`/`axstack-research-code-sol`/
   `axstack-explore-execution-sol`: `codex/sol` high in
   mixed/codex-only; intentionally absent in claude-only. Dispatch each
@@ -50,7 +54,8 @@
 - Optional seats: `axstack-arena-candidate-grok`,
   `axstack-arena-candidate-antigravity`, `axstack-research-web-google`,
   `axstack-research-x`, `axstack-checker`, `axstack-research-code-sol`,
-  `axstack-explore-execution-sol`, `axstack-auditor-sol`.
+  `axstack-explore-execution-sol`, `axstack-auditor-sol`,
+  `axstack-explore-codebase-flash`.
   Always dispatch optional seats when configured and available. Only a
   launch failure, trust/login prompt, or prompt block makes one absent:
   fence the attempt, record `absent (<reason>)`, name it once in the next

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

@@ -183,6 +183,7 @@ Deploying bases: <base -> integration | deploying; docs/workflow evidence>
 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>
+PR membership: <PR -> ordinary-chain | legacy-native-stack; direct dependencies incl unpublished; active authors; head/base branch/base SHA>
 IDs: <projectId + driver threadId/runId + dispatch identity receipt pointers>
 Runtime: <host + T3 version + installed Axstack SHA + installed Axstack version/check time + last reference read time + capabilities JSON path>
 Schedules: <scheduledTaskIds of every watch and manager schedule>

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

@@ -264,12 +264,12 @@ delete preserves the hold and recorded ID.
 ## Native PR links and watches
 
 After verified publication readback or adoption of an own PR, the driver calls
-`link_pull_request` with the full PR URL for every layer of a `gh stack`.
+`link_pull_request` with the full PR URL for every layer of an ordinary-chain or legacy `gh stack`.
 Before finishing PR work, including watch end or Close-out, the driver calls
 `list_thread_pull_requests` and links every missing run PR.
 Never link unrelated PRs.
 
-After verified publication readback of an own PR, for every layer of a `gh stack`,
+After verified publication readback of an own PR, for every layer of an ordinary-chain or legacy `gh stack`,
 the driver also calls `t3_thread_update` with `action: link_pull_request`,
 `pullRequest` containing its number, repository and full PR URL, and `threadId`
 set to the author thread, then reads back the PR link with

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

@@ -57,7 +57,7 @@ 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;
+[Candidate publication](candidate-publication.md) and opens at most one test-audit PR per week after independent review;
 for own PRs, automatic merge is the default under the
 [watch predicate](../../axstack-watch/SKILL.md#5-state-readiness-precisely).
 

package/skills/axstack/references/ui-verification.md

@@ -47,6 +47,7 @@ If a PR changes a mapped feature, its author updates the feature file in the sam
 For a missing skill, add "suggest `axstack-verify create`" to the receipt's `Unverified:` line.
 Never generate a verification skill automatically.
 For a broken or stale recipe, report the gap.
+Report a broken or stale recipe as a `low` finding naming `axstack-verify maintain`.
 Never let a broken or stale recipe waive existing acceptance obligations.
 Keep browser recipes tool-neutral for the verifier.
 

package/skills/axstack-align/SKILL.md

@@ -149,6 +149,11 @@ approval; record chosen document names and paths once per run.
    gaps. For substantial work, this summary becomes part of the draft spec in
    `axstack-spec`; spec approval is the one human checkpoint. Included and
    excluded work must be distinguishable, and no open item may appear settled.
+   When scope changes runnable behavior, the read-back records a Verification decision.
+   For an applicable `verify-<app>` skill, record the features that cover the change.
+   For a missing skill, the plan always includes `axstack-verify create` as the first PR.
+   Skipping this first PR requires plain AGREE from both `axstack-advisor-astra` and `axstack-advisor-opus` that a verification skill is unnecessary.
+   Record both advisers' reason in the Verification decision.
 2. Classify the result with the shared
    [proportional scope identity](../axstack/references/routing.md#proportional-scope-identity):
    - For work clarified as small, return a **small-change intent** handoff with