@adia-ai/adia-ui-forge 0.8.34 → 0.8.35

package/skills/adia-release/scripts/release-pack.mjs

@@ -68,7 +68,7 @@ import os from 'node:os';
 import path from 'node:path';
 import process from 'node:process';
 import { assertMonorepoRoot } from './assert-monorepo-root.mjs';
-import { resolvePackageChangelog, PACKAGE_NAMES, PACKAGE_ROSTER } from './package-paths.mjs';
+import { resolvePackageChangelog, PACKAGE_ROSTER } from './package-paths.mjs';
 import { GATE_ROSTER } from './gate-roster.mjs';
 
 const SCRIPT_DIR = path.dirname(new URL(import.meta.url).pathname);
@@ -81,7 +81,11 @@ const DEFAULT_DEPLOY_HOST = 'ui-kit.exe.xyz';
 const DEFAULT_NPM_SCOPE = '@adia-ai';
 
 // Single-sourced roster (H3, package-paths.mjs); order = publish order.
-const PACKAGES = PACKAGE_NAMES;
+// Filtered to `lockstep !== false`: a class-B package (gh#1133's
+// adia-plugins) cuts independently — this orchestrator never touches it.
+// See package-paths.mjs's `lockstep` field note.
+const LOCKSTEP_ROSTER = PACKAGE_ROSTER.filter((p) => p.lockstep !== false);
+const PACKAGES = LOCKSTEP_ROSTER.map((p) => p.name);
 
 function parseArgs(argv) {
   const args = {
@@ -166,14 +170,14 @@ function parseArgs(argv) {
   if (args.mode === 'from-scratch' && (args.substantivePackages || args.stubPackages)) {
     // Flags accept both name form (a2ui-corpus) and path form (a2ui/corpus);
     // normalize to name form for the roster set-difference.
-    const toName = (p) => (PACKAGE_NAMES.includes(p) ? p : p.replaceAll('/', '-'));
+    const toName = (p) => (PACKAGES.includes(p) ? p : p.replaceAll('/', '-'));
     const covered = new Set([
       ...(args.substantivePackages ?? []).map(toName),
       ...(args.stubPackages ?? []).map(toName),
     ]);
-    const missing = PACKAGE_NAMES.filter((p) => !covered.has(p));
+    const missing = PACKAGES.filter((p) => !covered.has(p));
     if (missing.length > 0) {
-      console.error(`error: --mode from-scratch covers only ${covered.size} of the ${PACKAGE_NAMES.length} lockstep`);
+      console.error(`error: --mode from-scratch covers only ${covered.size} of the ${PACKAGES.length} lockstep`);
       console.error('       packages — Step 4e (generate-release-notes) would die on a missing');
       console.error(`       [${args.version}] CHANGELOG section in the ${missing.length} ride-along(s):`);
       console.error(`         ${missing.join(', ')}`);
@@ -367,7 +371,7 @@ function shCapture(cmd, args) {
 // regenerations that simply run again.
 function detectHalfCut(args) {
   if (args.mode === 'handoff' || args.dry) return false;
-  const versions = PACKAGE_ROSTER.map(({ name, dir }) => {
+  const versions = LOCKSTEP_ROSTER.map(({ name, dir }) => {
     const p = path.join(REPO, dir, 'package.json');
     return { name, version: JSON.parse(fs.readFileSync(p, 'utf8')).version };
   });
@@ -452,7 +456,16 @@ function step3PreFlight(args) {
       console.log(`\n  ${g.n}/${GATE_ROSTER.length}. ${g.cmd}   # ${g.what} — [resume] deferred to Step 4g (notes not regenerated yet)`);
       continue;
     }
-    const cmd = g.versionArg ? `${g.cmd} --version ${hygieneVersion}` : g.cmd;
+    // targetVersionArg (gh#1135, REQ-06) is a distinct flag from versionArg:
+    // write-eval-health.mjs NAMES a new file after the cut's target version
+    // from the very start — there is no pre/post-bump claim to reconcile
+    // the way gate 24's README-currency check has, so it always takes
+    // `args.version` verbatim regardless of mode or resume.
+    const cmd = g.versionArg
+      ? `${g.cmd} --version ${hygieneVersion}`
+      : g.targetVersionArg
+        ? `${g.cmd} --version ${args.version}`
+        : g.cmd;
     console.log(`\n  ${g.n}/${GATE_ROSTER.length}. ${cmd}   # ${g.what}`);
     try {
       sh(cmd, args, { stdio: 'inherit' });
@@ -678,7 +691,7 @@ function step5Commit(args) {
     'packages/genui/adia-catalog/base.json',
     'packages/genui/adia-catalog/adia-pack.json',
     'packages/genui/adia-catalog/catalog-data.js',
-    ...PACKAGE_ROSTER.flatMap(({ name, dir, plugin }) => {
+    ...LOCKSTEP_ROSTER.flatMap(({ name, dir, plugin }) => {
       // Roster-driven (H3): each package stages its manifest + CHANGELOG;
       // plugins also stage .claude-plugin/plugin.json (the /plugin-update
       // cache key, moved by bump.mjs); factory additionally pins a2ui-mcp in
@@ -1026,7 +1039,7 @@ async function main() {
   // the two apart, so the ruling lives here — still BEFORE the pre-flight.
   if (args.mode === 'from-scratch' && !args.resume && !args.substantivePackages && !args.stubPackages) {
     console.error('error: --mode from-scratch needs --substantive-packages and/or --stub-packages');
-    console.error(`       covering all ${PACKAGE_NAMES.length} lockstep packages — with neither, no CHANGELOG gets`);
+    console.error(`       covering all ${PACKAGES.length} lockstep packages — with neither, no CHANGELOG gets`);
     console.error(`       a [${args.version}] section and Step 4e (generate-release-notes) dies after`);
     console.error('       the ~15-min pre-flight (gh#765). A resumed half-cut tree is exempt,');
     console.error('       but this tree is not half-cut (versions are not at the cut version).');
@@ -1157,7 +1170,7 @@ function selftest() {
     // after detectHalfCut, still before the pre-flight.
     const rejectShapes = [
       { flags: '--substantive x --xref y --stub-packages llm', marker: 'ride-along' },
-      { flags: `--stub-packages ${PACKAGE_NAMES.join(',')}`, marker: '--substantive and --xref' },
+      { flags: `--stub-packages ${PACKAGES.join(',')}`, marker: '--substantive and --xref' },
       { flags: '', marker: 'needs --substantive-packages and/or --stub-packages' },
     ];
     for (const { flags, marker } of rejectShapes) {
@@ -1181,7 +1194,7 @@ function selftest() {
 
     // …and a fully covered from-scratch roster (substantive ∪ stub = all
     // packages) must pass the guard and assemble its dry plan normally.
-    const stubs = PACKAGE_NAMES.filter((p) => p !== 'web-components').join(',');
+    const stubs = PACKAGES.filter((p) => p !== 'web-components').join(',');
     let coveredOut;
     try {
       coveredOut = execSync(

package/skills/adia-release/scripts/tag-lockstep.mjs

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
-// tag-lockstep.mjs — create 12 lockstep tags (umbrella vX.Y.Z + 11
-// per-package <pkg>-vX.Y.Z, including the 2 plugin packages that joined
-// the lockstep 2026-07-15) at HEAD or at a specified SHA.
+// tag-lockstep.mjs — create the lockstep tag set (umbrella vX.Y.Z + one
+// per-package <pkg>-vX.Y.Z per roster entry — package-paths.mjs is the
+// live census; 14 tags as of gh#607) at HEAD or at a specified SHA.
 //
 // Usage:
 //   node tag-lockstep.mjs --version 0.6.22
@@ -15,11 +15,13 @@
 import { execSync } from 'node:child_process';
 import process from 'node:process';
 import { assertMonorepoRoot } from './assert-monorepo-root.mjs';
-import { PACKAGE_NAMES } from './package-paths.mjs';
+import { PACKAGE_ROSTER } from './package-paths.mjs';
 
 // The roster is single-sourced in package-paths.mjs (H3) — the `adia-ui-*-v*`
 // tags trigger publish-adia-ui-{factory,forge}.yml like every other package.
-const PER_PACKAGE_NAMES = PACKAGE_NAMES;
+// Filtered to `lockstep !== false`: a class-B package (gh#1133's
+// adia-plugins) tags independently, never via this umbrella lockstep set.
+const PER_PACKAGE_NAMES = PACKAGE_ROSTER.filter((p) => p.lockstep !== false).map((p) => p.name);
 
 function parseArgs(argv) {
   const args = { version: null, at: null, deleteMode: false, dry: false, repo: process.cwd() };
@@ -91,7 +93,7 @@ function main() {
     const perPkg = tags.filter((t) => t !== `v${args.version}`);
     console.log(`\n[next] run F-N1:`);
     console.log(`  node scripts/release/check-release.mjs --all-pending`);
-    console.log(`\n[next] when F-N1 is 9/9 clean, push main + tags ONE-AT-A-TIME:`);
+    console.log(`\n[next] when F-N1 is clean across the roster, push main + tags ONE-AT-A-TIME:`);
     console.log(`  # A single \`git push origin <all tags>\` can trigger ZERO publish-on-tag`);
     console.log(`  # workflows (the GitHub batch-push skip — it bit the v0.7.14 cut).`);
     console.log(`  # Push each per-package tag separately so each publish-<pkg>.yml fires.`);
@@ -109,9 +111,9 @@ function selftest() {
   // Derive from the roster (package-paths.mjs is the single source) — a
   // hard-coded count here is exactly the drift gh#612 removed from the docs;
   // the v0.8.26 cut caught this one when agent+persona joined (11 → 13).
-  const expected = PACKAGE_NAMES.length + 1; // umbrella + one per package
+  const expected = PER_PACKAGE_NAMES.length + 1; // umbrella + one per package
   if (tags.length !== expected) {
-    console.error(`selftest FAIL: expected ${expected} tags (umbrella + ${PACKAGE_NAMES.length} per-package), got ${tags.length}`); process.exit(1);
+    console.error(`selftest FAIL: expected ${expected} tags (umbrella + ${PER_PACKAGE_NAMES.length} per-package), got ${tags.length}`); process.exit(1);
   }
   if (tags[0] !== 'v1.2.3') {
     console.error('selftest FAIL: umbrella tag must be first'); process.exit(1);

package/skills/adia-site-docs/SKILL.md

@@ -2,7 +2,8 @@
 name: adia-site-docs
 description: >-
   Review or author pages under site/pages/{architecture,getting-started,
-  guides,patterns,reference}/ — the 34-page docs site. Use when asked to add
+  guides,patterns,reference}/ — the docs site (count the pages on disk; it
+  grows). Use when asked to add
   or edit a getting-started/architecture/guides/patterns/reference page,
   review a site docs page for consistency, fix a callout that reads as plain
   text, or explain why an inline-code chip or a demo gallery looks broken.
@@ -24,7 +25,7 @@ guides: prose + `<code-ui>` + tables, no live demos) and reference/gallery
 (patterns, reference: the same skeleton plus `<preview-ui>` demo rows and a
 near-universal closing "Guidance for agents" callout).
 
-Full decomposition, the 4 concrete rules, and the training-harvest-surface
+Full decomposition, the convention rules, and the training-harvest-surface
 boundary this skill does NOT cover: read
 [`../../../../../.claude/docs/conventions/site-pages-authoring.md`](../../../../../.claude/docs/conventions/site-pages-authoring.md)
 in full before authoring or reviewing — it is the source of record; this
@@ -37,8 +38,8 @@ skill routes to it and enforces it, it does not restate it.
 | New page in an owned category | Read the convention doc's template section; copy the shared skeleton from a sibling page in the same category (narrative archetype vs. reference/gallery archetype). |
 | Callout / "meta content" block | `<alert-ui variant="warning\|info\|...">` with `<div slot="content">` (never `<span>` — the transpiler only treats `p`/`div`/`ul`/`ol` as prose; a `<span>` silently reorders mixed inline content on regen) for rich text — never a bare `data-*` attribute. A whole multi-heading section aimed at a different reader (not a short callout) is NOT `alert-ui`'s job either — wrong shape — the convention doc's rule 2 carries the working treatment (eyebrow `<tag-ui>` title-row, TKT-0011). |
 | Tamed admin-shell demo | Add `class="demo-frame"` to the shell instance + a page-local `<style>` block setting only `--demo-frame-height` (and any genuinely page-specific extra). That's `site/site.css`'s `.demo-frame` utility already covering `position`/`border`/`overflow`/`.demo-body` padding. |
-| A surface needs to read as "its own distinct object" against the page background (a chip, a pill) | Reuse `--a-canvas-well-strong` (`packages/web-components/styles/colors/semantics/core.css`) — verified ≥3:1 (WCAG 2.2 SC 1.4.11) in both schemes. `--a-canvas-well` alone is for a subtly-sunken panel; a new candidate token always runs through `color:color-verify` first. |
-| "Is this page consistent?" / review request | Check the page against the convention doc's rules 1–4 by name; a finding names the specific rule violated, not just "this looks off." |
+| A surface needs to read as "its own distinct object" against the page background (a chip, a pill) | Reuse `--a-canvas-well-strong` (`packages/web-components/styles/colors/semantics/core.css`) — verified ≥3:1 (WCAG 2.2 SC 1.4.11) in both schemes. `--a-canvas-well` alone is for a subtly-sunken panel; for a NEW candidate token, text/link AA pairs are gated by `npm run verify:contrast` — a non-text 3:1 (SC 1.4.11) check has no mechanical runner today, so prove that ratio by hand and cite it in the PR. |
+| "Is this page consistent?" / review request | Check the page against the convention doc's numbered rules by name (the doc's own headings are the roster — it has grown past four); a finding names the specific rule violated, not just "this looks off." |
 | Anything touching a real UI primitive not already listed above | Audit `packages/web-components/components/` before inventing markup (this repo's standing rule) — a fake `data-*`/`class` convention with no CSS is exactly the defect class this skill exists to prevent. |
 
 ## Verify after any change
@@ -47,8 +48,9 @@ skill routes to it and enforces it, it does not restate it.
 - `node scripts/build/site-a2ui.mjs --page <route>` for every page whose
   **markup** changed — regenerates the compiled A2UI artifact the
   docs-transpiler produces from this source; a CSS-only fix needs no regen.
-- `color:color-verify` for any new or changed token used for text or
-  UI-component contrast — prove the ratio, don't estimate it.
+- `npm run verify:contrast` for any new or changed token used for text or
+  link contrast (that gate covers text/link AA pairs only — a non-text 3:1
+  claim needs a hand-proved, cited ratio; no mechanical runner exists).
 - `npm run check:lightningcss-build` after any CSS change (`site/site.css`
   or a component's own `.css`).
 - **Visually verify any `alert-ui`/rich-slotted-content change in a

package/skills/adia-site-docs/intent.md

@@ -37,7 +37,7 @@ markup that silently renders as plain paragraphs), a hand-rolled
 independently reinvented the same "tame this admin-shell demo" CSS),
 and a background token picked for its "feels dark and subtle" name
 rather than its actual measured contrast (inline `<code>` used
-`--a-canvas-well`, verified via `color:color-verify` at ~1.1:1 against
+`--a-canvas-well`, hand-measured at ~1.1:1 against
 the page background — WCAG 2.2 SC 1.4.11 wants ≥3:1). All three are
 now fixed at the shared-CSS/token level (cascades to all 34 pages),
 but a NEW page authored without this skill's guidance would

package/skills/adia-ssr/SKILL.md

@@ -116,7 +116,7 @@ this one component:** before answering "yes, known issue, shape 2" for ANY new
 report, grep the component's own `static template` — if it's the literal
 `() => null`, shape 2 cannot be the cause, no matter how closely the symptom
 matches the old description. [`failure-shapes.md`](references/failure-shapes.md)
-§2 has the full survey (150 components checked) and cites exactly why every
+§2 has the full survey (150 components at the 2026-07 survey — the census has since grown) and cites exactly why every
 current children-accepting component is unaffected.
 
 ## Corpus of record

package/skills/adia-ssr/references/failure-shapes.md

@@ -1,10 +1,11 @@
 # SSR failure shapes — symptom → root cause → status
 
-Three distinct root-cause classes have surfaced from real SSR consumers (adiav2's
+The §-numbered root-cause classes below (count the `##` headings — the list
+grows) have surfaced from real SSR consumers (adiav2's
 `admin-portal-fe` and `factory-dashboard`, server-rendering AdiaUI via Astro 5 +
 `custom-elements-ssr`, which runs on linkedom — a DOM shim with no layout engine and
 missing many browser APIs). A new SSR bug report almost always maps onto one of
-these three; misclassifying it (e.g. treating a measurement-timing bug as a missing-API
+them; misclassifying it (e.g. treating a measurement-timing bug as a missing-API
 bug) sends the fix to the wrong place. Check symptom against this table first.
 
 ## 1 · Browser-only API called unconditionally → crash
@@ -19,8 +20,10 @@ not a partial/quirky implementation, an absence. Any unconditional call throws
 `TypeError` or `ReferenceError` (undefined global) immediately.
 
 **Status: FIXED** (gh#285, PR #292, merged 2026-07-17). `UIElement`'s constructor
-(`packages/web-components/core/element.js`) and 24 component/trait/module files had
-this shape. The fix pattern (feature-detect + fallback matched to how the reference is
+(`packages/web-components/core/element.js`) plus a sweep of component/trait/module
+files had this shape — the per-file tally is
+[`status-ledger.md`](status-ledger.md)'s #285 row (the ledger, not this line, is
+the count of record). The fix pattern (feature-detect + fallback matched to how the reference is
 used downstream) is [`guard-patterns.md`](guard-patterns.md) — apply that pattern to
 any NEW file that construct-calls one of these APIs; don't re-derive the shape from
 scratch.
@@ -50,7 +53,7 @@ projected text, does lose it), but **every named example in the issue currently
 has `static template = () => null`**: `admin-shell`, `admin-sidebar`, `nav-ui`,
 `text-ui`, `badge-ui`, `avatar-ui` all skip `stamp()` entirely (`if (result)
 stamp(result, this)` — `null` never enters the branch). A framework-wide survey
-(150 components) found every component with a NON-null template derives its
+(150 components at the time) found every component with a NON-null template derives its
 visible content from properties/attributes only (`check-ui`'s `label=`,
 `switch-ui`'s `label=`/`hint=`, `skip-nav`'s `text=`) — never from light-DOM
 children — so the destructive replace, where it does fire, only ever regenerates

package/skills/adia-ssr/references/guard-patterns.md

@@ -92,7 +92,7 @@ The shipped guard is `scripts/dev/audit-template-child-conflict.mjs`: it flags a
 NEW component that pairs a non-null `static template` with a yaml `slots.default`
 entry (critical) or a body-text usage example (advisory) — i.e. it prevents the
 conflict shape from being reintroduced, rather than patching the render lifecycle
-every one of the 150 components goes through. **A component author who hits this
+every component goes through (150 at the 2026-07 survey; the census grows). **A component author who hits this
 audit's finding fixes it by making the template `() => null`** (the pattern every
 current children-accepting component already uses — compose via CSS + `render()`'s
 own surgical DOM manipulation, matching `avatar-ui`'s `#imgEl`/`#initialsEl`

package/skills/adia-site-docs/evals/audit-report.md

@@ -1,30 +0,0 @@
-# skill-review — adia-site-docs
-
-Skill: packages/plugins/adia-ui-forge/skills/adia-site-docs/SKILL.md · Standards: skill-authoring-standards · Lint: clean
-Verdict: PASS (no blocking finding)
-
-Lint verbatim: `skill-postwrite-invocation-lint · clean · .../adia-site-docs/SKILL.md`
-
-| ID | Verdict | Severity | Evidence (file:line) | Fix |
-|----|---------|----------|----------------------|-----|
-| R1 | PASS | — | SKILL.md:40 ("Never restate position/border/overflow…"), :41 (`--a-canvas-well-strong` verified ≥3:1), :43 (audit primitives before inventing markup) — each survives deletion; removing any re-admits a concrete defect class. | — |
-| R2 | PASS | — | Desc SKILL.md:4-8 front-loads verbatim user phrasings ("add or edit a … page", "review a site docs page", "fix a callout that reads as plain text"); fences use the parseable `NOT for X (owner)` form :9-12. Corpus routing (evals/routing-corpus.json) covers 16 should-fire + 6 adversarial. | — |
-| R3 | PASS w/ note | minor | Species=procedural (intent.md:3); dials explicit and agree (SKILL.md:13-14); name head `adia-site-docs` is a domain-noun, not the generic zero-derivation verb the standard prescribes for procedural — but it matches the whole plugin's `adia-<domain>` grammar (sibling adia-author is identically formed). Consistent within the estate; flagged only for the record. | Keep — estate naming convention governs; no change. |
-| R4 | PASS w/ note | minor | Load-bearing rows instantiate concrete actions (SKILL.md:38-43). Negative imperatives run to ~4 ("do NOT invent" :38, "never a bare data-*" :39, "Never restate" :40, "don't reach for a raw ramp step without color-verify" :41) — at/over the ≤3 hard-gate guideline. | Optional: demote the two style-choice negatives (:38, :41) to positive form; reserve NEVER for :39/:40 catastrophic invariants. |
-| R5 | PASS | — | Deliberately routes to `.claude/docs/conventions/site-pages-authoring.md` (SKILL.md:28-32) rather than copying rules 1-4; convention doc confirmed present with matching `### 1..4` headings. Drift pair avoided by design — the strongest dimension. | — |
-| R6 | PASS | — | Task-shape contract table up front (SKILL.md:34-43); verify steps + stopping predicate at tail (:45-58); body 59 lines (well under 500 / 5,000-token head); reference one level deep. | — |
-| R7 | PASS w/ gap | minor | Output contract present (review finding "cites the specific rule … it violates" :57-58); stopping predicate present ("Done when …" :56). No *named failure branches* (e.g. "if `check:links` cannot run → report blocker, do not mark done"). | Add one failure branch to the Verify section for a check that cannot run. |
-| R8 | PASS | — | Numeric anchors on load-bearing dims: "34-page" (:5,20), "≥3:1 (WCAG 2.2 SC 1.4.11)" (:41), "rules 1-4" (:42,57). No vague quantifiers on load-bearing lines. | — |
-
-## Additional evidence (non-scored hygiene)
-
-- **Phantom fence paths** (minor): description fences `site/pages/examples/**` and `site/pages/gen-ui/**` (SKILL.md:11); neither directory currently exists under `site/pages/` (only architecture, getting-started, guides, patterns, reference). The fence spends description budget on surfaces that are not yet present. Keep if these are planned training-harvest surfaces (intent.md:52 treats them as governed by composition-and-examples.md); otherwise trim to reclaim characters. Not blocking — the fence is still correct if/when those surfaces land, and adversarial-02 tests it.
-- **intent.md citation drift** (minor, not in payload): intent.md:64 cites `evals/evals.json`, but the shipped corpus is `evals/routing-corpus.json`. intent.md is a forge artifact, not skill payload, so it does not affect triggering — but repair the citation in the same edit to keep the record honest.
-
-## Top 3
-
-1. (minor) R7 — add one named failure branch to the Verify section (a check that cannot run → report blocker, do not mark done); procedural bodies owe an explicit failure branch, currently absent (SKILL.md:45-58).
-2. (minor) R4 — negative-imperative count sits at ~4; demote the two style-choice negatives (:38 section shape, :41 ramp step) to positive phrasing, reserving hard gates for the two real invariants (:39 fabricated data-*, :40 restated demo-frame CSS).
-3. (minor) Phantom fence — reconcile `site/pages/examples/**` and `site/pages/gen-ui/**` (SKILL.md:11): confirm they are planned surfaces or trim the fence; and fix the `evals.json` → `routing-corpus.json` citation in intent.md:64.
-
-No blocking or major findings. The skill's reference-don't-restate discipline (R5) and measured contrast anchor (R8) are its strongest features.

package/skills/adia-ssr/evals/audit-report.md

@@ -1,63 +0,0 @@
-# adia-ssr skill audit (FLOOR)
-
-Skill: `packages/plugins/adia-ui-forge/skills/adia-ssr/` · Standards: skill-authoring-standards · Lint: clean
-Verdict: **PASS**
-
-Species: knowledge (`disable-model-invocation: false`, `user-invocable: false`) — sibling in
-shape to `packages/plugins/adia-ui-factory/skills/adia-tokens/`, confirmed.
-
-| ID | Verdict | Severity | Evidence (file:line) | Fix |
-|----|---------|----------|----------------------|-----|
-| R1 Behavior delta | PASS | — | `SKILL.md:67-73` (caveat: don't invent a component-local workaround for gh#284 — deleting it removes the one line steering Claude away from a plausible wrong answer); `SKILL.md:36-38` (gh#288 dependency on gh#284 — deleting it, Claude could treat #288 as independently actionable); `SKILL.md:51` (test-without-linkedom consult row — deleting it loses the exact routing signal to the one file that explains why the repo's default test env can't reproduce SSR bugs) | none |
-| R2 Trigger fidelity | PASS | — | Description (`SKILL.md:3-10`) phrasings "does X work under SSR", "why does X crash/disappear when server-rendered", "is this connect-time read safe" are the literal `should_route_to_ssr: true` phrases in `evals/routing-corpus.json:20,35,90`; fences ("NOT for implementing a fix (adia-author) or consumer host/hydration wiring (adia-host...)") correctly repel `ssr-adversarial-01/02/05` (routing-corpus.json:104-107, 110-114, 130-135) | none |
-| R3 Species/dial agreement | PASS | — | `SKILL.md:11-12` both dials explicit and correct for knowledge species; name `adia-ssr` follows the established local `adia-*` topic-noun convention (matches sibling `adia-tokens`, `adia-a2ui`) rather than the generic `x-patterns` grammar — acceptable under the project's own precedent | none |
-| R4 Register | PASS | — | Load-bearing lines cite exact file:line, PR, and issue numbers rather than describing generically, e.g. `SKILL.md:63-66` ("`UIElement.connectedCallback`... calls `stamp(result, this)`... currently line 194") — verified accurate, see Notes | none |
-| R5 No restatement | PASS | — | No drift-pair found against `component-token-contract.md` / `component-implementation-patterns.md` / AGENTS.md — none cover SSR. Pack explicitly fences out generic web-components-SSR theory (`SKILL.md:97-99`), so it doesn't restate model-general knowledge either | none |
-| R6 Position | MINOR | minor | Body is only ~108 lines (~2,000 tokens, well inside the 5,000-token survival window, so no practical compaction risk) — but structurally, "Deviation doctrine" and "Boundaries" (`SKILL.md:75-99`, gate-shaped content) sit *after* the "Worked example" (`SKILL.md:55-74`), inverted from the "contracts/gates first, examples last" rule | Move Deviation doctrine + Boundaries above the Worked example on next semantic edit; not urgent given total size |
-| R8 Quantities | PASS | — | `127+ primitives`, `24 component/trait/module files`, `12 files` calling `this.internals.*`, `~110-line shim`, dated `2026-07-17`, gh#284-288 — all load-bearing counts are numeric, none vague | none |
-
-R7 (Contracts): N/A — knowledge species, not procedural/command.
-
-## Notes — factual grounding (beyond the R1-R8 checklist, but relevant to a knowledge pack's core promise)
-
-Spot-checked every concrete claim against the actual repo state rather than trusting the pack's
-own self-description:
-
-- `packages/web-components/core/template.js:194` — `export function stamp(result, container)` is
-  exactly where `failure-shapes.md` and the Worked example say it is.
-- `packages/web-components/core/element.js` — `attachInternals` shim (`this.internals = typeof
-  this.attachInternals === 'function' ? this.attachInternals() : NOOP_INTERNALS`),
-  `adoptedStyleSheets` guard (`if (!('adoptedStyleSheets' in document)) return;`), and the
-  `connectedCallback` → `stamp()` call all match `guard-patterns.md` and `failure-shapes.md`
-  verbatim.
-- `packages/web-modules/shell/admin-sidebar/admin-sidebar.js` — `#syncCollapsedFromWidth` (zero-rect
-  `return` before the decision) and `#setupChildResizeObserver` (`typeof ResizeObserver ===
-  'undefined'` guard, deferred correction) match `guard-patterns.md` §3's cited code exactly,
-  including `SNAP_THRESHOLD`.
-- `packages/web-components/core/element.test.js:259` — the `describe('UIElement — SSR
-  browser-API absence (gh#285)'` block matches `test-without-linkedom.md`'s cited delete/try/finally
-  pattern.
-- `git log`: PR #292 (gh#285) and PR #290 (gh#286) both merged 2026-07-17, matching every date
-  cited in `status-ledger.md` and `consumer-workarounds.md`.
-- No `linkedom` in any `package.json` in the tree — confirms `test-without-linkedom.md`'s central
-  claim.
-- Live `gh issue view` for 284-288 today: #284 OPEN, #285 CLOSED, #286 CLOSED, #287 OPEN, #288
-  OPEN — matches `status-ledger.md`'s table exactly, row for row, including the "#287 is
-  unrelated" framing.
-
-Every citable fact in this pack checked out. This is unusually high grounding for a hand-authored
-knowledge pack — worth naming as the standard other `adia-*` knowledge skills should be held to.
-
-## Top 3
-
-1. **Ship as-is.** Zero blocking or major findings; lint clean; every code/issue citation
-   independently verified against the live repo and `gh issue view` — the pack's core promise
-   ("cited to the actual shipped/open code") is actually true today, not just claimed.
-2. **Routing corpus is well-formed and matches its own spec** — 12 trigger / 5 adversarial phrases
-   (29.4% adversarial, spec says ~29%), all 5 reference files covered by `expected_shape`, and the
-   3 adversarial near-misses (gh#287 bundler bug, a2ui pipeline, generic hydration theory) are
-   genuinely hard boundary cases, not straw men.
-3. **One minor, non-blocking structural nit (R6):** the gate-shaped "Deviation doctrine" and
-   "Boundaries" sections trail the "Worked example" instead of leading it. Harmless at this body
-   size (~2K tokens, nowhere near the 5K compaction cutoff) — fix opportunistically on the next
-   semantic edit to this file, not worth a dedicated pass.