@nurix/etna 0.19.51 → 0.19.53

package/data/harnesses/code/skills/design/data/voices/direct-operator.md

@@ -0,0 +1,29 @@
+---
+id: direct-operator
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Atlassian's 'bold, optimistic, practical' brevity mandate (atlassian.design/content/voice-and-tone-principles) and Material Design's clarity-to-anyone standard (m3.material.io/foundations/content-design)."
+license: open
+---
+# Voice: direct-operator
+
+**Feel:** Brisk and task-first — reads like a command line, not a conversation.
+
+Imperative mood by default; sentence fragments are acceptable where a full sentence adds nothing ("Upload failed. Retry."). No adjectives unless load-bearing. Numerals are always digits, units abbreviated once established. No exclamation points, no rhetorical questions, no throat-clearing openers ("Please note that…"). Density over politeness — every word has to justify its presence.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** imperative, fragments allowed
+- **error:** states failure plus count or reason, no softening
+- **success:** single clipped phrase, no embellishment
+- **destructive confirmation:** same flat register as everything else — no added urgency language, the plainness is the safeguard
+
+## Examples
+
+- **button:** "Create workspace"
+- **empty state (heading + motivation):** "No records" / "Import a file or add one manually to begin."
+- **error:** "Save failed. 3 fields are invalid."
+- **tooltip:** "Locks the row for editing by others."
+- **confirmation:** "Workspace created."

package/data/harnesses/code/skills/design/data/voices/earnest-helper.md

@@ -0,0 +1,29 @@
+---
+id: earnest-helper
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Intercom's PREACH framework (intercom.com/blog/preach-framework-for-customer-support-tone) — Proud, Responsible, Empathetic, Articulate, Concise, Human."
+license: open
+---
+# Voice: earnest-helper
+
+**Feel:** Owns the failure, states the fix, never grovels.
+
+First-person-plural ownership when the product is at fault ("we couldn't…"), second person when guiding the user's next step. Sentences are short and declarative; empathy is shown through precision and a clear next step rather than apology words ("sorry," "oops" are avoided). No exclamation points, even on success — confidence doesn't need punctuation. Numbers are digits throughout.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** second person, concise, no flourish
+- **error:** first-person-plural ownership ("we couldn't…"), immediate next step
+- **success:** short, no exclamation, confidence without decoration
+- **destructive confirmation:** states irreversibility explicitly, still no apology language
+
+## Examples
+
+- **button:** "Submit request"
+- **empty state (heading + motivation):** "No requests yet" / "Submit one and track its progress here."
+- **error:** "We couldn't submit that request. Reconnect and try again."
+- **tooltip:** "Requests are visible to your whole team once submitted."
+- **confirmation:** "Request submitted."

package/data/harnesses/code/skills/design/data/voices/editorial-composed.md

@@ -0,0 +1,29 @@
+---
+id: editorial-composed
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Material Design's AP-style clarity standard (m3.material.io/foundations/content-design/style-guide/ux-writing-best-practices) and Atlassian's 'practical, with a wink' brand register (atlassian.design/content/writing-style), slowed to an editorial cadence."
+license: open
+---
+# Voice: editorial-composed
+
+**Feel:** Measured and literate — composed sentences, unhurried but exact.
+
+Longer, fully-formed sentences that favor a subordinate clause over a fragment; still one idea per sentence, but the idea is given room. Verbs remain the engine of the sentence rather than being buried under nominalizations. Numbers under ten are spelled out even in most UI text; digits are reserved for data-dense contexts (tables, counters, timestamps). Restraint reads as taste, not coldness — warmth comes from word choice, never from exclamation.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** a fuller sentence, still verb-led
+- **error:** composed, no blame, the fix named in a complete sentence
+- **success:** a complete, satisfying sentence rather than a clipped label
+- **destructive confirmation:** the most fully-formed of the four — consequence and reversibility spelled out in full
+
+## Examples
+
+- **button:** "Add collection"
+- **empty state (heading + motivation):** "Nothing archived yet" / "Items you archive will be kept here, in order, for as long as you need them."
+- **error:** "The collection couldn't be saved. Review the highlighted fields and try again."
+- **tooltip:** "Determines the order collections appear in for every viewer."
+- **confirmation:** "Collection added and ready to share."

package/data/harnesses/code/skills/design/data/voices/quiet-concierge.md

@@ -0,0 +1,29 @@
+---
+id: quiet-concierge
+class: c2
+sourced: 2026-07-12
+source: "Distilled from Shopify Polaris content fundamentals (polaris-react.shopify.com — verb-first directness, plain language, 'remove until it breaks') and Atlassian voice & tone (atlassian.design — say it once, then get out of the way)."
+license: open
+---
+# Voice: quiet-concierge
+
+**Feel:** Understated and precise — says the necessary thing once, then steps back.
+
+Short-to-medium declarative sentences, verb-first for any instruction ("Add," "Move," "Archive"). Warmth comes from precision, not adjectives — no exclamation points, no stacked modifiers, no filler words ("just," "simply," "easily"). Numbers render as digits even under ten, to keep the eye moving. Contractions are allowed ("it's," "can't") to keep the register human. If a sentence can be cut without losing meaning, cut it.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** plain, verb-first, no ornament
+- **error:** flat statement of what happened, then the fix — no apology
+- **success:** states the fact and stops there
+- **destructive confirmation:** names exactly what's lost, in the same even register — precision is the only warning
+
+## Examples
+
+- **button:** "Add customer"
+- **empty state (heading + motivation):** "No reports yet" / "Reports appear here once your first one is generated."
+- **error:** "The file didn't upload. Check your connection and try again."
+- **tooltip:** "Archives the record without deleting its history."
+- **confirmation:** "Customer added."

package/data/harnesses/code/skills/design/data/voices/warm-guide.md

@@ -0,0 +1,29 @@
+---
+id: warm-guide
+class: c2
+sourced: 2026-07-12
+source: "Distilled from the Mailchimp Content Style Guide (styleguide.mailchimp.com) — voice & tone, writing principles, web elements, and grammar & mechanics pages: plainspoken warmth, dry humor, active voice, treats users as capable partners. Mailchimp's style guide content is published under a Creative Commons Attribution-NonCommercial 4.0 International License (CC BY-NC 4.0); reworded and distilled throughout, no verbatim reuse."
+license: licensed
+---
+# Voice: warm-guide
+
+**Feel:** Plainspoken and warm — talks to you like a colleague who respects your time.
+
+Medium sentences in active voice, contractions throughout. One dry aside is permitted per surface, never forced. Numbers under ten are spelled out in body copy, digits in dense UI (tables, counters). Confidence over cheerleading — no "Great job!"; encouragement is implied by clarity, not stated outright. The register never talks down to the reader.
+
+## Tone map
+
+Voice is constant; tone dials by situation.
+
+- **routine action:** relaxed, active voice, one idea per sentence
+- **error:** takes ownership ("we couldn't…"), calm next step, no exclamation
+- **success:** quietly confident, still no exclamation
+- **destructive confirmation:** slows down a beat, spells out what's being removed and that it can't be undone
+
+## Examples
+
+- **button:** "Send invoice"
+- **empty state (heading + motivation):** "Nothing here yet" / "Once you add a project, it'll show up in this list."
+- **error:** "We couldn't send that invoice. Check the email address and try again."
+- **tooltip:** "Sends a copy to your own inbox too."
+- **confirmation:** "Invoice sent."

package/data/harnesses/code/skills/design/references/compose.md

@@ -6,20 +6,16 @@ Build the app — all surfaces in one continuous context, the chosen package's d
 
 Per the primitives switch recorded in the project's `design.md`:
 
-- **`nurix`** — compose chrome from `@nurix/components`. The chrome recipes (`get_entry`, kind `chrome` — fetch only the recipes for surfaces in the structure doc) carry composition, states, and when-to-use; the component reference folder (`components/`) carries props, imports, and usage — consult the index for what exists, and open the touched category's API reference on need.
+- **`nurix`** — compose chrome from `@nurix/components`. The chrome recipes (`data/chrome/` — read only the recipes for surfaces in the structure doc) carry composition, states, and when-to-use; the component dictionary (`components/`) carries props, imports, and usage across both provenances — consult the index for what exists, and open the touched category's API reference on need.
 - **`native`** — the recipes are *specifications*: anatomy, the eight states, keyboard behavior, token reach — implement them with the incumbent stack's own components. The index's shadcn/fallback columns carry the composition; category API references never load.
 
 Recipes are starting points, not jails: restyle or extend them in place when the package demands it.
 
-## The consult, at your discretion
-
-The composition consult is available here — a whole-app paragraph in, candidate shapes + a component list + rulings out. It is advisory, never binding: you compose. The judgment rule for *when* lives in the router (SKILL.md § The coupled server); the short form: consult on a real knowledge gap or a rework signal, stay local when the canvas is the answer, and `record` every consult and every deviation from its advice. Unavailable is normal — compose locally, record it, continue.
-
 ## Composition rules
 
-- **Every surface starts from a chosen layout blueprint** — `get_entry` the chosen archetype's blueprint (kind `blueprint`); pick the shape reading the brief, record it in one line. Structural variety, not visual variety, is what reads as designed.
+- **Every surface starts from a chosen layout blueprint** (`data/blueprints/<archetype>.md`) — pick the shape reading the brief, record it in one line. Structural variety, not visual variety, is what reads as designed.
 - **Values come from the token artifact** — components consume the emitted custom properties and never invent raw values ([emission.md](emission.md) has the pipe rules). Switching packages must re-skin the whole app.
-- **Positive obligations apply** — `get_entry` the surface's archetype checklist (kind `checklist`); the checklists are ceilings: a sidebar ships with brand block, icons, and user context; a dashboard tile ships with number + comparison + trend + state + door; every surface ships its state matrix.
+- **Positive obligations apply** — load the surface's archetype checklist (`data/checklists/<archetype>.md`); the checklists are ceilings: a sidebar ships with brand block, icons, and user context; a dashboard tile ships with number + comparison + trend + state + door; every surface ships its state matrix.
 - **The register scope holds**: the display face never touches cells, buttons, labels, or form chrome; data numerals run the mono face with `tabular-nums`.
 - **Motion follows the package's §7** and the frequency law: actions performed 100+ times a day, and any keyboard-initiated action, get no animation, ever; panel/drawer motion is interruptible; entrances never `ease-in`.
 - **No ownership jails.** Any file may be edited at any time, including generated ones and library compositions.

package/data/harnesses/code/skills/design/references/content.md

@@ -4,7 +4,7 @@ Author the demo data **before composing surfaces**. Data credibility is the sing
 
 ## From the corpus
 
-Fetch the chosen domain's corpus — `search_catalog` (kind `corpus`) to find it, `get_entry` to load it: the body (vocabulary, number-shape recipes, the invariants block) arrives with its `people` and `companies` rosters in one payload.
+Fetch the chosen domain's corpus — `search_catalog` (family `corpus`) to find it, `get_entry` to load it: the body (vocabulary, number-shape recipes, the invariants block) arrives with its `people` and `companies` rosters in one payload.
 
 - Names come from the corpus roster; emails derive from names; roles are domain-correct.
 - Activity strings use the corpus vocabulary — a CRM logs "Intro call with Elena — pricing discussion", never webhook noise.
@@ -14,13 +14,13 @@ Fetch the chosen domain's corpus — `search_catalog` (kind `corpus`) to find it
 
 ## Voice
 
-Fetch the package-bound voice pack — `get_entry` the voice the package's §9 names. All authored strings — buttons, empty states, errors, tooltips, confirmations — speak in that voice, with tone varying by situation per the pack's tone map.
+Load the package-bound voice pack (`data/voices/<id>.md` — the package's §9 names it). All authored strings — buttons, empty states, errors, tooltips, confirmations — speak in that voice, with tone varying by situation per the pack's tone map.
 
 ## Chart choice
 
-Every data-bearing surface consults the chart-selection engine — **one graph question per consult**. The census rows the engine evaluates are fetched **once per session** via `get_entry("chart-census")`:
+Every data-bearing surface consults the chart-selection engine — **one graph question per consult**. The census ships beside the engine; nothing is fetched:
 
-1. Author the data signature (the judgment half): the question, measures, dimensions, semantic flags (temporal, parts-form-whole, target-exists, …), constraints — plus the session's `census` rows. Decompose multi-question asks first.
+1. Author the data signature (the judgment half): the question, measures, dimensions, semantic flags (temporal, parts-form-whole, target-exists, …), constraints. Decompose multi-question asks first.
 2. Run `node scripts/select-chart.mjs <signature.json>` and read the typed output: admissible set, eliminations with reason codes, ranking, recommendation, or a refusal code.
 3. **Honor refusals** — a refusal means the question isn't chartable as posed (often: it's a table). Never invent a measure to force a chart.
 4. `record` the pick in one line. Taking a non-recommended admissible option needs a reason on that line; taking an eliminated option is out of contract.

package/data/harnesses/code/skills/design/references/existing-apps.md

@@ -4,7 +4,7 @@ The same machinery runs on existing UIs, under a preservation contract.
 
 ## Judge — a user-invoked service
 
-A critique of an existing UI against the brief, the project's `design.md`, the archetype checklists, and the project's taste profile (`get_project`), producing a **severity-ranked (never scored) report**. Judge is a service the user asks for — never a self-check the skill runs on its own output. Read the actual rendered state (screenshots the user provides, or captures the user asks for); refuse to critique from source alone when the ask is "does it look right", and never imagine what unrendered code looks like. Each finding: severity, the on-screen element, what's wrong, the exact fix.
+A critique of an existing UI against the brief, the project's `design.md`, the archetype checklists, and the workspace's taste profile (`get_preferences`), producing a **severity-ranked (never scored) report**. Judge is a service the user asks for — never a self-check the skill runs on its own output. Read the actual rendered state (screenshots the user provides, or captures the user asks for); refuse to critique from source alone when the ask is "does it look right", and never imagine what unrendered code looks like. Each finding: severity, the on-screen element, what's wrong, the exact fix.
 
 ## Improve — judge + the fix pass
 

package/data/harnesses/code/skills/design/references/foundations.md

@@ -0,0 +1,57 @@
+# Foundations — the brief fixed doctrine
+
+Cross-cutting decisions every build makes once, stated at the length they deserve and no longer (the obviousness rule: what competent intelligence already knows gets nothing). Load the touched entry at the step that decides it, never the file whole.
+
+## The five status palettes
+
+Pick **one** per project at intake and hold it everywhere — status colors are semantics, not decoration, and deltas color by *meaning* (down is green when down is good):
+
+| Palette | success | warning | danger | info | neutral | Feel |
+| --- | --- | --- | --- | --- | --- | --- |
+| `signal` | `oklch(0.64 0.15 150)` | `oklch(0.75 0.15 80)` | `oklch(0.58 0.20 25)` | `oklch(0.60 0.14 250)` | `oklch(0.65 0.02 260)` | the default — clear, saturated, unmistakable |
+| `muted-pro` | `oklch(0.60 0.09 155)` | `oklch(0.68 0.10 75)` | `oklch(0.55 0.13 25)` | `oklch(0.58 0.08 250)` | `oklch(0.62 0.015 260)` | desaturated for dense dashboards — readable without shouting |
+| `warm-ledger` | `oklch(0.62 0.11 140)` | `oklch(0.70 0.13 60)` | `oklch(0.56 0.17 30)` | `oklch(0.60 0.10 230)` | `oklch(0.64 0.02 80)` | warm-neutral products (finance, ops review) |
+| `cool-console` | `oklch(0.66 0.12 165)` | `oklch(0.74 0.12 85)` | `oklch(0.60 0.18 15)` | `oklch(0.62 0.12 265)` | `oklch(0.66 0.02 250)` | cool/dark consoles — holds up on deep backgrounds |
+| `high-contrast` | `oklch(0.55 0.17 150)` | `oklch(0.60 0.16 70)` | `oklch(0.50 0.21 27)` | `oklch(0.50 0.16 255)` | `oklch(0.50 0.02 260)` | accessibility-first; every value ≥4.5:1 on white |
+
+Each value is the light-theme anchor; derive the dark-theme sibling by raising lightness ~0.08 and trimming chroma ~0.02. Severity ladders (P0–P3 and kin) map onto danger → warning → info → neutral, never onto new hues.
+
+## Data-viz palettes
+
+No database — three constraints, values yours: **categorical** series need distinguishable hues that survive colorblind simulation (rotate hue ≥40° apart, vary lightness too, ≤8 series then facet); **sequential** ramps run light→dark in one hue for magnitude; **diverging** ramps put two hues around a *meaningful* zero, neutral at the middle. Validate every ramp in both themes; charts consume package tokens, never raw hex.
+
+## Number, date, unit formatting
+
+Tabular figures in tables and KPIs; thousands separators; unit or currency attached to the number; consistent decimals per column; large values truncate meaningfully (`1.2M`, never `1,200,000` in a tile); timestamps show relative when recent and absolute on hover; timezones explicit anywhere ambiguity costs money.
+
+## Spacing & density
+
+The 2/4/6/8 scale, period. Operator surfaces default **compact** (data rows 32–36px) with a comfortable mode only when `product.md` says reading, not scanning. Density is a per-project decision made once, not a per-surface mood.
+
+## Radius & stroke
+
+Radius is identity — sharp (0–2px), soft (4–6px), or round (10px+) — chosen by the package and applied consistently; mixing radii on one surface reads as templated. One border weight per surface; elevation *or* borders separate layers, never both at full strength.
+
+## Loading, skeleton, progress
+
+Skeletons for layout-known loads, spinners only for unknowable ones, optimistic updates for high-frequency mutations with undo. Skeletons mirror the real layout's bones (no generic gray blocks). Nothing pulses faster than 1.2s.
+
+## Empty states
+
+The three empties (first-use, no-results, cleared-filter) each say what happened and what to do next, in the project voice. Art direction follows the package's restraint: an icon or nothing for dense tools; illustration only where the package's feel says warm. Never a bare "No data".
+
+## Keyboard
+
+The operator vocabulary: `⌘K` command palette, `j/k` traversal where lists dominate, `esc` closes the topmost layer only, `enter` commits, focus visible always. Declare shortcuts in a discoverable surface (palette footer or `?` overlay).
+
+## Dark mode physics
+
+Elevation becomes lightness (surfaces lighten as they rise — shadows barely read); desaturate fills ~15%; never pure black (`oklch(0.13–0.18 …)` floors); borders drop to low-alpha white; charts re-derive from dark-theme tokens, never inherit light values.
+
+## Code, log, terminal surfaces
+
+Mono face with `tabular-nums`; a shiki theme paired to the package (dark identity → dark code surface even in light theme is legitimate); log levels use the status palette; wrap off by default with horizontal scroll.
+
+## Polish
+
+Focus rings on-brand (2px, offset, the accent — never browser default blue on a styled app); selection color derived from the accent at low alpha; scrollbars styled thin on dense panes; cursor changes only where affordance is real.

package/data/harnesses/code/skills/design/references/intake.md

@@ -2,19 +2,19 @@
 
 Read the brief and choose from the menus: one identity package (the design.md system), any axis overrides the brief demands, layout blueprints per surface, and the product domain for content. Every choice is one recorded line.
 
-**Returning project first.** If the repo carries a `projectId`, open with `get_project`: the personality, the taste profile, and the recent decision lines are the session's context — then run the drift check (compare the repo's `design.md` against the server canonical; on mismatch, tell the user which is newer and ask). A returning project re-enters the steps with its identity already chosen; the rules below are for first intake.
+**Returning workspace first.** If the repo carries a `workspaceId` (or the Apollo context supplies one), open with `get_preferences`: the workspace's `design.md`, `taste.md`, and `product.md` rows are the session's context — then run the drift check (compare the repo's `design.md` against the server row; on mismatch, tell the user which is newer and ask). A workspace with a recorded identity re-enters the steps with that identity already chosen; the rules below are for first intake.
 
 ## Rules
 
 - **The brief's own words outrank any database default.** "Beautiful" means the ceiling, not the safe row.
 - **Adjectives become referents.** When the brief speaks in adjectives ("premium", "editorial"), name the 2–3 real products the brief is pointing at and pick the package whose recorded identity sits in that class — unnamed ambition becomes beige.
-- **Search is a retrieval aid, never a router.** `search_catalog` (kind `package`) with the brief's segment/keyword resemblance; shortlist 2–3 results by their head metadata (feel, reads-as, keywords), then choose reading the brief. After the choice, `get_entry` **once**: the chosen package's full design.md enters context and **stays in view through step 4**; unchosen candidates are never fetched.
+- **Search is a retrieval aid, never a router.** `search_catalog` (family `design_md`) with the brief's segment/keyword resemblance; shortlist 2–3 results by their head metadata (feel, reads-as, keywords), then choose reading the brief. After the choice, `get_entry` **once**: the chosen package's full design.md enters context and **stays in view through step 4**; unchosen candidates are never fetched.
 - **The escape hatch fires mechanically.** No catalog hit, plus a recorded one-line reason why the closest package fails → author a one-off project design.md in the package schema, `tier: project` — the validator is the schema authority and checks it like any library entry. This path is expected to be common; flag the file as a curation candidate for the roster.
-- **Register the project.** First intake ends with `register_project` — name, the consumer's container if it has one, and `fork: { slug, version }` pinning the chosen package as it was chosen (a copy, never a live read: later catalog edits cannot change a running project's identity). Commit the returned `projectId` to the repo. Escape-hatch one-offs register without a fork; the authored design.md is pushed via `record`.
-- **Axis overrides fetch the same way** — a recorded override names its axis entry; `get_entry` (kind `axis`) fetches exactly that entry.
-- **Set the primitives switch** — write one `primitives: nurix | native` line into the project's `design.md`. Default by the probe: the project resolves `@nurix/components` (check package.json / lockfile / node_modules) → `nurix`; otherwise — existing apps, foreign stacks, no library access — → `native`. Set once here; nothing downstream re-asks. Also write `source-package: <slug>@<version>` (or `authored` for escape-hatch one-offs).
-- **Write or update `product.md`**: users and their jobs, roles/permissions, action frequency, risk level, accessibility commitments, brand anti-references. Package choice, UX decisions, motion intensity, and demo data all cite it.
-- **The taste profile biases every choice** — `get_project` returns it (per-dimension feel/avoid lines); user reactions to shipped output update it via `record`. No profile yet = no bias, never a block.
+- **Record the identity.** First intake ends with `record`: the identity choice as a decision line, and the resolved fork pushed as the workspace's `design.md` preference row. The `workspaceId` is committed to the repo if it is not ambient. Design taste is workspace-level — an app never gets its own.
+- **Axis overrides fetch or read the single named entry** — color/font/gradient/chart-style overrides `get_entry` their dictionary entry; elevation/motion/iconography overrides read the named local entry under `data/`.
+- **Set the primitives switch** — write one `primitives: nurix | native` line into the project's `design.md`. Default by the probe: the project resolves `@nurix/components` (check package.json / lockfile / node_modules) → `nurix`; otherwise — existing apps, foreign stacks, no library access — → `native`. Set once here; nothing downstream re-asks. Also write `source-package: <slug>` (or `authored` for escape-hatch one-offs).
+- **Write or update `product.md`**: users and their jobs, roles/permissions, action frequency, risk level, accessibility commitments, brand anti-references. Package choice, UX decisions, motion intensity, and demo data all cite it. Push it as a preference row too — Studio shows it.
+- **The taste profile biases every choice** — `get_preferences` returns the workspace's `taste.md` (per-dimension feel/avoid lines); user reactions to shipped output update it via `record`. No profile yet = no bias, never a block.
 - **Stated-choice awareness:** if prior package picks are visible in the workspace, name them and say in one line why this pick repeats or differs — awareness, never forced rotation.
 - **Questions go to the user only when the answer changes the design** (theme, audience, density); everything else is inferred and marked inferred.
 
@@ -30,11 +30,11 @@ Step 1 ends with a preview block:
 - surface map with archetypes
 - planned deviations
 
-When a user is present, pause here **once** for confirm-or-redirect — a wrong pick costs one message now instead of a full build. Autonomous runs proceed. Either way the block goes to project memory — `record` it as decision lines heading this run's choices.
+When a user is present, pause here **once** for confirm-or-redirect — a wrong pick costs one message now instead of a full build. Autonomous runs proceed. Either way the block goes to workspace memory — `record` it as decision lines heading this run's choices, with the app as context.
 
 ## Outputs
 
-- `design.md` (project fork: chosen package + switch line + provenance + brief bindings; deviations accrue as they are recorded)
-- `product.md` written/updated
-- the project registered (or resumed) — `projectId` in the repo, the identity pin and the preview block recorded
+- `design.md` (project fork: chosen package + switch line + provenance + brief bindings; deviations accrue as they are recorded) — pushed as the workspace preference row
+- `product.md` written/updated and pushed
+- the identity pin and the preview block recorded
 - the chosen package's full design.md held in context

package/data/harnesses/code/skills/design/references/object-pass.md

@@ -15,7 +15,7 @@ Derive the object model and surface map using the UX-pattern decision layer (`re
 11. `state-matrix` — loading, the three empties (first-use, no-results, cleared), degraded, stale — per surface
 12. `standard-pages` / `ai-layer` / `dashboards` / `settings` — when the brief has them
 
-Each pass file carries its rule as prose; the current machine-readable decision table is the pass's catalog entry — `get_entry` the pass's ux-pass id when the step-2 decision needs it (curation edits the tables between skill releases; the served table is the authority) — and **follow the table's answer**. Disagreement is legitimate craft only when recorded — one `record` line naming the pass, the table's answer, yours, and why. An unrecorded divergence is the violation.
+Each pass file carries its rule as prose plus its machine-readable decision table; **follow the table's answer**. Disagreement is legitimate craft only when recorded — one `record` line naming the pass, the table's answer, yours, and why. An unrecorded divergence is the violation.
 
 When a pass fires a clarification code (an input the table needs that the brief doesn't give), resolve it: infer-and-mark when the answer doesn't change the design, ask when it does.
 

package/data/harnesses/code/skills/design/references/ship-gate.md

@@ -22,7 +22,7 @@ A Tier-1 failure blocks the ship; fix and re-run. Binary phrasing is the contrac
 
 ## Tier 2 — flags, never gates
 
-Sweep the operator tell list — fetched via `get_entry("tells")`, at this step only — plus the motion tells (`transition: all`; `ease-in` on an entrance; animation attached to a keyboard-triggered action). Flags cannot fail the build and trigger no in-run judging: each is **fixed or dismissed with one recorded line** through `record`, and every flag appears in the ship report for the human's eyes — numbers point eyes; they do not replace them. The validator may run this sweep warn-only after compose-step edits; nothing new ever fails the build mid-composition.
+Sweep `data/tells.csv` (the operator tell list), at this step only, plus the motion tells (`transition: all`; `ease-in` on an entrance; animation attached to a keyboard-triggered action). Flags cannot fail the build and trigger no in-run judging: each is **fixed or dismissed with one recorded line** through `record`, and every flag appears in the ship report for the human's eyes — numbers point eyes; they do not replace them. The validator may run this sweep warn-only after compose-step edits; nothing new ever fails the build mid-composition.
 
 ## The ship report
 

package/data/harnesses/code/skills/design/scripts/select-chart.mjs

@@ -2,10 +2,11 @@
 //
 // One graph question per call. The model authors the data-signature JSON (the judgment
 // half); this script computes elimination, scoring, ranking, and refusal (the mechanical
-// half) over the chart-leaf census rows the caller supplies — fetched once per session
-// via the design-mcp entry "chart-census" and passed in the signature's `census` array
-// (engines local, knowledge served). Deterministic: same signature + census in, same
-// output out. No network, stdlib only.
+// half) over the chart-leaf census at ../data/charts/census.csv — the census and this
+// engine are one designed artifact and ship together (dimension-placement chapter 12).
+// Callers may pass explicit census rows (module arg or the signature's `census` array);
+// the local CSV is the default. Deterministic: same signature + census in, same output
+// out. No network, stdlib only.
 //
 // OUTPUT CONTRACT (docs/features/design-skill/07-evaluation-integrity.md §B1 — exact):
 //   {
@@ -279,11 +280,16 @@ export function parseCensusCsv(text) {
   });
 }
 
-// Accepts census rows as served by design-mcp's "chart-census" entry (slug/ord, flags as
-// pipe-joined strings) or already in the engine's leaf shape, and normalizes onto it.
+export function loadDefaultCensus() {
+  const censusPath = path.join(path.dirname(fileURLToPath(import.meta.url)), '..', 'data', 'charts', 'census.csv');
+  return parseCensusCsv(fs.readFileSync(censusPath, 'utf8'));
+}
+
+// Accepts census rows in the engine's leaf shape (or a row shape with snake_case columns
+// and pipe-joined flag strings) and normalizes onto the leaf shape.
 export function normalizeCensusRows(rows) {
   if (!Array.isArray(rows) || rows.length === 0) {
-    throw new Error('census rows are required — fetch them once per session via the design-mcp entry "chart-census" and pass them in the signature\'s `census` array');
+    throw new Error('census rows are required — the shipped census at data/charts/census.csv is the default');
   }
   const toFlagList = (value) =>
     Array.isArray(value) ? value : value == null || value === '' ? [] : String(value).split('|').map((f) => f.trim());
@@ -547,7 +553,7 @@ export function selectChart(input, censusRows) {
   if (input == null || typeof input !== 'object' || Array.isArray(input)) {
     throw new Error('selectChart: input must be a data-signature object');
   }
-  const census = normalizeCensusRows(censusRows ?? input.census);
+  const census = normalizeCensusRows(censusRows ?? input.census ?? loadDefaultCensus());
   const { flags, structure } = deriveFlags(input);
 
   const refusal = deriveRefusal(input, structure);

package/data/harnesses/code/skills/design/scripts/validate-design-md.mjs

@@ -188,7 +188,7 @@ class YamlError extends Error {}
 
 const isObj = (v) => v !== null && typeof v === "object" && !Array.isArray(v);
 
-function parseYaml(src, label) {
+export function parseYaml(src, label) {
     const rawLines = src.split(/\r?\n/);
     const lines = [];
     for (let i = 0; i < rawLines.length; i++) {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nurix/etna",
-    "version": "0.19.51",
+    "version": "0.19.53",
     "description": "Bootstrap a project with a Nurix harness — copies the harness's CLAUDE.md, skills, agents, rules, and hooks directly into the project from a bundled payload (no marketplace fetch, no network).",
     "type": "module",
     "bin": {
@@ -42,5 +42,5 @@
         "agent",
         "plugin"
     ],
-    "etnaFingerprint": "add8db2442a5"
+    "etnaFingerprint": "b90b7910764f"
 }