axstack 0.40.1 → 0.41.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.40.1",
+  "version": "0.41.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": "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.",
+      "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. Also authors Publish article adaptations.",
       "modelClass": "sonnet"
     },
     {
@@ -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 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 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 bound to the artifact SHA-256 and recorded before review. 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.",
       "modelClass": "sonnet"
     },
     {

package/profiles/presets/codex-only.json

@@ -142,7 +142,7 @@
       "provider": "codex",
       "modeId": "full-access",
       "thinkingOptionId": "high",
-      "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.",
+      "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. Also authors Publish article adaptations.",
       "modelClass": "sol"
     },
     {
@@ -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 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 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 bound to the artifact SHA-256 and recorded before review. 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.",
       "modelClass": "luna"
     },
     {

package/profiles/presets/mixed.json

@@ -142,7 +142,7 @@
       "provider": "claude",
       "modeId": "bypassPermissions",
       "thinkingOptionId": "high",
-      "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.",
+      "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. Also authors Publish article adaptations.",
       "modelClass": "sonnet",
       "model": "claude-sonnet-5-5"
     },
@@ -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 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 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 bound to the artifact SHA-256 and recorded before review. 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.",
       "modelClass": "sol"
     },
     {

package/skills/axstack/references/lifecycle.md

@@ -151,7 +151,7 @@ nothing without tested independent review.
 
 Close-out requires the [close-out acceptance table](run-record.md#close-out-acceptance).
 
-PRs merge by forge state; close out: (1) settle every T3 worker run and archive eligible threads; (2) compact record with counts and denominators—user
+PRs merge by forge state; close out: (1) settle every T3 worker run and archive eligible threads. Settle each worker thread with `t3_thread_organize` and read back `settled: true`, because a finished task does not count; (2) compact record with counts and denominators—user
 interventions/deviations from plan/repairs; (3) `axstack-auditor`: settle
 non-zero/requested, else `counts zero`. A base auditor preflight rejection
 (no delegated task started) records `auditor: UNKNOWN (unlaunchable)` with the

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

@@ -125,9 +125,15 @@ If neither passing evidence nor a `Decisions` row with a user-accepted hold exis
 A recorded user-accepted hold in `Decisions` satisfies that clause for close-out; keep the unmet result explicit.
 Record the reason for each driver-elected repair in `Decisions`.
 
+The mandatory settlement row covers every run-owned delegated child and launched writer and can pass only with current, thread-bound `t3_thread_read` evidence showing `settled: true`.
+Task completion or `result_available` alone does not pass.
+A missing or failed read-back is a hold. A plain recorded reason does not satisfy the row.
+Close-out stays pending unless each unsettled exception has a user-accepted hold linked to its `Decisions` row.
+
 ```markdown
 | Acceptance check | Result | Evidence or user-accepted hold | Repair election (Decisions row + reason, or none) |
 | --- | --- | --- | --- |
+| Every run-owned delegated child and launched writer settled | passed | <current thread-bound t3_thread_read inventory ref: settled: true for each> | <Decisions row + reason, or none> |
 | <check + clause> | passed | <SHA + check/log pointer> | <Decisions row + reason, or none> |
 | <check + unmet clause> | held (user accepted) | <Decisions row + user acceptance receipt> | <Decisions row + reason, or none> |
 ```
@@ -205,9 +211,9 @@ Resume: <commands or evidence refs bound to exact revisions>
 | --- | --- | --- | --- | --- | --- |
 | <task> | <task IDs or none> | <role + session ID + worktree, or receipt ref> | <pending/in progress/complete/blocked> | <SHA + check/receipt refs> | <action + owner> |
 
-| Dispatch key | Provider/model echo | Configuration read-back | Completion receipt | Post-completion HEAD/porcelain check result |
-| --- | --- | --- | --- | --- |
-| <key> | <actual provider/model + evidence ref> | <options/runtimeMode + evidence ref> | <marker + IDs + evidence ref> | <compared HEAD/status + pass/hold + evidence ref> |
+| Dispatch key | Provider/model echo | Configuration read-back | Completion receipt | Post-completion HEAD/porcelain check result | Settle readback |
+| --- | --- | --- | --- | --- | --- |
+| <key> | <actual provider/model + evidence ref> | <options/runtimeMode + evidence ref> | <marker + IDs + evidence ref> | <compared HEAD/status + pass/hold + evidence ref> | settled: true (t3_thread_read <UTC>) or held: <reason> |
 
 Status: <active/paused/held/complete/Archived>
 Updated: <UTC timestamp>

package/skills/axstack/references/workspace-hygiene.md

@@ -37,6 +37,12 @@ These metadata actions do not remove worktrees. Accept matching delegated task
 or launched run completion under the runtime contract before settlement.
 After the driver accepts a launched writer's (author or repair) or delegated task's completion from terminal run evidence plus a verified receipt or candidate check, in the same driver turn it settles the matching thread with `t3_thread_organize` using `action: settle` as metadata only.
 The driver reads back `settled: true` with `t3_thread_read` on the writer thread for launched writers and on the `childThreadId` for delegated tasks.
+This extends the existing same-turn settle rule: a pinned run-owned child is still settled.
+T3's settle clears the pin, including one inherited from the parent at creation. There is no separate unpin step.
+Native T3 tools do not show pins, so the read-back stays `settled: true`.
+If the user asked to keep a child pinned, hold its settlement with that reason.
+A T3 refusal such as `parent_not_active` (the calling driver's own run is not live) puts `held: <error>` in the [run-record `Settle readback` column](run-record.md#compact-template). Never reactivate a parent.
+For close-out holds, follow the [run-record acceptance rules](run-record.md#close-out-acceptance).
 A missing or failed settle readback never triggers author repair: it holds only that dispatch's next advancement (publication, review routing, merge-ready) until resolved.
 Settling never removes, archives or abandons the thread or worktree.
 Retain the author worktree and thread unarchived until the PR merges or closes, with repairs returning to the same author.

package/skills/axstack-brainstorm/references/arena.md

@@ -37,6 +37,7 @@ hard-to-reverse choices; they replace the critique round for that question.
    average.
 6. **Present.** Return the synthesized design to the caller with its
    trade-off, judge verdicts per round, and what was grafted or rejected.
+   For candidate and judge threads, follow the [same-turn settle rule](../../axstack/references/workspace-hygiene.md#settlement).
    The user still decides; spec approval remains the one human checkpoint.
 
 Record the synthesis note (base, graft sources, rejections, dropouts, judge

package/skills/axstack-explain/SKILL.md

@@ -59,6 +59,11 @@ Follow [Fidelity](references/fidelity.md) for every visual.
 For whole-work understanding or defense, follow [Whiteboard defense](references/whiteboard-defense.md).
 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.
+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
 owners, and README/docs diagram edits go through Implement under these rules.
 Use inline SVG or CSS inside inline pages. Never use Mermaid in inline pages.
@@ -100,6 +105,8 @@ through [Anatomy](../axstack-anatomy/SKILL.md).
    claims or on request.
    The `axstack-explainer-review` always reviews every visual at its exact final
    bytes before delivery.
+   For inline HTML pages and Publish article adaptations, include the
+   [design review](references/visual-qa.md) and [Delivery](references/delivery.md) rules.
    Consequential claims include gap or missing-claim reports, blast-radius
    safety facts, spec readbacks, and every whiteboard-defense explanation in chat too.
    Bind it to the exact artifact identity.
@@ -119,3 +126,5 @@ through [Anatomy](../axstack-anatomy/SKILL.md).
    only when the user requests it.
 
 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.
+
+Vendored reference: [frontend-design](references/frontend-design/PROVENANCE.md), Apache-2.0.

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

@@ -16,6 +16,21 @@ 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.
+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.
 An anatomy page above the size cap follows [Anatomy](../../axstack-anatomy/SKILL.md)

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

@@ -0,0 +1,29 @@
+# Design
+
+Apply precedence in this order: 1) Axstack page rules 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.
+
+Credit: [taste-skill](https://github.com/Leonxlnx/taste-skill/tree/f624f37a) (MIT, `Leonxlnx/taste-skill` at `f624f37a`) and [frontend-design](frontend-design/PROVENANCE.md).

package/skills/axstack-explain/references/frontend-design/FRONTEND-DESIGN.md

@@ -0,0 +1,71 @@
+---
+name: frontend-design
+description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
+license: Complete terms in LICENSE.txt
+---
+
+# Frontend Design
+
+Approach this as the design lead at a design studio known for giving every client a distinct visual identity that is not mistaken for anyone else's. This client has already rejected proposals that felt cliché or templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take aesthetic risk if justified.
+
+## Ground your designs in the subject matter
+
+If the brief does not identify what the product or subject matter is, identify it yourself before designing, and confirm with the client. You can come up with one concrete subject, the design's audience, and the design's primary job, as a proposal. If there's any information in your memory about the client's preferences or context about what they're building, use that as a hint. The subject's industry, subject matter, materials, and vernacular are where distinctive visual choices come from — a design for a toy for girls aged 8–11 will be very aesthetically different from a dashboard for financial analysts. Build with the brief's real content and subject matter throughout.
+
+## Design principles
+
+For web designs, the hero is the first thing viewers will see. Open with the most characteristic thing in the subject's world, in the form that is most appropriate: a headline, an image, an animation, a live demo, an interactive moment, or other treatments. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the default treatment, so only use it if that's truly the best option.
+
+Typography carries the personality of the page. You don't need a different typeface for display or headline text and body content: use one family or two, and if two, make them clearly distinct.
+
+Choose your typefaces deliberately, not the default families you would reach for on any other project, and set a clear type scale following the default guidance of The Elements of Typographic Style with intentional weights, widths, and spacing. When type is used as a headline or visual element, use the type treatment itself as an active part of the design, not a neutral delivery vehicle for the content.
+
+Default to line lengths of less than 80 characters. Serif typefaces can have slightly longer line lengths; give serif body text slightly more line-height than a sans-serif.
+
+Avoid these default typographic treatments; they are the commonest tells of a generated page:
+- Accenting just a single word or phrase in a headline, like putting one word in italic/bold or a different color.
+- Using all caps for labels.
+- Adding unnecessary typographic labels above content.
+
+Visual structure is information. Structural devices like outlines, borders, numbering, eyebrows, dividers, labels, etc., encode useful information about the content rather than decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence — like a stepped process or a timeline. Before adding numbered markers, check the content really is a sequence.
+
+Use non-user-triggered motion sparingly and deliberately, only to draw attention. A single orchestrated moment — one page-load sequence or one reveal — lands better than scattered effects; fade-and-slide-up entrances on each section and hover transitions on every card are the generic default and read as AI-generated. Motion that answers a person's action (opening, expanding, confirming) is welcome when it shows what changed.
+
+Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy and placeholder content. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
+
+## Process: plan, review against the brief, build, critique
+
+For calibration, AI-generated design right now clusters around some traits:
+1. a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta or warm-clay accent (often near #D97757 — Anthropic's own Claude-interaction accent, so on a user's brief it reads as a tell);
+2. a near-black background with a single bright acid-green or vermilion accent;
+3. a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns;
+4. the SaaS-card kit: content chopped into identical rounded cards, one border-radius on everything regardless of hierarchy, the same soft grey shadow (rgba(0,0,0,.1)) under each, and gradient washes as decoration;
+5. template chrome that appears whatever the subject: a tracked-out ALL-CAPS eyebrow label above every heading; meta strings joined with middle dots ('A · B · C'); labels built as 'WORD — fragment' with a spaced em dash; tinted near-black (#0B0B0B, #111) standing in for black; a monospace face for small data labels; a '→' appended to link and button text.
+
+All traits are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. As with a hired human designer, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
+
+Work in two passes. First, brainstorm a short design plan based on the client's design brief: create a compact token system with color, type, layout, and principles.
+- Color: describe the core base palette as 4–6 named hex values.
+- Type: the typefaces and their roles.
+- Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Include alignment guidance; should the content be left aligned, center aligned, justified?
+- Principles: the high-level guidance for what makes this page unique.
+
+Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan.
+
+When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and an element-based selector like .cta). This can happen often with padding/margin between sections.
+
+## Restraint and self-critique
+
+Spend your boldness in one place. Let one element be the memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, visually accessible, harmonious color palettes. Critique your own work as you build, taking screenshots to review if your environment supports it — a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creatives have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
+
+## More on writing in design
+
+Words appear in a design for one reason: to make it easier to understand and use. They are design content, not decoration. Bring the same intentionality and minimalism to copywriting that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
+
+Write from the end user's perspective. Name things by what users will understand in simple language, not by how the system is built. A user manages notifications, not webhook config. Describe what something is or does in plain terms rather than selling it. Being specific and legible to new users is always better than being clever.
+
+Use active voice as default. A CTA says exactly what happens when it is used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
+
+Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
+
+Keep the tone conversational: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each written element do exactly one job.

package/skills/axstack-explain/references/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

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

@@ -0,0 +1,13 @@
+# frontend-design source
+
+Source: https://github.com/anthropics/skills
+Commit: `41bbe19d1a1a7eaab5e7bb9050a417e5c6cffc8f`
+
+- `skills/frontend-design/SKILL.md` → `FRONTEND-DESIGN.md`: renamed, bytes unchanged.
+  Git blob: `a5333457c414d20d625f307df945842c0952ecc3`.
+- `skills/frontend-design/LICENSE.txt` → `LICENSE.txt`: bytes unchanged.
+  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`.

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

@@ -2,6 +2,17 @@
 
 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.
+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.
+For Publish, the reviewer opens `axstack-ui-verifier` PNGs at 728px dark and
+360px light, with paths bound to the artifact SHA-256 and recorded before review.
+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.
+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.
+
 Use this checklist for every HTML explanation and other visual artifacts where
 rendering matters.
 

package/skills/axstack-publish/SKILL.md

@@ -43,15 +43,26 @@ For public mode, run Explain's [self-contained asset check](../axstack-explain/r
 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.
 
-Add a standalone light/dark theme with inline defaults and `prefers-color-scheme`
-so the article works outside T3; honor an explicit user theme request.
+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)
+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.
 Theme adaptation changes bytes: save `final.html`, its byte count and SHA-256,
 then rerun the referenced Explain page checks on these final bytes.
+Before independent review, have `axstack-ui-verifier` preview these exact bytes with
+Playwright MCP at 728px dark and 360px light and record both screenshots with paths,
+their artifact SHA-256 and the Explain QA results.
 Require a fresh independent `axstack-explainer-review` on the final bytes.
-Preview these exact bytes with Playwright MCP at 728px dark and 360px light;
-record both screenshots and the Explain QA results.
+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.
 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.
 
 ## 3. Publish from the driver