axstack 0.42.1 → 0.43.0

package/README.md

@@ -22,8 +22,9 @@ 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`), and T3 Code `0.0.46-nightly.20261003.2610` or newer
-on PATH. The providers selected by your preset must be available inside T3.
+CLI (`gh`), and T3 Code stable `0.1.0` or newer
+on PATH. Nightly and other prerelease builds are unsupported. 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)
 (recommended), [codex-only](profiles/presets/codex-only.json), or

package/docs/getting-started.md

@@ -9,7 +9,10 @@ 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, and
-T3 Code `0.0.46-nightly.20261003.2610` or newer. These executables must be on PATH.
+T3 Code stable `0.1.0` or newer. These executables must be on PATH.
+Nightly and other prerelease builds are unsupported. Install or update T3 from
+its stable channel, ensure the stable `t3` executable is on PATH, and rerun
+`axstack check` if this prerequisite fails. Check does not install or switch T3.
 The providers required by your chosen preset must be available inside T3.
 See [installation](installation.md) for harness paths and
 [host operations](host-operations.md) for provider and project setup.
@@ -37,7 +40,7 @@ A successful check exits 0. Its four capability rows mean:
 | `bun` | The running Bun version meets the floor. |
 | `git` | Git's version command succeeds. |
 | `gh` | The GitHub CLI's version command succeeds. |
-| `t3` | T3's version command succeeds and meets the floor. |
+| `t3` | T3's version command succeeds and reports stable >=0.1.0. |
 
 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 reports the

package/docs/installation.md

@@ -8,7 +8,7 @@ does not dispatch agents, edit T3 settings, run a scheduler, or maintain a
 workflow database.
 
 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
+T3 Code stable `0.1.0` 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`. Vendored anatomy code runs with Bun;
@@ -129,7 +129,12 @@ legacy native-stack operations, which probe `gh stack --help` separately:
 | `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. |
-| `t3` | `t3 --version` succeeds and its output meets the T3 version floor. |
+| `t3` | `t3 --version` succeeds and reports a stable release >=0.1.0; nightly and other prerelease builds fail. |
+
+For an old, nightly, prerelease or malformed T3 version, install or update T3 Code
+from its stable channel, ensure the stable `t3` executable is on PATH, and rerun
+`axstack check`. Check only probes capabilities; it never installs T3 or changes
+its update channel or settings.
 
 `--bundle` additionally validates the bundle and reports its skill-file count
 and preset names; it does not compare every installed skill's bytes.

package/package.json

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

@@ -151,7 +151,7 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "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 browser interaction pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. T3 resolves Claude classes from saved capabilities; a Claude rejection holds. Design review follows design.md for every inline HTML page and every Publish article adaptation. For inline pages the reviewer itself renders exact bytes with html_preview at 728px dark and 360px light as a non-publishing self-check. For Publish the reviewer opens axstack-ui-verifier PNGs at 728px dark and 360px light plus 390px mobile and 1440px desktop, covering all four widths in both themes with paths bound to the artifact SHA-256 and recorded before review. Inspect the 1440px desktop screenshot for balanced composition, intentional horizontal margins, bounded prose measure, typography, section spacing and chart legibility. Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels. Apply Delivery's one design-only repair round within the two-round limit, disclosed cosmetic exception and unknown-render holds. Chat Mermaid and anatomy keep their existing review.",
+      "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 browser interaction pass belongs to axstack-ui-verifier. Any artifact change invalidates its review. T3 resolves Claude classes from saved capabilities; a Claude rejection holds. Design review follows design.md hard rules and FRONTEND-DESIGN.md (calibration defaults, restraint and quality floor) for every inline HTML page and every Publish article adaptation. For inline pages the reviewer itself renders exact bytes with html_preview at 728px dark and 360px light as a non-publishing self-check. For Publish the reviewer opens axstack-ui-verifier PNGs at 728px dark and 360px light plus 390px mobile and 1440px desktop, covering all four widths in both themes with paths bound to the artifact SHA-256 and recorded before review. Inspect the 1440px desktop screenshot for balanced composition, intentional horizontal margins, bounded prose measure, typography, section spacing and chart legibility. Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels. A page failing to look decent is a blocking design finding, repaired by the same author within the two-round visual limit. If only design findings remain after the second round, deliver the visual with each finding named. Never describe a remaining finding as fixed or a clean pass. Apply Delivery's normal holds for other failures and unknown renders. Chat Mermaid and anatomy keep their existing review.",
       "modelClass": "sonnet"
     },
     {

package/profiles/presets/codex-only.json

@@ -151,7 +151,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "xhigh",
-      "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 browser interaction 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. Design review follows design.md for every inline HTML page and every Publish article adaptation. For inline pages the reviewer itself renders exact bytes with html_preview at 728px dark and 360px light as a non-publishing self-check. For Publish the reviewer opens axstack-ui-verifier PNGs at 728px dark and 360px light plus 390px mobile and 1440px desktop, covering all four widths in both themes with paths bound to the artifact SHA-256 and recorded before review. Inspect the 1440px desktop screenshot for balanced composition, intentional horizontal margins, bounded prose measure, typography, section spacing and chart legibility. Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels. Apply Delivery's one design-only repair round within the two-round limit, disclosed cosmetic exception and unknown-render holds. Chat Mermaid and anatomy keep their existing review.",
+      "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 browser interaction 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. Design review follows design.md hard rules and FRONTEND-DESIGN.md (calibration defaults, restraint and quality floor) for every inline HTML page and every Publish article adaptation. For inline pages the reviewer itself renders exact bytes with html_preview at 728px dark and 360px light as a non-publishing self-check. For Publish the reviewer opens axstack-ui-verifier PNGs at 728px dark and 360px light plus 390px mobile and 1440px desktop, covering all four widths in both themes with paths bound to the artifact SHA-256 and recorded before review. Inspect the 1440px desktop screenshot for balanced composition, intentional horizontal margins, bounded prose measure, typography, section spacing and chart legibility. Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels. A page failing to look decent is a blocking design finding, repaired by the same author within the two-round visual limit. If only design findings remain after the second round, deliver the visual with each finding named. Never describe a remaining finding as fixed or a clean pass. Apply Delivery's normal holds for other failures and unknown renders. Chat Mermaid and anatomy keep their existing review.",
       "modelClass": "luna"
     },
     {

package/profiles/presets/mixed.json

@@ -152,7 +152,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "medium",
-      "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 browser interaction 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. Design review follows design.md for every inline HTML page and every Publish article adaptation. For inline pages the reviewer itself renders exact bytes with html_preview at 728px dark and 360px light as a non-publishing self-check. For Publish the reviewer opens axstack-ui-verifier PNGs at 728px dark and 360px light plus 390px mobile and 1440px desktop, covering all four widths in both themes with paths bound to the artifact SHA-256 and recorded before review. Inspect the 1440px desktop screenshot for balanced composition, intentional horizontal margins, bounded prose measure, typography, section spacing and chart legibility. Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels. Apply Delivery's one design-only repair round within the two-round limit, disclosed cosmetic exception and unknown-render holds. Chat Mermaid and anatomy keep their existing review.",
+      "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 browser interaction 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. Design review follows design.md hard rules and FRONTEND-DESIGN.md (calibration defaults, restraint and quality floor) for every inline HTML page and every Publish article adaptation. For inline pages the reviewer itself renders exact bytes with html_preview at 728px dark and 360px light as a non-publishing self-check. For Publish the reviewer opens axstack-ui-verifier PNGs at 728px dark and 360px light plus 390px mobile and 1440px desktop, covering all four widths in both themes with paths bound to the artifact SHA-256 and recorded before review. Inspect the 1440px desktop screenshot for balanced composition, intentional horizontal margins, bounded prose measure, typography, section spacing and chart legibility. Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels. A page failing to look decent is a blocking design finding, repaired by the same author within the two-round visual limit. If only design findings remain after the second round, deliver the visual with each finding named. Never describe a remaining finding as fixed or a clean pass. Apply Delivery's normal holds for other failures and unknown renders. Chat Mermaid and anatomy keep their existing review.",
       "modelClass": "sol"
     },
     {

package/skills/axstack-explain/SKILL.md

@@ -61,7 +61,8 @@ Dispatch every visual Explain delivers to `axstack-explainer` with a bounded
 evidence brief, including inline pages, chat Mermaid and anatomy figures.
 The `axstack-explainer` loads [design.md](references/design.md) and reads
 [FRONTEND-DESIGN.md](references/frontend-design/FRONTEND-DESIGN.md) for every inline HTML page
-and every Publish article adaptation.
+and every Publish article adaptation, using frontend-design as the sole design authority
+subject to design.md's hard rules.
 Never load either reference for chat Mermaid or anatomy figures.
 Explicitly requested standalone HTML files keep their existing review and Visual QA.
 Plain-prose answers stay driver-written; other phases retain their own Mermaid

package/skills/axstack-explain/references/delivery.md

@@ -14,22 +14,18 @@ naming the held page and the reason.
 Whiteboard-defense plain prose still requires `axstack-explainer-review`.
 If a required author or reviewer seat is unavailable, hold the visual and
 answer in plain prose naming the held visual.
-Replace a visual still failing checks after two repair rounds with the same
-author by plain prose with the reason.
-For inline HTML pages and Publish article adaptations, apply [design.md](design.md):
-a named tell is blocking for one design-only repair round with the same author,
-counting within the two-round visual limit.
-Never start a second design-only round.
-A cosmetic tell remaining in fresh exact-byte renders becomes a disclosed
-non-blocking design exception, recorded in evidence and named in delivery.
-Never describe the exception as fixed or a clean design pass.
-This exception never waives source-fidelity, security, asset, theme, layout,
-accessibility, interaction or publication requirements.
-A tell causing any such defect keeps that defect's normal hold and repair rules.
+Except for design-only findings below, replace a visual still failing checks after
+two repair rounds with the same author by plain prose with the reason.
+For inline HTML pages and Publish article adaptations, judge the exact-byte renders
+against [FRONTEND-DESIGN.md](frontend-design/FRONTEND-DESIGN.md), including its calibration defaults,
+restraint and quality floor, plus [design.md](design.md)'s hard rules.
+A page failing to look decent is a blocking design finding, repaired by the same author within the two-round visual limit.
+If only design findings remain after the second round, deliver the visual with each finding named and recorded in evidence.
+Never describe a remaining finding as fixed or a clean pass.
+Hard-rule, fidelity, security, asset, theme, accessibility, layout-defect, interaction
+and publication failures keep their normal holds and repair rules.
 An unavailable, unreadable or stale render leaves design review unknown and holds
 the visual or publication; inline delivery may use the plain-prose fallback above.
-An unknown check is never a tell that expires after one round.
-Overall look is advisory.
 
 The driver never writes a substitute visual.
 Each repair round returns findings to the same author and rechecks the exact final bytes.

package/skills/axstack-explain/references/design.md

@@ -1,37 +1,14 @@
 # Design
 
-Apply precedence in this order: 1) Axstack page rules for the output kind plus this file's subject, colour, motion, font and no-notes rules, 2) source fidelity, 3) named tells, 4) frontend-design for approach and everything else.
-Inline pages favour restraint; published articles may vary boldly within levels 1–3.
-
-Named tells:
-- Eyebrow labels or tiny tracked caps.
-- A single styled accent word.
-- Gradients, glass or resting shadows.
-- Emoji or decorative blobs.
-- Rows of identical cards or bordered boxes.
-- More than two typefaces or five sizes.
-- Body text outside full ink or default left alignment.
-
-Diagram edges and arrows, timeline order, tables and code paths are content, not ornament.
-Anatomy follows its kit.
-A behaviour required by a higher-priority rule is never a tell.
-
-The actual subject and question determine structure.
-Never stop to confirm the subject.
-Inline colour: `--background` is ground, `--foreground` is ink, `--muted-foreground` serves only secondary text, `--ring` is the single accent.
-Published articles may use a small named palette checked in light and dark.
-Motion is static by default; any animation is CSS-only and respects reduced motion.
-Inline pages use only T3 font variables.
-Published articles use system font stacks.
-Never use font files or network requests.
-Never keep design notes or history across pages; frontend-design's note-keeping hint does not apply.
-
-## Standalone Publish layout
-
-Give standalone Publish articles mobile gutters, a bounded prose measure and intentional horizontal margins for balanced desktop composition.
-Centre the reading column or use a deliberate asymmetric layout that balances the whole viewport.
-Set readable body typography and line height, clear heading hierarchy and generous section spacing for standalone articles.
-Size chart labels, values, units and spacing for legibility at mobile and desktop widths in both themes.
-Choose dimensions and rhythm for the article's content; the inline T3 frame supplies its own surrounding space.
-
-Credit: [taste-skill](https://github.com/Leonxlnx/taste-skill/tree/f624f37a) (MIT, `Leonxlnx/taste-skill` at `f624f37a`) and [frontend-design](frontend-design/PROVENANCE.md).
+[FRONTEND-DESIGN.md](frontend-design/FRONTEND-DESIGN.md) is the sole design authority for every visual choice — palette, typography, layout, spacing, structure, motion and self-critique — on every inline HTML page and every Publish article adaptation.
+These hard rules win on conflict.
+
+- Never load network resources or font files. Inline pages use T3 font variables or system font stacks. Published articles use system font stacks.
+- Inline pages follow the live T3 theme: derive every colour from T3 theme variables — ground from `--background`, ink from `--foreground`, all other colours via `color-mix()` with them or T3 semantic/chart variables (`--muted-foreground`, `--accent`, `--success`, `--warning`, `--destructive`, `--info`, `--chart-1`…`--chart-6`). Keep every colour legible in light and dark. `var()` fallbacks are allowed for standalone viewing. Never switch inline palettes on `prefers-color-scheme`; T3's theme leaves that query unchanged. Never redefine T3's own variables in inline pages. Published articles support light and dark via `prefers-color-scheme` outside T3.
+- Keep pages responsive down to 360px with visible keyboard focus, reduced motion respected and sufficient contrast in both themes.
+- Never stop to confirm the subject: the brief and evidence are the subject.
+- Never keep design notes or history across pages. This overrides frontend-design's note hint.
+- Source fidelity beats any design choice: diagram edges, order, tables and code paths show the source.
+- For non-anatomy inline pages only, follow [inline-pages.md](inline-pages.md): its Embed fit and Page rules sections also win on conflict. Anatomy follows its own kit.
+
+Credit: [frontend-design](frontend-design/PROVENANCE.md).

package/skills/axstack-explain/references/frontend-design/PROVENANCE.md

@@ -9,5 +9,4 @@ Commit: `41bbe19d1a1a7eaab5e7bb9050a417e5c6cffc8f`
   Git blob: `f433b1a53f5b830a205fd2df78e2b34974656c7b`.
 
 License: Apache-2.0; the complete upstream licence accompanies this reference.
-This payload is not registered as a skill. Axstack's owned design guidance
-sets precedence and scope in `../design.md`.
+This payload is not registered as a skill. Axstack's hard rules live in `../design.md`.

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

@@ -7,21 +7,25 @@ The driver publishes the page in its own thread.
 
 Use T3 theme variables and follow the live theme.
 Only an explicit user theme request overrides the page theme.
-Use `--background`, `--foreground`, `--muted-foreground`, `--ring`,
-`--font-sans`, and `--font-mono` for their named purposes.
-
-Use fluid width, with zero outer horizontal padding.
-Never use an outer frame, banner, or viewport heights.
-Anatomy may retain its figure card as an inner panel with at least 16px padding
-and `var(--radius)`; its page wrapper still has zero gutters and no background.
-Let content set the page height. Use fixed chart heights.
-Set frame `height` to the larger contentHeight of the two previews, capped at 2000.
+For inline pages other than anatomy, follow [design.md](design.md) for the theme rule and visual design authority.
+Anatomy follows its own kit.
 
 Choose the page shape from its content rather than a fixed template.
 Map stages to a connected diagram, sequence to a timeline, comparison to side
-by side or table, and separate equal items to a list.
-Prefer diagrams and timelines. Avoid grids of bordered boxes.
-Keep borders minimal and use color only where it has meaning.
+by side or table, and separate equal items to a list; frontend-design can refine this content-shape mapping guidance.
+
+## Embed fit
+
+The T3 frame is borderless on the thread background, with its left edge aligned to reply text.
+Use fluid width with zero horizontal padding on the outermost element.
+Never add an outer card, border or banner title.
+A banner title means an outer header block or band; an ordinary page heading is allowed.
+Keep html, body and the outermost element without a background colour.
+Give any inner box with its own background at least 16px padding on every side and `var(--radius)` corners.
+Anatomy may retain its figure card as an inner panel with at least 16px padding and `var(--radius)`; its page wrapper still has zero gutters and no background.
+Never use viewport heights.
+Let content set the page height. Use fixed chart heights.
+Set frame `height` to the larger contentHeight of the two previews, capped at 2000.
 
 ## Page rules
 

package/skills/axstack-explain/references/visual-qa.md

@@ -2,7 +2,7 @@
 
 For inline pages, follow [Inline pages](inline-pages.md) instead of this checklist.
 
-Design review against [design.md](design.md) covers every inline HTML page and every Publish article adaptation.
+Design review against [design.md](design.md) hard rules and [FRONTEND-DESIGN.md](frontend-design/FRONTEND-DESIGN.md) covers every inline HTML page and every Publish article adaptation, including its calibration defaults, restraint and quality floor.
 For inline pages, the reviewer itself renders exact bytes with `html_preview` at
 728px dark and 360px light as a non-publishing self-check.
 This supplements the driver's required previews and any verifier pass.
@@ -14,7 +14,10 @@ bounded prose measure, typography, section spacing and chart legibility.
 Inspect the 360px and 390px mobile screenshots for gutters, readable text and chart labels.
 Check every width and theme for clipping and horizontal scroll, recording defects and observations.
 The driver forwards those paths and SHA-256; changed bytes require fresh screenshots and review.
-Apply [Delivery](delivery.md)'s one-round design repair, disclosed cosmetic exception and unknown-render holds.
+A page failing to look decent is a blocking design finding, repaired by the same author within the two-round visual limit.
+If only design findings remain after the second round, deliver the visual with each finding named.
+Never describe a remaining finding as fixed or a clean pass.
+Follow [Delivery](delivery.md) for other failure holds and unknown-render holds.
 Chat Mermaid, anatomy and explicitly requested standalone HTML files keep their existing review and Visual QA.
 Interaction checks remain with `axstack-ui-verifier`; source-fidelity review is unchanged.
 

package/skills/axstack-publish/SKILL.md

@@ -42,12 +42,10 @@ to remove private paths, IDs, credentials, prompts, messages and internal record
 For public mode, run Explain's [self-contained asset check](../axstack-explain/references/inline-pages.md#check-the-exact-bytes).
 Reuse Explain's [page rules](../axstack-explain/references/inline-pages.md#page-rules)
 and [Visual QA](../axstack-explain/references/visual-qa.md) for checks and verifier routing.
-[Inline zero-padding embed rules](../axstack-explain/references/inline-pages.md#shape-and-theme) apply only to T3 frames.
-Use [design.md](../axstack-explain/references/design.md) for standalone Publish layout.
 
 Send the article adaptation, including art direction and standalone light/dark theme,
 to `axstack-explainer` with a bounded brief.
-The explainer follows Explain's [design guidance](../axstack-explain/references/design.md)
+The explainer loads and follows Explain's [design guidance](../axstack-explain/references/design.md)
 and reads [frontend-design](../axstack-explain/references/frontend-design/FRONTEND-DESIGN.md).
 Require inline defaults and `prefers-color-scheme` so the article works outside T3;
 honor an explicit user theme request.
@@ -59,13 +57,19 @@ covering all four widths in both themes, and record screenshots with paths,
 their artifact SHA-256 and the Explain QA results.
 Require a fresh independent `axstack-explainer-review` on the final bytes.
 The driver forwards the verifier PNG paths and bound artifact SHA-256 for the
-reviewer's design review against design.md, alongside source-fidelity review.
-Apply Explain's [Delivery](../axstack-explain/references/delivery.md) one-round design repair
-and disclosed cosmetic exception; that exception leaves all other requirements binding.
+reviewer's design review against FRONTEND-DESIGN.md (calibration defaults, restraint
+and quality floor) plus design.md's hard rules, alongside source-fidelity review.
+A page failing to look decent is a blocking design finding, repaired by the same author within the two-round visual limit.
+If only design findings remain after the second round, deliver the visual with each finding named and recorded in evidence.
+Never describe a remaining finding as fixed or a clean pass.
+Follow Explain's [Delivery](../axstack-explain/references/delivery.md) for normal holds
+on hard-rule, fidelity, security, asset, theme, accessibility, layout-defect,
+interaction and publication failures.
 Any subsequent byte change invalidates checks and review: repeat this step.
-Hold publication while any required check or review is missing or failed.
-Unavailable, unreadable or stale renders leave design review unknown and hold publication;
-unknown is never passed or a cosmetic exception.
+Hold publication while any required check or review is missing or failed, except for
+the design-only delivery after the second round above.
+Unavailable, unreadable or stale renders leave design review unknown and hold publication.
+Never treat unknown design review as a pass.
 
 ## 3. Publish from the driver
 

package/src/capabilities.js

@@ -1,6 +1,6 @@
 // Host capability checks. Injected execution keeps tests off live runtimes.
 export const BUN_FLOOR = '1.3.14';
-export const T3_FLOOR = '0.0.46-nightly.20261003.2610';
+export const T3_FLOOR = '0.1.0';
 
 export const PROBE_LIMITATIONS = [
   'T3 orchestration MCP readiness, provider auth, models and effort are verified by driver preflight inside a T3 thread, never from the binary probe.',
@@ -13,7 +13,7 @@ const CHECK_LABELS = {
   bun: 'bun >= 1.3.14 runtime',
   git: 'git CLI',
   gh: 'gh CLI',
-  't3-binary': `T3 Code CLI >= ${T3_FLOOR}`,
+  't3-binary': `T3 Code CLI stable >= ${T3_FLOOR}`,
 };
 
 // Ordinary PRs need Git and gh; legacy native-stack operations probe separately.
@@ -24,22 +24,13 @@ export const PROBE_COMMANDS = {
 };
 
 function validT3Version(stdout) {
-  const match = /^(?:t3\s+)?v?(\d+\.\d+\.\d+)(?:-nightly\.(\d{8})(?:\.(\d+))?)?$/.exec(stdout.trim());
-  const [floorVersion, floorNightly] = T3_FLOOR.split('-nightly.');
-  const [floorDate, floorBuild] = floorNightly.split('.');
-  if (!match || !meetsFloor(match[1], floorVersion)) return false;
-  if (!match[2]) return true;
-  const date = match[2];
-  const iso = `${date.slice(0, 4)}-${date.slice(4, 6)}-${date.slice(6, 8)}`;
-  const parsed = new Date(`${iso}T00:00:00Z`);
-  return Number.isFinite(parsed.getTime()) && parsed.toISOString().slice(0, 10) === iso
-    && (match[1] !== floorVersion || date > floorDate || (date === floorDate && match[3] !== undefined
-      && Number(match[3]) >= Number(floorBuild)));
+  const match = /^(?:t3\s+)?v?((?:0|[1-9]\d*)\.(?:0|[1-9]\d*)\.(?:0|[1-9]\d*))$/.exec(stdout.trim());
+  return !!match && meetsFloor(match[1], T3_FLOOR);
 }
 
 function validateT3Result(result) {
   if (!result?.ok || validT3Version(String(result.stdout ?? ''))) return result;
-  return { ok: false, stdout: `requires T3 >= ${T3_FLOOR}; got ${String(result.stdout ?? '').trim() || 'malformed version'}` };
+  return { ok: false, stdout: `Install T3 Code stable >= ${T3_FLOOR} on PATH; rerun axstack check. Got: ${String(result.stdout ?? '').trim() || 'malformed version'}` };
 }
 
 // Pure semver-floor comparison over numeric prefix segments ("1.3.14" style;