axstack 0.36.0 → 0.37.0

package/README.md

@@ -88,10 +88,11 @@ and [guides](docs/guides.md) for features, reviews, watches, debugging and relea
 | 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. |
+| Understand | [axstack-anatomy](skills/axstack-anatomy/SKILL.md) | Build an isometric physical-object figure with the vendored anatomy kit. |
 
 Explanations default to checked inline T3 pages above a short reply.
-Use [archify](https://github.com/tt-a1i/archify) (MIT) only on an explicit viewer request.
+Use Anatomy only on an explicit isometric or physical-object figure request.
+Every Explain visual is authored and independently reviewed; plain prose stays proportional.
 
 ## How work stays controlled
 
@@ -126,10 +127,13 @@ Eligible own PRs use guarded automatic merge; see [merge boundaries, exclusions,
 ## Some notes
 
 - T3 Code is the only supported active runtime. Axstack adds no daemon or runtime
-  database. The exception is one opt-in systemd user timer `axstack-default-sync`,
-  running a stateless script that rewrites only T3 `defaultModelSelection`.
-  It has no workflow state and launches no agent; see
-  [Host operations](docs/host-operations.md#new-chat-default-sync).
+  database. The exceptions are exactly two opt-in systemd user timers:
+  `axstack-default-sync` rewrites only T3 `defaultModelSelection`, and
+  `axstack-single-server` removes duplicate `t3 serve` process trees for one
+  base dir while keeping the recorded server. Both run stateless scripts, keep
+  no workflow state and launch no agent; see
+  [New-chat default sync](docs/host-operations.md#new-chat-default-sync) and
+  [Single T3 server](docs/host-operations.md#single-t3-server).
 - The recorded owning watch thread merges eligible own PRs; excluded PRs use a merge card.
 - This is an early project; expect the workflows to evolve.
 

package/bin/axstack.js

@@ -13,7 +13,7 @@ import {
   uninstallBundle,
   validateBundle,
 } from '../src/installer.js';
-import { BUN_FLOOR, checkArchify, checkCapabilities, meetsFloor, runRealCheck } from '../src/capabilities.js';
+import { BUN_FLOOR, checkCapabilities, meetsFloor, runRealCheck } from '../src/capabilities.js';
 import { findLegacyRoutingLines } from '../src/instructions.js';
 import { harnessLocations } from '../src/locations.js';
 
@@ -43,7 +43,7 @@ function packageVersion() {
 const HELP = `axstack — Axstack setup CLI (installation bookkeeping only)
 
 Usage:
-  axstack install --preset <mixed|codex-only|claude-only> --bundle <dir> --skills-dir <dir> [--tools-dir <dir>] [--instructions <file>] [--claude-settings <file>|--no-claude-settings] [--harness <name>] [--force] [--yes]
+  axstack install --preset <mixed|codex-only|claude-only> --bundle <dir> --skills-dir <dir> [--instructions <file>] [--claude-settings <file>|--no-claude-settings] [--harness <name>] [--force] [--yes]
   axstack check [--bundle <dir>] [--instructions <file>] [--skills-dir <dir>|--harness <name>]
   axstack uninstall --skills-dir <dir> [--instructions <file>] [--claude-settings <file>|--no-claude-settings] [--harness <name>] [--force] [--yes]
   axstack --help | --version
@@ -62,8 +62,6 @@ Flags:
                       Aliases: codex = codex-only; claude = claude-only.
   --skills-dir <dir>  Explicit install target. Overrides harness skill defaults
                       and automatic legacy Codex skill retirement.
-  --tools-dir <dir>   Pinned archify copies. Defaults to ~/.axstack/tools.
-                      Must be outside skills roots and contain no symlink path.
   --instructions <file>
                       Instruction file to receive the owned routing block.
                       Harness defaults: ~/.claude/CLAUDE.md for Claude,
@@ -107,10 +105,11 @@ function parseArgs(argv) {
   }
   out.command = rest.shift();
   const wantsValue = new Set([
-    '--bundle', '--skills-dir', '--tools-dir', '--instructions', '--harness', '--preset', '--claude-settings',
+    '--bundle', '--skills-dir', '--instructions', '--harness', '--preset', '--claude-settings',
   ]);
   while (rest.length > 0) {
     const tok = rest.shift();
+    if (tok === '--tools-dir') throw new Error('--tools-dir is obsolete; archify provisioning has been retired');
     if (tok === '--profile') {
       throw new Error(
         '--profile is obsolete in the T3 Code installer; role data is installed as axstack/roles.json and legacy Paseo cleanup is separate',
@@ -309,7 +308,6 @@ async function main() {
         bundleDir: flags.bundle ? resolve(flags.bundle) : PACKAGE_ROOT,
         skillsDir,
         preset: flags.preset,
-        toolsDir: flags['tools-dir'] ? expandHome(flags['tools-dir']) : undefined,
         instructionsPath,
         inheritedInstructions: legacyCodexManifest?.instructions,
         force: !!flags.force,
@@ -409,18 +407,6 @@ async function main() {
     }
     if (command === 'check') {
       const report = await checkCapabilities(runRealCheck);
-      const toolSkillsDir = flags['skills-dir'] ? expandHome(flags['skills-dir']) :
-        flags.harness ? resolveHarnessTarget(flags.harness) : null;
-      if (toolSkillsDir) {
-        const tool = await checkArchify(toolSkillsDir);
-        console.log(`archify record: ${tool.recordFile}`);
-        if (tool.record) console.log(`archify copy: ${tool.record.path}; recorded SHA: ${tool.record.sha}; checked-out SHA: ${tool.actual ?? 'unavailable'}`);
-        if (tool.reason) {
-          console.log(`archify: ${tool.reason}`);
-          report.gaps.push(`archify: ${tool.reason}`);
-        }
-        console.log(tool.chrome ? `Chrome: ${tool.chrome}` : 'WARN Chrome: unavailable (viewer verification needs Chrome)');
-      }
       if (flags.bundle) {
         const bundle = await validateBundle(resolve(flags.bundle));
         const presetNames = Object.keys(bundle.presets);

package/docs/getting-started.md

@@ -26,7 +26,7 @@ axstack check --harness codex
 ```
 
 Installation writes owned skills and instructions, preserving unrelated content,
-and fetches the pinned archify tool for explicit viewer requests. Reload the
+with the vendored anatomy kit included. Reload the
 harness's skills in T3 after installation. Use the [installation reference](installation.md) for other
 harnesses, source installs or conflicts.
 
@@ -40,13 +40,13 @@ A successful check exits 0. Its four capability rows mean:
 | `t3` | T3's version command succeeds and meets the floor. |
 
 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.
+PRs/chains use Git and `gh pr`. With this harness target, check also reports the
+owned instruction binding. Any reported gap exits 1; follow
+[troubleshooting](installation.md#exit-codes-and-troubleshooting) before starting a task.
 
 Explanations default to checked inline T3 pages above a short reply.
-Use archify only on an explicit viewer request. Spec approval readbacks also
+Use Anatomy only on an explicit isometric or physical-object figure request.
+Every Explain visual receives author and reviewer dispatches. Spec approval readbacks also
 use inline pages, identifying the revision you approve.
 
 Check does not prove live provider readiness, schedule activation or mobile delivery.

package/docs/host-operations.md

@@ -44,9 +44,10 @@ the affected operation. Provider/model routing, Linear documents through the
 executor MCP, and live schedule behavior need separate preflights.
 
 Installation creates no production schedule and never enables a timer.
-Axstack allows one opt-in systemd user timer `axstack-default-sync` as the
-scheduler exception: it runs a stateless script that rewrites only T3
-`defaultModelSelection`, has no workflow state and launches no agent.
+Axstack allows exactly two opt-in systemd user timers as scheduler exceptions:
+`axstack-default-sync` rewrites only T3 `defaultModelSelection`, and
+`axstack-single-server` removes duplicate server processes for one base dir.
+Both run stateless scripts, keep no workflow state and launch no agent.
 Every verified own-PR publication arms or joins the driver's chat-run watch.
 Its bound T3 schedule uses the cadence in [Chat-run watch activation](#chat-run-watch-activation).
 See [Chat-run PR watch](workflows.md#chat-run-pr-watch) for authority, schedule identity and stop conditions.
@@ -204,8 +205,9 @@ retirement. No broad scratch deletion or forced worktree removal applies.
 Manual review and user-driven `axstack-watch` remain outside this schedule.
 Requested peer reviews cover any accessible repository. T3 owns schedules,
 threads, runs, and delegated tasks; Axstack adds no queue engine, cursor files,
-or historical runtime fallback. The only scheduler exception is the opt-in
-systemd user timer described in [New-chat default sync](#new-chat-default-sync).
+or historical runtime fallback. The only scheduler exceptions are the two opt-in
+systemd user timers described in [New-chat default sync](#new-chat-default-sync)
+and [Single T3 server](#single-t3-server).
 
 ## Review automation
 
@@ -282,3 +284,73 @@ Rollback: remove the pool drop-in, reload, and restore the full selection in T3
 The sibling `<settings>.axstack-default-sync.lock` directory prevents overlap
 (unchanged/locked). Empty locks older than sixty seconds are removed and retried
 once; fresh contention reports locked.
+
+## Single T3 server
+
+This opt-in timer checks once per minute for this user's `t3 serve` processes
+with the selected base dir (target default `$HOME/.t3`). Each server's base dir
+comes from its `--base-dir <dir>` or `--base-dir=<dir>` flag, then its own
+`T3CODE_HOME`, then its own `$HOME/.t3`, reading the latter values from that
+process's environment. An unreadable or missing environment without an explicit
+flag, or missing base-dir values, makes the whole run hold and kill nothing.
+It keeps the pid recorded in `<base>/userdata/server-runtime.json`.
+With zero or one known matching server it does nothing; with duplicates but no
+valid readable keeper it holds. Duplicate servers must have started strictly
+before the keeper, comparing field 22 (`starttime`) of `/proc/<pid>/stat`.
+An unknown start time or any duplicate started at or after the keeper holds
+the whole run, preserving a possible starting replacement. The script also
+holds if its own pid or an ancestor appears in the planned victim set.
+Otherwise it snapshots descendants before killing each duplicate server first,
+then its children with SIGKILL. The keeper and its descendants are protected.
+It starts no server, reads no database and interrupts no runs automatically.
+
+Preview the one-line JSON decision without killing or notifying:
+
+```sh
+bun ~/.agents/skills/axstack/scripts/single-server.js --dry-run
+```
+
+`--base-dir <dir>` selects a different base dir; `--proc-root <dir>` supplies
+a process-tree fixture (default `/proc`). `--help` lists the flags. Decisions
+are `unchanged`, `hold`, `would-kill` or `killed`, with reason, keeper, matching
+server pids and killed pids (proposed victims in dry-run). Non-ESRCH kill failures
+add their pids to `failed`; remaining kills continue, successful kills still
+notify if configured, and the command exits 1. Exit 0 includes holds;
+exit 1 reports invalid input, discovery, kill or notification failure.
+
+Under host-mutation authority, copy both assets and enable the timer:
+
+```sh
+mkdir -p ~/.config/systemd/user
+cp ~/.agents/skills/axstack/systemd/axstack-single-server.service ~/.config/systemd/user/axstack-single-server.service
+cp ~/.agents/skills/axstack/systemd/axstack-single-server.timer ~/.config/systemd/user/axstack-single-server.timer
+systemctl --user daemon-reload
+systemctl --user enable --now axstack-single-server.timer
+systemctl --user list-timers axstack-single-server.timer
+journalctl --user -u axstack-single-server.service
+```
+
+Installation only copies assets; it never enables either timer. The single-server
+timer starts one minute after user-manager startup and repeats every minute.
+Override Bun/skills paths or add `--base-dir` through the service's `ExecStart`
+drop-in, clearing the existing `ExecStart` first.
+
+To notify only after a kill, use `systemctl --user edit axstack-single-server.service`
+and add a per-host command, then reload:
+
+```ini
+[Service]
+Environment="AXSTACK_SINGLE_SERVER_NOTIFY=hermes send --to telegram --quiet"
+```
+
+The VPS has Hermes locally; other hosts can use
+`Environment="AXSTACK_SINGLE_SERVER_NOTIFY=ssh '<relay-host>' hermes send --to telegram --quiet"`.
+Replace `<relay-host>` with the authorized gateway's hostname.
+The script runs the command via `sh -c`, sending a short message on stdin with
+hostname, kept pid and killed pids. It notes that runs started by the killed
+server may remain `running` and need `t3_thread_interrupt`. Notification failure
+exits 1 after the kills; command output is suppressed. Dry-run, unchanged and
+hold decisions never notify. Verify delivery under the host's notification authority.
+
+Disable with `systemctl --user disable --now axstack-single-server.timer` and
+stop any active one-shot with `systemctl --user stop axstack-single-server.service`.

package/docs/installation.md

@@ -11,9 +11,8 @@ 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
-`node:fs` and `node:fs/promises`. The pinned archify tool is the sole external-tool
-exception: installation uses Git and the network, and Bun runs its Node-oriented
-code. This exception introduces no Node.js runtime requirement.
+`node:fs` and `node:fs/promises`. Vendored anatomy code runs with Bun;
+installation has no tool network or Git step and adds no Node.js runtime requirement.
 
 For project setup, remote access, provider runtimes, and relay validation, see
 [Host operations](host-operations.md).
@@ -76,16 +75,11 @@ the settings sidecar preserves the value while any other install still owns it.
 - `--yes` confirms writes under the user's home directory. Tests use temporary
   homes and fixtures only.
 
-Explanations default to inline T3 pages; use archify only on an explicit viewer request.
-Installation sparse-clones archify at the reviewed full SHA in `src/archify-pin.js`
-into `<tools-dir>/archify-<sha>`. It verifies HEAD before use and keeps the
-payload's licence and third-party notices. The manifest owns
-`<skills-dir>/axstack-diagram/archify.json`, which records `{path, sha}`.
-The adjacent `<tools-dir>/archify-<sha>.owners.json` lists its skills-root owners.
-Multiple roots share one copy. Repeat installs leave unchanged files untouched.
-An offline, Git-less, or failed clone still installs the skills, reports
-`archify: unavailable (<reason>)`, and exits 0. An existing SHA mismatch fails.
-`AXSTACK_ARCHIFY_REPO` is a test-only repository override; fixtures use a local repository without network access.
+Explanations default to inline T3 pages. Use Anatomy only on an explicit
+isometric or physical-object figure request. Every visual is authored and
+independently reviewed through the selected preset's explanation roles.
+Repeat installs leave unchanged files untouched. Legacy tool copies are
+released by ownership on upgrade and uninstall; retained copies report why.
 
 See [Account selection environment](concepts.md#account-selection-environment)
 for the picker cache directory and test-only usage endpoint variables.
@@ -96,10 +90,13 @@ Run these with Bun from the installed `<skills-dir>/axstack/scripts/` directory:
 `resolve-models.js` (model IDs), `pick-instance.js` (dispatch account),
 `pr-digest.js` (PR discovery), `archive-evidence.js` (evidence archive), and
 `sync-default.js [--settings <path>] [--dry-run]` (New-chat default; `AXSTACK_SYNC_POOL` opts into cross-driver rotation).
+`single-server.js [--base-dir <dir>] [--proc-root <dir>] [--dry-run]` removes
+duplicate `t3 serve` process trees while keeping the recorded runtime pid.
 `account-usage.js` shares usage retrieval and the five-minute cache between
 picker and sync. The opt-in systemd user unit files ship in `axstack/systemd/`;
-installation copies them as assets and never enables the timer.
-See [Host operations](host-operations.md#new-chat-default-sync) for activation.
+installation copies them as assets and never enables either timer.
+See [New-chat default sync](host-operations.md#new-chat-default-sync) and
+[Single T3 server](host-operations.md#single-t3-server) for activation.
 
 ## Role presets
 
@@ -142,13 +139,6 @@ owned, missing, unowned, edited, or bound to a different path. Hand-written
 legacy routing outside the owned block is reported for manual migration and
 preserved byte for byte.
 
-With `--skills-dir` or `--harness`, check reports the archify record path, copy
-path, recorded SHA, and checked-out SHA. A missing record, missing copy, or SHA
-mismatch fails the check. Chrome absence prints a warning and does not fail it.
-`ARCHIFY_CHROME` selects the Chrome executable. Without it, check looks for
-common Chrome and Chromium executables on PATH. A check without a skills target
-probes host capabilities only.
-
 Check does not prove MCP readiness, provider/model availability, schedule
 activation, or mobile delivery. Effective permission, skill reload, task
 execution, and end-to-end compatibility also require their own runtime receipts.
@@ -164,14 +154,10 @@ bytes match the manifest. Uninstall with `--force` can remove edited owned files
 Custom, unknown, and unrelated files survive. Directories
 are pruned only when empty, and the target root is never removed.
 
-Uninstall drops that skills root from archify's owners file. It removes the copy
-only when no owners remain, HEAD matches the recorded SHA, and
-`git status --porcelain --ignored` is empty. Otherwise it keeps the copy and
-reports why, even with `--force`. A pin bump or a changed `--tools-dir` releases
-the old copy through the same guard. Installation clones into a temporary sibling
-and renames it into place. A later owner or manifest write failure restores
-ownership and removes only a copy created by that installation. Older manifests
-without an archify record still load.
+Legacy tool release drops only this skills root's ownership. It removes an
+unchanged real copy only at its recorded SHA with no other owners and no
+tracked, untracked or ignored edits. Otherwise it reports why the copy stays.
+Edited or unowned legacy records stay intact; failed manifest writes restore owners.
 
 ## Environment variables
 
@@ -181,8 +167,6 @@ without an archify record still load.
   and the legacy skills manifest; it does not change the shared skill default.
 - `CLAUDE_CONFIG_DIR` selects the directory containing `settings.json` for
   Claude settings management; `--claude-settings` overrides that file.
-- `ARCHIFY_CHROME` selects the Chrome executable used by the archify check.
-- `AXSTACK_ARCHIFY_REPO` is a test-only repository override for archify fixtures.
 
 ## Exit codes and troubleshooting
 
@@ -191,13 +175,12 @@ For every command (install, check, uninstall, help and version), Bun below
 1.3.14 exits 1 before argument parsing or any capability report.
 
 - Install exits 1 for argument or validation errors: an unknown command or flag,
-  missing flag value, obsolete `--profile`, conflicting Claude settings flags,
+  missing flag value, obsolete `--profile` or `--tools-dir`, conflicting Claude settings flags,
   Bun below the floor, missing or invalid preset, unresolved skills target,
-  unavailable default tools path, malformed bundle or manifest, unsafe path or
-  symlink, overlapping skills/tools roots, or a refused home write without `--yes`.
+  malformed bundle or manifest, unsafe path or
+  symlink, overlapping roots, or a refused home write without `--yes`.
 - Install exits 1 for ownership or transaction failures: an unknown destination
-  without `--force`, conflicting instruction-path binding, edited or unowned
-  archify record, existing archify SHA mismatch, Claude settings/sidecar conflict,
+  without `--force`, conflicting instruction-path binding, Claude settings/sidecar conflict,
   concurrent edit, filesystem failure, or failed recovery.
 - Install exits 1 for an instruction conflict that was preserved. Resolve the
   reported block conflict manually before retrying.
@@ -206,19 +189,18 @@ For every command (install, check, uninstall, help and version), Bun below
 - Install exits 1 for a legacy retirement failure after a canonical Codex install;
   that canonical install can already be complete. Preserve the reported assets
   and resolve the retirement error before retrying.
-- Check exits 1 for any reported gap: a failed capability row, invalid archify
-  record/copy/SHA, non-owned instruction binding, or legacy routing outside the
+- Check exits 1 for any reported gap: a failed capability row,
+  non-owned instruction binding, or legacy routing outside the
   owned block. Check exits 1 for argument, bundle-validation, and filesystem errors.
 - Uninstall exits 1 for argument, validation, ownership-binding, home-confirmation,
   or transaction errors; preserved user edits are reported without failing.
 
 Install exits 0 for a clean or idempotent result, preserved edits to ordinary
-owned skills, or unavailable archify caused by an offline host, missing Git, or
-clone failure. Check exits 0 when there are no gaps, and Chrome absence is a warning.
+owned skills. Check exits 0 when there are no gaps.
 Uninstall exits 0 on completion, including preserved user edits and retained
-archify copies. Help and version exit 0 when the Bun floor is met.
+legacy tool copies. Help and version exit 0 when the Bun floor is met.
 
-Start with the reported path and reason. Choose an explicit skills or tools path
+Start with the reported path and reason. Choose an explicit skills path
 when a default cannot resolve. Use `--yes` only for intended home writes, and
 `--force` only after deciding to replace the specific asset. Back up edited files
 before changing ownership. An incomplete rollback reports manual recovery needs;

package/docs/workflows.md

@@ -33,16 +33,17 @@ Direct routes need no spec ceremony:
   questions using independent, read-only seats.
 - `axstack-correct` reports repeated mistakes and proposes stronger checks.
   Only the user invokes it.
+- [axstack-anatomy](../skills/axstack-anatomy/SKILL.md) builds an isometric,
+  physical-object, or anatomy-style figure with the vendored kit and Bun.
 - `axstack-explain` separates implemented, intended, tested, live, and unknown
   behavior. Explanations default to checked inline T3 pages above a short reply.
-  Consequential or complex claims, archify output, or a user request require
-  independent explanation review; interactive pages receive a verifier pass.
-- [axstack-diagram](../skills/axstack-diagram/SKILL.md) selects inline SVG or CSS
-  inside pages and Mermaid for chat fallback, GitHub, and docs.
-  Explain loads it for every diagram. Use
-  [archify](https://github.com/tt-a1i/archify) (MIT) only on an explicit viewer request,
-  authored by `axstack-explainer`, with a pinned tool, a passing finalize receipt,
-  rendered QA, and node-and-edge source review.
+  Every visual is authored by `axstack-explainer` and independently reviewed by
+  `axstack-explainer-review`; interactive pages receive a verifier pass.
+  Whole-work understanding and defense covers high-level flow, decisions,
+  data/state, misbehaviour at trust boundaries and visible failure, with open
+  evidence gaps. Narrow questions stay proportional.
+  Explain owns SVG/CSS in inline pages and Mermaid in chat, GitHub and docs.
+  Use Anatomy only on an explicit isometric or physical-object figure request.
 - `axstack-improve` returns a small ranked set of evidenced improvement
   candidates without editing code. Its test-audit lens marks every declaration
   in one owner boundary R/F/C/D, reports reviewed and eligible counts, and routes
@@ -138,7 +139,9 @@ 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.
+`axstack-explainer-review` uses Sol medium; `axstack-explainer` pins
+`claude-sonnet-5-5` high with class `sonnet`. Both roles cover every Explain
+visual, including chat Mermaid and anatomy figures.
 In `claude-only`, `axstack-auditor` uses the Claude Sonnet class at high effort.
 The new `-sol` auditor, research-code, and explore-execution seats use Sol high
 in `mixed` and `codex-only`; `claude-only` records each as intentionally absent.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.36.0",
+  "version": "0.37.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

@@ -142,7 +142,7 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "notes": "Archify viewer author: authors archify only on an explicit viewer request, with source fidelity. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
+      "notes": "Visual author: authors every visual Explain delivers, including pages, chat Mermaid and anatomy figures, with source fidelity. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
       "modelClass": "sonnet"
     },
     {
@@ -151,7 +151,7 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "notes": "Independent explanation reviewer: reviews consequential or complex claims, archify output, or on request. Checks the exact artifact for text and source fidelity. The rendered pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
+      "notes": "Independent explanation reviewer: always reviews every visual. Reviews consequential or complex driver-written prose or on request. Checks the exact artifact for text and source fidelity. The rendered pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
       "modelClass": "sonnet"
     },
     {
@@ -160,7 +160,7 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "notes": "Read-only UI verifier: uses T3 preview_* tools against the given build, URL, or artifact; captures screenshots, interactions, accessibility, desktop/mobile, and reduced-motion evidence in the dispatch evidence folder; returns a verdict with evidence paths. Performs the inline page interaction pass for every interactive page, bound to the exact bytes and SHA-256. Never edits source. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
+      "notes": "Read-only UI verifier: uses the configured verifier browser tools against the given build, URL, or artifact; captures screenshots, interactions, accessibility, desktop/mobile, and reduced-motion evidence in the dispatch evidence folder; returns a verdict with evidence paths. Performs the inline page interaction pass for every interactive page, bound to the exact bytes and SHA-256. Never edits source. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
       "modelClass": "sonnet"
     },
     {

package/profiles/presets/codex-only.json

@@ -142,7 +142,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "high",
-      "notes": "Archify viewer author: authors archify only on an explicit viewer request, with source fidelity. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
+      "notes": "Visual author: authors every visual Explain delivers, including pages, chat Mermaid and anatomy figures, with source fidelity. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
       "modelClass": "sol"
     },
     {
@@ -151,7 +151,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "xhigh",
-      "notes": "Independent explanation reviewer: reviews consequential or complex claims, archify output, or on request. Checks the exact artifact for text and source fidelity. The rendered pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
+      "notes": "Independent explanation reviewer: always reviews every visual. Reviews consequential or complex driver-written prose or on request. Checks the exact artifact for text and source fidelity. The rendered pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
       "modelClass": "luna"
     },
     {
@@ -160,7 +160,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "medium",
-      "notes": "Read-only UI verifier: uses T3 preview_* tools against the given build, URL, or artifact; captures screenshots, interactions, accessibility, desktop/mobile, and reduced-motion evidence in the dispatch evidence folder; returns a verdict with evidence paths. Performs the inline page interaction pass for every interactive page, bound to the exact bytes and SHA-256. Never edits source. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
+      "notes": "Read-only UI verifier: uses the configured verifier browser tools against the given build, URL, or artifact; captures screenshots, interactions, accessibility, desktop/mobile, and reduced-motion evidence in the dispatch evidence folder; returns a verdict with evidence paths. Performs the inline page interaction pass for every interactive page, bound to the exact bytes and SHA-256. Never edits source. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
       "modelClass": "sol"
     },
     {

package/profiles/presets/mixed.json

@@ -142,8 +142,9 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "notes": "Archify viewer author: authors archify only on an explicit viewer request, with source fidelity. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
-      "modelClass": "sonnet"
+      "notes": "Visual author: authors every visual Explain delivers, including pages, chat Mermaid and anatomy figures, with source fidelity. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
+      "modelClass": "sonnet",
+      "model": "claude-sonnet-5-5"
     },
     {
       "id": "axstack-explainer-review",
@@ -151,7 +152,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "medium",
-      "notes": "Independent Sol medium explanation reviewer: reviews consequential or complex claims, archify output, or on request. Checks the exact artifact for text and source fidelity. The rendered pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
+      "notes": "Independent Sol medium explanation reviewer: always reviews every visual. Reviews consequential or complex driver-written prose or on request. Checks the exact artifact for text and source fidelity. The rendered pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. Resolve the class from saved T3 capabilities at run start; rejection and unavailable settings hold without substitution.",
       "modelClass": "sol"
     },
     {
@@ -160,7 +161,7 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "notes": "Read-only UI verifier: uses T3 preview_* tools against the given build, URL, or artifact; captures screenshots, interactions, accessibility, desktop/mobile, and reduced-motion evidence in the dispatch evidence folder; returns a verdict with evidence paths. Performs the inline page interaction pass for every interactive page, bound to the exact bytes and SHA-256. Never edits source. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
+      "notes": "Read-only UI verifier: uses the configured verifier browser tools against the given build, URL, or artifact; captures screenshots, interactions, accessibility, desktop/mobile, and reduced-motion evidence in the dispatch evidence folder; returns a verdict with evidence paths. Performs the inline page interaction pass for every interactive page, bound to the exact bytes and SHA-256. Never edits source. T3 resolves Claude classes from saved capabilities; a Claude rejection holds.",
       "modelClass": "sonnet"
     },
     {

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

@@ -22,9 +22,11 @@
   `axstack-arena-judge-opus` judges round 1; `axstack-escalation-fable`/`axstack-arena-judge-astra` judge round 2.
   High-stakes/trigger: fresh [contract](contracts.md) session.
   `axstack-auditor` audits; `axstack-checker` reports discrepancies.
-- `axstack-explainer` authors archify only on an explicit viewer request.
-- `axstack-explainer-review` reviews consequential or complex claims, archify
-  output, or on request; `codex/sol` medium in mixed.
+- `axstack-explainer` authors every visual Explain delivers, including pages,
+  chat Mermaid and anatomy figures; mixed pins Sonnet 5.5 high exactly.
+- `axstack-explainer-review` always reviews every visual; `codex/sol` medium in mixed.
+  Consequential or complex driver-written prose keeps its review rule; every
+  whiteboard defense is consequential, in chat too.
 - `axstack-diligence`: read-only [diligence checks](diligence.md) for every PR
   review round and bounded research, spec, ticket, receipt, and release claims.
 - `axstack-ui-verifier`: owns the inline page interaction pass under [UI checks](ui-verification.md)

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

@@ -1,6 +1,6 @@
 # UI verification
 
-Every Playwright, browser, or rendered-UI check outside the three named browser
+Every Playwright, browser, or rendered-UI check outside the two named browser
 exceptions, including a "confirm it in the browser" step, goes through async
 `delegate_task` to `axstack-ui-verifier` from the run's role snapshot. Give it the exact build, URL, or artifact and the private
 dispatch's evidence folder. The verifier is read-only: it never edits source.
@@ -8,30 +8,26 @@ The PR writer remains the sole writer.
 
 Before using a PR preview URL, the UI verifier must read [PR previews](preview.md).
 
-The first named browser exception is archify `finalize` as a headless build gate.
-Keep finalize outputs only in the private evidence folder.
-Never replace the verifier's rendered pass with finalize.
-
-The second named browser exception is the driver's two `html_preview`
+The first named browser exception is the driver's two `html_preview`
 runs at 728px dark and 360px light.
 Never replace the verifier's interaction pass with `html_preview`.
 Follow [Inline pages](../../axstack-explain/references/inline-pages.md) for the page checks.
 
-The third named browser exception permits dispatched roles to use
+The second named browser exception permits dispatched roles to use
 `html_preview` as a non-publishing self-check.
 Dispatched-role self-checks never replace the driver's two previews or the `axstack-ui-verifier` pass.
 Dispatched roles never call `html_render`.
-All other browser checks outside the three named exceptions remain delegated to `axstack-ui-verifier`.
+All other browser checks outside the two named exceptions remain delegated to `axstack-ui-verifier`.
 
 Read the [T3 runtime boundary](t3-runtime.md) before dispatch; for candidate
 checks use its driver-made disposable detached checkout at the pinned candidate SHA.
-The verifier uses T3 `preview_*` tools for rendered checks.
+Use the configured verifier browser and honor the user browser-tool policy.
 Candidate browser and visual checks must run in the delegated `axstack-ui-verifier` in its own detached checkout; outputs go to its private evidence folder, never the driver worktree.
 
 For every interactive page, require a real-browser `axstack-ui-verifier` interaction pass.
 Give the evidence path and SHA-256 of the exact bytes in the verifier brief.
 The verifier serves the exact bytes on loopback.
-The verifier opens the page with `preview_open` using `open:false`.
+The verifier opens the loopback page in its configured browser.
 The verifier checks clicks, keyboard, focus order, screen-reader names, expanded states, and reduced motion.
 Require that `performance.getEntriesByType('resource')` is empty.
 The detached-checkout rule does not apply to a page without a candidate.