@design-intelligence/ghost 0.29.0 → 0.31.0

package/dist/init-payloads/{vessel-light/anti-goal.median.md → median/standard.model-defaults.md}

@@ -1,10 +1,14 @@
 ---
-context: Any greenfield visual surface or first-draft copy.
+for: Any greenfield visual surface or first-draft copy.
 ---
 
-This is the model's median, not your brand. Each rule is reject→replace.
-Delete every line your brand legitimately violates — `ghost validate` will
-warn on any check reference the deletion orphans — delete the paired flag too.
+Shared defaults: the model's median, not your brand. Every rule below is a
+**Default** — a starting position that protects unsteered work from generic
+model behavior, never an obligation. Explicit brand guidance in the cover, a
+foundation, or a matching context may deliberately replace any of them.
+Each rule is reject→replace. Delete every line your brand legitimately
+violates — `ghost validate` will warn on any check reference the deletion
+orphans — delete the paired flag too.
 
 These are not aesthetic opinions. Where a count is given, it is the measured
 convergence of 300 unsteered generations across three frontier models (the

package/dist/init-payloads/skeleton/brand.md

@@ -1,14 +1,13 @@
 ---
-context: Any task that should express this brand.
+for: Any task that should express this brand.
 ---
 
 This cover is unwritten. ghost gather always places this page in an agent's
 context; that is delivery status, not a claim that every sentence applies to
 every task. Use it for what cannot be retrieved by task: what this brand is about,
 in one paragraph, in the brand's own voice. The temperature its words and
-motion share. And the refusals only this brand makes — not generic don'ts
-(those live in each foundation's misuse list, and the model's cliches live
-in the cliche nodes), but the lines this brand alone draws.
+motion share. And the refusals only this brand makes — not generic don'ts,
+but the lines this brand alone draws.
 
 Until a human writes it, the working stance is: quiet, precise, content
 first, decoration never. Treat that as provisional and say so in your
@@ -19,5 +18,10 @@ single element, it belongs in that element's chapter. In a single view, it
 belongs in the composition foundation. Only across the whole body of work —
 temperature, density, restraint — it belongs here.
 
+Generic don'ts do not live here either: element-scoped rejections live in
+each foundation's Never section, and the model's measured defaults live in
+the shared `standard.model-defaults` node. This page holds only the refusals
+this brand alone makes.
+
 The budget is one screen. When this page is real, delete every sentence of
 scaffolding above — including this one.

package/dist/init-payloads/skeleton/context.conversation.md

@@ -1,24 +1,33 @@
 ---
-context: Chat threads, agent consoles, and prompt composers.
+for: Chat threads, agent consoles, and prompt composers.
 ---
 
 In this context: AI conversation threads, agent consoles, review assistants,
 and prompt composers. Elsewhere, the defaults hold.
 
+## Usage
+
 Conversation UI is not chat cosplay. The assistant speaks on the page
-surface as plain text: no bubble, no border, no fill. Wrapping assistant
-messages in cards makes the system look defensive and wastes density —
-hierarchy comes from prose, spacing, and type.
+surface as plain text — hierarchy comes from prose, spacing, and type.
+Wrapping assistant messages in cards makes the system look defensive and
+wastes density. Tool calls are operational evidence, not conversation.
+
+## Rules
 
-User turns are compact muted surfaces aligned right. They mark authorship
-without turning the thread into alternating balloons.
+- Assistant turns render as plain text on the page surface: no bubble, no
+  border, no fill.
+- User turns are compact muted surfaces aligned right — authorship marked
+  without turning the thread into alternating balloons.
+- Tool calls collapse to a labeled one-line summary with status; expand only
+  when the user asks, then show mono content inside the disclosed area.
+- The prompt input is one bordered surface. The textarea stays empty of
+  controls; attachments, model choice, and send live in a single row below
+  it.
+- Stop and send are mutually exclusive states of the same action area.
 
-Tool calls are operational evidence. Collapse them to a labeled one-line
-summary with status; expand only when the user asks, then show mono content
-inside the disclosed area.
+## Never
 
-The prompt input is one bordered surface. The textarea stays empty of
-controls so writing remains the focus; attachments, model choice, and send
-live in a single row below it. There is one primary send action — stop and
-send are mutually exclusive states of the same action area, never two
-competing primaries.
+- Never wrap assistant messages in cards or bubbles — plain text on the
+  page surface.
+- Never render two competing primary actions in the composer — stop and
+  send share one action area.

package/dist/init-payloads/skeleton/foundation.color.md

@@ -1,39 +1,47 @@
 ---
-context: Choosing or applying color.
+for: Choosing or applying color.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 Color is assigned by role, not by taste. The roles are the source of truth;
 raw color values are implementation detail, never product language. If a
-container needs a color, it first needs a role: `background`, `foreground`,
-`card`, `popover`, `primary`, `secondary`, `muted`, `accent`, `border`,
-`input`, `ring`, and the status roles.
-
-The status roles — destructive, success, warning, info — exist only when
-meaning demands them. Destructive means destructive or error. Success means
-success. None of them are brand accents.
-
-One view does not perform a color palette. If a status color is present, the
-rest of the view stays on the base roles. Richness beyond this comes from a
-closed expression set (`--expression-*`), used at the volume the situation
+container needs a color, it first needs a role. Richness beyond the base
+spine comes from a closed expression set, used at the volume the situation
 allows — a marketing page may turn it up; a settings form stays quiet.
 
-## Palette
-
-Open — ask the human; do not freehand. The fixed relationship: a quiet base
-spine is the default atmosphere in every medium, and a closed expression set
-supplies the rest, its volume set by situation, never by taste. The open
-question: what is this brand's base spine, and what are the named hues of
-its expression set — how many, and which? When the human answers, restate
-this section as the brand's current answer and record the values where your
-materials live. Until then, proceed with a quiet provisional spine and label
-it provisional.
-
-## Misuse
-
-- Status colors never moonlight as atmosphere, in any context.
-- Expression never touches what you click. Buttons, inputs, and links stay
-  on the base roles everywhere. A colored control is a different design
+The status roles exist only when meaning demands them. None of them are
+brand accents.
+
+## Rules
+
+- Every colored element uses a named role: `background`, `foreground`,
+  `card`, `popover`, `primary`, `secondary`, `muted`, `accent`, `border`,
+  `input`, `ring`, or a status role.
+- Status roles carry their meaning exactly: destructive means destructive or
+  error, success means success, warning warns, info informs.
+- When a status color is present, the rest of the view stays on the base
+  roles. One view does not perform a color palette.
+- Expression color comes only from the closed `--expression-*` set, at the
+  volume the situation allows.
+- Known gap — the palette is unanswered. The fixed relationship: a quiet
+  base spine is the default atmosphere in every medium, and a closed
+  expression set supplies the rest, its volume set by situation, never by
+  taste. The open question: what is this brand's base spine, and what are
+  the named hues of its expression set — how many, and which? Ask the human;
+  do not invent values. Until answered, proceed with a quiet provisional
+  spine and label it provisional. When answered, restate this rule as the
+  brand's current answer and record the values where your materials live.
+
+## Never
+
+- Never use status colors as atmosphere, in any context — status color
+  appears only where its meaning applies.
+- Never put expression color on what you click. Buttons, inputs, and links
+  stay on the base roles everywhere; a colored control is a different design
   system.
-- No one-off hex values. If a color has no role, it has no place.
+- Never use a one-off hex value — if a color has no role, it has no place;
+  give it a role or delete it.

package/dist/init-payloads/skeleton/foundation.composition.md

@@ -1,30 +1,32 @@
 ---
-context: Assembling any view.
+for: Assembling any view.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 Composition is the layer above layout: layout gives the stacks and gaps;
 composition decides what dominates, what recedes, and what comes last.
+Primacy comes from scale, position, and space. Actions land last — the user
+reads, then decides.
 
-Every view has exactly one focal point — one element at the largest scale.
-If two elements compete for primacy, demote or delete one; never resolve
-the tie by making both big.
-
-One primary action per view: the action the view exists to complete.
-Everything else steps down the control ladder (see the controls
-foundation). If two buttons both look primary, the composition failed.
-
-Actions land last. Calls to action render at the end of reading order —
-the user reads, then decides.
+## Rules
 
-Separation escalates: whitespace first, then a divider, then a container —
-in that order, never skipping a step.
+- Every view has exactly one focal point — one element at the largest scale.
+  If two elements compete for primacy, demote or delete one.
+- One primary action per view: the action the view exists to complete.
+  Everything else steps down the control ladder (see the controls
+  foundation).
+- Calls to action render at the end of reading order.
+- Separation escalates: whitespace first, then a divider, then a container —
+  in that order, never skipping a step.
 
-## Misuse
+## Never
 
-- Never fake a focal point with decoration. Primacy comes from scale,
+- Never fake a focal point with decoration — primacy comes from scale,
   position, and space.
 - Never promote a second action to primary because something wants
-  emphasis; step the other one down instead.
+  emphasis — step the other one down instead.
 - Never separate with a container when whitespace would do.

package/dist/init-payloads/skeleton/foundation.controls.md

@@ -1,7 +1,10 @@
 ---
-context: Any view with actions or inputs.
+for: Any view with actions or inputs.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 The control emphasis ladder is exactly five rungs: primary, secondary,
@@ -12,18 +15,23 @@ may hold is a composition rule — see the composition foundation: one.
 Destructive is a meaning, not a rung. It is rare, it names the destructive
 act directly, and it is never borrowed for urgency, emphasis, or brand heat.
 
-Fields are quiet until active: hairline border, muted placeholder, clear
-label, and a focus ring when the user engages. The ring is guidance, not
-decoration. Errors state facts next to the field that caused them — never
-hidden in modals, toasts, or generic banners when the user needs to fix one
-input.
+Fields are quiet until active. The focus ring is guidance, not decoration.
+
+## Rules
 
-Controls take the control radius; see the layout foundation for the two
-radius roles.
+- Every action picks a rung from the five-rung ladder; no invented emphasis
+  levels.
+- Fields render with a hairline border, muted placeholder, clear label, and
+  a focus ring when the user engages.
+- Errors state facts next to the field that caused them — never hidden in
+  modals, toasts, or generic banners when the user needs to fix one input.
+- Controls take the control radius; see the layout foundation for the two
+  radius roles.
 
-## Misuse
+## Never
 
-- Never two competing primary buttons.
-- Never destructive styling as attention-getting.
-- Never expression color on a control — what you click stays on the base
-  roles everywhere.
+- Never render two competing primary buttons — step one down the ladder.
+- Never use destructive styling as attention-getting — destructive names a
+  destructive act, nothing else.
+- Never put expression color on a control — what you click stays on the
+  base roles everywhere.

package/dist/init-payloads/skeleton/foundation.layout.md

@@ -1,45 +1,49 @@
 ---
-context: Laying out any view.
+for: Laying out any view.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 All layout is stacks. Rhythm comes from relationships between siblings, not
-from isolated margins pasted onto whichever element was last touched. The
-gap steps are exactly five: `--gap-xs` through `--gap-xl`. Choose the gap
-that states the relationship; do not tune by single pixels to make a
+from isolated margins pasted onto whichever element was last touched. Choose
+the gap that states the relationship; do not tune by single pixels to make a
 screenshot pass. The default is column, medium gap. Columns are for almost
 everything — forms, cards, modal bodies, settings, page sections. Rows are
 conditional: controls, metadata lines, paired label/value moments. If a row
 wraps awkwardly, it wanted to be a column.
 
 Surface is the only way an element gets a background, border, radius, or
-shadow. The vocabulary is closed: role, padding, radius, border, elevation.
-The default surface is flat — no border, no shadow. We do not outline
-everything to prove layout exists.
-
-The elevation tiers are exactly three: card, popover, modal. Elevation
-implies hierarchy — a card sits in flow, a popover floats above it, a modal
-interrupts the task. Pick the tier that matches the interaction.
+shadow. The default surface is flat — no border, no shadow. We do not
+outline everything to prove layout exists. Elevation implies hierarchy — a
+card sits in flow, a popover floats above it, a modal interrupts the task.
 
 Borders are structural — inputs and overlays — not decorative frames around
 ordinary text. Use space, tone, and type hierarchy instead.
 
-## Radius
-
-Open — ask the human; do not freehand. The fixed relationship: controls and
-surfaces carry different radius roles, and the two never swap. Buttons and
-inputs take `--radius-control`; cards and containers take
-`--radius-surface`. One radius for what you click, one for what contains.
-The open question: how round is a control, and how round is a surface? When
-answered, restate this section as the brand's current answer. Until then,
-choose provisional values and label them.
-
-## Misuse
-
-- No ad-hoc margins between siblings — they hide the rhythm. Change the
-  stack gap or split the stack.
-- No custom shadows because a composition feels flat, and no modal gravity
-  on a routine card. Component shadows belong to the primitives that own
-  them.
-- Never one radius everywhere by reflex.
+## Rules
+
+- The gap steps are exactly five: `--gap-xs` through `--gap-xl`.
+- The surface vocabulary is closed: role, padding, radius, border,
+  elevation.
+- The elevation tiers are exactly three: card, popover, modal. Pick the
+  tier that matches the interaction.
+- Buttons and inputs take `--radius-control`; cards and containers take
+  `--radius-surface`. The two never swap.
+- Known gap — the radius values are unanswered. The fixed relationship: one
+  radius for what you click, one for what contains. The open question: how
+  round is a control, and how round is a surface? Ask the human; do not
+  invent values. Until answered, choose provisional values and label them.
+  When answered, restate this rule as the brand's current answer.
+
+## Never
+
+- Never add ad-hoc margins between siblings — they hide the rhythm; change
+  the stack gap or split the stack.
+- Never add a custom shadow because a composition feels flat, and never give
+  modal gravity to a routine card — component shadows belong to the
+  primitives that own them.
+- Never apply one radius everywhere by reflex — the control and surface
+  roles exist to differ.

package/dist/init-payloads/skeleton/foundation.motion.md

@@ -1,34 +1,40 @@
 ---
-context: Any transition, animation, or hover treatment.
+for: Any transition, animation, or hover treatment.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 Motion is evidence of a state change. It confirms hover, press, reveal,
 collapse, entrance, exit, and spatial movement. It does not entertain.
-
-The entire vocabulary is three duration roles and one ease. Fast is for
-hover and press. Normal is for reveals, fades, and small state changes. Slow
-is reserved for spatial transitions where the user needs to understand
-movement. Prefer opacity and small transforms.
+Prefer opacity and small transforms.
 
 In editorial and marketing contexts, entrances may be staged — scroll
 reveals and section transitions are part of editorial rhythm, still built
 from the three durations and the one ease. In product UI the same staging is
 decoration.
 
-## Character
+## Rules
 
-Open — ask the human; do not freehand. Motion and voice share one
-temperature: however warm or cool the brand's words are, its movement
-matches. See the voice foundation for the other half of this answer. The
-open question here: what character does the one ease carry? When answered,
-restate this section. Until then, use a quiet standard ease and label it
-provisional.
+- The entire vocabulary is three duration roles and one ease.
+- Fast is for hover and press. Normal is for reveals, fades, and small
+  state changes. Slow is reserved for spatial transitions where the user
+  needs to understand movement.
+- Known gap — the ease's character is unanswered. Motion and voice share
+  one temperature: however warm or cool the brand's words are, its movement
+  matches; see the voice foundation for the other half. The open question:
+  what character does the one ease carry? Ask the human; do not invent an
+  answer. Until answered, use a quiet standard ease and label it
+  provisional. When answered, restate this rule as the brand's current
+  answer.
 
-## Misuse
+## Never
 
-- Nothing loops except explicit loading states. Decorative pulsing,
+- Never loop anything except explicit loading states — decorative pulsing,
   floating, glowing, and attention-seeking keyframes are off-language.
-- No novelty easings because a surface feels static.
-- If removing an animation does not reduce comprehension, it was decoration.
+- Never reach for a novelty easing because a surface feels static — fix
+  spacing, copy, and hierarchy first.
+- Never keep an animation whose removal would not reduce comprehension — it
+  was decoration.

package/dist/init-payloads/skeleton/foundation.type.md

@@ -1,44 +1,51 @@
 ---
-context: Any view containing text.
+for: Any view containing text.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 Hierarchy is a closed vocabulary, not a size slider. Every piece of text
 picks from a named set; anything outside the set is a broken primitive, not
-a variant.
-
-The text variants are exactly six: display, headline, title, body, label,
-mono. Variant names are jobs. Display leads a rare editorial moment.
-Headline names a section. Title anchors a card, dialog, or compact region.
-Body carries reading. Label names structure — field labels, category tags,
-metadata, compact status. Mono carries code and machine detail.
+a variant. Variant names are jobs: display leads a rare editorial moment,
+headline names a section, title anchors a card, dialog, or compact region,
+body carries reading, label names structure — field labels, category tags,
+metadata, compact status — and mono carries code and machine detail.
 
-The tones are exactly seven: default, muted, inverse, success, warning,
-info, destructive. Tone is part of the message. Hierarchy starts with tone
-and weight before size — a secondary note usually wants muted body or label,
-not a smaller custom font. If prose needs emphasis, improve the sentence
-before adding a style.
+Tone is part of the message. Hierarchy starts with tone and weight before
+size — a secondary note usually wants muted body or label, not a smaller
+custom font. If prose needs emphasis, improve the sentence before adding a
+style.
 
 The heading scale is editorial: it exists for pages composed outside the
 text variants — heroes and editorial moments. Product UI never mixes the two
 vocabularies in one view. A modal title is not a poster.
 
-Balanced text is for headings and compact statements, never long body copy.
-
-## Typeface
-
-Open — ask the human; do not freehand. The fixed relationship: one typeface
-is the voice of the interface, everywhere, with a mono partner only for
-code, tool detail, and machine output. The open question: what typeface is
-this brand's voice, what mono partners it, and what rhythm does the
-editorial heading scale carry? When answered, restate this section as the
-brand's current answer. Until then, choose a quiet provisional pair and
-label it provisional.
+## Rules
 
-## Misuse
-
-- No faked hierarchy with arbitrary font sizes. Choose the variant that
-  matches the job.
+- The text variants are exactly six: display, headline, title, body, label,
+  mono.
+- The tones are exactly seven: default, muted, inverse, success, warning,
+  info, destructive.
 - Status tones appear only when the words carry that state meaning.
-- Never a second display face to make a view feel branded.
+- Balanced text is for headings and compact statements, never long body
+  copy.
+- Known gap — the typeface is unanswered. The fixed relationship: one
+  typeface is the voice of the interface, everywhere, with a mono partner
+  only for code, tool detail, and machine output. The open question: what
+  typeface is this brand's voice, what mono partners it, and what rhythm
+  does the editorial heading scale carry? Ask the human; do not invent
+  values. Until answered, choose a quiet provisional pair and label it
+  provisional. When answered, restate this rule as the brand's current
+  answer.
+
+## Never
+
+- Never fake hierarchy with arbitrary font sizes — choose the variant that
+  matches the job.
+- Never apply a status tone to words that do not carry that state meaning —
+  use default or muted instead.
+- Never add a second display face to make a view feel branded — brand
+  expression comes from the one voice, scale, and composition.

package/dist/init-payloads/skeleton/foundation.voice.md

@@ -1,7 +1,10 @@
 ---
-context: Writing or editing any copy.
+for: Writing or editing any copy.
 ---
 
+Starter guidance the brand owner has not yet reviewed. Cite it as provisional
+until a human edits or confirms this chapter.
+
 ## Usage
 
 Copy states what happened, what is possible, or what the user must decide.
@@ -12,18 +15,20 @@ Voice and motion carry the same temperature: a brand whose copy is warm does
 not move coldly, and a brand whose copy is spare does not bounce. When you
 set one, check the other.
 
-## Warmth
+## Rules
 
-Open — ask the human; do not freehand. The open question: how warm or cool
-does this brand sound — and, by the shared temperature, how does it move?
-See the motion foundation for the other half. When answered, restate this
-section as the brand's current answer. Until then, write plainly and label
-the tone provisional.
+- Error and failure copy states the fact and the next step.
+- Known gap — the warmth is unanswered. The open question: how warm or cool
+  does this brand sound — and, by the shared temperature, how does it move?
+  See the motion foundation for the other half. Ask the human; do not invent
+  an answer. Until answered, write plainly and label the tone provisional.
+  When answered, restate this rule as the brand's current answer.
 
-## Misuse
+## Never
 
-- No exclamation points as a substitute for having something to say.
-- No apologizing for the interface ("Oops!"). State the fact and the next
+- Never use exclamation points as a substitute for having something to
+  say — state the fact.
+- Never apologize for the interface ("Oops!") — state the fact and the next
   step.
-- Never restate this section as answered when it was your own provisional
-  choice.
+- Never restate an open question as answered when the answer was your own
+  provisional choice — label it provisional until a human confirms it.

package/dist/init-payloads/skeleton/glossary.md

@@ -1,39 +1,51 @@
 ---
 kinds:
+  - name: standard
   - name: foundation
   - name: context
-  - name: cliche
 ---
 
+# standard
+
+Shared guidance that is not specific to this brand. Every rule carries one of
+two authority labels. An **Obligation** is a requirement brand preference
+cannot waive — accessibility, safety, honesty, functional integrity; the
+brand controls how it is expressed, not whether it holds. A **Default** is a
+recommended starting position that protects unsteered work from generic model
+behavior; explicit brand guidance in the cover, a foundation, or a matching
+context may deliberately replace it. When a default with a paired check is
+overridden, adapt or remove the check flag in the same change.
+
 # foundation
 
-The core elements — color, type, controls, layout, motion, voice — plus
-composition, the rules for assembling them into a view. Each foundation
-node is a chapter: usage rules that hold no matter what the brand values
-turn out to be, the brand's open questions (unanswered in this starter,
-marked as decisions only a human can make), and the chapter's misuse list.
-Follow the usage rules as written. Never fill in an open value and present
-it as the brand's.
+The brand's load-bearing decisions — color, type, controls, layout, motion,
+voice, and composition, the rules for assembling them into a view. Each
+foundation node is a chapter: usage law that holds no matter what the brand
+values turn out to be, the brand's open questions (unanswered in this
+starter, marked as decisions only a human can make), and the chapter's
+rejected moves. Follow the rules as written. Never fill in an open value and
+present it as the brand's. A brand carries only the foundations its evidence
+supports; these chapters are subjects, not mandatory slots.
 
 # context
 
 Where the defaults bend: a context names a situation — an AI conversation
 thread, a data-dense console, a transactional email — and states only what
-inverts there. Read a context only when its situation matches the task.
-Rules from the wrong context are contamination, not guidance.
-
-# cliche
-
-The defaults a generative model falls back on when no brand is steering it.
-These are nobody's brand. Each entry pairs the tired move with the honest
-replacement. Gather before styling anything greenfield; enforced by paired
-checks at review.
+inverts there. A situation may combine surface, channel, modality, audience,
+or moment. Read a context only when its situation matches the task. Rules
+from the wrong context are contamination, not guidance.
 
 ---
 
+Node bodies in this package follow one shape: `## Usage` carries the
+worldview and decision logic; `## Rules` carries observable requirements a
+reviewer can assess in the finished artifact; `## Never` pairs each rejected
+move with its replacement; an optional `## Skeleton` (always last) carries
+literal opening structure. A node includes only the sections it needs.
+
 The cover node (`brand.md`, declared in the manifest) is the one page always
 in context: what the brand is, its temperature, and the refusals only it
-makes. The ghost skill's `authoring` recipe explains how to grow this skeleton
-into a real ghost package: write the cover, answer each
-chapter's open question, prune the cliches your chapters absorb, then add
-materials and examples.
+makes. The ghost skill's `authoring` recipe explains how to grow this starter
+into a real ghost package: write the cover, answer each chapter's open
+question, prune the shared defaults your chapters absorb, then add materials
+and examples.

package/dist/init-payloads/vessel-light/checks/conversation-grammar.md

@@ -3,8 +3,8 @@ name: Conversation grammar
 description: Flags conversation UI that breaks plain assistant text, prompt-input structure, primary-action discipline, or collapsed tool output.
 severity: high
 references:
-  - grammar.conversation
-  - grammar.surfaces
+  - context.conversation
+  - foundation.surfaces
 ---
 
 Apply this check to diffs that touch AI threads, agent consoles, prompt composers, chat messages, or tool-call rendering.