axstack 0.34.3 → 0.34.4

package/docs/getting-started.md

@@ -1,5 +1,7 @@
 # Getting started
 
+Linux is the only supported host OS.
+
 Install Axstack, check your host, then ask for one bounded task in T3 Code.
 For the mental model, read [concepts](concepts.md); for other journeys, use
 [guides](guides.md).
@@ -24,8 +26,8 @@ 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 harness's skills in T3 after
-installation. Use the [installation reference](installation.md) for other
+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:

package/docs/host-operations.md

@@ -134,10 +134,9 @@ messages under the accepted fleet risk.
 
 ## Chat-run watch activation
 
-A bound T3 schedule resumes the driver thread on a 30-minute fallback while
-native PR watches are armed and work and release are settled.
-Unsettled work or release, unavailable or unarmed native watches for any open
-member, or failed re-arming restore five minutes. Human-only waits use 60 minutes
+A bound T3 schedule wakes the driver thread on a normal 30-minute cadence.
+Unavailable or unarmed native watches for any open member, failed re-arming,
+or a resumed question run restore five minutes. Human-only waits use 60 minutes
 under [Chat-run watch runtime](../skills/axstack-watch/references/watch-runtime.md#chat-run-watch).
 A T3 "stopped watching" notice triggers a PR re-check and native re-arm in that same turn.
 The run record holds the schedule ID and driver thread.

package/docs/installation.md

@@ -1,5 +1,7 @@
 # Installation
 
+Linux is the only supported host OS.
+
 Axstack's Bun CLI installs owned chat skills plus one selected role snapshot and
 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

package/docs/workflows.md

@@ -151,8 +151,7 @@ later installation changes without re-resolution.
 
 Peer roles use the stable IDs `axstack-reviewer-primary` and
 `axstack-reviewer-peer`; their provider/class mappings come only from the
-selected preset. The mixed cross-provider peer pair is Sol high followed by
-Opus medium. The mixed peer coordinator and review-lane binding
+selected preset and the ordered reviewer table above. The mixed peer coordinator and review-lane binding
 `axstack-owner` uses Sol high and never reviews. `axstack-reviewer-secondary`
 is used in the authored mapping and, alongside `axstack-reviewer-primary`,
 in codebase findings mode.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.34.3",
+  "version": "0.34.4",
   "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/skills/axstack/references/autopilot.md

@@ -89,7 +89,7 @@ Never require a manual `axstack-watch` invocation.
 The driver remains the single owner and sole run-record writer.
 Never create a per-PR session or an ownership hand-off.
 Read the [T3 runtime boundary](t3-runtime.md) and use its bound
-`schedule_task` wake (`everyMs:300000`), recording the scheduledTaskId.
+`schedule_task` wake (`everyMs:1800000`), recording the scheduledTaskId.
 Follow [Native PR links and watches](t3-runtime.md#native-pr-links-and-watches)
 alongside that bound schedule.
 Apply [Chat-run watch runtime](../../axstack-watch/references/watch-runtime.md#chat-run-watch)

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

@@ -136,7 +136,8 @@ Record the reason for each driver-elected repair in `Decisions`.
 
 Record concise IDs, SHAs, URLs, status, timestamps, next actions, and evidence
 references. Private records include the checkout, evidence and worktree paths
-that the schema requires. Include no tokens, transcripts, full worker output,
+that the schema requires. Include no other machine-specific paths in private records.
+Include no tokens, transcripts, full worker output,
 credentials or private prompts. Publication of a sanitized summary needs separate
 authority.
 

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

@@ -238,15 +238,24 @@ the failed attempt's branch is kept until salvage. Unknown liveness holds
 replacement; reconcile the old writer before admitting another.
 
 With an unsettled launched thread, the driver turn must end only while a bound
-`schedule_task` with `bindToCurrentThread:true`, `everyMs:300000` is armed and
-its ID recorded. Each wake must reconcile all unsettled runs, including a
+`schedule_task` with `bindToCurrentThread:true` is armed at the default
+`everyMs:1800000` or for its 5-minute recovery cases in
+[Chat-run watch runtime](../../axstack-watch/references/watch-runtime.md#chat-run-watch),
+with its ID recorded. Each wake must reconcile all unsettled runs, including a
 writer that died without sending; failed runs hold incomplete work. The watch
 inherits the driver model/workspace and adds no runtime of Axstack's own.
 T3 queues a scheduled wake even while the driver is busy, so copies pile up.
-At the start of each run-watch wake, the driver must cancel every other queued
-copy of its own run-watch prompt with `t3_queue_list` and `t3_queue_cancel`,
-keeping every other queued message, including user and worker messages.
+After a provider error, server restart or Stop, T3 holds the queue: held
+messages do not start, and later queued messages are held too.
+At the start of each run-watch wake, the driver lists every queued message with
+`t3_queue_list` and treats it as stranded.
+The driver must cancel every queued copy of its own run-watch prompt.
 One wake reconciles all those copies.
+For each stranded worker receipt or PR-watch update, the driver must read it
+with `t3_queue_read`, act on it in that wake, then cancel it with `t3_queue_cancel`.
+A queued user message is a pending local action, so the driver must keep every
+queued user message and report it in its reply even on an otherwise unchanged
+wake, because only the user resumes a held queue.
 
 Once nothing remains unsettled the driver must `delete_scheduled_task` for the
 run watch and use `list_scheduled_tasks` to read back its absence; an uncertain
@@ -291,10 +300,10 @@ If re-arming fails, restore the bound 5-minute schedule.
 When the run waits only on a user decision or a human-only step, including a
 user merge, with no unsettled worker and no PR needing watch events, change
 the run watch cadence to 60 minutes at once.
-When work restarts, restore the normal 5-minute cadence.
+When work restarts, restore the normal 30-minute cadence.
 Keep native PR watches.
 For chat-run cadence changes, follow [Chat-run watch runtime](../../axstack-watch/references/watch-runtime.md#chat-run-watch)
-for 30-minute fallback eligibility, 5-minute recovery, and schedule update read-back.
+for the normal 30-minute cadence, 5-minute recovery, and schedule update read-back.
 The schedule still reconciles author and review tasks, readiness, and release.
 When a PR merges or closes, or its watch is torn down, call `unwatch_pull_request`
 and keep its link.

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

@@ -1,6 +1,6 @@
 # UI verification
 
-Every Playwright, browser, or rendered-UI check outside the three named author
+Every Playwright, browser, or rendered-UI check outside the three 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,21 +8,16 @@ 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 author browser exception is archify `finalize` as a headless build gate.
+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 author browser exception is the driver's two `html_preview`
+The second named browser exception is the driver's two `html_preview`
 runs at 728px dark and 360px light.
-Scan the exact bytes of every page for remote src, srcset, and href on loaded
-resources, `@import`, `url()`, `fetch`, XHR, WebSocket, EventSource, and meta refresh.
-Reject scan matches except local url(#id) references such as SVG markers and gradients.
-Require correct layout, theme, zero console errors, empty `missingImages`,
-height, network, and word count.
 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 author browser exception permits dispatched roles to use
+The third 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`.
@@ -36,8 +31,8 @@ Candidate browser and visual checks must run in the delegated `axstack-ui-verifi
 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.
-Open the page with `preview_open` using `open:false`.
-Check clicks, keyboard, focus order, screen-reader names, expanded states, and reduced motion.
+The verifier opens the page with `preview_open` using `open:false`.
+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.
 
@@ -57,7 +52,8 @@ Keep browser recipes tool-neutral for the verifier.
 
 ## Proof standards
 
-Apply these standards to the verifier's candidate checks and inline-page interaction pass.
+Apply these standards wherever referenced, including the verifier's candidate checks
+and inline-page interaction pass.
 
 Drive the real user path.
 Capture the action, the resulting state and its side effects.

package/skills/axstack-diagram/SKILL.md

@@ -13,7 +13,7 @@ Use archify HTML only on an explicit viewer request.
 The configured `axstack-explainer` authors the viewer; follow [Archify](references/archify.md).
 Use inline SVG or CSS inside inline pages.
 Never use Mermaid in inline pages.
-Use Mermaid for chat fallback, GitHub, and docs.
+Use Mermaid for chat, GitHub, and docs.
 Include `accTitle` and `accDescr` in each Mermaid view.
 Never use theme init in Mermaid.
 Split large Mermaid diagrams into views.
@@ -23,5 +23,6 @@ Explain owns evidence, claim labels, the word cap, dispatch, and delivery.
 Diagram owns format and visual rules.
 Never call explain.
 For direct use, keep fidelity and rendered QA.
+For direct viewer requests, follow [Explain's declared launch path](../axstack-explain/SKILL.md#2-choose-proportional-output).
 
 Ideas: [archify](https://github.com/tt-a1i/archify), [diagram-design](https://github.com/cathrynlavery/diagram-design), [visual-explainer](https://github.com/nicobailon/visual-explainer), [Matt Pocock](https://github.com/mattpocock/skills), and [poteto](https://github.com/poteto/how); guidance uses Axstack's own words.

package/skills/axstack-explain/SKILL.md

@@ -71,11 +71,11 @@ Diagram never calls explain.
    Each card has at most 40 words and cites its source, as defined in
    [Archify](../axstack-diagram/references/archify.md).
    Count node labels, headings, captions, and all non-card text.
-2. Use chat only for an explicit chat request, an answer without a Q2 trigger,
-   or inline-page fallback. Q2 triggers are the conditions in the description.
+2. Use chat only for an explicit chat request, an answer outside the description's conditions,
+   or inline-page fallback.
    Use a compact diagram when useful.
    For chat answers, never dispatch an agent when applying its Mermaid rules inline.
-3. For a Q2 trigger, create an inline page by default.
+3. For the conditions in the description, create an inline page by default.
    Honor an explicitly requested artifact format.
    Use archify only on an explicit viewer request, through the configured
    `axstack-explainer`. The reply adds only what the page omits.

package/skills/axstack-explain/references/inline-pages.md

@@ -48,7 +48,7 @@ Scan for `@import`, `url()`, `fetch`, XHR, WebSocket, EventSource, and meta refr
 Reject scan matches except local `url(#id)` references such as SVG markers and gradients.
 
 Before publishing, run `html_preview` at 728px dark and 360px light.
-The driver's two previews are an author exception to delegated browser checks.
+The driver's two previews are a named browser exception to delegated browser checks.
 Require correct layout, theme, height, network, word count, zero console errors,
 and empty `missingImages`.
 Check every claim against its source.
@@ -59,8 +59,6 @@ For every interactive page, require a real-browser `axstack-ui-verifier` pass
 for clicks, keyboard, and expanded states.
 Give the evidence path and SHA-256 of the exact bytes in the verifier brief.
 Follow [UI verification](../../axstack/references/ui-verification.md) for that pass.
-The pass covers focus order, screen-reader names, reduced motion, and an empty
-`performance.getEntriesByType('resource')` list.
 
 ## Publish or fall back
 

package/skills/axstack-watch/SKILL.md

@@ -78,7 +78,7 @@ load. When the watch needs a new owner or automated observation, first read
 [T3 runtime](../axstack/references/t3-runtime.md). Reconcile before creating
 anything. Task-owned observations use their recorded wakes and expiry.
 `axstack-monitor` stays an optional read-only observer for standalone watch
-that never sends. For own open PRs in chat-run mode, use the 30-minute fallback when eligible under
+that never sends. For own open PRs in chat-run mode, use the normal 30-minute cadence under
 [Chat-run watch runtime](references/watch-runtime.md#chat-run-watch);
 the bound T3 schedule resumes the original driver thread. One read-only PR observation needs
 neither. Start no automation for a read-only check.

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

@@ -34,7 +34,7 @@ after verified readback, subject to the user's explicit publication boundary.
 
 The initiating T3 thread remains the sole driver and `progress.md` writer.
 Initially use the bound run watch from [T3 runtime](../../axstack/references/t3-runtime.md):
-`schedule_task` with `bindToCurrentThread:true`, `everyMs:300000`, a stable
+`schedule_task` with `bindToCurrentThread:true`, `everyMs:1800000`, a stable
 `clientRequestId`, and the authorized watch prompt. Record the schedule ID,
 driver thread, chosen mechanism and native schedule lifetime; the watch inherits the driver binding at creation.
 Follow [Provider bindings](../../axstack/references/t3-runtime.md#preflight-and-binding) before arming the watch and for schedule recreation on self-switch.
@@ -45,20 +45,17 @@ Use `update_scheduled_task` on the recorded schedule ID for cadence changes and
 When the run waits only on a user decision or a human-only step, including a
 user merge, with no unsettled worker and no PR needing watch events, change
 the run watch cadence to 60 minutes at once.
-When work restarts, restore the normal 5-minute cadence.
+When work restarts, restore the normal 30-minute cadence.
 Keep native PR watches.
-Only while every open watched PR has an armed native `watch_pull_request`, all
-launched work is settled, and the release step is settled or inapplicable, use
-the bound chat-run schedule as a 30-minute fallback (`everyMs:1800000`).
-Because delegated tasks deliver native completion wakes, unsettled delegated
-tasks alone keep the 30-minute fallback eligible.
+Because launched writers, delegated tasks and native PR watches deliver their
+own wakes, use the normal 30-minute cadence (`everyMs:1800000`) even while
+launched work or the release step is unsettled.
 A resumed `AXSTACK-QUESTION` child run lacks a native completion wake, so it
 keeps the 5-minute cadence (`everyMs:300000`) until its result is accepted.
 If native `watch_pull_request` is unavailable or unarmed for any open member,
 or re-arming fails, restore the bound chat-run schedule to 5 minutes (`everyMs:300000`).
 On the next event on a watched PR, re-evaluate the wake cadence against the
 fallback conditions in the same turn.
-If launched work or the release step becomes unsettled, restore the 5-minute cadence (`everyMs:300000`).
 Apply these conditions before ending each driver turn, including after initial
 arming or a work restart; the 60-minute human-only wait rule above still applies.
 Read back each schedule update and record its receipt; an uncertain update holds affected work.