@orkestrel/scaffold 0.0.63 → 0.0.65

package/dist/host/agents/skills/enterprise-bootstrap/references/inspection.md

@@ -1,20 +1,25 @@
 # Instruments
 
-Reach for an instrument here where a capture cannot settle the claim. Run every one with its negative
-control, in the same conditions, on the real compiled cascade the page loads. Treat an instrument
-whose negative control passes as broken and refuse its reading as evidence;
-`.claude/rules/quality.md` owns that law where it is present.
-
-Take each entry's property, population, reading, negative control, and coverage as written, and hold
-every entry to these rules.
-
-- **Report the population.** A reading carries the population it walked. An empty population fails
-  the run, because an extractor that quietly matched nothing satisfies every other assertion.
-- **Draw every negative control from outside the population.** Name the membership rule first, then
-  pick a negative control the rule excludes. Reject a negative control that rule admits.
-- **Enter a negative control through the same door the surface enters.** A negative control handed
-  straight to the reading tests the reading alone, so pair it with one appended to the tree, the stylesheet,
-  or the registry the instrument walks wherever the instrument has an extraction step.
+Reach for an instrument where a capture cannot settle the claim. Run it against the compiled
+cascade the page loads, with its negative controls under the same conditions. Treat a missed
+negative control as a broken instrument and refuse its reading as evidence;
+`.claude/rules/quality.md` owns that law where present.
+
+Keep mechanical results separate from visual judgments. Take each entry's property, population,
+reading, negative control, and coverage as its contract. Report failures and untested coverage, not
+a pass label alone.
+
+- **Report the population.** Name the membership rule and count what the extractor walked. An
+  expected but empty population fails. Mark a genuinely absent feature not applicable with its
+  reason; do not count it as passing.
+- **Keep controls independent.** Construct known-invalid fixtures in the harness, outside the
+  production population and the accepted set. Include them in the test run through the same
+  extraction path, and exclude them from production counts. Do not filter the defect out before
+  the reader can see it.
+- **Test extraction as well as reading.** Pair a directly fed fixture with one appended to the
+  tree, stylesheet, or registry wherever extraction exists. Remove harness mutations afterward.
+- **Bound the claim.** Name files, routes, themes, viewports, states, and exclusions actually read.
+  Unsupported input and unavailable tooling remain open, never passed by assumption.
 
 ## Contents
 
@@ -22,146 +27,229 @@ every entry to these rules.
 - [Declared class combinations](#declared-class-combinations)
 - [Style escapes](#style-escapes)
 - [Token discipline](#token-discipline)
+- [Declared design scales](#declared-design-scales)
 - [Custom rule doing a utility's job](#custom-rule-doing-a-utilitys-job)
+- [Color-mode inheritance](#color-mode-inheritance)
 - [Composited contrast in both themes](#composited-contrast-in-both-themes)
 - [One glyph, one meaning](#one-glyph-one-meaning)
+- [Responsive task and reflow](#responsive-task-and-reflow)
+- [Responsive interaction continuity](#responsive-interaction-continuity)
+- [Rendered design review](#rendered-design-review)
 - [When an authored rule is already earned](#when-an-authored-rule-is-already-earned)
 
 ## Authored class in the shipped cascade
 
-- **Property.** Every class token the surface's own templates and components author has a rule in
-  the compiled CSS the page loads.
-- **Population.** The class tokens the authored markup carries, read against every stylesheet the
-  page loads: the vendor build, each skin, and the project's own.
-- **Reading.** Subtract the tokens the loaded stylesheets define from the tokens the markup carries.
-  A remainder fails the run and names each token with the file that authored it. Report the token
-  population walked, and fail a run that walked none.
-- **Negative control.** A fed control and an appended control, each of which the reading must report.
-  Feed the first — a token no stylesheet defines — straight to the reading. Append the second through
-  the extraction door: an element built in the harness carrying that undefined token on an SVG
-  `class` attribute, added to the tree the reading walks. Each sits outside the population, which is
-  authored tokens the cascade resolves.
-- **Coverage.** The fed negative control covers the subtraction. The appended negative control covers the extractor,
-  and it is what fails a reading that never leaves the root or that drops SVG tokens by reaching for
-  `className`, where the value is an `SVGAnimatedString` rather than a string. Together they prove
-  authored tokens are a subset of the cascade. The instrument says nothing about a cascade rule
-  nobody authored, a token a build step or a script adds after the read, or whether a resolved rule
-  paints what the author intended.
+- **Property.** Every styling class the surface authors resolves in the loaded CSS. Separately name
+  legitimate behavior/test hooks that require no CSS; never excuse an intended utility as a hook.
+- **Population.** Authored class tokens, including SVG and conditional states, against vendor,
+  skin, dependency, generated-utility, and project stylesheets actually loaded.
+- **Reading.** Parse selectors, subtract the defined styling tokens from the authored set, and
+  report each unresolved token with its source. Enumerate declared conditional classes not reached
+  in the mounted tree separately; an unreachable stylesheet is an open dependency, not an empty one.
+- **Negative control.** Feed an undefined styling token to the reader, then append a harness SVG
+  carrying that token through the same tree extractor. Both must be reported.
+- **Coverage.** The two controls cover set comparison and extraction, including SVG's non-string
+  `className`. Use `getAttribute('class')` or an equivalent safe reader. Resolution does not prove
+  the rule wins the cascade, paints the intended result, or covers a state never enumerated.
 
 ## Declared class combinations
 
-- **Property.** Every multi-utility chrome string the surface reuses is declared once by name with
-  the invariant it holds, and the markup carries no undeclared combination.
-- **Population.** The declared combinations, each with its name and its invariant, and every
-  multi-utility string the authored markup carries.
-- **Reading.** Match each string in the markup against the declared set. An undeclared combination
-  fails and names the element that carries it.
-- **Negative control.** A fed control and an appended control, each of which the reading must refuse.
-  Feed the first — a string one utility away from a declared combination — straight to the reading.
-  Append the second through the extraction door: an element built in the harness carrying that same
-  undeclared string on an SVG `class` attribute, added to the tree the reading walks. Each sits
-  outside the declared set.
-- **Coverage.** The fed negative control covers the match against the declared set. The appended negative
-  control covers the extractor, and it is what fails a reading that never leaves the root or that drops SVG
-  tokens by reaching for `className`. Together they prove reused chrome is declared. The instrument
-  does not prove a declared invariant is true, and it does not read a single utility used alone.
-- **Never substitute a cancellation heuristic.** A rule that flags a string for its utility count, or
-  for mixing categories, refuses the legitimate transparent read chrome that keeps a read view and an
-  edit view from reflowing.
+- **Property.** Reused multi-utility chrome has one named declaration and a stated invariant.
+- **Population.** Declared combinations and the authored instances of those reusable patterns.
+  Declare the pattern scope; do not require a registry entry for every one-off layout string.
+- **Reading.** Compare token sets within that scope to the named contracts. Report an undeclared
+  or divergent instance. Keep utility order irrelevant unless the host's class merger makes it
+  meaningful; record that merger when it applies.
+- **Negative control.** Feed a combination one utility away from its contract, then append an
+  instance carrying that mutation through the same extractor, including an SVG fixture. Report both.
+- **Coverage.** This proves instances match declarations, not that an invariant renders correctly.
+  Pair geometry or contrast invariants with their own measurements. Never substitute utility-count
+  or mixed-category heuristics; a valid transparent read-only treatment can use several utilities.
 
 ## Style escapes
 
-- **Property.** The surface's own markup carries no `style` attribute and no `<style>` element.
-- **Population.** The elements of a freshly mounted, undriven tree — the surface as authored, before
-  any interaction drives it.
-- **Reading.** Collect every element carrying an inline declaration or an embedded style element and
-  report it with its markup. Any hit fails.
-- **Exemptions, declared by name.** Exempt the framework's own runtime styles and name each exemption
-  in the instrument: a Bootstrap Modal, Offcanvas, Collapse, or Dropdown writes inline styles as it
-  runs, and a conditional-visibility directive such as `v-show` emits `style="display: none"` at
-  mount. Run the reading on an undriven tree, because a reading taken after a journey drives the
-  surface reports on the framework rather than on the author.
-- **Negative control.** An element carrying an inline declaration, built in the harness rather
-  than taken from the surface, fed to the reading. It sits outside the surface's own markup and the
-  reading must report it.
-- **Coverage.** The instrument reads authored markup at mount. It does not see a style a component
-  writes after the person interacts, a rule authored in a stylesheet, or an escape inside a
-  third-party component's own markup.
+- **Property.** Authored markup carries no `style` attribute or `<style>` element.
+- **Population.** Authored templates and the freshly mounted, undriven tree. Keep source and mounted
+  readings distinct so generated framework styles are not mistaken for authored declarations.
+- **Reading.** Report inline declarations and embedded style elements with their source or element.
+  Record framework/runtime exemptions by producer and purpose, never a blanket component exemption.
+  Bootstrap overlay positioning and conditional-visibility directives may write runtime styles.
+- **Negative control.** Feed an element with an inline declaration, then append an inline-styled
+  element and a `<style>` element to the harness tree. Every non-exempt fixture must be reported.
+- **Coverage.** This covers authored and mount-time escapes, not later interactions or third-party
+  internals outside the declared scope. Drive later states separately when making claims about them.
 
 ## Token discipline
 
-- **Property.** No authored rule carries a literal color, and every custom paint resolves through a
-  token in each color mode the product ships.
-- **Population.** The project's own authored stylesheet rules, and the resolved value of each
-  custom-painted property in each color mode.
-- **Reading.** A literal color in an authored declaration fails. For each custom paint, read the
-  resolved value once per mode; a mode that leaves it unresolved fails, and so does a pair of modes
-  that resolve it identically where the design says the modes differ.
-- **Negative control.** A rule carrying a literal color, and a paint whose token the cascade does
-  not define, both fed to the reading rather than authored into the surface. Each sits outside the
-  population of authored rules that pass, and the reading must report both.
-- **Coverage.** The instrument covers authored rules and the paints it was given. It does not judge
-  whether the chosen token is the right one, and it reads no vendor rule and no inline declaration —
-  [Style escapes](#style-escapes) covers those.
+- **Property.** Literal colors live only in declared primitive definitions. Semantic and component
+  paint resolve through the declared token layers in each shipped color mode.
+- **Population.** Project-authored color declarations and token references, the named primitive
+  definition locations, and custom-painted properties reached in each theme and state.
+- **Reading.** Parse declarations, not color-looking text in comments or strings. Permit raw colors
+  only in the named primitive definitions; reject literals in component paint, unresolved or cyclic
+  references, and a component bypassing semantic tokens. Check RGB partners where consumed. A theme
+  pair may resolve identically unless the design contract requires it to differ.
+- **Negative control.** Accept a valid primitive definition as a positive fixture. Feed a literal
+  component fill and an undefined token reference; append both to a harness stylesheet through the
+  same extractor. The valid definition must survive and every invalid fixture must fail.
+- **Coverage.** This proves declared paint follows the token boundary in the read scope. It does not
+  prove mode adaptation, foreground ownership, legibility, or visual quality. Use Color-mode inheritance for the cascade contract. Vendor literals are not authored violations;
+  rendered contrast still measures their effect. Inline paint belongs to Style escapes.
+
+## Declared design scales
+
+- **Property.** Authored type, spacing, width, radius, and elevation treatments use declared roles,
+  shipped scale steps, or documented extensions rather than untracked one-off values.
+- **Population.** The project's scale/role definitions and authored declarations consuming them.
+  Include breakpoint rules, component variants, and any declared fluid sizing formulas.
+- **Reading.** Resolve each treatment to its role or accepted step. Report undeclared values,
+  missing generated selectors, `em` font sizes, and `.small` nested inside `.small`. Validate fluid formulas against their declared bounds; do not reject
+  legitimate intermediate computed values as off-scale. Confirm required grouping relationships in
+  the rendered review rather than inferring them from token names.
+- **Negative control.** Feed an undeclared spacing value and append an off-scale type declaration
+  through the stylesheet extractor. Report both. Accept a declared fluid value inside its bounds.
+- **Coverage.** This checks consistency with a system, not whether the system suits the task. A
+  perfectly on-scale layout can still have ambiguous grouping, poor line breaks, or the wrong density.
 
 ## Custom rule doing a utility's job
 
-- **Property.** Every authored selector expresses something no shipped utility expresses, or records
-  the reason the utility does not fit.
-- **Population.** The selectors in the project's own stylesheets.
-- **Reading.** For each selector, name the utility that would carry the same declarations. A selector
-  a shipped utility already expresses fails unless it carries the recorded reason.
-- **Negative control.** A rule restating a shipped utility exactly — a padding declaration matching
-  a spacing step — fed to the reading rather than authored into the stylesheet. It sits outside the
-  set of authored selectors that pass, and the reading must report it.
-- **Coverage.** The instrument reads declarations, not intent. A rule that does a utility's job
-  alongside something else passes it, so a person still reads the authored stylesheet.
+- **Property.** Each authored selector expresses a need no shipped utility expresses, or records
+  why the utility does not fit. Declared component-variable overrides and generated utilities stay
+  on their extension rung; they are not automatically bespoke styling violations.
+- **Population.** Project-authored selectors, their declarations, and the loaded utility rules.
+- **Reading.** Compare declarations and name the equivalent utility when one exists. Report a
+  duplicate without a recorded reason. Read mixed-purpose rules too; adding an unrelated declaration
+  does not excuse the duplicated part.
+- **Negative control.** Feed a rule that exactly repeats a shipped padding utility, then append it
+  through the stylesheet extractor. Report it in both runs.
+- **Coverage.** This checks expressible equivalence, not the intent or merit of an exception. Review
+  the reason and styling-rung authorization separately; specificity and state scope can matter.
+
+## Color-mode inheritance
+
+- **Property.** Ordinary content inherits its body or component foreground. Quiet adaptive fills
+  add no arbitrary text color. Intentional solid and local-mode boundaries own a measured pair;
+  native component states retain their foreground behavior. Take the contract from
+  [color-modes.md](color-modes.md).
+- **Population.** Rendered text, status marks, badges, tags, links, fields, selected controls, table
+  cells, and overlays in the actual loaded build. Include supported nested modes, skin overrides,
+  and portal mount points; name the boundaries that own an explicit foreground.
+- **Reading.** Drive the existing mounted tree from light to dark and back. Read computed text,
+  painted backgrounds, relevant custom properties, and winning declarations after each transition.
+  Confirm quiet ordinary text matches its intended inherited foreground; identify the owner when
+  a component legitimately differs. Check supported system preference and reload behavior when the
+  mode controller is in scope. A class-name match or a changing variable alone does not pass.
+- **Negative control.** Add fixed `text-dark` on a dark body surface, a stock `.badge` with a subtle
+  fill but no inheritance reset in light mode, and an opposite-mode plain region without its owned
+  foreground/background pair. Require the reader to detect each violated contract. For projects
+  using aliases, add a root-resolved foreground alias inherited into an opposite-mode scope.
+  Verify each control is invalid in that build; a class name alone does not establish the defect.
+- **Coverage.** Pair the cascade reading with Composited contrast; correct inheritance can still
+  produce insufficient contrast on a changed surface. An isolated stock fixture establishes only
+  that fixture's behavior, not the host skin or application. Unreached states and mounts stay open.
 
 ## Composited contrast in both themes
 
-- **Property.** Every pairing the surface paints meets its bar in every theme: 4.5:1 for anything
-  information-bearing, 3:1 for textless marks and the chrome that carries state.
-- **Population.** The pairings the surface renders, read per theme on the compiled cascade, with
-  every translucent layer composited. Exempt disabled controls, per [SKILL.md](../SKILL.md) →
-  Surfaces, color, contrast.
-- **Reading.** Composite the painted layers, read the ratio, and fail anything under its bar with the
-  pairing named. Take the mechanics from [bootstrap-reference.md](bootstrap-reference.md) → Measuring
-  the bars.
-- **Negative control.** An opaque pairing and a translucent stack, each of which the reading must
-  fail. Compose the opaque pairing in the harness at a ratio known to sit under the bar. Compose the
-  stack with a translucent layer over a floor, so its composited ratio sits under the bar while its
-  top layer read alone sits above it. Each is composed in the harness rather than taken from the
-  surface, so each sits outside the rendered population.
-- **Coverage.** The opaque pairing covers the ratio arithmetic. The translucent stack covers the
-  compositing step, and it is what fails a reader that takes the top layer's declared color and skips
-  the layers under it. Together they measure what rendered, in the themes and viewports the run
-  entered. A pairing that appears only in a state the run never reached is unmeasured, so name the
-  states the run covered beside the result.
+- **Property.** Every measured pairing meets the package bar: 4.5:1 for information-bearing text,
+  3:1 for meaningful textless marks and state/focus chrome, in each declared theme and reached state.
+- **Population.** Rendered text and meaningful graphics, their actual surfaces, and all paint layers
+  affecting contrast. Name exemptions for disabled controls; do not exempt readable metadata.
+- **Reading.** Composite translucent backgrounds onto the opaque base and translucent foregrounds
+  onto that result before calculating contrast. Include ancestor opacity where relevant. Report the
+  pairing, ratio, bar, theme, and state for each failure. Take the mechanics from
+  [bootstrap-reference.md](bootstrap-reference.md) → Measuring the bars.
+- **Negative control.** Feed an opaque pair known to fail and a translucent stack whose composited
+  ratio fails although a flat read would pass. Append both through the rendered-pair extractor and
+  require all failures. Include the same theme scopes and paint mechanism as the production run.
+- **Coverage.** Flat computed colors cannot settle text over images, gradients, masks, blend modes,
+  or unsupported compositing. Read the actual background under the text with an appropriate method,
+  or mark the pairing open. Never average an image into a passing color. Name unvisited states;
+  measurements from one surface, theme, or crop do not establish another.
 
 ## One glyph, one meaning
 
-- **Property.** Each status meaning takes one glyph, each glyph serves one meaning, and every
-  registered glyph resolves in the icon set the product actually ships.
-- **Population.** The registry of meanings and glyphs the surface uses, and the shipped icon set.
-- **Reading.** A meaning registered twice, a glyph registered against two meanings, or a glyph the
-  shipped set does not resolve fails, each named.
-- **Negative control.** A registry entry binding a second meaning to a glyph already registered,
-  plus a glyph name the shipped set lacks. Both sit outside the registered set, and the reading must
-  report both.
-- **Coverage.** The instrument proves the registry is consistent and resolvable. It does not prove
-  the markup draws the registered glyph for the meaning it carries, so pair it with a capture of the
-  states that use marks.
+- **Property.** Each registered status meaning takes one glyph; each registered glyph serves one
+  status meaning and resolves in the icon set the product ships.
+- **Population.** The surface's status registry and the shipped icon set. Keep generic action icons
+  outside this status-only contract unless the project explicitly includes them.
+- **Reading.** Report duplicate meanings, a status glyph bound to two meanings, and missing glyphs.
+- **Negative control.** Feed a second meaning for a registered glyph and an unavailable glyph name;
+  append equivalent invalid entries through the registry extractor. Report both kinds of failure.
+- **Coverage.** This proves registry consistency, not that the markup uses the correct glyph or that
+  its optical size and contrast work. Capture the states that use the marks and inspect their names.
+
+## Responsive task and reflow
+
+- **Property.** The declared task remains readable and operable without unintended page overflow,
+  concealed content, or clipped controls at the widths in [responsive-layout.md](responsive-layout.md).
+- **Population.** Changed routes, responsive regions, required task fields/actions, local scrollers,
+  and their reached data states. Include conditional content and loaded fonts/assets. Name the
+  Bootstrap build and every environment substitution; a missing dependency is not a passing page.
+- **Reading.** Record viewport and container bounds, document width, local client/scroll dimensions,
+  critical text bounds, effective target sizes, and required content/action visibility. Check both
+  sides of each actual transition. Use a small declared rounding tolerance. Keep intentional data
+  scrolling separate from document overflow; identify the owner and prove reach to its final item.
+  Read task regions as well as `documentElement.scrollWidth`; hidden overflow is not a repair.
+- **Negative control.** Feed a too-wide region to the bounds reader; append an oversized child,
+  conceal it behind a clipping parent, and hide a required primary action in separate harness runs.
+  Each defect must be reported by the same production extraction path. Include a positive local
+  table scroller so the reader cannot pass by banning all overflow.
+- **Coverage.** Test 320/390 CSS px, a wide view, each used boundary, long content, and short height.
+  Record enlarged-text and real browser-zoom tests separately. Reducing the viewport is a reflow
+  proxy, not execution of 400% browser zoom. Geometry does not establish aesthetics, full text
+  contrast, real-device keyboard behavior, or an exhaustive accessibility result.
+
+## Responsive interaction continuity
+
+- **Property.** Narrow/wide changes preserve access, state, and meaningful focus; responsive chrome
+  does not leave a stale overlay, scroll lock, or trap.
+- **Population.** Navigation triggers/panels, forms, selections, filters, sort/pagination, disclosures,
+  and overlays changed by a breakpoint. Record which controls are functional and which are fixtures.
+- **Reading.** Complete the narrow primary flow. Open/close navigation with pointer and keyboard,
+  test Escape/focus return, resize while open, and return below the threshold. Carry selected IDs,
+  filters, sort, field values, and active detail context through both directions. Check reachable
+  dialog actions in a short viewport and with enlarged text. Confirm actual row/filter changes,
+  not merely `aria-sort`, labels, or a success message.
+- **Negative control.** Remove the required narrow trigger, break its target, and erase a selected
+  record during a harness resize. Drive the same interaction assertions; each must fail. Mark an
+  absent component not applicable rather than treating an empty locator set as success.
+- **Coverage.** Desktop mouse, keyboard, and emulated touch are separate runs. Keep real-device
+  browser chrome/soft keyboard, unsupported engines, persistence, and server actions open unless
+  exercised. For dual presentations, inspect IDs and the accessibility tree: only the active view
+  may expose its controls. Attribute presence alone does not establish any interaction result.
+
+## Rendered design review
+
+Use captures for these judgments, not synthetic negative controls. Record the criterion, capture,
+viewport/theme/state, finding, and disposition. A missing capture leaves the judgment open. For a
+requested review round or campaign, use `orkestrel-polish-surface` rather than creating one here.
+
+- **Task and hierarchy:** the main information and action lead; supporting content remains readable;
+  labels, semantics, and destructive rank match the work. Check a grayscale view as a hierarchy aid.
+- **Grouping and density:** inter-group gaps exceed internal gaps; labels/help/errors stay with the
+  right control after wrapping. Width serves the content; rails, forms, and tables use it deliberately.
+- **Type and reflow:** line length, baseline alignment, line-height, numeric comparison, and fallback
+  text work at the declared widths and enlarged text. No essential content is clipped or hidden.
+- **Color, depth, and imagery:** light/dark transitions preserve hierarchy without gratuitous text overrides; color has a second encoding;
+  elevation describes layers; crops and icon sizes preserve useful detail; the frame stays quiet.
+- **States and restraint:** first-use, filtered-empty, loading, partial, and error retain a useful
+  next step. Long or missing content holds up. The signature belongs to the brief; accessories do not
+  compete with the task. Motion-free operation remains complete.
+
+A visual review does not establish keyboard behavior, contrast arithmetic, or full WCAG conformance.
+Pair each such claim with the relevant instrument or interaction test and its actual coverage.
 
 ## When an authored rule is already earned
 
-Leave rung 4 to the developer, per [SKILL.md](../SKILL.md) → When custom CSS is justified. Write an
-authored rule without asking only when every one of these holds:
+Leave rung 4 to the developer, per [SKILL.md](../SKILL.md) → When custom CSS is justified. Write a
+rule without asking only when every condition holds:
 
-- an instrument here reports the vendor cascade failing a stated bar — the focus ring under 3:1, the
-  status text under 4.5:1, the shipped component with no class for the state the surface must
-  show;
-- the rule cites that reading beside it, naming the instrument, the bar, and the value read;
-- the rule restores the bar and does nothing else;
-- the rule is written over `--bs-*` tokens, so both color modes move with the theme.
+- an instrument reports a vendor failure against a stated requirement, such as a focus ring below
+  3:1 or information-bearing status text below 4.5:1;
+- the rule cites the instrument, failing reading, and required bar beside it;
+- rungs 1–3 cannot restore the requirement, and the rule repairs that failure without unrelated polish;
+- the rule uses `--bs-*` paint tokens and declared scales, and the repaired result is re-measured in
+  every affected theme and state.
 
-Treat anything wider as a proposal: name what the rule would buy, and stop.
+A visual preference alone does not open this exception. Treat anything wider as a proposal: name
+what the rule would buy and stop until authorized.

package/dist/host/agents/skills/enterprise-bootstrap/references/responsive-layout.md

@@ -0,0 +1,187 @@
+# Responsive layout
+
+> Part of the `enterprise-bootstrap` package. Use before composing a screen, shell, toolbar,
+> form, overlay, or data view. Operate layer: [SKILL.md](../SKILL.md).
+
+## Contents
+
+- [Declare the contract](#declare-the-contract)
+- [Build the base](#build-the-base)
+- [Expand by available space](#expand-by-available-space)
+- [Keep the task intact](#keep-the-task-intact)
+- [Handle navigation and overlays](#handle-navigation-and-overlays)
+- [Prove the result](#prove-the-result)
+
+## Declare the contract
+
+Record one row per distinct region before writing its layout. Reuse a region's contract instead
+of repeating it on every screen. Take the host's supported range; absent one, prove normal content
+at 320 CSS px and compose first at a representative 390 CSS px. These are verification widths,
+not new Bootstrap breakpoints or guarantees about physical devices.
+
+| Region           | Narrow behavior                                               | Expansion condition                     | Information/actions retained                       | Overflow                     |
+| ---------------- | ------------------------------------------------------------- | --------------------------------------- | -------------------------------------------------- | ---------------------------- |
+| Navigation       | Named trigger opens a drawer                                  | Rail plus usable main content fit       | Same destinations and current state                | Drawer body only when needed |
+| Search/actions   | Search and actions stack; filters wrap or disclose            | Labels and hit areas fit together       | Search, active filters, clear path, primary action | None                         |
+| Record list      | Identity, decision fields, primary action; details disclosure | Comparison columns fit beside any rail  | Same data, sorting, selection, actions             | None for the list            |
+| Comparison table | Named, keyboard-operable local scroller                       | Columns fit without a scroller          | All comparison columns and row identity            | Table region only            |
+| Form/dialog      | One reading column; natural height                            | Related fields or explanation have room | Labels, errors, consequences, cancel/commit        | One vertical owner           |
+| Hero/preview     | Copy, actions, then legible evidence                          | Both columns remain useful              | Thesis, primary action, useful demonstration       | Decorative layer only        |
+
+Name the actual thresholds used and why. Do not give every region the same breakpoint by habit.
+Build and use the narrow primary flow before adding desktop chrome or finishing details.
+
+## Build the base
+
+Use Bootstrap's mobile-first direction: unprefixed rules apply from the smallest width; `sm`,
+`md`, `lg`, `xl`, and `xxl` add behavior at their minimum widths. `xs` has no class infix.
+Take the installed breakpoint map, not device labels, from
+[Breakpoints & layout](bootstrap-reference.md#breakpoints--layout).
+
+Prefer shipped structure before custom media queries:
+
+```html
+<!-- One field per row until the content supports a pair. -->
+<div class="row g-3">
+	<div class="col-12 col-md-6"><!-- labelled field --></div>
+	<div class="col-12 col-md-6"><!-- related labelled field --></div>
+</div>
+
+<!-- Stretch actions at the base; use their natural widths from sm. -->
+<div class="d-grid gap-2 d-sm-flex flex-sm-wrap">
+	<button type="submit" class="btn btn-primary">Save changes</button>
+	<button type="button" class="btn btn-outline-secondary">Cancel</button>
+</div>
+
+<!-- Give search its own narrow row rather than crushing its input. -->
+<form class="row g-2 align-items-end" role="search" aria-label="Find invoices">
+	<div class="col-12 col-md">
+		<label class="form-label" for="invoice-search">Search invoices</label>
+		<input class="form-control" id="invoice-search" type="search" />
+	</div>
+	<div class="col-12 col-sm-6 col-md-auto">
+		<label class="form-label" for="invoice-status">Status</label>
+		<select class="form-select" id="invoice-status">
+			<option>All statuses</option>
+		</select>
+	</div>
+</form>
+```
+
+Keep DOM order meaningful before arranging columns. Do not use visual `order-*` to separate focus
+order from reading order. Use `p-3 p-lg-4` and `g-3 g-lg-4` to grow outer space independently of
+control size. Keep `.row` gutters inside a compatible container or padded parent; do not add
+unbudgeted `gap-*` to percentage columns whose widths already total the row.
+
+Check the generated CSS. Stock width/height, overflow, and general position utilities do not all
+ship breakpoint variants. Do not invent `w-md-auto`, `overflow-lg-auto`, `position-lg-sticky`, or
+`min-w-0`. Responsive sticky helpers are a separate shipped family. Take missing roles through
+[Layout and type extensions](bootstrap-reference.md#layout-and-type-extensions).
+
+## Expand by available space
+
+Measure the content container after rails, gutters, and panel padding. A wide viewport can contain
+a narrow main region, split pane, or dialog. Delay columns, keep an intrinsic layout, or use an
+authorized container-query extension when reuse requires it. A viewport breakpoint alone does not
+prove the component fits.
+
+Let flex/grid children shrink: use the project's zero-inline-minimum role and, for custom grids,
+`minmax(0, 1fr)` where appropriate. Break long identifiers at safe opportunities; expose complete
+values through a usable detail view when truncation is unavoidable. Never shrink amounts, labels,
+or input text to rescue a desktop row. Let identity/amount headers wrap independently and bound
+long action labels to their container; a wrapping parent does not constrain an oversized child.
+Preserve native input scrolling for long editable values.
+
+Use a content-led maximum width, not an unconditional fixed width or `vw-100` inside a padded
+container. Let content set height. Prefer ordinary page scrolling to a phone-sized nested viewport;
+reserve bounded table scrolling for a documented comparison task. Do not use `vh-100`, transforms,
+CSS zoom, or root `overflow-x-hidden` to make an oversized layout appear to fit.
+
+Keep large typography and presentation space responsive without shrinking body text or hit areas.
+Bootstrap RFS scales supported type; it does not reflow navigation, dialogs, or preview content.
+A readable line count beats mechanically preserving a desktop hero's proportions.
+
+## Keep the task intact
+
+Choose a data strategy by the task, not a fixed ranking:
+
+- **Record work:** use a compact list or labelled stack when the job is finding and acting on one
+  record. Keep identity, status, amount, due date, and the relevant action directly discoverable;
+  put secondary details behind a named disclosure. Generate variants from one data/state model.
+- **Comparison work:** retain a semantic table when column comparison is essential. Local horizontal
+  scrolling is valid; name the region, provide a scroll cue, and verify keyboard reach to both ends.
+  Keep search and pagination outside it. Do not turn every comparison into cards.
+- **Priority columns:** omit a column from the narrow presentation only when the same information is
+  available through an operable detail path. `d-none` alone is not a content strategy.
+
+Do not render two independent forms or state stores for narrow/wide variants. Keep IDs unique and
+only the active representation in the accessibility/focus tree. Preserve filters, values, selected
+record IDs, sort, and open-detail context across a live resize. Restore focus to the equivalent
+visible control if its representation disappears; do not steal unrelated focus. Track the control
+before hiding it: the browser may move focus to the body before a media-query listener runs.
+A dialog closed after reflow returns to the visible equivalent of its original trigger.
+
+Keep search and action bars in normal flow. Stack or wrap ordinary controls before considering a
+scroller; put additional filters behind a working disclosure with active-filter count and reset.
+Use a wrapping group of independent buttons or a select, not a joined `.btn-group` bent over two
+rows. Keep consequential button labels visible. Preserve the current page and previous/next when
+reducing a pager's numbered links.
+
+Keep record actions outside a clipped table wrapper when necessary. Popper placement alone does
+not guarantee escape from an overflow ancestor. Prefer a root-mounted dialog or an existing
+portal implementation over z-index escalation.
+
+Make touch targets comfortable without making text larger: prefer 44×44 CSS px for primary mobile
+controls; retain the package's 24×24 minimum for every applicable target. Enlarge the actual button
+or associated label, not merely the icon's surrounding decoration. Keep action affordances visible
+without hover. Measure effective label hit areas for native checkboxes and switches.
+
+## Handle navigation and overlays
+
+Use `navbar-expand-*` or responsive `offcanvas-*` from the installed build. Match the trigger's
+visibility threshold to the inline panel. Preserve one destination set, a named trigger, current
+state, keyboard operation, Escape, and focus return. Exercise a drawer opened below a threshold,
+resized above it, then returned below; no stale backdrop, body scroll lock, or invisible focus trap
+may remain. Do not assume the host wrapper behaves exactly like the stock plugin.
+
+Keep overlay width within the viewport and height content-led with an explicit vertical scroll
+owner. Bootstrap's `modal-fullscreen-*-down` belongs to its modal structure, not a native `<dialog>`.
+For native dialogs, declare a bounded logical size in the stylesheet when needed; keep consequences,
+fields, safe dismissal, and commit reachable on short screens and with enlarged text. Check the
+initial view as well as the scrolled footer. When action focus would hide the beginning, focus a
+static top heading with `tabindex="-1"`; keep a safe dismissal in the tab sequence. Follow the
+[dialog focus guidance](https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/).
+
+Let nonessential sticky chrome become static on narrow or short screens. Where fixed controls are
+required, reserve their space, account for safe-area insets, and check focus visibility. Use a
+supported dynamic viewport unit only for a genuine viewport-bound requirement; it does not prove
+virtual-keyboard behavior. Test the soft keyboard and browser chrome on a real supported device,
+or leave that coverage open.
+
+Keep theme ownership intact during reflow. A dark hero or drawer on a light page establishes its
+foreground/background at its boundary; ordinary descendants inherit. Take adaptive subtle fills
+and exceptions from [color-modes.md](color-modes.md), not a separate mobile palette.
+
+## Prove the result
+
+Run [Responsive task and reflow](inspection.md#responsive-task-and-reflow) and
+[Responsive interaction continuity](inspection.md#responsive-interaction-continuity). Check 320 and
+390 CSS px, one wide view, and `b−1`, `b`, `b+1` for each used breakpoint; deduplicate overlaps.
+Check narrow/short landscape, long unbroken identifiers, expanded copy, enlarged text, and the
+states actually used. Cross light/dark with the important narrow/wide states.
+
+Require both geometry and task evidence. A page with no horizontal overflow can still hide its
+primary action, clip a menu, or push decision fields into an undiscoverable scroller. Conversely,
+a valid local two-dimensional scroller is not a page-level reflow failure.
+
+Capture narrow output first and inspect it before desktop. Preserve before/after evidence for
+regressions; run known-invalid controls through the same readers. State the Bootstrap build,
+browser, assets, CSS viewport, state, and exclusions. Do not call a screenshot, class scan, reduced
+viewport, device-pixel-ratio change, or emulated touch a real-device or complete accessibility pass.
+
+Take upstream behavior from Bootstrap's [breakpoints](https://getbootstrap.com/docs/5.3/layout/breakpoints/),
+[grid](https://getbootstrap.com/docs/5.3/layout/grid/), [flex](https://getbootstrap.com/docs/5.3/utilities/flex/),
+[offcanvas](https://getbootstrap.com/docs/5.3/components/offcanvas/), and
+[tables](https://getbootstrap.com/docs/5.3/content/tables/). Distinguish this package's test matrix
+from the requirements and two-dimensional-content exception in
+[WCAG reflow](https://www.w3.org/WAI/WCAG22/Understanding/reflow.html).