@orkestrel/scaffold 0.0.108 → 0.0.109

package/dist/host/AGENTS.md

@@ -9,7 +9,7 @@
 - `*/types.ts` is authoritative for public APIs. Never undo a user's type edit.
 - `.agents/orchestration.md` governs agent operation and cannot weaken this file. Harness bridges (`.claude/AGENTS.md`, `.codex/config.toml`, `.cursor/rules/orchestration.mdc`) add harness mechanics only.
 - A skill under `.agents/skills/` is a procedure. Follow it when the user or a dispatch names it, or when its trigger fires. A skill cannot weaken this file or a rule.
-- Before editing, read: this file; each rule the Rule map scopes to the paths you touch; the named skill and the references it names; the matching guide under `guides/` and `ROADMAP.md` when present. Read nothing else up front.
+- Before editing, read: this file; each rule whose `paths` frontmatter matches the paths you touch; the named skill and the references it names; the matching guide under `guides/` and `ROADMAP.md` when present. Read nothing else up front.
 - Rules state how to write. Guides state what to build. On conflict, stop and report the conflict.
 - A rule file's stated exception to a law in this file applies.
 
@@ -43,7 +43,7 @@ configs/  thin target wrappers around root Vite/TypeScript configuration
 - **NEVER** use mocks, behavioral fakes, module replacement, framework spies, or fake clocks for project-owned behavior. Use real implementations, recorders, temporary resources, protocol-faithful fixture servers, and inert data stubs.
 - **ALWAYS** make interface properties and public return collections readonly.
 - **ALWAYS** define reusable and public types in `*/types.ts` before implementation.
-- **ALWAYS** inspect the declared and installed `@orkestrel/*` capabilities before writing overlapping logic. Reuse a primitive whose semantics match; never wrap one to rename it.
+- **ALWAYS** check whether an `@orkestrel` package already provides a capability before writing logic, a tool, or an instrument that could overlap it. Read the package guides first: `guides/README.md` maps them, and a target holds them under `node_modules/@orkestrel/scaffold/dist/host/guides/`. When a guide leaves the question open, read the package's source in a checkout beside the repository. When no checkout exists, read its repository at `https://github.com/orkestrel/<package>`, online or cloned under `tmp/`. Reuse a primitive whose semantics match; never wrap one to rename it.
 - **ALWAYS** finish the requested implementation: no stubs, deferred logic, or hidden follow-up.
 - **ALWAYS** write a script as TypeScript run by Node (`node path/to/script.ts`, type stripping, `node:` modules only): a skill script, a probe, a launcher, an instrument, a one-off tool. Never write a bash, PowerShell, or Python script. The Claude Code Cloud hooks under `scripts/` are the one bash exception, and that folder holds nothing else.
 
@@ -72,6 +72,8 @@ configs/  thin target wrappers around root Vite/TypeScript configuration
 
 Types, tests, and implementation decide every step; comments, TSDoc, and guides follow the final implementation. Report results against the goal, and prefer the smallest change that reaches green over a perfect one.
 
+Open a task with its goal, its acceptance criteria, and the cheapest pass/fail check that proves them. Before writing a fixture, proof, or tool around a command, run that command on real data. `.agents/orchestration.md` § Depth, breadth, and machinery sizes the effort and rules on what becomes a package.
+
 Size the change before touching a file. Take the largest row whose trigger applies: large, then medium, then small. Run only what the row names.
 
 | Size   | Trigger                                                                                                                                                                                                 | Do                                                                                                                                                                                                           |
@@ -89,7 +91,7 @@ Within the size, in order:
 3. **Implement.** Conform to the types. Place each declaration in its kind file. Update the barrel.
 4. **Test.** Cover happy paths, edge cases, failures, and boundaries with deterministic tests against real implementations. For a defect, record the failing command and count before the fix and the same command green after.
 5. **Consolidate.** Remove duplication, nested functions, and superfluous wrappers without widening the API.
-6. **Document.** Once the implementation is final, update the matching guide, comments, and TSDoc in one minimal pass. Before then, write, revise, and review no prose.
+6. **Document.** After the implementation is final, update the matching guide, comments, and TSDoc in one minimal pass. Before then, write, revise, and review no prose.
 
 Test ladder, narrowest first; stop at the boundary the change size names:
 
@@ -108,24 +110,24 @@ Test ladder, narrowest first; stop at the boundary the change size names:
 
 ## Rule map
 
-Each row is a normative extension of this file. Its `paths` frontmatter controls automatic loading; read the row when its subject matches your change.
-
-| Rule                             | Governs                                                                |
-| -------------------------------- | ---------------------------------------------------------------------- |
-| `.claude/rules/names.md`         | Identifiers, API shape, acronyms, lifecycle vocabulary, files/folders  |
-| `.claude/rules/typescript.md`    | TypeScript syntax, imports, immutability, errors, TSDoc                |
-| `.claude/rules/architecture.md`  | Centralized files, exports, classes, modules, extension points, stores |
-| `.claude/rules/patterns.md`      | Options, managers, emitters, guards, parsers, contracts                |
-| `.claude/rules/tests.md`         | Test behavior, helpers, probes, browser tests, Vitest configuration    |
-| `.claude/rules/workspace.md`     | Src/app environments, aliases, isolation, builds, scripts, tooling     |
-| `.claude/rules/application.md`   | App composition, entries, manifest safety, lifecycle, integration      |
-| `.claude/rules/browser.md`       | Vue/browser architecture and platform usage                            |
-| `.claude/rules/styles.md`        | SCSS/CSS centralization, tokens, mixins, layers, naming                |
-| `.claude/rules/portability.md`   | Host branching, paths, line endings, processes, terminals, OS claims   |
-| `.claude/rules/documentation.md` | Guides, parity, roadmap, showcase, examples, skill files               |
-| `.claude/rules/writing.md`       | Prose in guides, replies, commits, and instruction files               |
-| `.claude/rules/quality.md`       | Evidence, probes, instruments, performance, research, completion       |
-| `.claude/rules/campaign.md`      | The `.orkestrel/` campaign folder: layout, content, session start      |
+Each row is a normative extension of this file. A rule's `paths` frontmatter controls automatic loading, and `.claude/rules/writing.md` carries none and loads always. Read the row when its subject matches your change.
+
+| Rule                             | Governs                                                                                                                                     |
+| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
+| `.claude/rules/names.md`         | Identifiers, API shape, helper prefixes, acronyms, fleet name ownership, lifecycle vocabulary, files and folders                            |
+| `.claude/rules/typescript.md`    | TypeScript syntax, imports, types, immutability, bindings and state, errors, TSDoc                                                          |
+| `.claude/rules/architecture.md`  | Centralized files, declaration placement, kind purity, wrappers, functions, classes, middleware, plugins, stores, barrels                   |
+| `.claude/rules/patterns.md`      | Ecosystem reuse, options, managers, emitters, validation and contracts, foreign contracts                                                   |
+| `.claude/rules/tests.md`         | Test contract, cross-cutting proofs, probes, live-service and expensive proofs, shared helpers, browser tests, runner configuration         |
+| `.claude/rules/workspace.md`     | Src/app environments, aliases, configuration, builds, test project matrix, typechecking scopes, scripts, policy instruments, text integrity |
+| `.claude/rules/application.md`   | App composition, CLI selections, entries, manifests, server runner                                                                          |
+| `.claude/rules/browser.md`       | Vue and browser architecture: composables, reactivity, platform APIs                                                                        |
+| `.claude/rules/styles.md`        | SCSS/CSS centralization, tokens, mixins, layers, folders, proofs, naming                                                                    |
+| `.claude/rules/portability.md`   | Host branching, line endings, paths, processes, terminals, scripts and packaging, host claims                                               |
+| `.claude/rules/documentation.md` | Guides, parity, examples, agent-facing surfaces, skill files                                                                                |
+| `.claude/rules/writing.md`       | Prose in guides, replies, commits, and instruction files                                                                                    |
+| `.claude/rules/quality.md`       | Evidence, probes, instruments, performance, ecosystem reuse, hardening, completion                                                          |
+| `.claude/rules/campaign.md`      | The `.orkestrel/` campaign folder: layout, content, session start, hand off and close                                                       |
 
 ## Writing
 

package/dist/host/agents/orchestration.md

@@ -52,6 +52,7 @@ The harness's own engine orchestrates: Claude Fable 5.1 or Claude Opus 5.5 in Cl
 - Route by judgment load. Objective, constraint-heavy, mechanical-precision work goes to `astra`. API shape, naming, and documentation voice go to `opus`. A bounded unit whose brief or types fix its names, API, and architecture goes to `builder`, whatever its private lines; a unit that spans packages or leaves one of those open goes to `astra` or `opus`.
 - Route all context absorption, distillation, broad mapping, and exploratory or fishing reads to `grok` on Cursor Grok 4.7 Extra High: terrain, prior art, diff sweeps, scattered sources. Keep decision-bearing reading with the decision owner. Fall back to `distiller` or `researcher` only when the Cursor bench is dark, and record the fallback; ease or cost never authorizes a fallback.
 - Keep small tedious precise tasks native: Claude Haiku in Claude, Codex Luna in Codex. Use `scout` for an exact bounded lookup; keep bench drivers, `checker`, and `verifier` on their mapped native engines. A bounded file scope does not turn context absorption or exploratory reading into a native lookup.
+- Route a unit that authors path-containment, import-resolution-boundary, unescaped-input, or credential-exposure proofs to `opus` from the start where `opus` runs on Claude, and record the Codex bench dark for that unit only. Under native Codex roles, report a harness refusal through § Deviation protocol.
 - Route gates to `verifier`. A writer's self-reported gate is not evidence.
 - Under the Codex mapping, put falsify lanes on Astra or Sol at high effort; keep Luna for gates and verifier runs, never for a lane that must resolve runtime claims.
 - Work directly on a one-file change or a one-line fix, subject to the preceding routing rules. Route standalone lookups through `scout`. Dispatch when isolation, parallelism, a second engine, or a large read pays for the brief.
@@ -77,10 +78,33 @@ The harness's own engine orchestrates: Claude Fable 5.1 or Claude Opus 5.5 in Cl
 ## Pace
 
 - Spend process only where it changes a result. Launch, run, and report: no fixed clock windows, readiness-only turns, per-command acknowledgments, hash pins of a brief, or process queries beyond the recorded process ids.
-- Re-run a check only when its inputs changed; never repeat a passing check to collect another receipt.
-- Ask the user only for a decision that is theirs: scope, a conflicting ruling, a credential, publication, or a commit or push the law reserves. Decide routine matters yourself, such as time and lane allowances, retries, and order, and report them.
+- When a verifier lane fails in its harness rather than in the gate, run the gate once yourself and read its exit code; write no comparator, snapshot, or retry chain to obtain evidence.
+- Keep valid receipts. Re-run a check only when its inputs, configuration, environment, or claim changed; never repeat a passing check to collect another receipt.
+- Ask the user only for a decision that is theirs: scope, the spend ceiling and stop line § Hold the plan names, a conflicting ruling, a credential, publication, or a commit or push the law reserves. Decide routine matters yourself, such as time and lane allowances, retries, and order, and report them, with time in whole minutes.
 - Never end a turn with work pending and nothing that will wake the session: run the work as a tracked background command or a child whose completion notifies, or schedule a wake. While a lane runs, continue independent work.
-- Keep the goal, the current step, and the next action visible in the campaign plan, and report progress against the goal at each milestone.
+
+## Hold the plan
+
+- Open with the goal and acceptance criteria per `AGENTS.md` § Work loop, then estimate the scope: the units, the review and evidence each needs, and what stays out. When the estimate is large, agree with the user the estimate, the spend ceiling, and the stop line: how much lane time the work can take, and the point at which work stops and reports.
+- Before each unit, name the plan step it serves. Cut a unit no step needs; set an unplanned idea aside in the plan and return to the step.
+- Add a tracked file only where the request, the plan, or a rule names it.
+- After every unit return, unexpected result, or user message, compare the work with the plan: mark what is done, restate the next step, and set aside what no longer serves the goal.
+- When the work outgrows its estimate, stop, re-estimate, and bring the user the choice to cut, defer, or extend before continuing.
+- When the user questions the plan, test it against the evidence in hand: reopen it where the evidence disagrees and report what changed; where the evidence holds, answer with that evidence.
+- Answer a status question before dispatching more work, and close every report the same way: the goal, what is done against it, what is measured, what remains, and the next step.
+
+## Depth, breadth, and machinery
+
+- Size the effort to the task before spending: a lookup takes one lane, routed per § Routing, and only open-ended work with independent, high-value parts fans out, per § Parallelism.
+- Locate the evidence with short broad probes before any deep pass: a run of the shipped command, a census, a search. Go deep only on a defect or gap a run has shown, in one lane, with the narrowest instrument that answers it: a counting probe or a mutation.
+- When a failure recurs, read the exact input and output of the failing case before adding capability, and fix the cause.
+- Deepen in rounds and report a usable result after each. Stop at the first result that clears the acceptance criteria and name the gaps that remain.
+- Prove a change in one consumer, with its gate green, before spreading it to the rest.
+- Use the simplest method that can clear the criteria, starting with what an `@orkestrel` package already provides, looked up per `AGENTS.md` § Non-negotiable rules. Add machinery only after that method fails a measured check, and build nothing for a hypothetical need.
+- Do a one-use step inline. Keep a tool one unit runs more than once as a throwaway under `tmp/`, deleted with the unit and never committed.
+- When a second unit, package, or campaign needs a tool, move it out of `tmp/`: into a skill script under `.agents/skills/` when it only runs a procedure, and into its own package, with its own tests and release, when it carries correctness claims of its own or an identity consumers pin, replay, or audit. Write the promotion path and the removal path when you first build it.
+- When a throwaway grows a mechanism per step instead of answering its question, stop and map it against the owning packages before building more.
+- Ship the proven fix first, and run experiments behind it under a stated cap.
 
 ## Size gate
 
@@ -94,7 +118,7 @@ The harness's own engine orchestrates: Claude Fable 5.1 or Claude Opus 5.5 in Cl
 
 - Never run a review on a small change. Never run a second design round on the same brief.
 - A review judges types, tests, and implementation. It reports comment, TSDoc, or guide wording only where the text contradicts the final behavior, and no fix round opens for prose alone.
-- A fix round re-audits the repaired claim only. A fix that adopted the reviewer's prescription verbatim closes with a mutation probe (disable the load-bearing line, watch the test fail, restore it). A fix that departs from it gets one pass by an independent reviewer per § Engines.
+- A fix round re-audits the repaired claim only. A fix that adopted the reviewer's prescription verbatim closes with a mutation probe (disable the load-bearing line, watch the test fail, restore it); `node .agents/skills/orkestrel-falsify/scripts/mutate.ts --edits EDITS.md -- COMMAND` runs the probe and proves the restore. A fix that departs from it gets one pass by an independent reviewer per § Engines.
 - When review rounds at one seam keep surfacing defects without converging on their source, follow `.agents/skills/orkestrel-falsify/SKILL.md` § End the depth search.
 - An all-confirmed round ends the audit. A round needs an added or repaired claim to test; reviewer appetite is not a subject.
 
@@ -105,7 +129,7 @@ A large change opens with a concise goal and its exit criterion, short enough to
 1. **Absorb.** Map the terrain with the `orkestrel-scout` skill's `map.ts`, then `grok` distills it and the prior art. In an Orkestrel repository, `verifier` or another tool-capable role collects manifests, lockfiles, installed declarations, and registry readings, and `orkestrel` reconciles them.
 2. **Design.** One independent round: `planner` (subjective) and `analyst` (objective) on one brief, clean contexts, blind to each other. Reconcile into one plan: units, owned files, dependencies, parallel and serial order, acceptance criteria, exit criterion, ledger.
 3. **Implement.** Dispatch units per § Routing and § Parallelism.
-4. **Integrate.** Apply returned patches to shared files serially. A type, mechanism, or criterion found here is a successor unit, never an integration edit.
+4. **Integrate.** Apply returned patches to shared files serially with `node .agents/skills/orkestrel-dispatch/scripts/patch.ts EDITS.md --plan`, then `--apply`. A type, mechanism, or criterion found here is a successor unit, never an integration edit.
 5. **Audit.** One `orkestrel-falsify` round on the integrated result, an independent reviewer per § Engines in each lane; add `checker` when the criteria are mechanical.
 6. **Verify.** `verifier` runs the tree-wide gates once.
 7. **Re-baseline.** Strike satisfied units, restate transformed ones, add units the exit criterion already required. A re-baseline never moves the exit criterion; that needs the user.
@@ -119,8 +143,8 @@ A large change opens with a concise goal and its exit criterion, short enough to
 - One writer per checkout, except under `orkestrel-parallel`: there, at most three writers share one checkout, each owns disjoint files and disjoint regions of shared files, and one runner lane owns every test, check, and build process. Otherwise give parallel writers disjoint owned files, and give a writer its own worktree under `tmp/worktrees/` only when two units must write the same files at once. Commit a checkpoint before a writing dispatch.
 - Fold every branch, clone, copy, or worktree an agent creates back into the original checkout's main branch with its changes left uncommitted there, so the user sees the whole difference from that branch. Commit inside the branch, clone, copy, or worktree as its unit needs, then remove it and delete its branch.
 - In a checkout another session shares, read the branch and `git status` before a write, and stop and ask the user when another session's uncommitted work is present.
-- Shared files are report-only; a unit returns an exact patch. Under `orkestrel-parallel`, a writer edits its owned regions of a shared file directly.
-- Scope validation by the claim and its input dependencies, not by writer ownership alone. Under `orkestrel-parallel`, the runner owns checks and obtains the required write holds. Preserve valid receipts; rerun a check when its inputs, configuration, environment, or claim changed. Never run tree-wide `format`, lint `--fix`, or `build` beside a live writer.
+- Shared files are report-only; a unit returns an exact patch as an edit file that `.agents/skills/orkestrel-dispatch/scripts/patch.ts` applies. Under `orkestrel-parallel`, a writer edits its owned regions of a shared file directly.
+- Scope validation by the claim and its input dependencies, not by writer ownership alone. Under `orkestrel-parallel`, the runner owns checks and obtains the required write holds; § Pace rules on reruns. Never run tree-wide `format`, lint `--fix`, or `build` beside a live writer.
 - One Grok lane at a time; queue the rest. An empty lane beside a live probe is starvation, not darkness.
 - The Orchestrator's own sweep is a writing dispatch: run it before or after the units, never beside them.
 
@@ -140,15 +164,15 @@ A large change opens with a concise goal and its exit criterion, short enough to
 
 Every working file lives under the checkout's gitignored `tmp/`, in the directory its kind names.
 
-| Directory                                  | Holds                                                                                              |
-| ------------------------------------------ | -------------------------------------------------------------------------------------------------- |
-| `tmp/claude/`, `tmp/codex/`, `tmp/cursor/` | bench briefs, launch scripts, journals, `.err` files, last-message files, login logs, per harness  |
-| `tmp/units/`                               | native unit briefs, reports, claims files, and unit records                                        |
-| `tmp/probes/`                              | runtime probes the `probe` Vitest project collects and the `probe` MCP server arms                 |
-| `tmp/type/`                                | the type stage's workspace mirror, owned by `@orkestrel/probe`                                     |
-| `tmp/captures/`                            | screenshots, resolved-style snapshots, and other capture portfolios                                |
-| `tmp/browsers/`                            | the journeys a `browse` server saves, their runs and captures, and its profiles under `.profiles/` |
-| `tmp/worktrees/`                           | worktrees the Orchestrator creates for a parallel writer                                           |
+| Directory                                  | Holds                                                                                                                                                                       |
+| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `tmp/claude/`, `tmp/codex/`, `tmp/cursor/` | bench briefs, launch scripts, journals, `.err` files, last-message files, login logs, per harness                                                                           |
+| `tmp/units/`                               | native unit briefs, reports, claims files, and unit records                                                                                                                 |
+| `tmp/probes/`                              | runtime probes the `probe` Vitest project collects and the `probe` MCP server arms, and a skill script's scratch under its own subdirectory (`census/`, `lint/`, `mutate/`) |
+| `tmp/type/`                                | the type stage's workspace mirror, owned by `@orkestrel/probe`                                                                                                              |
+| `tmp/captures/`                            | screenshots, resolved-style snapshots, and other capture portfolios                                                                                                         |
+| `tmp/browsers/`                            | the journeys a `browse` server saves, their runs and captures, and its profiles under `.profiles/`                                                                          |
+| `tmp/worktrees/`                           | worktrees the Orchestrator creates for a parallel writer                                                                                                                    |
 
 ## .orkestrel layout
 
@@ -158,7 +182,7 @@ Every working file lives under the checkout's gitignored `tmp/`, in the director
 
 `orkestrel-dispatch` owns the brief template, launch mechanics for native and bench units, long-running commands, liveness, and recovery. Load it before a bench lane, a campaign unit, or any command that outlives the turn. The floor that follows binds every dispatch.
 
-- A small native unit's brief is the dispatch message: scope, law references, expected result. Write a brief file with the dispatch skill's `scripts/brief.ts` at `tmp/units/<unit>-brief.md` (native) or `tmp/<bench>/<unit>-brief.md` (bench) when the unit is a bench lane, belongs to a campaign, or might need re-running. A re-run gets `<unit>-brief-<n>.md`; never edit a launched brief.
+- Write each brief per `.agents/skills/orkestrel-dispatch/SKILL.md` § Write the brief. A brief file lives at `tmp/units/<unit>-brief.md` (native) or `tmp/<bench>/<unit>-brief.md` (bench), and a re-run at `<unit>-brief-<n>.md`.
 - State in every brief: role and engine, one objective, the evidence slice, owned and off-limits files, the acceptance criteria cheap-first, the return shape, the deviation contract, and that the executor performs the work itself and spawns nothing.
 - Capture a campaign unit's report to `tmp/units/<unit>-report.md`, or read the bench's last-message file.
 - Launch every multi-minute command as a harness-tracked background command through `node .agents/skills/orkestrel-dispatch/scripts/launch.ts` under a cap sized from prior runs, and read a bench answer with that skill's `scripts/result.ts`. Every launcher, probe, and instrument is a TypeScript file run by `node`, never a shell or Python script. Read liveness from the artifact the work produces. Kill only a recorded process id, never a pattern, and confirm the process and its descendants are gone before another writer takes its files.
@@ -192,13 +216,14 @@ The Orchestrator triages: obvious correction → tighten and re-dispatch; missin
 
 - Keep the model, options, tools, and instruction prefix unchanged while they fit the task. Check the active provider and harness before claiming that a change preserves or invalidates caching. Treat a continued session as retained context, not as a cache hit; a cache hit depends on the provider, the prefix, and the retention window. Claim a saving only from recorded usage.
 - Keep the always-on instruction set small and load supporting rules by scope. When instructions change, use the harness's documented reload mechanism and tell affected agents what changed. Do not assume a file edit updates an active session.
-- Give reading and driver roles no instruction files (`omitClaudeMd` in Claude Code) when their charter carries the floor they need.
+- Give reading and driver roles no instruction files when their charter carries the floor they need.
 - Route bulk reads per § Routing and keep only the distillate.
 
 ## Acceptance
 
 - No writer's and no bench's self-assessment is authoritative. The Orchestrator accepts after the review and the gates the size gate names.
 - Accept when the exit criterion is met and the gates are green. Reopening an accepted criterion is the user's instruction, not a reviewer's finding.
+- Before calling work ready, try the shipped result as the user will, on the build they run, and report what did not run.
 - Substitute an engine only when the same session recorded the bench dark; name the fallback in the brief and the carrying commit.
 - In a repository whose package the registry already serves, commit on the main branch and push it only on the user's go-ahead.
 - Commit by explicit paths. Before a push, read `git log @{upstream}..` and push only commits meant to publish together; hold a push while a commit depends on an unpublished local pin.

package/dist/host/agents/platforms/windows.md

@@ -26,10 +26,10 @@ The commands an agent runs on a Windows host, and their quirks. `.claude/rules/p
 - `Get-FileHash` prints uppercase hexadecimal, and Node's `createHash` prints lowercase. Compare digests case-insensitively.
 - Redirecting a native command's standard error with `2>&1` wraps each line in an error record and sets `$?` to false on success. Let the harness capture standard error.
 
-## Harness approval on this host
+## Release packs and terminals
 
-- Keep every program-carrying command in a TypeScript file run by `node`. A heredoc, `node -e`, an `&&` chain, or a `${...}` argument trips the harness's approval classifier; a one-shot read-only check can run inline.
-- Run a `Remove-Item` as its own short command with a relative path. The classifier blocks a command that pairs it with a path-like literal elsewhere, such as a `'\'` string. Verify with `git status`.
+- Git Bash ships no `script` binary, so an agent cannot give npm a TTY there; the operator runs a browser-authorized `npm login` or `npm publish` in a real terminal.
+- A pack made on Windows records `0644` for an entry git tracks as `100755`. Compare release packs between hosts by paths, sizes, and content hashes, and report executable-mode differences separately.
 
 ## Deleting untracked files
 

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

@@ -19,17 +19,15 @@ Invoke `$orkestrel-harden` for each package implementation unit. This skill owns
 
 ## Execute the campaign
 
-1. **Create one registry.** Record the campaign goal, authoritative session, repositories, branches, dirty state, declared/resolved versions, dependency edges, guide state, write scope, and exclusions.
-2. **Bound context.** Scout only packages and consumers relevant to the behavior. Use registry/canonical sources for the rest of the fleet.
-3. **Trace the real flow.** Follow public types and one concrete consumer end to end. Identify where ergonomics break and which layer owns the reusable mechanism.
-4. **Assign ownership.** Keep core host-independent. Keep server free of browser assumptions and browser free of Node assumptions. Keep product policy in applications.
-5. **Judge downstream friction.** Treat consumer gymnastics as evidence, not automatic proof. Decide whether the consumer misused a coherent API or exposed a general upstream defect.
-6. **Design in dependency order.** Update guides and types first in the lowest owning package, then update every affected consumer atomically. Do not add compatibility shims.
-7. **Harden each unit.** Apply `$orkestrel-harden` to every touched package with the exact owned scope and acceptance criteria.
-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 review `.agents/orchestration.md` § Size gate names on the integrated result, with one cross-package architecture and ergonomics pass over the whole graph. Do not review each unit separately.
+Run `.agents/orchestration.md` § Campaign for the phases, the review, and the gates, and `$orkestrel-harden` for each package unit. Record the live state of every relevant repository per [fleet.md](references/fleet.md) § Verify live state. This skill adds:
+
+1. **Trace the real flow.** Follow public types and one concrete consumer end to end. Identify where ergonomics break and which layer owns the reusable mechanism.
+2. **Assign ownership.** Keep core host-independent. Keep server free of browser assumptions and browser free of Node assumptions. Keep product policy in applications.
+3. **Judge downstream friction.** Treat consumer gymnastics as evidence, not automatic proof. Decide whether the consumer misused a coherent API or exposed a general upstream defect.
+4. **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.
+5. **Validate local changes safely.** When necessary, use built artifacts in an isolated consumer and prove the resolved graph, per [fleet.md](references/fleet.md) § Validate local packages.
+
+The review is one cross-package architecture and ergonomics pass over the whole graph, not one per unit.
 
 ## Accept the result
 
@@ -40,7 +38,6 @@ Completion requires:
 - every changed public contract, consumer, test, and guide is aligned;
 - real round-trip behavior is proven at the correct layer;
 - package versions/ranges/guides are reported from live evidence;
-- every touched repository's requested local gates are green;
-- no in-scope work is deferred.
+- every touched repository's requested local gates are green.
 
 Report the final package graph, ownership decisions, shipped behavior, exact verification, residual risk, and any user decision still required.

package/dist/host/agents/skills/orkestrel-align/references/fleet.md

@@ -1,5 +1,7 @@
 # Fleet alignment
 
+This reference governs fleet alignment across repositories: verifying live state, planning dependency order, and verifying consumers.
+
 ## Verify live state
 
 For every relevant repository, record:
@@ -29,19 +31,11 @@ Keep one authoritative session per package. Re-establish live state before actin
 
 ## Validate local packages
 
-When a dependent must verify a local package:
-
-- build the dependency;
-- consume its built artifact only in an isolated or explicitly authorized consumer;
-- prove every relevant resolution points to the intended artifact;
-- run the dependent's targeted then final local gates;
-- restore temporary overrides, manifest edits, and lockfile state.
-
-Do not treat an undeclared source-checkout import as consumer proof.
+When a dependent must verify a local package, pin it to a built tarball in an isolated or explicitly authorized consumer, run the dependent's targeted then final local gates, and restore the pin, per `.agents/skills/orkestrel-publish/references/release.md` § Fix a dependency before it publishes. Do not treat an undeclared source-checkout import as consumer proof.
 
 ## Align guides and verification
 
-Refresh dependency guides through the current scaffold workflow when the owning repository and scope permit it. Report drift rather than hand-editing a vendored guide whose canonical source lives elsewhere.
+Refresh dependency guides with `scaffold catalog` when the owning repository and scope permit it. Report drift rather than hand-editing a vendored guide whose canonical source lives elsewhere.
 
 Run package-local verification from dependencies to dependents. A passing lower package does not prove its consumer; a passing consumer does not replace lower-package invariants.
 

package/dist/host/agents/skills/orkestrel-align/references/integration.md

@@ -42,6 +42,6 @@ Place each proof at the highest useful layer:
 
 Use the actual packages and transports. Use temporary resources or protocol-faithful fixture servers for deterministic network boundaries. Use the real external service when its behavior is the claim. Never simulate an owned package with a mock or fake.
 
-When the claim is that a foreign client can consume the stack — an editor, an agent CLI, a third-party protocol client — one representative real client of that class drives the surface end to end before the claim ships. Record the exact commands, the authentication and approval model that client needed, and every part of the surface it could not reach. Protocol-level tests prove the protocol; only the client proves the integration.
+Prove a claim that a foreign client can consume the stack per `.agents/skills/orkestrel-harden/references/hardening.md` § Use real implementations.
 
 Test both successful composition and contract disagreement: invalid options, unavailable capability, partial failure, abort/cleanup, version mismatch, and lifecycle ordering where applicable.

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

@@ -14,18 +14,16 @@ than this summary of it.
 
 ## Select the environments
 
-`--src` selects published src environments and `--app` selects private app environments.
-The selections are independent, at least one is required, and each offers `core`, `browser`,
-and `server`.
+`scaffold new` takes the independent selections `--src` and `--app`; `guides/scaffold.md` § Command line
+and § Select at creation own the options and the combinations they refuse. The table names what each
+app environment owns.
 
-| Selection   | What it owns                                                             |
-| ----------- | ------------------------------------------------------------------------ |
-| app/core    | Host-independent contracts and composition; check and test only          |
-| app/browser | Vue runtime behind an `index.html` entry, `vue-tsc`, real Chromium tests |
-| app/server  | Node runtime, `dist/app/server/main.cjs` with only `node:*` external     |
-
-Core-only, browser-only, and server-only applications are valid. A browser+server pair
-includes app/core so the shared transport contracts have one host-independent owner.
+| Selection   | What it owns                                                                               |
+| ----------- | ------------------------------------------------------------------------------------------ |
+| app/core    | Host-independent contracts and composition; check and test only                            |
+| app/browser | Framework-independent DOM runtime behind an `index.html` entry, `tsc`, real Chromium tests |
+| app/vue     | Vue runtime with `App.vue` behind an `index.html` entry, `vue-tsc`, real Chromium tests    |
+| app/server  | Node runtime, `dist/app/server/main.cjs` with only `node:*` external                       |
 
 ## Execute the workflow
 
@@ -39,50 +37,26 @@ includes app/core so the shared transport contracts have one host-independent ow
    thin target wrappers and scoped tsconfigs.
 4. **Implement completely** — entries, barrels, centralized declarations, one-class
    implementation files, environment parsing, lifecycle, builds, and scripts — under the
-   placement and manifest laws. Parse the options container and its host and port leaves
-   before mutation, rejecting wrong-shaped containers, empty hosts, and non-integer,
-   negative, or out-of-range ports with a coded error and its guard.
-5. **Own the shutdown contract.**
+   placement and manifest laws in `.claude/rules/application.md`.
+5. **Own the shutdown contract** of the runner `.claude/rules/application.md` requires:
    - Serialize lifecycle transitions in call order.
    - Re-request port zero on an ephemeral restart.
    - Close lingering active connections deterministically on stop.
    - Release the runner's signal listeners idempotently on stop.
-   - Isolate asynchronous failures by runner generation, so an older transition cannot
-     release a newer run's listeners.
-   - Return the runner from convenience startup rather than hiding that cleanup.
-6. **Keep boundary enforcement inside the configured toolchain.** Each layer owns what it
-   can express:
-   - Oxlint `no-restricted-imports` — literal-string declared package, alias, and
-     conventional relative import direction.
-   - Oxfmt — formatting.
-   - `tests/setupPolicy.ts` — the narrow TypeScript compiler-API pass over computed and
-     template-literal specifiers, declaration placement, and the barrel law.
-   - Scoped TypeScript projects — host-global isolation.
-   - Vite's real builds and environment-boundary plugin — Vue, CSS, assets, workers,
-     runtime resolution, and physical workspace containment. Its parsed HTML asset
-     callbacks reject forced inlining before any direct asset read, and non-inlined
-     output assets are audited by physical source path.
-
-   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
-     compiler for `.vue` blocks, Vite's HTML parser callbacks, its bundled Lightning CSS
-     dependency analyzer, and the TypeScript compiler API for the narrow coding-law pass.
+6. **Keep boundary enforcement inside the configured toolchain**, per
+   `.claude/rules/workspace.md` § Typechecking and environment isolation and § Tooling.
+   - Add no standalone boundary script and no second parser or source-language analyzer.
    - Disable the browser application's public directory, so an unmanaged file copy cannot
      ship outside the module graph.
    - Keep browser-only runtime tooling development-only.
    - Require explicit authorization before adding a Sass compiler.
-
 7. **Prove it on real hosts.**
    - Run app/browser tests on Playwright-backed Vitest Browser Mode against real DOM.
      Probe the installed executable directly with `existsSync(chromium.executablePath())`
      rather than guessing a channel or reading an environment flag.
    - Bind port zero on loopback in app/server tests and use real fetch.
    - Prove executable readiness, collision exit, signal termination, and port release with
-     real child-process tests. Windows reports `ChildProcess.kill('SIGTERM')` as OS
-     termination by signal, while POSIX delivery exercises the graceful listener and exits
-     zero.
+     real child-process tests.
    - Probe the actual capability in a capability-dependent test, and scope any skip
      narrowly.
 8. **Document and prove parity** for every app export and behavioral method: guide,
@@ -92,10 +66,6 @@ includes app/core so the shared transport contracts have one host-independent ow
    `.agents/orchestration.md` § Size gate names for the change and the repository gates in
    their required order.
 
-Do not add showcase, authentication, persistence, proxy, styling-system, or product
-policy unless the request requires it. Do not leave placeholders, compatibility shims,
-empty setup files, or deferred app behavior.
-
 ## Accept the result
 
 Completion requires:
@@ -109,6 +79,4 @@ Completion requires:
 - guide parity green over every app export and behavioral method;
 - the repository gates green in their required order from an independent `verifier`.
 
-A selected environment still unwired, a real-host proof not taken, or an open parity row
-means the run is not finished. Report what each environment owns, the exact proof and gate
-evidence, and any residual risk. Do not call an in-scope omission future work.
+Report what each environment owns, the exact proof and gate evidence, and any residual risk.

package/dist/host/agents/skills/orkestrel-build/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: 'Build Orkestrel Application'
-  short_description: 'Design and harden Orkestrel app environments'
+  short_description: 'Wire and harden Orkestrel app environments'
   default_prompt: 'Use $orkestrel-build to build or harden this workspace application layer.'

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

@@ -13,8 +13,8 @@ auditing the agent, rule, skill, and process layer; [field-testing.md](reference
 before running or judging a live field pass of an agent-facing surface;
 [retention.md](references/retention.md) before retiring the campaign folder.
 
-The debrief judges the artifact and the process that produced it; neither is exempt. Record a
-practice that worked as a refinement, so it repeats.
+The debrief judges the artifact and the process that produced it. Record a practice that worked
+as a refinement.
 
 ## The debrief laws
 
@@ -43,23 +43,25 @@ practice that worked as a refinement, so it repeats.
 
 ## Run the round
 
-1. **Scope and gather.** Name the campaign(s) under debrief. Assemble the record: unit
-   ledger, deviations and recoveries, audit verdicts and their reconciliations, gate
-   history, and any live transcripts. State what evidence exists and what must be
+1. **Scope and gather.** Name the campaign(s) under debrief. Assemble the record from the
+   campaign folder (`.claude/rules/campaign.md` § Layout): `plan.md`, `ledger.md`, `gaps.md`,
+   `ideas.md`, and the verdict files, plus deviations and recoveries, gate history, and any
+   live transcripts. State what evidence exists and what must be
    produced fresh.
 2. **Field evidence.** Drive what was built with real consumers where a consumable
    surface exists. Record every pass verbatim.
 3. **Artifact audits.** Layer and boundary truth: does app code belong a layer down in
    src, does src carry application policy, does either duplicate a declared ecosystem
    primitive? Package promotion: what grew into a reusable mechanism that belongs in an
-   existing package or justifies a new one — mapped dependency-first so promotion order
-   is executable. Sweep test infrastructure both ways: name every local test helper or
-   fixture whose semantics an installed shared-package export already covers (compare
-   against the declarations each repository compiles with, and adopt rather than keep),
-   and name every instrument two or more packages built independently (count a value set
-   fed through one proof loop as one implementation, whether the set sits beside the
-   loop or its assertions are spelled out one by one). Every row ends implement, repair,
-   retain, or intentionally exclude, with evidence.
+   existing package or justifies a new one, judged by the extraction signals in
+   `.agents/orchestration.md` § Depth, breadth, and machinery and mapped dependency-first
+   so promotion order is executable. Sweep test infrastructure both ways: name every
+   local test helper or fixture whose semantics an installed shared-package export already
+   covers (compare against the declarations each repository compiles with, and adopt
+   rather than keep), and name every instrument two or more packages built independently
+   (count a value set fed through one proof loop as one implementation, whether the set
+   sits beside the loop or its assertions are spelled out one by one). Every row ends
+   implement, repair, retain, or intentionally exclude, with evidence.
 4. **Process retrospective.** Walk the campaign record for both failure and success:
    dispatches that deviated and why; recoveries that worked (codify the mechanism that
    saved them); estimates versus observed durations; audit rounds that caught real
@@ -77,8 +79,9 @@ practice that worked as a refinement, so it repeats.
    orchestration contract) with the owner's direction where the root contract is
    touched; re-prove per the re-proving law in § "The debrief laws".
 8. **Propagate.** Portable changes are made in the scaffold repository's host inventory,
-   staged, gated, and pushed — editing one project's checkout propagates nothing. Verify
-   the generated-workspace proofs stay green so new projects inherit the refined canon.
+   staged, gated, and committed; editing one project's checkout propagates nothing. Push on
+   the user's go-ahead (`.agents/orchestration.md` § Acceptance). Verify the
+   generated-workspace proofs stay green so new projects inherit the refined canon.
 9. **Dispose.** Present the disposition map — finding table with carriers, the canon
    delta, what remains open — and retire the campaign folder through
    [retention.md](references/retention.md), which owns the checks, the go-ahead, the
@@ -89,5 +92,5 @@ practice that worked as a refinement, so it repeats.
 Each round ends with one fixed report: the finding table (id, evidence pointer, bucket,
 carrier), the canon delta (files created or changed, per layer: agents, rules, skills,
 process, guide, roadmap), the re-proof evidence, and exactly one terminal line —
-`DEBRIEF: FOLDED` when every finding has a carrier and the propagation is pushed, or
+`DEBRIEF: FOLDED` when every finding has a carrier and the propagation is committed in scaffold, or
 `DEBRIEF: OPEN` with the blocking items.

package/dist/host/agents/skills/orkestrel-debrief/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: 'Debrief Closed Campaign'
   short_description: 'Fold a closed campaign into portable truth on field evidence'
-  default_prompt: 'Use $orkestrel-debrief to debrief the closed campaign: field passes, findings ledger, fix loops, canon refinement, propagation, disposal.'
+  default_prompt: 'Use $orkestrel-debrief to debrief the closed campaign: field passes, finding table, fix loops, canon refinement, propagation, disposal.'

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

@@ -5,17 +5,18 @@ model consumes.
 
 ## The tier ladder
 
-Test from the top down, and do not stop at the tier that passes:
-
-1. **Frontier** (the harness's default model) — proves the surface works at all.
-2. **Mid tier** (for example, a codex mechanical model) — proves the surface survives a
-   harness's schema abbreviation and a model that reads less carefully.
-3. **Small harness-native** (for example, Haiku or a codex high-volume model) — the
-   acceptance tier: these must walk the surface unaided, or the surface is not done.
-4. **Local floor** (a quantized 2B-class model through a real tool-calling client) — not
-   an acceptance gate; a stochastic probe that exposes teaching gaps nothing else hits.
-   Its residual failures must be provably consumer-floor (malformed emission, attention
-   loss), never surface darkness — every refusal it received must have named the fix.
+Test from the top down, and do not stop at the tier that passes. Map each tier to an engine
+per `.agents/orchestration.md` § Roles and name the map in the dispatch.
+
+1. **Frontier** (the harness's default engine) — proves the surface works at all.
+2. **Mid tier** — proves the surface survives a harness's schema abbreviation and an engine
+   that reads less carefully.
+3. **Small native** (the mechanical roles' engine) — the acceptance tier: it must walk the
+   surface unaided, or the surface is not done.
+4. **Local floor** (a small quantized model through a real tool-calling client) — not an
+   acceptance gate; a stochastic probe that exposes teaching gaps nothing else hits. Its
+   residual failures must be provably consumer-floor (malformed emission, attention loss),
+   never surface darkness — every refusal it received must have named the fix.
 
 ## The pass discipline
 
@@ -48,23 +49,9 @@ Read every trace against these; each maps to a class of surface fix:
 | Opaque-wall regression  | A correct structure abandoned after an unnamed refusal                 | Every refusal names the subject, path, expectation, and candidates                                         |
 | Repetition fixpoint     | The identical failing call repeated verbatim                           | The refusal must change the caller's information state; if it already does, the residual is consumer-floor |
 
-## The teaching-surface doctrine
-
-What the field passes repeatedly prove:
-
-- **Descriptions are the surviving surface.** Harnesses abbreviate nested schemas;
-  the tool description reaches every model intact. The critical path — a worked example,
-  the key nesting, the reply shape — lives there, importance-first, so a model that
-  stops reading early still gets it.
-- **Every refusal orients, names, or corrects.** Subject, exact key path, expected
-  shape, valid candidates, missing versus unexpected — a refusal that names nothing ends
-  runs; a refusal that names everything converges even a 2B model.
-- **Strictness with teaching beats tolerance.** Never coerce, never silently drop;
-  refuse with the correction in the message. Encode untrusted identifiers (JSON-encoded,
-  length-capped) so malformed input cannot fake or balloon a diagnostic.
-- **Acknowledge or state, never both.** Mutations return acknowledgements; reads return
-  state; the split is stated in both tools' descriptions so neither is polled for the
-  other's job.
+## Judge the fix
+
+Rule each fix against `.claude/rules/documentation.md` § Agent-facing surfaces.
 
 ## The scoreboard