@orkestrel/scaffold 0.0.125 → 0.0.126

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -76,6 +76,7 @@ The harness's own engine orchestrates: Claude Fable 5.1 or Claude Opus 5.5 in Cl
76
76
  - On continuation, the Orchestrator sends the next bounded objective and the facts changed after the last turn. The continued agent reads changed or missing authority and the source regions that objective needs, and rechecks mutable facts such as source state and process liveness. Do not repeat unchanged bulk reads merely because a unit resumes. A continuation that changes scope or acceptance, or authorizes a fix, is written first as `<unit>-brief-<n>.md` and sent as a pointer to that file; a message alone continues only an unchanged objective.
77
77
  - Consult a suitable peer at the stop set for a seam, or earlier when a consequential approach remains open, evidence conflicts, or attempts stop narrowing a failure, without waiting for the user, and record the question, recommendation, evidence, and next check in the plan. Give the peer the question, relevant evidence, attempted approaches, constraints, and requested answer. Use an existing specialist when its context helps and a fresh peer when the question needs an independent challenge.
78
78
  - Keep consultation read-only and bounded. Ask for a recommendation, its evidence, uncertainty, and a concrete next check. The executor retains the work; the Orchestrator rules on scope and acceptance. Advice grants no authority and does not satisfy an independent review gate.
79
+ - Before a writer builds a consultant's proposal, test each claim the proposal rests on with probes on both arms, the base and the proposal applied by temporary mutation, and rule from those readings, never from the consultant's reasoning.
79
80
  - Resolve conflicting advice against the contract and observable evidence. Do not add consultation to routine steps or repeat it without a changed question or evidence.
80
81
  - When a requested launch channel fails, record the failure and whether a child was created. Before retrying an uncertain launch, inspect the recorded task or session. Use a permitted fallback with its actual model and options disclosed; retry a refused route only after a relevant condition changes.
81
82
 
@@ -134,7 +135,7 @@ The harness's own engine orchestrates: Claude Fable 5.1 or Claude Opus 5.5 in Cl
134
135
  - 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.
135
136
  - When a brief restates a ruling, give the reviewer the ruling's own text beside the brief, and make any disagreement between the two a claim.
136
137
  - Before a repair is dispatched, class its remedy as a correction, a design question, or a deferral; a remedy that adds a mechanism (a file operation, a state, a protocol step, or a retry class) is a design question that goes to one `planner` or `analyst` pass carrying measured platform facts.
137
- - A fix round re-audits the repaired claim only. A fix that departs from the reviewer's prescription gets one pass by an independent reviewer per § Engines.
138
+ - A fix round re-audits the repaired claim only, in a fresh context. After the re-audit's findings are repaired, one closure check reads whether each closed and tests no other claim. A fix that departs from the reviewer's prescription gets one pass by an independent reviewer per § Engines.
138
139
  - Every repair, a prescription adopted verbatim included, closes with a mutation probe on its load-bearing line (disable it, 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. Where the repair adds or changes a process proof, the proof's repeat run under suite load closes it too.
139
140
  - Before another round at the same seam, weigh whether a further repair beats a design question, set and state in the brief the stop for that seam and its reason, re-examine it at every round per § Depth, breadth, and machinery, and end the depth search with a design question when a round introduces as many defects as it closes, a repair adds a mechanism, findings stop converging, or the cost outgrows the goal's importance. `.agents/skills/orkestrel-falsify/SKILL.md` § End the depth search owns how the search ends.
140
141
  - A repair round at a seam carries only rows whose remedy serves that seam; a finding outside it waits for the next round or the deferral list.
@@ -12,7 +12,7 @@ One round. It ends with a ruling. `.agents/orchestration.md` § Size gate decide
12
12
 
13
13
  Run from the checkout root. The script's opening comment owns its behavior.
14
14
 
15
- - `scripts/mutate.ts --edits EDITS.md -- COMMAND [ARGS...]` runs the mutation probe. It resolves an edit file, the `### <path>` block shape that `.agents/skills/orkestrel-dispatch/scripts/patch.ts` reads, before it touches a file; saves the originals under `tmp/probes/mutate/`; writes the mutated files; runs the command with no shell and its output on standard error; restores the bytes and proves each file's SHA-256 digest; runs the command again; and prints one JSON line with both exits. A mutation that leaves the suite uncollected also reads as a failing run, so read the command's own test count on standard error. A run killed mid-command leaves the tree mutated: the next run refuses to start while a run directory remains and names the line that restores it, `scripts/mutate.ts --restore tmp/probes/mutate/run-NAME`, which writes the saved originals back, proves each digest from the manifest, and deletes the directory. Exit 0 when the mutated run failed and the restored run passed (or a `--restore` is proven), 3 when either did not, 2 when a restore is not proven or the command cannot start, 64 usage, an edit that does not resolve, or a run directory left behind.
15
+ - `scripts/mutate.ts --edits EDITS.md -- COMMAND [ARGS...]` runs the mutation probe. It resolves an edit file, the `### <path>` block shape that `.agents/skills/orkestrel-dispatch/scripts/patch.ts` reads, before it touches a file; saves the originals under `tmp/probes/mutate/`; writes the mutated files; runs the command with no shell and its output on standard error; restores the bytes and proves each file's SHA-256 digest; runs the command again; and prints one JSON line with both exits. A mutation that leaves the suite uncollected also reads as a failing run, so read the command's own test count on standard error. When the probe compares two arms rather than proving a kill, read the `mutatedExit` and `restoredExit` fields from the JSON line: exit 3 reports a passing mutated run. A run killed mid-command leaves the tree mutated: the next run refuses to start while a run directory remains and names the line that restores it, `scripts/mutate.ts --restore tmp/probes/mutate/run-NAME`, which writes the saved originals back, proves each digest from the manifest, and deletes the directory. Exit 0 when the mutated run failed and the restored run passed (or a `--restore` is proven), 3 when either did not, 2 when a restore is not proven or the command cannot start, 64 usage, an edit that does not resolve, or a run directory left behind.
16
16
 
17
17
  ## Run a round the size gate does not name when
18
18
 
@@ -249,7 +249,7 @@ When a comparison has a written pairwise graph, select by that graph, preserve p
249
249
 
250
250
  ### Compare the shippable intervention, including what it loses
251
251
 
252
- When copying, quotes, aliases, units, field kinds, or reader size is proposed as a treatment, evaluate each as a different intervention, run with only metadata the public contract carries, set the keep rule as a cost ratio before the column runs, retain latent errors and lost right answers, and inspect shared brief vocabulary in purported holdouts.
252
+ When copying, quotes, aliases, units, field kinds, or reader size is proposed as a treatment, evaluate each as a different intervention, run with only metadata the public contract carries, set the keep rule as a cost ratio before the column runs, counting a refusal's removed right values apart from its removed wrong values, retain latent errors and lost right answers, compare each arm with its rival on the same rows at the same coverage with a minimum coverage per class, give the rival every input the arm sees, and inspect shared brief vocabulary in purported holdouts.
253
253
 
254
254
  - **Refuse.** Usage frequency as counterfactual benefit, because a usage count measures wording, not value. An additive oracle as the replacement fitted method, because the two are different interventions. Field descriptions fitted from the writers' own brief, or fitted synonyms, called independent generalization, because writers who share descriptions share vocabulary, so quote only blind readings. Filling fields by a model's index links or quoted evidence, because index links add silent errors and quoting costs more right answers than the wrong answers it removes. Unit lists through alias channels, because units collide. A provider's need for prompt teaching of structured-output descriptions generalized to every provider, because that behavior is recorded on one provider.
255
255
  - **Reading.** In the `@orkestrel/learn` package, on the reader research quote-field intervention: quote fields remove six accepted wrongs but cost 99 right answers and raise latent errors.
@@ -471,7 +471,7 @@ When an expensive use depends on a freeze, a grade, progress, a replay, or next-
471
471
 
472
472
  ### Separate developmental evidence, confirmation, and answer-path quality
473
473
 
474
- When a study reports a measurement, hold the populations apart as the law states, fit preprocessing only on training data, measure accepted wrong, latent wrong, useful coverage, and the answers-only user's final decision, run helpful correction as a separate scenario, keep unknown, unselected, and unreached distinct, and replace a changed subject's assertions.
474
+ When a study reports a measurement, hold the populations apart as the law states, fit preprocessing only on training data, measure accepted wrong, latent wrong, useful coverage, and the answers-only user's final decision, read the rows that decide a change by hand beside its score, run helpful correction as a separate scenario, keep unknown, unselected, and unreached distinct, and replace a changed subject's assertions.
475
475
 
476
476
  - **Refuse.** An old green result carried to a changed subject, because “none survives as a proof”. A labeling floor as a quality control, because that floor “cannot fail”. A label disagreement on equal products as a product difference, because that disagreement “is the labelers' own”. Semantic substitution from a lexical score, because its correlations did not earn that substitution. A population audit that asserts counts alone, because every count can hold while strata fail to cross, one value dominates, boundary values land together, or a ceiling under the bar makes the run measure the grid: in `@orkestrel/learn`, every count holds while all 200 ordinary messages are approvals and one pair of boundary values sits on 202 of 600 subjects. An audit with no negative control, because an audit proves itself by refusing the draw it was written to reject, so rerun it on the prior draw, per `.claude/rules/quality.md` § Instruments. A sum of sole-blocker rows as a bound, because removing one blocker changes which rows the others block and can add wrong rows: report each removal's row-level right and wrong, as `@orkestrel/learn` read `Superseded` gaining 126 right and adding 0 wrong and `Support` gaining 5 right and adding 1 wrong.
477
477
  - **Reading.** In the `@orkestrel/learn` package, on its study: “only the rubric contains population membership and expected outputs”. The answers-path scenario stays a specification, not a completed result, and no completed carrier is recorded.
@@ -64,11 +64,11 @@ Resolve every target and every population by ARIA role and accessible name as re
64
64
 
65
65
  ## Read the variant once
66
66
 
67
- A browser application born by `scaffold new` carries the journey axis: the
68
- `configs/app/vite.journey.config.ts` wrapper, the root `appJourney` factory, the `test:journey`
69
- script, and that script's place in the `test` chain. That wiring fans the journey suite out into one
70
- Vitest project per variant, and each project provides its own variant. Read the variant once at run
71
- start, and let it choose the capture destination, the matrix row, and the statechart run together.
67
+ For a browser application born by `scaffold new`, use its journey axis: the
68
+ `configs/app/vite.journey.config.ts` wrapper, the root `appJourney` factory, and the `test:journey`
69
+ script. Place the script by `.claude/rules/workspace.md` § Test project matrix.
70
+ Read the variant once at run start from the Vitest project the wrapper creates for it, and let it
71
+ choose the capture destination, the matrix row, and the statechart run together.
72
72
 
73
73
  - Read `inject('variant')` for this run's variant name, `inject('variants')` for the declared list,
74
74
  and `inject('capture')` for whether this run writes frames.
@@ -79,16 +79,14 @@ start, and let it choose the capture destination, the matrix row, and the statec
79
79
  viewports for this application.
80
80
  - Activate the axis in a workspace born before it: write `configs/app/vite.journey.config.ts`, run
81
81
  `scaffold audit`, and add any missing planned dependencies it names before `scaffold repair`.
82
- Then add `npm run test:journey` to the `test` script after `npm run test:app`.
83
- The repair defines `appJourney` in the root configuration, emits `test:journey`, `journey`, and
84
- `capture`, and excludes the journey suite from the ordinary `app:browser` project. It does not rewrite the `test`
85
- chain, so the chain entry is yours to add. Add that entry before the repair instead where you
86
- prefer: `test:journey` names a configuration rather than a project, so neither order blocks the
87
- repair.
82
+ Check that the repair defines `appJourney` in the root configuration, emits `test:journey`,
83
+ `journey`, and `capture`, and excludes the journey suite from the ordinary `app:browser` project.
84
+ Place each script by `.claude/rules/workspace.md` § Test project matrix. When the repair preserves
85
+ an authored `test` chain, apply that placement to the chain yourself.
88
86
  - Name each variant per [captures.md](references/captures.md) → Variants.
89
87
  - Keep the provided variants as serializable `JourneyVariant` data: `name`, `width`, and `height`.
90
88
  Compose no callback merely to pass that data to a capture.
91
- - Keep `npm run test:journey` as the whole-suite gate in the `test` chain. Use the scoped commands
89
+ - Use `npm run test:journey` for the whole suite. Use the scoped commands
92
90
  under Choosing what to run for iteration and stamped frames; keep the root configuration's
93
91
  `CAPTURE === '1'` read and its `capture` provide unchanged.
94
92
  - Keep the journeys in `tests/app/browser/integration.test.ts`, and the journeys of the `vue`
@@ -103,12 +101,14 @@ start, and let it choose the capture destination, the matrix row, and the statec
103
101
  `scaffold audit` reports a manifest and a wrapper that disagree as one of these findings. Settle the one it reports before trusting a green run.
104
102
 
105
103
  - The manifest names a Vitest configuration for `test:journey` that the plan does not emit and the target does not hold. Write the wrapper and run `scaffold repair`, or remove the `test:journey` script and its chain invocation.
106
- - The manifest does not invoke `npm run test:journey` from its `test` chain. Add `npm run test:journey` to the `test` script after `npm run test:app`.
104
+ - When a private manifest does not invoke `npm run test:journey` from its `test` chain, add that invocation after `npm run test:app`.
105
+ - When a publishing manifest's `test` chain exactly matches the former generated chain, run `scaffold repair` or `scaffold overwrite` to remove its application and journey gate invocations. When the chain differs, remove those invocations yourself. Run the helper suites on demand.
107
106
 
108
- `scaffold audit` reports the invocation question only when no chain from `test` reaches
109
- `npm run test:journey` through literal `npm run` calls, so a chain reaching it through an
110
- intermediate script raises none. It reports the configuration question only for a `test:*` script
111
- whose text names `vitest`, so a script naming another runner's configuration raises none either.
107
+ For a private workspace's missing-invocation question, inspect literal `npm run` calls through
108
+ intermediate scripts as well as the `test` script. For a publishing helper-suite question, inspect
109
+ the reported caller and invocation, including literal Vitest calls through application and journey wrappers.
110
+ For an absent-configuration question, inspect
111
+ `test:*` scripts whose text names `vitest`.
112
112
 
113
113
  ### Choosing what to run
114
114
 
@@ -152,8 +152,7 @@ Climb this ladder using only declared owner, case, and variant names:
152
152
  before `npm run capture -- --changed HEAD`.
153
153
  3. A section or page: `npm run journey -- pages:mail:inbox` or `npm run journey -- pages:mail`.
154
154
  4. A group: `npm run journey -- pages`.
155
- 5. `all` at the gate: `npm run journey -- all`, retaining `npm run test:journey` in the repository's
156
- whole-suite test chain.
155
+ 5. The whole suite: `npm run journey -- all`.
157
156
 
158
157
  Follow a refusal's exact next commands before widening a selection. Use the matching `capture`
159
158
  script only when the work needs frames, and apply [captures.md](references/captures.md) before
@@ -20,11 +20,12 @@ Native Codex agents, and Codex lanes another harness hosts. `.codex/config.toml`
20
20
 
21
21
  ## Quirks
22
22
 
23
- - Before a Codex lane that requires a tool server, verify the entry's resolution and handshake from that lane's checkout under the effective configuration. On "required MCP servers failed to initialize", read the user-level configuration for a same-named entry.
23
+ - Before a Codex lane that requires a tool server, verify the entry's resolution and handshake from that lane's checkout under the effective configuration. On "required MCP servers failed to initialize", read the user-level configuration for a same-named entry: Codex merges its keys into the project's entry, so a user-level `cwd` resolves the project's relative `args` from that directory (2026-11-08). Remove the user-level `cwd` rather than give the project entry an absolute path.
24
24
  - When a Codex lane runs a long command, brief the yield fallback before launch: the longest yield interval, output to a file, process-list reads until the tracked command exits, and no kill. The lane cannot set a timeout; brief it to proceed without asking for one.
25
25
  - When the shell yields before the command exits, start nothing else, and confirm no owned leftover remains before the next lane; a lane that started the next test file broke the one-runner bound (2026-10-22).
26
26
  - When a brief launches a long command, name its terminal record, such as the launcher's `exit=` line; a lane read a finished step as running and polled it for six minutes (2026-10-22).
27
27
  - When a review brief describes risks in offensive-security wording, the provider's filter can end the lane without a verdict (2026-10-20). Brief the review as quality assurance of the user's own code in neutral words, require an early verdict file, retry once, then use a recorded fallback.
28
+ - When a Codex lane writes probes under `tmp/probes/`, brief it to name its probe folder in its report and to leave the folder when the automatic approval review refuses the deletion (`blocked by policy`); delete the folder after the lane returns.
28
29
  - When a `codex exec` run is killed, treat it as dead only when its `codex-code-mode-host` child is gone too.
29
30
  - When a Codex child runs through a hosting harness, it can reach that harness's messaging tools; probe them before a writer or runner depends on them (`references/t3.md`).
30
31
  - When a launch fails on a tool server's handshake timeout, relaunch that lane alone; a lane beside it started with the same server (2026-10-19). Stagger launches that start the same server.
@@ -44,15 +44,15 @@ Treat generated package identifiers, versions, layers, and dependency ranges as
44
44
  | Package | Version | Layer | Runtime dependencies | Peer dependencies |
45
45
  | ----------------------- | --------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
46
46
  | `@orkestrel/abort` | `0.0.16` | L1 | `@orkestrel/contract` `^0.0.22` | |
47
- | `@orkestrel/agent` | `0.0.36` | L5 | `@orkestrel/tool` `^0.0.22`, `@orkestrel/abort` `^0.0.16`, `@orkestrel/queue` `^0.0.20`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/ndjson` `^0.0.16`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21`, `@orkestrel/workflow` `^0.0.26`, `@orkestrel/workspace` `^0.0.15` | |
47
+ | `@orkestrel/agent` | `0.0.38` | L5 | `@orkestrel/tool` `^0.0.22`, `@orkestrel/abort` `^0.0.16`, `@orkestrel/queue` `^0.0.20`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/ndjson` `^0.0.16`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21`, `@orkestrel/workflow` `^0.0.26`, `@orkestrel/workspace` `^0.0.15` | |
48
48
  | `@orkestrel/brief` | `0.0.17` | L4 | `@orkestrel/reason` `^0.0.17`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/interpret` `^0.0.22` | |
49
49
  | `@orkestrel/browser` | `0.0.32` | L5 | `@orkestrel/mcp` `^0.0.42`, `@orkestrel/html` `^0.0.15`, `@orkestrel/pool` `^0.0.20`, `@orkestrel/tool` `^0.0.22`, `@orkestrel/codec` `^0.0.9`, `@orkestrel/router` `^0.0.20`, `@orkestrel/server` `^0.0.26`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/markdown` `^0.0.20`, `@orkestrel/websocket` `^0.0.18` | |
50
50
  | `@orkestrel/budget` | `0.0.17` | L1 | `@orkestrel/contract` `^0.0.22` | |
51
- | `@orkestrel/capture` | `0.0.3` | L3 | `@orkestrel/process` `^0.0.17`, `@orkestrel/timeout` `^0.0.15`, `@orkestrel/contract` `^0.0.21` | `vite` `^8.3.5`, `vitest` `^4.1.12 \|\| ^5.0.5`, `playwright` `^1.61.0`, `@vitest/browser-playwright` `^4.1.12 \|\| ^5.0.5` |
51
+ | `@orkestrel/capture` | `0.0.4` | L3 | `@orkestrel/process` `^0.0.18`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22` | `vite` `^8.3.6`, `vitest` `^4.1.12 \|\| ^5.1.0`, `playwright` `^1.61.0`, `@vitest/browser-playwright` `^4.1.12 \|\| ^5.0.5` |
52
52
  | `@orkestrel/codec` | `0.0.9` | L1 | `@orkestrel/contract` `^0.0.22` | |
53
53
  | `@orkestrel/console` | `0.0.19` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
54
54
  | `@orkestrel/contract` | `0.0.22` | L0 | | |
55
- | `@orkestrel/csv` | `0.0.12` | L2 | `@orkestrel/codec` `^0.0.8`, `@orkestrel/contract` `^0.0.21` | |
55
+ | `@orkestrel/csv` | `0.0.13` | L2 | `@orkestrel/codec` `^0.0.9`, `@orkestrel/contract` `^0.0.22` | |
56
56
  | `@orkestrel/database` | `0.0.21` | L2 | `@orkestrel/sqlite` `^0.0.17`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/indexeddb` `^0.0.17` | |
57
57
  | `@orkestrel/emitter` | `0.0.15` | L1 | `@orkestrel/contract` `^0.0.22` | |
58
58
  | `@orkestrel/form` | `0.0.16` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
@@ -64,10 +64,10 @@ Treat generated package identifiers, versions, layers, and dependency ranges as
64
64
  | `@orkestrel/lsp` | `0.0.14` | L3 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/jsonrpc` `^0.0.2`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22` | |
65
65
  | `@orkestrel/markdown` | `0.0.20` | L2 | `@orkestrel/html` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
66
66
  | `@orkestrel/mcp` | `0.0.42` | L4 | `@orkestrel/sse` `^0.0.13`, `@orkestrel/tool` `^0.0.22`, `@orkestrel/codec` `^0.0.9`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/jsonrpc` `^0.0.2`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/websocket` `^0.0.18` | `@orkestrel/router` `^0.0.20`, `@orkestrel/server` `^0.0.26` |
67
- | `@orkestrel/middleware` | `0.0.27` | L4 | `@orkestrel/abort` `^0.0.15`, `@orkestrel/budget` `^0.0.16`, `@orkestrel/timeout` `^0.0.15`, `@orkestrel/contract` `^0.0.21` | `@orkestrel/server` `^0.0.25`, `@orkestrel/database` `^0.0.20` |
68
- | `@orkestrel/msg` | `0.0.15` | L2 | `@orkestrel/codec` `^0.0.8`, `@orkestrel/contract` `^0.0.21` | |
67
+ | `@orkestrel/middleware` | `0.0.28` | L4 | `@orkestrel/abort` `^0.0.16`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22` | `@orkestrel/server` `^0.0.26`, `@orkestrel/database` `^0.0.21` |
68
+ | `@orkestrel/msg` | `0.0.16` | L2 | `@orkestrel/codec` `^0.0.9`, `@orkestrel/contract` `^0.0.22` | |
69
69
  | `@orkestrel/ndjson` | `0.0.16` | L1 | `@orkestrel/contract` `^0.0.22` | |
70
- | `@orkestrel/ollama` | `0.0.30` | L6 | `@orkestrel/tool` `^0.0.22`, `@orkestrel/agent` `^0.0.36`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/ndjson` `^0.0.16`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22` | |
70
+ | `@orkestrel/ollama` | `0.0.32` | L6 | `@orkestrel/tool` `^0.0.22`, `@orkestrel/agent` `^0.0.38`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/ndjson` `^0.0.16`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22` | |
71
71
  | `@orkestrel/pool` | `0.0.20` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
72
72
  | `@orkestrel/probe` | `0.0.29` | L5 | `@orkestrel/lsp` `^0.0.14`, `@orkestrel/mcp` `^0.0.42`, `@orkestrel/pool` `^0.0.20`, `@orkestrel/tool` `^0.0.22`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22` | `vitest` `^4.1.12 \|\| ^5.1.0`, `typescript` `^6.0.3 \|\| ^7.0.2` |
73
73
  | `@orkestrel/process` | `0.0.18` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
@@ -78,21 +78,21 @@ Treat generated package identifiers, versions, layers, and dependency ranges as
78
78
  | `@orkestrel/reason` | `0.0.17` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
79
79
  | `@orkestrel/relation` | `0.0.19` | L3 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21` | |
80
80
  | `@orkestrel/router` | `0.0.20` | L2 | `@orkestrel/abort` `^0.0.16`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
81
- | `@orkestrel/scaffold` | `0.0.124` | L3 | `@orkestrel/console` `^0.0.19`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/markdown` `^0.0.20`, `@orkestrel/template` `^0.0.13` | |
82
- | `@orkestrel/sea` | `0.0.21` | L3 | `@orkestrel/emitter` `^0.0.14`, `@orkestrel/process` `^0.0.17`, `@orkestrel/contract` `^0.0.21` | |
81
+ | `@orkestrel/scaffold` | `0.0.125` | L3 | `@orkestrel/console` `^0.0.19`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/markdown` `^0.0.20`, `@orkestrel/template` `^0.0.13` | |
82
+ | `@orkestrel/sea` | `0.0.22` | L3 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/process` `^0.0.18`, `@orkestrel/contract` `^0.0.22` | |
83
83
  | `@orkestrel/server` | `0.0.26` | L3 | `@orkestrel/abort` `^0.0.16`, `@orkestrel/codec` `^0.0.9`, `@orkestrel/router` `^0.0.20`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22` | |
84
84
  | `@orkestrel/sqlite` | `0.0.17` | L1 | `@orkestrel/contract` `^0.0.22` | |
85
85
  | `@orkestrel/sse` | `0.0.13` | L2 | `@orkestrel/codec` `^0.0.9`, `@orkestrel/contract` `^0.0.22` | |
86
- | `@orkestrel/study` | `0.0.11` | L7 | `@orkestrel/tool` `^0.0.22`, `@orkestrel/abort` `^0.0.16`, `@orkestrel/agent` `^0.0.36`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/ollama` `^0.0.30`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22` | |
87
- | `@orkestrel/table` | `0.0.14` | L2 | `@orkestrel/emitter` `^0.0.14`, `@orkestrel/contract` `^0.0.21` | |
86
+ | `@orkestrel/study` | `0.0.15` | L7 | `@orkestrel/tool` `^0.0.22`, `@orkestrel/abort` `^0.0.16`, `@orkestrel/agent` `^0.0.38`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/ollama` `^0.0.32`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22` | |
87
+ | `@orkestrel/table` | `0.0.15` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
88
88
  | `@orkestrel/template` | `0.0.13` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
89
89
  | `@orkestrel/terminal` | `0.0.23` | L3 | `@orkestrel/sse` `^0.0.13`, `@orkestrel/form` `^0.0.16`, `@orkestrel/console` `^0.0.19`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21` | |
90
90
  | `@orkestrel/test` | `0.0.33` | L1 | `@orkestrel/contract` `^0.0.22` | `vitest` `^4.1.12 \|\| ^5.1.0`, `playwright` `^1.64.1` |
91
91
  | `@orkestrel/timeout` | `0.0.16` | L1 | `@orkestrel/contract` `^0.0.22` | |
92
92
  | `@orkestrel/tool` | `0.0.22` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
93
- | `@orkestrel/toolbox` | `0.0.25` | L6 | `@orkestrel/form` `^0.0.16`, `@orkestrel/tool` `^0.0.22`, `@orkestrel/agent` `^0.0.36`, `@orkestrel/server` `^0.0.26`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21`, `@orkestrel/relation` `^0.0.19`, `@orkestrel/terminal` `^0.0.23`, `@orkestrel/workflow` `^0.0.26`, `@orkestrel/workspace` `^0.0.15` | |
93
+ | `@orkestrel/toolbox` | `0.0.27` | L6 | `@orkestrel/form` `^0.0.16`, `@orkestrel/tool` `^0.0.22`, `@orkestrel/agent` `^0.0.38`, `@orkestrel/server` `^0.0.26`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21`, `@orkestrel/relation` `^0.0.19`, `@orkestrel/terminal` `^0.0.23`, `@orkestrel/workflow` `^0.0.26`, `@orkestrel/workspace` `^0.0.15` | |
94
94
  | `@orkestrel/websocket` | `0.0.18` | L2 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22` | |
95
- | `@orkestrel/worker` | `0.0.19` | L4 | `@orkestrel/pool` `^0.0.19`, `@orkestrel/queue` `^0.0.19`, `@orkestrel/emitter` `^0.0.14`, `@orkestrel/contract` `^0.0.21`, `@orkestrel/database` `^0.0.20` | |
95
+ | `@orkestrel/worker` | `0.0.20` | L4 | `@orkestrel/pool` `^0.0.20`, `@orkestrel/queue` `^0.0.20`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21` | |
96
96
  | `@orkestrel/workflow` | `0.0.26` | L4 | `@orkestrel/abort` `^0.0.16`, `@orkestrel/queue` `^0.0.20`, `@orkestrel/budget` `^0.0.17`, `@orkestrel/emitter` `^0.0.15`, `@orkestrel/timeout` `^0.0.16`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21` | |
97
97
  | `@orkestrel/workspace` | `0.0.15` | L3 | `@orkestrel/emitter` `^0.0.15`, `@orkestrel/contract` `^0.0.22`, `@orkestrel/database` `^0.0.21` | |
98
98
 
@@ -29,6 +29,7 @@ These rules govern how a claim is established: the evidence read before a change
29
29
  - A clean reproduction of a reported defect means your input was weaker than the reporter's; get theirs before ruling. An input the compiler rejects refutes that input, not the finding.
30
30
  - "No tests found", an empty match, or a runner that resolved nothing reports on the harness. Confirm the probe was collected before reading a result.
31
31
  - Prefer an observation to a derivation. When a measurement and an argument disagree, the argument is wrong until the measurement is shown broken.
32
+ - When a probe compares a candidate with its base, extract the base with the `git archive` command into its own tree under `tmp/probes/`, link the checkout's `node_modules` directory into that tree, run the same probe in both trees, and read each arm from the JSON file it writes.
32
33
  - Read a gate bare. A `| tail` or `| grep` behind it hides the failing lines and reports the pipe's exit code.
33
34
 
34
35
  ## Instruments
@@ -45,6 +46,7 @@ These rules govern how a claim is established: the evidence read before a change
45
46
  - Read a receipt as evidence about its claim, never as a gate result.
46
47
  - State the instrument's coverage beside its result. Match the instrument to the question: a text search reports on text; a claim about declarations or call sites needs the compiler or a parser.
47
48
  - Report a question unanswered rather than answering it with a weaker instrument.
49
+ - When a verdict reads rows or numbers, refuse the verdict on an empty result or on a missing or non-finite number; never read either as zero or as a pass.
48
50
  - Baseline a published-artifact claim against the published artifact (the tarball, the deployed asset). Prove a module cycle by loading the built entry points.
49
51
  - Promote an instrument that settled a claim into a test, with its control, before accepting the work it settled.
50
52
 
@@ -55,6 +57,7 @@ These rules govern how a claim is established: the evidence read before a change
55
57
  - Refuse a micro optimization (hoisting a small array, caching one cheap read, shaving a constant) unless its own measurement shows a gain worth having.
56
58
  - Keep an algorithmic repair (a superlinear term, a repeated layout) when the measurement shows it.
57
59
  - Before the run, size the fixtures, the sample count, and the threshold to the case, and state the reasoning and the result that makes the change worth keeping.
60
+ - Before setting a floor on a quality or cost reading, read the spread its setting shows under a small unrelated change, and set the floor outside that spread.
58
61
  - Read the difference between methods against each side's reported uncertainty, and record no difference smaller than the result stated before the run.
59
62
  - Report every measurement with the host's other load during the run, its memory and console counts included.
60
63
  - When a brief changes a hot path, name a measured cost bar at the input limit, and read the cost there before acceptance: an ordinary-length test cannot read a superlinear term.
@@ -37,11 +37,13 @@ These rules govern what a test asserts and where it lives, the cross-cutting and
37
37
  - Use recorders for calls/events, temporary resources for stateful boundaries, protocol-faithful fixture servers for deterministic network peers, and the real external service when its behavior is the claim.
38
38
  - Prefer inert customizable data and input stubs.
39
39
  - Allow a scripted boundary stub only when it implements the real interface or protocol minimally, to drive the system under test. It never reimplements project-owned behavior and never stands in for the integration being claimed.
40
+ - When a dependency's release changes a wire a scripted boundary stub serves, update the stub to the wire as the dependency sends it, and keep every caller-facing assertion.
40
41
  - Bind a test fixture server to `127.0.0.1` on an ephemeral port (`listen(0)`), never to `::1` and never to a fixed port: a host without IPv6 fails `EAFNOSUPPORT`, and a fixed port flakes on occupancy.
41
42
  - Cover happy paths, error paths, empty input, boundary values, `NaN`, positive/negative zero, cycles, and Map/Set order where relevant.
42
43
  - Test observable behavior, not implementation details.
43
44
  - Assert the membership a discovered or globbed set must have, not a total that a partly empty population satisfies. A glob spanning two locations passes a size check while one of them matches nothing.
44
45
  - Never assert an implementation against itself. Compare the answer to a declaration, a fixture, or a second mechanism that could disagree with it. Re-deriving the answer the same way the source derives it produces a test that passes for every value the source ever returns, and it reads exactly like a real one.
46
+ - When two mechanisms agree, also drive the real harness's call to them on an input whose answer is known: their parity reads neither one's call site.
45
47
  - Probe a host-varying property at runtime, on the host the test is running on, and assert against what the probe returned. Filesystem case folding, path separators, permission bits, and rename semantics differ per host, and a thrown error's class or message differs per Node major, so a fixture built on one host describes that host and silently measures something else on the next.
46
48
  - Assert a runtime-chosen result as the property it must have, not as the number one run produced. Compression, timing, and buffer sizing are the runtime's choice, so pin the relationship the test depends on — that the encoded form is larger, that the second call is faster — and let the assertion fail when the input drifts out of the range where that relationship holds.
47
49
  - Measure an elapsed interval with `performance.now()`, never `Date.now()`. `Date.now()` returns whole milliseconds, so an interval built from two of its readings truncates at both ends and can under-report by a millisecond — enough to fail a boundary assertion against a timer that behaved correctly. `performance.now()` is monotonic and sub-millisecond, and it does not move when the wall clock does.
@@ -347,6 +349,7 @@ Before accepting that a behavior cannot be tested, look for the seam that would
347
349
 
348
350
  - Treat a collaborator reached through a hard-coded global — a stream, a clock source, a spawn, a fetch — as a missing injection point, not an untestable truth.
349
351
  - An injected collaborator with a real minimal implementation is a sanctioned boundary stub, not a mock of project-owned behavior.
352
+ - When a recording replays a wire, keep run-local identity, such as a random id or a clock reading, off it: after reading on the real peer that it treats the field as a label, send a key every run sends alike, such as the item's position, and map the answers back at the caller.
350
353
  - Add the seam rather than shipping the gap whenever the design would welcome it anyway, and whenever a sibling collaborator is already injected.
351
354
  - Record a genuinely irreducible gap where a reader meets it: what is unproven, why it cannot be driven, and what would change that. A silent untested guard reads exactly like a tested one.
352
355
 
@@ -185,7 +185,7 @@ one environment, so each is its own project:
185
185
  | `config` | `tests/config.test.ts` | Root configuration resolves its aliases, projects, and outputs, and the `configs/` leaves behind them | `test` |
186
186
  | `setup` | `tests/setup*.test.ts` other than either `setup:browser` proof | Prove root setup behavior in Node with `setup.ts`. | `test` |
187
187
  | `setup:browser` | `tests/setupBrowser.test.ts`, `tests/setupStyles.test.ts` | Prove browser and style setup behavior in Playwright Chromium with `setup.ts` and `setupBrowser.ts`. | `test` |
188
- | `journey:<variant>` | `tests/app/<application>/integration.test.ts` | Drive the application the Vite mode selects at the declared variant viewport in Playwright Chromium with `setup.ts` and `setupBrowser.ts`. | `test` through the journey scripts |
188
+ | `journey:<variant>` | `tests/app/<application>/integration.test.ts` | Drive the application the Vite mode selects at the declared variant viewport in Playwright Chromium with `setup.ts` and `setupBrowser.ts`. | On demand; `test` when private |
189
189
  | `guides` | `tests/guides.test.ts` | Every documented API exists, every public API is documented, every compared summary, example, and pitch equals its source, and every executable fence returns what the guide says it returns | `test` |
190
190
  | `conformance` | `tests/conformance.test.ts` | Where this package drifts from the official tooling it tracks | `test` |
191
191
  | `tree` | `tests/tree.test.ts` | The laws this package states about its own real tree that no vendored proof carries | `test` |
@@ -215,8 +215,8 @@ one environment, so each is its own project:
215
215
  factory, which resolves the Vite mode to `browser` or an app-side browser extension and collects
216
216
  `tests/app/<application>/integration.test.ts` for that application. The factory merges its
217
217
  `override` last, through `mergeOverride`, so an override replaces nothing it does not name. Exclude each collected suite
218
- from its application project, and run `test:journey` and one `test:journey:<framework>` per
219
- app-side browser extension after the application projects in `test`.
218
+ from its application project. Generate `test:journey` and one `test:journey:<framework>` per
219
+ app-side browser extension, and place them by the gate-placement paragraph that follows.
220
220
 
221
221
  Keep `conformance`, `tree`, `integration`, `distribution`, `studies`, and `service` as separate
222
222
  subjects.
@@ -230,6 +230,11 @@ parallelism in `service`. In a `private: true` workspace, never declare `prepubl
230
230
  `distribution`, reach `service` from `test`, and retain each isolated project's configuration.
231
231
  In both kinds of workspace, run `studies` on demand through `npm run test:studies` alone.
232
232
  Keep `test:studies` out of every gate and chain.
233
+ In a publishing workspace, run application and journey suites on demand through `test:app`,
234
+ `test:app:<environment>`, `test:app:<framework>`, `test:journey`, and
235
+ `test:journey:<framework>`. Keep them out of every release gate and chain.
236
+ In a `private: true` workspace, keep `test:app` in `test`, followed by `test:journey` and
237
+ each `test:journey:<framework>` the workspace declares.
233
238
 
234
239
  One project sits on neither axis. `probe` includes `tmp/probes/**/*.test.ts` so an agent can run a
235
240
  throwaway instrument against real sources, aliases and setup. Declare no proof there. Keep the