@orkestrel/scaffold 0.0.44 → 0.0.45

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

@@ -41,7 +41,7 @@ so network-controlled descriptions never enter agent instruction context.
 | `@orkestrel/brief`      | `0.0.3`  | L4    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/interpret` `^0.0.10`, `@orkestrel/reason` `^0.0.7`                                                                                                                                                                                            |
 | `@orkestrel/browser`    | `0.0.11` | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/html` `^0.0.4`, `@orkestrel/websocket` `^0.0.9`                                                                                                                                                                                               |
 | `@orkestrel/budget`     | `0.0.7`  | L1    | `@orkestrel/contract` `^0.0.12`                                                                                                                                                                                                                                                                                           |
-| `@orkestrel/console`    | `0.0.8`  | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                                                            |
+| `@orkestrel/console`    | `0.0.9`  | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                                                            |
 | `@orkestrel/contract`   | `0.0.12` | L0    |                                                                                                                                                                                                                                                                                                                           |
 | `@orkestrel/csv`        | `0.0.4`  | L1    | `@orkestrel/contract` `^0.0.12`                                                                                                                                                                                                                                                                                           |
 | `@orkestrel/database`   | `0.0.11` | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/indexeddb` `^0.0.8`, `@orkestrel/sqlite` `^0.0.8`                                                                                                                                                                                             |
@@ -52,12 +52,13 @@ so network-controlled descriptions never enter agent instruction context.
 | `@orkestrel/indexeddb`  | `0.0.8`  | L1    | `@orkestrel/contract` `^0.0.12`                                                                                                                                                                                                                                                                                           |
 | `@orkestrel/interpret`  | `0.0.10` | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/reason` `^0.0.7`, `@orkestrel/template` `^0.0.4`                                                                                                                                                                                              |
 | `@orkestrel/markdown`   | `0.0.9`  | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/html` `^0.0.4`                                                                                                                                                                                                                                                               |
-| `@orkestrel/mcp`        | `0.0.18` | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/sse` `^0.0.5`, `@orkestrel/tool` `^0.0.11`, `@orkestrel/websocket` `^0.0.9`                                                                                                                                                                   |
+| `@orkestrel/mcp`        | `0.0.19` | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/process` `^0.0.3`, `@orkestrel/sse` `^0.0.5`, `@orkestrel/tool` `^0.0.11`, `@orkestrel/websocket` `^0.0.9`                                                                                                                                    |
 | `@orkestrel/middleware` | `0.0.16` | L2    | `@orkestrel/abort` `^0.0.7`, `@orkestrel/budget` `^0.0.7`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/timeout` `^0.0.7`                                                                                                                                                                                                 |
 | `@orkestrel/msg`        | `0.0.7`  | L0    |                                                                                                                                                                                                                                                                                                                           |
 | `@orkestrel/ndjson`     | `0.0.7`  | L1    | `@orkestrel/contract` `^0.0.12`                                                                                                                                                                                                                                                                                           |
 | `@orkestrel/ollama`     | `0.0.10` | L6    | `@orkestrel/agent` `^0.0.16`, `@orkestrel/budget` `^0.0.7`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/ndjson` `^0.0.7`, `@orkestrel/timeout` `^0.0.7`, `@orkestrel/tool` `^0.0.11`                                                                                                                                     |
 | `@orkestrel/pool`       | `0.0.8`  | L2    | `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                                                                                             |
+| `@orkestrel/process`    | `0.0.3`  | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                                                            |
 | `@orkestrel/program`    | `0.0.9`  | L4    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/qualifier` `^0.0.10`, `@orkestrel/rater` `^0.0.11`, `@orkestrel/reason` `^0.0.7`                                                                                                                                                              |
 | `@orkestrel/qualifier`  | `0.0.10` | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/reason` `^0.0.7`                                                                                                                                                                                                                              |
 | `@orkestrel/queue`      | `0.0.9`  | L3    | `@orkestrel/abort` `^0.0.7`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/database` `^0.0.10`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/timeout` `^0.0.7`                                                                                                                                                               |
@@ -65,8 +66,8 @@ so network-controlled descriptions never enter agent instruction context.
 | `@orkestrel/reason`     | `0.0.7`  | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                                                            |
 | `@orkestrel/relation`   | `0.0.9`  | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/database` `^0.0.10`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                           |
 | `@orkestrel/router`     | `0.0.10` | L2    | `@orkestrel/abort` `^0.0.7`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                               |
-| `@orkestrel/scaffold`   | `0.0.42` | L3    | `@orkestrel/console` `^0.0.8`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/markdown` `^0.0.9`, `@orkestrel/template` `^0.0.4`                                                                                                                                                             |
-| `@orkestrel/sea`        | `0.0.8`  | L2    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`                                                                                                                                                                                                                                                            |
+| `@orkestrel/scaffold`   | `0.0.44` | L3    | `@orkestrel/console` `^0.0.8`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/markdown` `^0.0.9`, `@orkestrel/process` `^0.0.3`, `@orkestrel/template` `^0.0.4`                                                                                                                              |
+| `@orkestrel/sea`        | `0.0.9`  | L3    | `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/process` `^0.0.3`                                                                                                                                                                                                                             |
 | `@orkestrel/server`     | `0.0.14` | L3    | `@orkestrel/abort` `^0.0.7`, `@orkestrel/contract` `^0.0.12`, `@orkestrel/emitter` `^0.0.7`, `@orkestrel/router` `^0.0.10`, `@orkestrel/timeout` `^0.0.7`                                                                                                                                                                 |
 | `@orkestrel/sqlite`     | `0.0.8`  | L1    | `@orkestrel/contract` `^0.0.12`                                                                                                                                                                                                                                                                                           |
 | `@orkestrel/sse`        | `0.0.5`  | L0    |                                                                                                                                                                                                                                                                                                                           |
@@ -110,12 +111,12 @@ account rather than on the dependency's. A superfluous diff obliges nothing.
 The `Layer` column above is the publish round, derived from the runtime edges in the same
 row. `L0` depends on nothing else in the fleet and publishes first; each later layer
 publishes only after every layer before it is on the registry. A row with no layer sits in
-a cycle and cannot be placed in a round at all. Two packages in one layer are independent
+a cycle and cannot be placed in a round at all. Packages in one layer are independent
 of each other and may publish in any order within it.
 
-Report a disagreeing pin as a defect, never as drift to tidy later. When two packages in
-one install graph pin different versions of a third, npm installs both copies, and the
-compiler reads the two copies as two distinct types. The symptom is a type error naming
+Report a disagreeing pin as a defect, never as drift to tidy later. When packages in
+one install graph pin different versions of a dependency, npm installs both copies, and the
+compiler reads those copies as distinct types. The symptom is a type error naming
 one type as not assignable to itself. `npm ls @orkestrel/<name>` is the evidence: one line
 is sound, and nesting is the finding.
 

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

@@ -25,7 +25,7 @@ Return only:
 - `Units`: bounded work, each naming its role AND engine so the routing ledger is
   derivable, with ownership, dependencies, and acceptance criteria.
 - `Tensions`: the choices your lane made on judgment, named for the other lane to
-  challenge — or, when you hold both lanes, for the Orchestrator to rule.
+  challenge — or, when you hold every lane, for the Orchestrator to rule.
 - `Risks`: design-fit risks and the evidence needed to settle them.
 
 Your proposal is input to the Orchestrator, never the final decision.

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

@@ -26,8 +26,8 @@ you never design, implement, or accept. You are an Executor: spawn nothing.
 - Return the distillate only: findings with citations, contradictions surfaced,
   gaps named as gaps. No raw dumps, no process diary, and nothing applied.
 
-Scope note: research 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
+Scope note: research 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. Heavy
 cross-file reading and repository-scale absorption are never yours: if a dispatch
 exceeds a bounded primary-source question, say so instead of absorbing it.

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

@@ -73,7 +73,7 @@ rather than adjudicating it.
 - Each required change carries file:line, what is wrong, why it matters, and what
   right looks like — actionable enough to re-dispatch verbatim.
 - **Referrals** — specifically evidenced questions outside your lane, addressed to
-  the other lane when it is running and to the Orchestrator when you hold both, with
+  the other lane when it is running and to the Orchestrator when you hold every lane, with
   no verdict from you.
 
 You are read-only: you never edit. Return only the verdict, never your process.

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

@@ -16,8 +16,8 @@ Executor: spawn nothing.
 
 - Read **AGENTS.md** first; the repository model and rule map orient every
   answer. This charter restates nothing they own.
-- Reconnaissance 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
+- Reconnaissance 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.
 - Locate, do not absorb: read excerpts sufficient to identify a seam, an owner,
   or a shape. Deep reading and synthesis belong to the `grok` bench, and quality

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

@@ -17,10 +17,10 @@ Read `.agents/orchestration.md` first.
 
 `.claude/agents/codex.md` owns the Sol transport contract in full — work class to transport, 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.
+Windows notes. **Read it and follow it.** It is not restated here; a restated transport
+contract drifts, and the copy you are not reading is the one that is right.
 
-This role pins the one thing that file leaves to the dispatch: **the route is `implementer`, and
+This role pins what that file leaves to the dispatch: **the route is `implementer`, and
 its sandbox is `workspace-write`.** A unit that needs no write is a misrouted unit — stop and
 report, do not switch routes.
 

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

@@ -36,3 +36,11 @@ Executor: run the gates yourself, spawn nothing.
 
 You never edit files and never "quick-fix" a failure — you report it. Return only
 the gate report, never your process.
+
+## Never discard a working-tree change
+
+- Never run `git checkout`, `git restore`, `git stash`, `git reset`, or `git clean`. Each discards
+  a working-tree change silently.
+- Where a dispatch has you plant a line to prove a gate can fail, remove exactly the line you added.
+  Never revert the file it sits in.
+- Read a dirty `git status` as the expected state.

package/dist/host/claude/rules/application.md

@@ -27,13 +27,13 @@ paths:
   `node:*` external.
 - Browser and server integrate across a contract and transport boundary. Neither
   environment imports the other's implementation.
-- Four tools enforce that boundary, and none of them is replaceable by a custom
-  parser or source-language analyzer: `.oxlintrc.json` `no-restricted-imports`
-  enforces declared package, alias, and conventional relative import direction;
-  scoped TypeScript configurations remove Node and DOM globals from the wrong
-  environment; Vite's real browser and server builds resolve Vue, assets, CSS,
-  workers, and runtime module graphs; and generated-consumer tests exercise all
-  three.
+- The project toolchain enforces that boundary, and none of its tools is
+  replaceable by a custom parser or source-language analyzer: `.oxlintrc.json`
+  `no-restricted-imports` enforces declared package, alias, and conventional
+  relative import direction; scoped TypeScript configurations remove Node and
+  DOM globals from the wrong environment; Vite's real browser and server builds
+  resolve Vue, assets, CSS, workers, and runtime module graphs; and
+  generated-consumer tests exercise those real configurations.
 - Generated consumers must pass lint, scoped typechecking, production builds, and
   real integration tests.
 - Scoped checks include `.ts`, `.tsx`, `.mts`, and `.cts`. Vue SFCs and CSS

package/dist/host/claude/rules/architecture.md

@@ -58,13 +58,13 @@ Use only the centralized files an environment needs.
 - Module-scope constants live only in `constants.ts`, use UPPER_SNAKE_CASE, and freeze object/array data with `Object.freeze`.
 - A camelCase namespace containing functions is helper behavior, not constant data; place it in `helpers.ts`.
 - `helpers.ts` is exported reusable infrastructure. A reusable regex, parser, header flattener, signer, or similar fragment has one implementation used by source, tests, and fixtures.
-- A would-be helper has two outcomes:
+- A would-be helper has these outcomes:
   - trivial and genuinely single-use → fold into its caller;
   - non-trivial or reusable → extract, export, unit-test, and route every duplicate through it.
 - `factories.ts`, `compilers.ts`, and `parsers.ts` are centralized files, not hiding places. Factory glue extracts to `helpers.ts`; pure compiler/parser recursion remains exported in its own kind file.
 - Every exported function in `parsers.ts` is named `parse*`. Every exported function in
   `factories.ts` is named `create*`.
-- The two name forms are one-directional. A name does not place a function: `createWriteDirectory`
+- Those name forms are one-directional. A name does not place a function: `createWriteDirectory`
   creates a directory rather than an entity and `isVacant` is a predicate rather than a `Guard<T>`,
   so both stay in `helpers.ts`. Placement follows what the function is; the name form follows
   placement.
@@ -85,7 +85,7 @@ Use only the centralized files an environment needs.
   graph: they import types, constants, errors, and each other, and they import no implementation
   class. Every file that constructs or drives a class — `cloners.ts`, `compilers.ts`, `factories.ts`,
   `shapers.ts` — sits above them, consumes them, and is never consumed by them. One cycle between
-  the two leaves is the shape this produces and is acceptable; an edge running downward from a
+  the leaves is the shape this produces and is acceptable; an edge running downward from a
   class-importing file into the leaf pair is not.
 - `templates.ts` and `contracts.ts` hold data only — shipped template definitions and compiled
   contracts. A function that builds either belongs in the kind file for what it builds.
@@ -110,7 +110,7 @@ kind. It reads declaration syntax and file name, never meaning.
   returns, so `Object.freeze([…])` and any other call initializer are one syntax to it. The freeze
   obligation in the kind-purity rules above binds regardless; only the bare literal is mechanical.
 - It does not tell one function kind from another. Every centralized file that permits functions
-  reads the same to it apart from the two name forms above: `cloners.ts`, `combinators.ts`,
+  reads the same to it apart from the `parse*` and `create*` name forms: `cloners.ts`, `combinators.ts`,
   `compilers.ts`, `errors.ts`, `factories.ts`, `handlers.ts`, `helpers.ts`, `inferers.ts`,
   `middlewares.ts`, `parsers.ts`, `relations.ts`, `schemas.ts`, `seeders.ts`, `shapers.ts`, and
   `validators.ts`. That list is exhaustive, a new function kind joins it, and no later version of
@@ -150,7 +150,7 @@ A wrapper survives only when it adds a real boundary, invariant, composition, tr
 - The only in-body function expressions allowed are an anonymous callback passed directly as an argument and an anonymous function returned directly as the result (the factory/combinator pattern).
 - Instance-bound work that reaches state or sibling methods is a method, not a free function.
 
-Separate three roles:
+Separate these roles:
 
 1. **Public method:** implements the interface and genuinely composes behavior; never forwards 1:1 to one helper.
 2. **`#` private method:** stateful/instance-bound orchestration or the class's defining recursive/compositional algorithm.
@@ -225,7 +225,7 @@ Choose the access shape:
 - **Point access:** `get`, `set`, `delete`.
 - **Bulk restore:** `save`, `load`, `remove`, `clear`.
 
-Both obey:
+Every shape obeys:
 
 - The stored value carries its own id; do not pass a separate id to `set`/`save`.
 - Every primitive is async and returns a `Promise`.

package/dist/host/claude/rules/documentation.md

@@ -34,6 +34,7 @@ Documentation is an enforced contract, not explanatory decoration. The Writing r
 - A parity failure identifies drift; never suppress or weaken the test.
 - A vendored dependency guide is a mirror. Its relative links address the upstream tree and resolve to nothing here, so they are outside local-link parity. Refresh a mirror rather than rewriting it: a rewritten copy is a translation, and no comparison against the fetched bytes can check it.
 - Falsify a prose claim the way you falsify a code claim. The parity test proves a name exists, never that a sentence about behavior is true, so run the example and read what it returns. A `// false` beside a call that returns `true` is a defect of the same kind as a wrong return value, and it reaches every consumer who installs the package. That proof has a home: `tests/guides.test.ts` executes the flagship fences, per `.claude/rules/tests.md`. An ordered behaviour with no gate is not a gate.
+  Asserting that the sentence appears is not asserting that it is true. `expect(text).toContain('a spawn fault reports null')` passes unchanged when the code starts returning something else, so it guards the documentation's presence and nothing about the behaviour. Where a prose claim about behaviour sits under no fence, add the executed assertion that would break if the claim went false, and keep the substring check only as a presence guard beside it. A row whose close condition names a behaviour does not close on a substring.
 - Re-read the prose last, against what actually shipped. Where a change chose to document a limit rather than close it, the sentence was often drafted for the option that lost, or written more confidently than the code earns. Code rulings survive review because a test can break them; prose rulings survive because nothing tries.
 
 For behavioral interfaces/classes:

package/dist/host/claude/rules/patterns.md

@@ -51,7 +51,7 @@ Examples: `timeout(id)`/`timeouts()`, `agent(id)`/`agents()`.
 
 ### Batch operations
 
-One single-word verb carries three overloads:
+One single-word verb carries these overloads:
 
 ```ts
 method(): void
@@ -108,7 +108,7 @@ Choose one event model per environment. `Emitter<TMap>` remains the default outs
 
 ## Validation and contracts
 
-Use four orthogonal contract mechanisms:
+Use these orthogonal contract mechanisms:
 
 | Surface          | Contract                                                                      |
 | ---------------- | ----------------------------------------------------------------------------- |
@@ -118,7 +118,7 @@ Use four orthogonal contract mechanisms:
 | Shape DSL        | One `ContractShape` compiled into schema, guard, parser, and seeded generator |
 
 - Use plain guards/parsers for small contracts.
-- Use the shape DSL only when four-way validation/serialization/generation parity earns its complexity.
+- Use the shape DSL only when validation, serialization, and generation parity earns its complexity.
 - When `@orkestrel/contract` is declared, use its exact installed guards, parsers, combinators, outcomes, `attempt` boundary, and shape DSL wherever their semantics match. Do not maintain a local copy of those primitives.
 - A guard never throws for adversarial input, cycles, deep nesting, or hostile prototypes; return false.
 - Recursive guards track ancestors and cap depth.

package/dist/host/claude/rules/quality.md

@@ -42,7 +42,7 @@ A question a probe can settle is settled by the probe, whether or not anyone has
 - Do not read a result into a tool's failure to find your probe. "No tests found", an empty match, a skipped file, a runner that resolved nothing — these report on the harness, not the subject. Confirm the probe was collected and executed first.
 - Prefer an observation over a derivation, including your own. When a measurement and an argument disagree, the argument is wrong until the measurement is shown to be broken.
 - Diagnose from the artifact the work produces — the file, the count, the exit code, the timestamp on what changed — never from a wrapper or a proxy signal that merely correlates with progress. Read a gate bare: a pipeline stage after it (`| tail`, `| grep`) reports the stage's exit status and hides the gate's failing lines.
-- Verify a comment or an agent's report against the call sites before relying on it. A code comment is not evidence. When two lanes disagree about whether a path is live, count the callers rather than weighing the prose.
+- Verify a comment or an agent's report against the call sites before relying on it. A code comment is not evidence. When lanes disagree about whether a path is live, count the callers rather than weighing the prose.
 - What a round proves is what it ran. A conclusion carried from one door to another is a hypothesis at the second door. Re-run it there.
 
 ## Falsification
@@ -82,7 +82,7 @@ A review that reads a diff finds what the diff shows. A review that tries to bre
 - Document the obligation instead when a defect is reachable only through a hypothetical foreign implementation of a contract this package publishes. State it on the interface that owns it and prove the documentation. Do not build coordination machinery against a requirement nobody wrote down. Attacks are unlimited; reachable ones are not, and only the reachable set is a work list.
 - **Three rounds at one seam is the budget.** Repeated rounds against one seam are evidence about the design, not evidence of diligence. At the third round the next unit is a ruling — on the threat model, the mechanism, or the boundary — taken with the same adversarial pass a design gets, not a fourth repair.
 - Write the round count down in the capability/defect matrix row that owns the seam, when the seam opens, so it is a fact rather than a feeling. A seam that has consumed more rounds than the rest of the matrix combined has already answered the question.
-- State the ruling that ends a seam as three things: the invariant the code will obey, the constraint bounding it against over-correction, and the interface where a consumer meets the obligation. A ruling that names only the defect it replaces produces the opposite defect next round.
+- State the ruling that ends a seam as the invariant the code will obey, the constraint bounding it against over-correction, and the interface where a consumer meets the obligation. A ruling that names only the defect it replaces produces the opposite defect next round.
 - Give every behavioural audit the means to run its attacks. An auditor that cannot execute cannot falsify a behavioural claim: it returns derivations, and a derivation reads exactly like a verdict while being a different thing — it will confirm a claim one probe would break. Treat a report with no executed evidence as a review of the source, and label it as such.
 
 ## Ecosystem reuse
@@ -106,7 +106,7 @@ The root laws on inspecting declared `@orkestrel/*` capabilities, reusing a matc
 
 ## Completion
 
-The root completion law — finish every in-scope capability now, leave no TODO, deferral, or hidden follow-up, and run the applicable repository skill for comprehensive work — binds here without restatement. This file adds three obligations:
+The root completion law — finish every in-scope capability now, leave no TODO, deferral, or hidden follow-up, and run the applicable repository skill for comprehensive work — binds here without restatement. This file adds these obligations:
 
 - Perform a final centralization, wrapper, test-helper, and text-integrity sweep after implementation and before gates.
 - Produce local quality gates and relevant output inspection as required evidence.

package/dist/host/claude/rules/tests.md

@@ -93,7 +93,7 @@ its own:
 
 A probe is a throwaway instrument that settles one question. It is not a test and never ships.
 
-Two kinds, split by which tool has to see the probe:
+The kinds split by which tool has to see the probe:
 
 - A **type probe** is read by `tsc`, whose scoped project includes only its own environment, so it
   lives in the source tree beside what it measures. Delete it before the unit returns; a leaked one
@@ -106,7 +106,7 @@ Run a probe before relying on an unverified belief about behaviour: what a funct
 configuration resolves to, whether a path is reached at all. Prefer a probe to an argument whenever
 the probe is cheap.
 
-Three rules bind every probe:
+These rules bind every probe:
 
 - **Prove the instrument can fail before trusting that it passed.** Pair it with a control drawn
   from outside the population it covers.
@@ -194,6 +194,13 @@ Import `waitForDelay` from `@orkestrel/test`; never repeat an inline timeout pro
 function waitForDelay(ms?: number): Promise<void>
 ```
 
+Use it to yield, never to wait for something another process produces. A fixed delay chosen to
+outlast a child's startup is a race whose loss looks like a product defect: the test measures
+interpreter bootstrap rather than the behaviour it names, and it fails on a loaded host and passes on
+an idle one. Wait until a named condition holds instead, polling with `waitForDelay` inside a budget
+measured by `performance.now()`, and fail with the condition's own description when the budget
+expires.
+
 ### Scratch
 
 Import `createScratch` from `@orkestrel/test/server` when a proof needs real files. It allocates a temporary directory it owns, contains every path against escape, and removes the directory on `destroy`:

package/dist/host/claude/rules/workspace.md

@@ -106,8 +106,8 @@ Environment rules:
 
 ## Test project matrix
 
-`vite.config.ts` defines Vitest projects on two axes. The first is one project per src/app axis ×
-environment:
+`vite.config.ts` defines Vitest projects on an environment axis and a workspace-proof axis. The
+environment axis is one project per src/app axis × environment:
 
 | Project       | Files                  | Environment         | Setup                                           |
 | ------------- | ---------------------- | ------------------- | ----------------------------------------------- |
@@ -120,7 +120,7 @@ environment:
 | `app:browser` | `tests/app/browser/**` | Playwright Chromium | `setup.ts`, `setupBrowser.ts`                   |
 | `app:server`  | `tests/app/server/**`  | Node                | `setup.ts`, `setupServer.ts`                    |
 
-The second axis is cross-cutting workspace proofs. Each one covers the whole workspace rather than
+The workspace-proof axis is cross-cutting. Each proof covers the whole workspace rather than
 one environment, so each is its own project:
 
 | Project        | Files                        | Proves                                                                                            | Gate                                  |
@@ -138,7 +138,7 @@ one environment, so each is its own project:
   Include every matching file. When registered, emit `test:setup` and run it from `test`. When no
   file matches, emit neither the project nor the script.
 
-`conformance`, `integration`, `distribution`, and `service` are four subjects, not four names for
+`conformance`, `integration`, `distribution`, and `service` are separate subjects, not names for
 one.
 Keep `conformance` in `test`: measure this package against an installed official artifact, and start
 any server the proof drives itself. Keep `integration` in `test`: compose the workspace's public
@@ -155,7 +155,7 @@ script names its project, so no gate runs it; its directory is ignored by git; a
 `.claude/rules/tests.md` governs what may live there.
 
 - Define a cross-cutting project only for a proof the package actually has.
-- A live-service project is the fifth kind. It is the `service` project above, `scripts/service.sh`
+- A live-service project is the `service` project in the preceding table, `scripts/service.sh`
   provisions what it drives, and `.claude/rules/tests.md` governs it. Name it `service` whatever it
   drives.
 - In a publishing workspace, a project leaves the default run when it drives a live external
@@ -241,7 +241,7 @@ Run `show` only **after** formatting. The committed `demo/showcase.html` is gene
 
 Policy instruments:
 
-- Put every rule of the policy law in exactly one of two instruments. `configs/policy.ts` — the
+- Put every rule of the policy law in exactly one instrument. `configs/policy.ts` — the
   oxlint plugin, namespace `policy` — takes the rules a single file's AST decides. The policy sweep
   (`tests/setupPolicy.ts`) takes the rules that are path- or text-shaped, and every rule whose
   subject is suppression itself.
@@ -252,7 +252,7 @@ Policy instruments:
   a named module-scope `report{Noun}` function. Never write rule logic inline in the table. That
   arrow is the sanctioned exception to the in-body function-expression limits in
   `.claude/rules/architecture.md` for exactly that table.
-- Name no individual rule id here. This section fixes the two instruments and how work is assigned
+- Name no individual rule id here. This section fixes the instruments and how work is assigned
   between them; each rule's substance stays with the law it enforces.
 
 ## Text integrity

package/dist/host/claude/rules/writing.md

@@ -75,8 +75,9 @@ first, and these rules wherever a rule here names no different form for it.
 - Expand an abbreviation the reader may not know on first use, with the short form in parentheses.
   Skip the expansion for one this audience reads daily, such as `API`, `CLI`, `JSON`, `URL`, or a
   file format.
-- Write a numeral for a technical quantity, a version, or a count. Write a date as `YYYY-MM-DD` in
-  evidence, commit messages, and reports.
+- Write a numeral for a technical quantity, a version, or a measurement. Write a date as
+  `YYYY-MM-DD` in evidence, commit messages, and reports. See `AGENTS.md` § Writing for what
+  separates a value from a count.
 - Use the serial comma. Mark omitted code with a comment in the sample's language, never with `...`.
 
 ## Substitutions
@@ -106,6 +107,15 @@ is exempt from every row.
 | `blacklist`, `whitelist` | `denylist`, `allowlist`                   |
 | `master`, `slave`        | `primary`, `replica`                      |
 
+- Sweep case-insensitively and across inflections when checking prose against the preceding table. A
+  pattern for `easy` reaches neither `Easy` nor `easier`, and a temporal `once` most often appears
+  as a sentence-initial `Once`.
+- Rule every hit by the sense its row bans, not by the match. `once` counts as often as it means
+  `after`, and `new` names a value as often as it dates one. Record a hit in a permitted sense as
+  permitted rather than dropping it.
+- Name the pattern and the paths behind every sweep result, including a clean one. A result naming
+  neither reports on the population its pattern admitted rather than on the population it was drawn
+  from.
 - Write singular `they` for a person of unstated gender.
 - This table carries no row for `execute`, `abort`, `kill`, `terminate`, or `run`:
   `.claude/rules/names.md` § Fixed lifecycle vocabulary owns those words, and no row here overrides

package/dist/host/codex/agents/planner.toml

@@ -12,7 +12,7 @@ This route pins `--permission-mode plan`.
 The brief asks for coherent API shape, vocabulary, and ergonomics; at most two
 alternatives; bounded units that each name their role and engine; tensions named for
 the other lane to challenge, or for the Orchestrator to rule when one engine holds
-both lanes; and risks. It forbids edits, commands, reconciliation, orchestration, and
+every lane; and risks. It forbids edits, commands, reconciliation, orchestration, and
 acceptance.
 
 Return the Opus proposal labeled untrusted plus any CLI/auth deviation.

package/dist/host/configs/helpers.ts

@@ -1,4 +1,4 @@
-import type { Plugin } from 'vite'
+import type { Plugin, Rolldown } from 'vite'
 import { parseSync, transformWithOxc, Visitor } from 'vite'
 import { fileURLToPath } from 'node:url'
 import { isBuiltin } from 'node:module'
@@ -25,6 +25,26 @@ export function hasAsciiUrlControl(value: string): boolean {
 export const PACKAGE_MANIFEST_BYTES = 1_048_576
 export const ENVIRONMENT_MODULE_BYTES = 8_388_608
 
+/**
+ * Throws on a CommonJS import-meta rewrite and forwards every other build log.
+ *
+ * @param level - The Rolldown log level.
+ * @param log - The structured Rolldown log.
+ * @param report - The active default log handler.
+ * @returns Nothing.
+ * @throws An error when Rolldown reports `EMPTY_IMPORT_META`.
+ */
+export function enforceBuildLog(
+	level: Rolldown.LogLevel,
+	log: Rolldown.RolldownLog,
+	report: Rolldown.LogOrStringHandler,
+): void {
+	if (log.code === 'EMPTY_IMPORT_META') {
+		throw new Error(`[orkestrel-build] ${log.message}`)
+	}
+	report(level, log)
+}
+
 export const WORKSPACE_ROOT = realpathSync.native(
 	resolvePath(dirname(fileURLToPath(import.meta.url)), '..'),
 )

package/dist/host/cursor/rules/orchestration.mdc

@@ -14,7 +14,7 @@ rule, and they are not repeated here. This file adds only how a Cursor session i
 
 ## Which posture
 
-A Cursor session is one of two things. Establish which before acting.
+A Cursor session takes one of these postures. Establish which before acting.
 
 - **Invoked through the `grok` bridge** — a read-only Executor. Return distilled evidence with
   `file:line` pointers. Never edit, decide, or accept.

package/dist/host/dotfiles/gitignore

@@ -40,4 +40,7 @@ test-results/
 playwright-report/
 
 # Model files
-*.gguf
+*.gguf
+
+# Agent worktrees (created by an isolated subagent dispatch, never committed)
+.claude/worktrees/