@orkestrel/scaffold 0.0.44 → 0.0.46

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

@@ -14,7 +14,7 @@
 - [Forms in production](#forms-in-production)
 - [JavaScript lifecycle](#javascript-lifecycle)
 - [Accessibility](#accessibility)
-- [Enterprise patterns](#enterprise-patterns) — [App shell](#app-shell) · [Dense data tables](#dense-data-tables) · [Filter & search bars](#filter--search-bars) · [Wizards & multi-step forms](#wizards--multi-step-forms) · [The five states](#the-five-states) · [Feedback discipline](#feedback-discipline) · [Destructive actions](#destructive-actions)
+- [Enterprise patterns](#enterprise-patterns) — [App shell](#app-shell) · [Dense data tables](#dense-data-tables) · [Filter & search bars](#filter--search-bars) · [Wizards & multi-step forms](#wizards--multi-step-forms) · [The data states](#the-data-states) · [Feedback discipline](#feedback-discipline) · [Destructive actions](#destructive-actions)
 - [RTL](#rtl)
 - [Print](#print)
 - [Performance](#performance)
@@ -129,7 +129,7 @@ In Sass: `$enable-dark-mode` (default true), `$color-mode-type: data` (attribute
 
 ## Theming & Design Tokens
 
-### The three-tier token model
+### The tiered token model
 
 Enterprise theming survives rebrands and dark mode only when tokens are tiered:
 
@@ -211,7 +211,7 @@ Remove with `map-remove($utilities, "width")` or set the key to `null`. This is
 
 - **Top-aligned labels by default** — the evidence (eye-tracking form research) shows fastest completion and the cleanest single-column scan, and they survive narrow screens without reflow. Reserve left-aligned labels for dense read-back forms where vertical compression matters more than speed.
 - Visible label or `.form-floating` — never placeholder-only (disappears on input, fails accessibility).
-- **Do not say the same thing twice.** When the host already names the request — a card heading, a dialog title, a section header stating the question — the form associates with that name via `aria-labelledby` instead of repeating the prompt in its own label. Repetition reads as two different questions to a screen-reader user and as clutter to everyone else.
+- **Do not say the same thing twice.** When the host already names the request — a card heading, a dialog title, a section header stating the question — the form associates with that name via `aria-labelledby` instead of repeating the prompt in its own label. Repetition reads as separate questions to a screen-reader user and as clutter to everyone else.
 - One column beats multi-column for completion; use the form grid (`row g-3` + `col-md-*`) only for genuinely paired fields (city/state/zip).
 
 ```html
@@ -508,19 +508,21 @@ Give header cells an **opaque background** (`bg-body-secondary` or a table varia
 - One toolbar above the table: search input first (`role="search"` on the form), then the 2–4 highest-value filters as `form-select`/segmented controls, overflow filters behind a "Filters" button (offcanvas on mobile, dropdown/collapse on desktop).
 - **Active filters must be visible and dismissible** — chips/badges with an ✕ and a "Clear all" — users must see _why_ the list is short. A filtered-empty state repeats the escape hatch.
 - Debounce live search; show result counts ("128 results") so feedback is immediate; filter state belongs in the URL when views are shareable.
-- Toolbars that overflow: `flex-nowrap overflow-auto` beats wrapping into a two-row toolbar mid-task — do not crush icon targets below 24px.
+- Toolbars that overflow: `flex-nowrap overflow-auto` beats wrapping the toolbar onto a second row mid-task — do not crush icon targets below 24px.
 
 ### Wizards & multi-step forms
 
-- Show step progress: current position, total, and step names ("Step 2 of 4 — Billing"); `list-group-numbered` or a simple nav renders it honestly.
+- Show step progress: current position, total, and step name (for example, "Billing — step ⟨n⟩ of
+  ⟨total⟩", where the wizard fills in its own runtime position and total); `list-group-numbered` or
+  a simple nav renders it honestly.
 - Validate per step before advancing; never let a step advance carrying invalid data.
 - Back never loses data. Persist partial state (save-and-resume) for anything beyond ~3 steps or that crosses sessions.
 - Never re-ask what a previous step collected (Redundant Entry, 3.3.7) — carry it forward or offer "same as above".
-- Last step: a review summary with per-section edit links, then one clearly-named commit action ("Create account", not "Submit").
+- Review step: a review summary with per-section edit links, then one clearly-named commit action ("Create account", not "Submit").
 
-### The five states
+### The data states
 
-Design **all five** for every data surface: ideal (populated), empty, loading, partial, error. A component is not done until all five exist.
+Design **every one** for every data surface: ideal (populated), empty, loading, partial, error. A component is not done until all of them exist.
 
 - **Skeleton vs spinner:** skeleton (`placeholder` + `placeholder-glow`) when you know the content's shape and it fills a region — tables, cards, detail panes — because it holds layout and shortens perceived wait. Spinner for short, indeterminate, or in-control waits (inside a button, a small inline fetch).
 - **Thresholds (guidance):** under ~1s show nothing — a flashed loader is worse than none; ~1–10s show a spinner or skeleton; beyond ~10s show determinate progress (percent or step) so it does not feel hung.
@@ -565,7 +567,7 @@ Do not type-gate a single-row delete; do not one-tap a tenant wipe. Confirm only
 
 ## Performance
 
-- **Ship one CSS system, not two.** Bootstrap plus a second framework (or a parallel bespoke layer) doubles payload and guarantees specificity fights.
+- **Ship one CSS system and no more.** Bootstrap plus a second framework (or a parallel bespoke layer) doubles payload and guarantees specificity fights.
 - **Compressed, the full build is cheap; incomplete builds are not.** Trimming via a Sass-subset build (import only the parts used — see [Theming](#theming--design-tokens)) is the sanctioned diet. Aggressive purge tools are the risky one: Bootstrap adds classes **at runtime** (`show`, `showing`, `fade`, `collapsing`, `modal-open`, `modal-backdrop`, `offcanvas-backdrop`, tooltip/popover generated markup) — purging without safelisting them ships UIs whose modals silently stop rendering. If you purge, safelist every JS-toggled class and test every overlay.
 - **Icons:** Bootstrap Icons is a separate package — prefer inline SVG or an SVG sprite (crisp, styleable via `currentColor`, no font flash) over the icon font; load only the icons used.
 - **JS:** the bundle is small, but only load it where behavior exists; per-component ESM imports (`bootstrap/js/dist/modal`) trim further in bundlers.

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

@@ -423,7 +423,7 @@ Multiple targets: give each panel `.multi-collapse` and point separate triggers
 </dialog>
 ```
 
-`role="alertdialog"` for a destructive confirm, `role="dialog"` otherwise; `aria-labelledby` points at the heading. The element's own `close` event is where the host clears the state that opened it, so Esc and the buttons all close by one path. The scrim is the UA's `::backdrop`, which no Bootstrap class touches — restyling it is a rung-4 decision.
+`role="alertdialog"` for a destructive confirm, `role="dialog"` otherwise; `aria-labelledby` points at the heading. The element's own `close` event is where the host clears the state that opened it, so Esc and the buttons all close by one path. The scrim is the UA's `::backdrop`, which no Bootstrap class touches — restyling it requires the custom-CSS tier.
 
 Bootstrap's `.modal` is the answer when the project already drives its dialogs through Bootstrap's JS:
 
@@ -670,7 +670,7 @@ Real switchable tab panels (JS-driven — buttons, not scroll anchors):
 <button class="btn btn-primary disabled placeholder col-4" aria-hidden="true"></button>
 ```
 
-Always wrap skeletons in `aria-hidden="true"` — they are visual scaffolding, not content. Skeleton-vs-spinner decision rules: [bootstrap-reference.md](bootstrap-reference.md) → The five states.
+Always wrap skeletons in `aria-hidden="true"` — they are visual scaffolding, not content. Skeleton-vs-spinner decision rules: [bootstrap-reference.md](bootstrap-reference.md) → The data states.
 
 ### Popover (Requires Popper.js)
 
@@ -1002,7 +1002,7 @@ The textless mark that survives both themes — dots, ticks, rings, pulses — i
 
 ### Selection fills
 
-A selected row, pill, or filter chip repaints everything inside it — marks included. Two traps, both invisible until the selected state is captured in both themes:
+A selected row, pill, or filter chip repaints everything inside it — marks included. These traps stay invisible until the selected state is captured in both themes:
 
 - **A mark on an active fill of the same family disappears.** `.active` on a `list-group-item`, `nav-pill`, or `page-item` sets the item's own color, and a `text-bg-primary`-family mark inside it inherits or loses to that fill — present in the markup, gone on screen. Carry no tone class inside the fill ([SKILL.md](../SKILL.md) → Surfaces, color, contrast). Verify by capturing the selected row, not by reading the class list.
 - **`btn-check` filter labels invert in dark.** A `btn-outline-secondary` label reads as "chosen" in light and as "muted" in dark, because the checked fill and the surface swap relative weight. Give chosen filters an accent variant (a real theme color) rather than the neutral outline, so "chosen" reads the same way in both modes.

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

@@ -57,17 +57,17 @@ product's, and keep the data surfaces disciplined and conventional enough to rea
 
 ## Process: brainstorm, explore, plan, critique, build, critique again
 
-Calibrate against the three looks AI-generated design currently clusters around: (1) a warm cream
+Calibrate against the looks AI-generated design currently clusters around: (1) a warm cream
 background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a
 near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style
-layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are
+layout with hairline rules, zero border-radius, and dense newspaper-like columns. Each is
 legitimate for some briefs; they are defaults rather than choices, and they appear regardless of
 subject. Follow the brief exactly where it pins a visual direction — the brief's own words always
 win, including when they ask for one of these looks. Where the brief leaves an axis free, spend that
 freedom somewhere other than these defaults. Balance the moves you have already proven against
 experimenting where the brief invites it.
 
-Work in two passes. First, brainstorm a short design plan from the brief: a compact token system
+Work in passes. First, brainstorm a short design plan from the brief: a compact token system
 with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type:
 name the typefaces for 2+ roles — a characterful display face used with restraint, a complementary
 body face, and a utility face for captions or data where one is needed. Layout: state a layout

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

@@ -226,7 +226,7 @@ Notes: `s`/`e` are logical start/end — they flip automatically under RTL; neve
 .text-truncate
 ```
 
-Two composition traps in this group:
+The composition traps in this group:
 
 - **`fs-*` without `lh-1` grows the row.** A resized glyph or mark keeps the parent's line-height, so the line box stretches and the row sits taller than its neighbors. Pair `fs-*` with `lh-1` on anything that is a mark rather than a paragraph.
 - **`text-truncate` zeroes a flex item's automatic minimum size** (that's the `min-width: 0` it carries). Inside a flex _column_, that also removes the floor that kept a heading at its own height: a growing sibling then squeezes the title from the bottom until it clips. Floor the title with `flex-shrink-0` and let the growing sibling absorb the change.

package/dist/host/agents/skills/orkestrel-align-packages/SKILL.md

@@ -36,7 +36,7 @@ Invoke `$orkestrel-harden-package` for each package implementation unit. This sk
 8. **Prove the round trip.** Put integration coverage at the highest package that can exercise the real composed behavior. Retain focused deterministic coverage in lower packages.
 9. **Validate local changes safely.** When necessary, use built artifacts in an isolated consumer and prove the resolved graph. Restore temporary manifest/lockfile state.
 10. **Verify topologically.** Run local gates for touched packages from dependencies to dependents and inspect relevant generated outputs.
-11. **Review the campaign.** Run the two-lane adversarial pass plus a mechanical checker on each implementation unit, then one cross-package architecture and ergonomics review over the whole graph.
+11. **Review the campaign.** Run the adversarial pass plus a mechanical checker on each implementation unit, then one cross-package architecture and ergonomics review over the whole graph.
 
 ## Accept the result
 

package/dist/host/agents/skills/orkestrel-build-application/SKILL.md

@@ -73,7 +73,7 @@ includes app/core so the shared transport contracts have one host-independent ow
      callbacks reject forced inlining before any direct asset read, and non-inlined
      output assets are audited by physical source path.
 
-   Then hold these four limits:
+   Then hold these limits:
    - Add no standalone boundary script, and no second parser or source-language analyzer
      duplicating those layers. Reach for the toolchain's own facilities instead: Vite's
      Oxc/Rolldown AST for TypeScript and JavaScript asset references, the official Vue SFC
@@ -98,7 +98,7 @@ includes app/core so the shared transport contracts have one host-independent ow
 8. **Document and prove parity** for every app export and behavioral method: guide,
    examples, manifest index, and the parity specifiers walking the existing `src` and
    `app` roots and every selected alias.
-9. **Verify.** Run the rules' cleanup sweeps over source and tests. Then run the two-lane
+9. **Verify.** Run the rules' cleanup sweeps over source and tests. Then run the
    adversarial pass, a mechanical conformance pass, and the repository gates in their
    required order. Generated CI runs those gates on the declared minimum Node release and
    on the current major.

package/dist/host/agents/skills/orkestrel-debrief/SKILL.md

@@ -75,7 +75,7 @@ a practice that worked so it repeats.
    [instruction-audit.md](references/instruction-audit.md). What confused an executor is
    a defect in the instruction, not the executor.
 6. **Reconcile into the ledger.** Number the findings, attach verbatim evidence, bucket
-   every one. Where two audit lanes disagree, rule each divergence on the record with
+   every one. Where audit lanes disagree, rule each divergence on the record with
    the reason.
 7. **Land the refinements.** Dispatch fix-now findings as bounded units under the
    repository's engine contract; make the canon edits (charters, rules, skills,

package/dist/host/agents/skills/orkestrel-debrief/references/field-testing.md

@@ -1,7 +1,7 @@
 # Field testing an agent-facing surface
 
-The method for producing the live evidence a debrief judges by. Proven across a five-model
-roster and portable to any surface a model consumes.
+The method for producing the live evidence a debrief judges by. It ports to any surface a
+model consumes.
 
 ## The tier ladder
 

package/dist/host/agents/skills/orkestrel-debrief/references/instruction-audit.md

@@ -1,10 +1,10 @@
 # Auditing the instruction set
 
 The method for judging the agents, rules, skills, and orchestration contract against a
-campaign's record. Proven across two debrief rounds; the instruction layer is code — it
-gets the same adversarial, evidence-first treatment as any surface.
+campaign's record. The instruction layer is code — it gets the same adversarial,
+evidence-first treatment as any surface.
 
-## Two blind passes, one brief
+## Blind passes, one brief
 
 Run a subjective lane and an objective lane on the SAME brief, in parallel, neither
 seeing the other's answer before both return:
@@ -27,11 +27,11 @@ record.
 ## The objective lanes
 
 - **Duplication diff.** Whole-line and obligation-level comparison across charters, rules,
-  and skills. A charter that restates a rule drifts from it; a rule stated twice has two
-  owners.
+  and skills. A charter that restates a rule drifts from it; a rule restated elsewhere has
+  more than one owner.
 - **Mechanical-equivalence groups.** Cluster roles by frontmatter (tools, model, effort,
-  mode). Two roles in one group are either genuinely distinct by context binding — or a
-  duplicate.
+  mode). Roles in one group are either genuinely distinct by context binding — or
+  duplicates.
 - **Charter-versus-usage drift.** For each role, compare the charter's promises against
   how the campaign actually dispatched it: unused powers, exercised powers the charter
   never granted, deviation reports the charter's wording caused.
@@ -69,7 +69,7 @@ Findings land as one of:
   probe-first, journal-first, verdict shapes, launch ownership) land in the operating
   contract, mirrored across providers.
 
-## Three questions every round asks
+## The questions every round asks
 
 - **Which findings came from falsification rather than diff reading**, and is the brief
   shape that produced them doctrine yet? Route to the Falsification law in

package/dist/host/agents/skills/orkestrel-falsify/SKILL.md

@@ -58,7 +58,7 @@ diff is a rule the brief cannot satisfy.
 | a policy, design, or process proposal   | the proposal, the canon it must satisfy, and the record of what motivated it          |
 
 **A subject can occupy more than one row; supply every row it occupies.** A ruling whose fixes
-already landed as edits is both the third row and the first, and withholding the diff on the grounds
+already landed as edits is both a proposal and a code change, and withholding the diff on the grounds
 that the subject is "a proposal" leaves the auditor unable to check whether a fix changed anything
 nobody claimed.
 
@@ -69,21 +69,22 @@ nobody claimed.
   looking like authority — and it fails silently, because an auditor does not report a heading it
   never saw. Check before dispatch; propagate the missing file rather than restating its contents in
   the brief. This is the reason restatement felt necessary, and it is the wrong cure.
-- Run the **two-lane adversarial pass** on one identical brief: a subjective lane and an objective
+- Run the **adversarial pass** on one identical brief: a subjective lane and an objective
   lane, each a fresh subagent with a clean context, blind to each other. Reconcile them yourself.
   `.agents/orchestration.md` owns lane definitions, engine assignment, and what happens when an
   engine is dark; do not restate them here.
 - A round run with one lane is a deviation. Record it rather than glossing it. If an engine is
-  unavailable, the remaining engine runs both lanes — it never drops one.
-- **Pair every finder with an independent refuter when the round fans out past two lanes.** The
+  unavailable, the remaining engine runs every lane — it never drops one.
+- **Pair every finder with an independent refuter when the round fans out past the subjective and
+  objective lanes.** The
   refuter receives one slice's findings, never that finder's work, and is briefed to BREAK them
   rather than to re-audit the subject. It reproduces each stated vector itself and defaults to
   refuted when uncertain.
-- Refute on any of six grounds, and name which: the vector does not reproduce; the behaviour is
+- Refute on any of these grounds, and name which: the vector does not reproduce; the behaviour is
   correct and documented; it is unreachable through the public API or a documented seam; it asks
   for new capability rather than naming a defect; it restates a finding an earlier round
   repaired; or its diagnosis is wrong — then CONFIRM with the correction.
-- Only a survivor earns a fix unit. An unrefuted finding is a hypothesis. The two scope grounds,
+- Only a survivor earns a fix unit. An unrefuted finding is a hypothesis. The scope grounds,
   unreachable and new capability, are what keep a round from drifting into a redesign.
 - **Give every auditor the means to run its attacks.** A lens that can only read returns derivations,
   and a derivation reads exactly like a verdict — it will confirm a claim that one probe would break.
@@ -124,7 +125,7 @@ nobody claimed.
 Every auditor in every round returns exactly this, and nothing else. One shape makes rounds
 comparable; a round that invents its own cannot be read against the last one.
 
-1. **Numbered verdicts**, one per claim, in the brief's order. Exactly one of four values:
+1. **Numbered verdicts**, one per claim, in the brief's order. Exactly one of these values:
 
    | value           | meaning                                                                                | evidence                                                                                                                                                      |
    | --------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -133,10 +134,11 @@ comparable; a round that invents its own cannot be read against the last one.
    | `UNRESOLVED`    | cannot be decided from the evidence available                                          | what would settle it                                                                                                                                          |
    | `NOT-EVIDENCED` | a claim about a rendered or externally driven surface the supplied capture cannot show | which capture is missing                                                                                                                                      |
 
-   The first two rows defer; only the last two are this skill's, because the law does not name them.
-   `BROKEN` and `UNRESOLVED` are **separate**: a claim nobody could decide has not been falsified,
-   and it cannot supply the fields falsification requires. `NOT-EVIDENCED` is the token the
-   `analyst` and `reviewer` charters already require; it is kept, not re-invented.
+   `CONFIRMED` and `BROKEN` defer; only `UNRESOLVED` and `NOT-EVIDENCED` are this skill's, because
+   the law does not name them. `BROKEN` and `UNRESOLVED` are **separate**: a claim nobody could
+   decide has not been falsified, and it cannot supply the fields falsification requires.
+   `NOT-EVIDENCED` is the token the `analyst` and `reviewer` charters already require; it is kept,
+   not re-invented.
 
 2. **Findings fitting no claim**, if any, each substantiated to the same standard as `BROKEN`.
 
@@ -147,7 +149,7 @@ comparable; a round that invents its own cannot be read against the last one.
    VERDICT: FAIL — <n> broken, <u> unresolved, <e> not-evidenced, <x> findings outside the claims
    ```
 
-   **`PASS` requires all four to be true**: every claim `CONFIRMED`, nothing `UNRESOLVED`, nothing
+   **`PASS` requires every one of these to be true**: every claim `CONFIRMED`, nothing `UNRESOLVED`, nothing
    `NOT-EVIDENCED`, and no substantiated finding outside the claims. A single substantiated finding
    forces `FAIL` no matter how the numbered claims landed — otherwise a round can report a real
    defect and still emit the word that authorises the release.
@@ -173,8 +175,8 @@ Follow `references/reconcile.md`. The obligations that are not delegable:
   vectors teaches the lane those vectors matter, and a lane can hand back the brief's own questions as
   the subject's claims — demanding coverage for a property the subject never documented. Grep the
   subject for the claim the finding rests on. Where it is not there, the finding is against the brief.
-- **A disagreement between auditors is rarely a tie to average.** It is usually two correct answers
-  to two different questions. Find the question each one answered.
+- **A disagreement between auditors is rarely a tie to average.** It is usually correct answers
+  to different questions. Find the question each one answered.
 - **Bound every finding**: state what is _not_ broken, and why the adjacent behaviour that looks the
   same is correct. An audit that reports everything is as useless as one that reports nothing.
 - **Bound the fix before briefing it.** Establish what over-correcting would break, and include that

package/dist/host/agents/skills/orkestrel-falsify/references/brief.md

@@ -78,9 +78,9 @@ repair to carry the next defect; a round that finds them is converging, not fail
 - _"CONFIRMED requires naming the attack you tried that failed."_ — the single most effective
   sentence, because it converts a confirmation from an opinion into a report of work done.
 - _"A claim you cannot decide is UNRESOLVED, not CONFIRMED — say what would settle it."_
-- _"Assume this chain has one more."_ — with the count of prior rounds and how many were provoked by
-  a defect the previous round believed closed.
-- _"Do not hedge toward an imagined consensus."_ — when two auditors run blind, each will otherwise
+- _"Assume this chain has one more."_ — naming the prior rounds and which of them a defect the
+  previous round believed closed provoked.
+- _"Do not hedge toward an imagined consensus."_ — when auditors run blind, each will otherwise
   soften toward what it guesses the other said.
 
 Do **not** write _"an audit returning only confirmations has not tried."_ It reads as pressure to

package/dist/host/agents/skills/orkestrel-falsify/references/reconcile.md

@@ -1,6 +1,6 @@
 # Reconciling a round and ruling on it
 
-Two auditors return. Neither accepts; the orchestrator does. This is where a round becomes a
+The auditors return. Neither accepts; the orchestrator does. This is where a round becomes a
 decision, and it is not delegable.
 
 ## Reproduce before you act
@@ -16,7 +16,7 @@ catch cannot distinguish _the subject threw_ from _my harness threw_ — a missi
 arity, a `require` in an ESM context all surface as the finding you were hoping to see. Construct
 first, let harness failures crash loudly, and only guard the call under test.
 
-Reproduction produces three outcomes, and all three matter:
+Reproduction produces these outcomes, and all of them matter:
 
 - the finding **confirms** and is often **wider** than reported — the reproduction reaches doors the
   auditor did not try;
@@ -32,18 +32,18 @@ code under test reports a pass that means nothing, and it will read exactly like
 
 ## A disagreement is rarely a tie
 
-When two auditors return opposite verdicts on one claim, do not average them and do not prefer the
+When auditors return opposite verdicts on one claim, do not average them and do not prefer the
 engine you trust more. **Reproduce first** — running the disagreement settles most of them outright,
 and it is the only method that can also find what neither auditor saw. Then find the question each
 one answered. The common shapes:
 
 - **Both right about different objects.** One tested a case the other did not construct. This is a
-  `SPLIT-CLAIM`: the claim was a universal that carried more than one subject. It is **not** a third
-  verdict value — one falsifying input makes a universal claim `BROKEN`, and succeeding on a
+  `SPLIT-CLAIM`: the claim was a universal that carried more than one subject. It is **not** a
+  further verdict value — one falsifying input makes a universal claim `BROKEN`, and succeeding on a
   different object does not undo that. Split it, keep the original `BROKEN` if any subclaim is
   broken, and carry the split into the successor brief.
 - **Both right about different halves of one claim number.** Same resolution: the claim number was
-  carrying two claims. Split and renumber.
+  carrying more than one claim. Split and renumber.
 - **One right on the mechanism, the other on the criterion.** Take both. The reconciled ruling is
   frequently neither proposal, and better than either, because each supplied a constraint the other
   violated.
@@ -60,7 +60,7 @@ memory. A reader six months out must be able to tell an unbiased blind verdict f
 after an auditor saw its counterpart's evidence — otherwise the whole value of running blind is
 unverifiable after the fact.
 
-Two rules, both enforceable:
+These rules are enforceable:
 
 1. **A returned verdict is never edited** — not by the auditor, not by the orchestrator.
 2. **Anything an auditor says after seeing another's report is a separate file beside that verdict**,
@@ -82,7 +82,7 @@ State what is **not** broken, and why the adjacent behaviour that looks identica
 finding without a boundary is an alarm, and alarms get discounted wholesale — including the true
 ones next to them.
 
-Two boundaries earn their keep:
+These boundaries earn their keep:
 
 - **Credit what the round got right.** If the hostile inputs adjacent to the hole are correctly
   contained, say so and list them. It sharpens the finding to a point instead of an area.
@@ -95,8 +95,8 @@ Two boundaries earn their keep:
 Establish what over-correcting would break, and put it in the fix brief as a constraint. Both ends
 are usually wrong:
 
-- **too little** — a patch to the one function, leaving the package holding two standards for the
-  same thing, which is the inconsistency that produced the finding;
+- **too little** — a patch to the one function, leaving the package holding conflicting standards
+  for the same thing, which is the inconsistency that produced the finding;
 - **too much** — adopting the strictest sibling's rule verbatim, breaking a legitimate caller
   pattern, and tripping "no refusal was widened into a regression" in the next round.
 
@@ -124,7 +124,7 @@ are easiest to construct. That sampling proves discrimination _within_ the popul
 routinely reported as proof the instrument works.
 
 So before running controls, write down the instrument's **membership rule** in one sentence, then
-ask what the rule excludes. Draw at least one control from there. Two shapes have already cost a
+ask what the rule excludes. Draw at least one control from there. These shapes have already cost a
 round each:
 
 - an AST comparison whose controls were all drawn from the literal classes present in the bodies it
@@ -132,9 +132,9 @@ round each:
 - a call-closure pin whose controls were all body-reachable functions, green for a function reached
   only through a parameter default.
 
-Then write the two sentences that matter: what the controls established, and what they did not. The
-second sentence is the one that gets skipped, and skipping it is how an instrument's credibility
-outruns its evidence.
+Then write the sentences that matter: what the controls established, and what they did not. What
+they did not establish is the one that gets skipped, and skipping it is how an instrument's
+credibility outruns its evidence.
 
 ## Ruling
 

package/dist/host/agents/skills/orkestrel-harden-package/SKILL.md

@@ -51,7 +51,7 @@ Load [hardening.md](references/hardening.md) for the hardening lane and for any
 10. **Document the final behavior.** Update the governing guide, examples, method tables, limitations, and parity coverage. Document architectural limits honestly.
 11. **Audit completion.** Inspect test discovery, `.todo`/`.skip`/conditional skip use, source/test helper duplication, exports, environment isolation, unexpected text corruption, and the entire diff.
 12. **Verify.** Run the repository-prescribed gates in order and inspect the generated outputs relevant to the request.
-13. **Review independently, and never by the author.** When orchestration is available, run the two-lane adversarial pass — subjective design fit and objective correctness — plus a mechanical checker, per `.agents/orchestration.md`. Add a dedicated adversarial round for security, concurrency, destructive paths, or external input. A unit's auditor is an engine that did not write it; same-engine re-review returns the author's own blind spot. Resolve every required finding, then rerun affected verification.
+13. **Review independently, and never by the author.** When orchestration is available, run the adversarial pass — subjective design fit and objective correctness — plus a mechanical checker, per `.agents/orchestration.md`. Add a dedicated adversarial round for security, concurrency, destructive paths, or external input. A unit's auditor is an engine that did not write it; same-engine re-review returns the author's own blind spot. Resolve every required finding, then rerun affected verification.
 
 ## Accept the result
 

package/dist/host/agents/skills/orkestrel-human-journey/SKILL.md

@@ -78,15 +78,15 @@ placement and scope `.claude/rules/tests.md` fixes.
   announced location.
 - Assert the whole page's perception never matches the vocabulary the product does not speak —
   engine, schema, and implementation words the interface is supposed to translate.
-- Report a bare accessible name that answers for two reachable elements on one screen as a surface
+- Report a bare accessible name that answers for more than one reachable element on one screen as a surface
   finding, and target through role or region until the surface is fixed.
 
 ## Prove the refusals
 
 - Give every surface a refusal family: the controls a person must not reach in the state the
   journey has put the surface in.
-- Assert the exact failure voice the case means. Never write an assertion that accepts either of
-  two voices.
+- Assert the exact failure voice the case means. Never write an assertion that accepts more than
+  one voice.
 - Cover the restrictions the interface imposes on itself: a collapsed panel's field, a verb
   belonging to another kind of object, a control disabled until its precondition lands.
 - When a refusal changes voice after a markup change, read it as a role or reachability change

package/dist/host/agents/skills/orkestrel-human-journey/references/captures.md

@@ -21,7 +21,7 @@ capture(state: string): Promise<string | undefined>
 
 ## The registry
 
-Declare two frozen lists in the journey file: the state names, and the variants.
+Declare a frozen list of state names and a frozen list of variants in the journey file.
 
 - Name a state for its surface and its condition — `answer-partial`, `start-storage-failure`,
   `case-delete-confirmation`.
@@ -35,12 +35,12 @@ Declare two frozen lists in the journey file: the state names, and the variants.
 ## Variants
 
 - Name a variant as one value carrying both the theme and the viewport, such as `dark-390`. Never
-  split them into two selectors: a split lets a run write a filename describing a combination it
+  split them into separate selectors: a split lets a run write a filename describing a combination it
   did not render.
 - Render one variant per run, and produce the portfolio — the registry times the variants — by
   repeating the run once per variant.
 
-## The two proofs
+## The proofs
 
 | Proof                | Runs                        | Asserts                                                                                        |
 | -------------------- | --------------------------- | ---------------------------------------------------------------------------------------------- |

package/dist/host/agents/skills/orkestrel-human-journey/references/layer.md

@@ -42,7 +42,7 @@ resolveAccessible(role: string, name: string): HTMLElement
 
 ### The failure voices
 
-Keep these distinct, and never merge two into one message.
+Keep these distinct, and never merge any of them into one message.
 
 | Condition                                  | The voice it must throw                                          |
 | ------------------------------------------ | ---------------------------------------------------------------- |
@@ -51,8 +51,8 @@ Keep these distinct, and never merge two into one message.
 | Several matches are reachable              | `Interactive target "<name>" is ambiguous across <n> elements`   |
 | Still off-viewport after being scrolled to | `Interactive target "<name>" is unreachable after scrolling`     |
 
-- Report an absent control and a present-but-unreachable one as different findings: the first names
-  a missing control, the second names the interface gating one that exists.
+- Report an absent control and a present-but-unreachable one as different findings: absence names
+  a missing control, and unreachability names the interface gating one that exists.
 - Report ambiguity as a finding about the surface. Name the match count in the message, and
   re-target the journey by role or region.
 

package/dist/host/agents/skills/orkestrel-polish-surface/SKILL.md

@@ -38,7 +38,7 @@ supposed to produce it. Source-reading review passes a component that renders no
 Choose the smallest scope that satisfies the request:
 
 - **Verdict:** one portfolio, one lane, no fixes.
-- **Round:** portfolio → three independent verdicts → reconciliation → fix units →
+- **Round:** portfolio → independent verdicts → reconciliation → fix units →
   recapture.
 - **Campaign:** rounds repeated until one terminal converged line, then independent gates.
 
@@ -53,8 +53,8 @@ confirmed finding in scope and rebuilding the harness gaps the verdicts expose.
 2. **Seed candidates.** Turn your own mid-integration observations into numbered
    confirm-or-refute candidates inside the verdict brief. Observations that stay in your
    head are neither evidence nor findings.
-3. **Take three independent verdicts** on the SAME portfolio, in the fixed shape below. The
-   three lanes are subjective design fit; objective state truth; and mechanical inventory of
+3. **Take independent verdicts** on the SAME portfolio, in the fixed shape below. The
+   lanes are subjective design fit; objective state truth; and mechanical inventory of
    copy, classes, icons, and accessibility attributes. This is the surface variant of the
    adversarial pass in `.agents/orchestration.md`, so its rules bind: each lane is a fresh
    subagent with a clean context, run in parallel, blind to the others until all have

package/dist/host/claude/agents/analyst.md

@@ -18,9 +18,9 @@ Read `.agents/orchestration.md` first.
 `.claude/agents/codex.md` owns the Sol transport contract in full — which work class uses MCP and
 which uses the journaled CLI, the exact `codex exec` form, the journal and session-id discipline,
 the recovery ladder, and the Windows notes. **Read it and follow it.** It is not restated here;
-two copies of a transport contract drift, and the one you are not reading is the one that is right.
+a restated transport contract drifts, and the copy you are not reading is the one that is right.
 
-This role pins exactly one thing that file leaves to the dispatch: **the route is `analyst`, and its
+This role pins what that file leaves to the dispatch: **the route is `analyst`, and its
 sandbox is `read-only` in the current checkout.** Never widen it. An analyst unit that appears to
 need a write is a misrouted unit — stop and report, do not switch routes.
 

package/dist/host/claude/agents/checker.md

@@ -11,8 +11,8 @@ You are the **Checker** — the mechanical conformance auditor in this project's
 role set (see .agents/orchestration.md). You are exhaustive, evidence-first, and independent of
 the builder. You are an Executor: do the audit yourself, spawn nothing.
 
-Conformance review belongs to Grok first. You are the last step of the tedious-work
-ladder — Grok, then Luna on Codex, then you — so a dispatch reaching you should
+Conformance review belongs to Grok first. You sit at the end of the tedious-work
+ladder, after Grok and Luna on Codex, so a dispatch reaching you should
 already record why the benches above it were unavailable.
 
 ## Job

package/dist/host/claude/agents/codex.md

@@ -24,9 +24,9 @@ CODEX_IMPLEMENTER_EFFORT=high
 
 Raise the analyst to `xhigh` only for a stated hard reasoning need. Use `gpt-5.6-terra`
 only for explicitly mechanical, taste-free roles. Use `gpt-5.6-luna` for absorption,
-distillation, scouting, and bounded research when the Cursor bench is dark — it is the
-second step of the tedious-work ladder, and the substitution is recorded. Never switch
-models silently.
+distillation, scouting, and bounded research when the Cursor bench is dark — it sits
+between Cursor Grok and Sonnet on the tedious-work ladder, and the substitution is
+recorded. Never switch models silently.
 
 ## Transport — pick by work class
 
@@ -43,7 +43,7 @@ models silently.
 
 ## Prepare the journaled CLI launch
 
-Your two jobs are drafting the brief and running short MCP exchanges. For long work you
+Your jobs are drafting the brief and running short MCP exchanges. For long work you
 prepare the launch and return it; the Orchestrator runs it as a harness-tracked
 background command under a hard cap.
 
@@ -52,7 +52,7 @@ never travel as shell arguments. Return the exact resolved command with a pointe
 
 `timeout <cap> codex exec --json -C <working-directory> --sandbox <route-sandbox> --model gpt-5.6-sol -c "model_reasoning_effort=\"high\"" --output-last-message tmp/codex/<unit>-last.md "Read and execute the brief at tmp/codex/<unit>-brief.md exactly. Your final message must be the report it specifies." < /dev/null > tmp/codex/<unit>.jsonl`
 
-- Return three things: the brief path, that resolved command, and the journal path. Leave
+- Return the brief path, that resolved command, and the journal path. Leave
   `<cap>` unresolved — the Orchestrator owns it, per **Long-running commands → Launching**
   in `.agents/orchestration.md`. You hold no record of prior runs.
 - Never launch, background, poll, sleep-loop, restart, or kill an exec.