@orkestrel/scaffold 0.0.119 → 0.0.121

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.
Files changed (73) hide show
  1. package/dist/bin/main.js +19 -19
  2. package/dist/bin/main.js.map +1 -1
  3. package/dist/host/agents/skills/orkestrel-journey/references/layer.md +10 -10
  4. package/dist/host/agents/skills/orkestrel-journey/references/statechart.md +1 -1
  5. package/dist/host/agents/skills/orkestrel-journey/references/styles.md +3 -3
  6. package/dist/host/claude/agents/orkestrel.md +52 -51
  7. package/dist/host/claude/rules/tests.md +2 -2
  8. package/dist/host/claude/rules/typescript.md +2 -3
  9. package/dist/host/guides/abort.md +0 -4
  10. package/dist/host/guides/agent.md +5 -5
  11. package/dist/host/guides/brief.md +7 -15
  12. package/dist/host/guides/browser.md +1 -1
  13. package/dist/host/guides/budget.md +1 -5
  14. package/dist/host/guides/capture.md +2 -2
  15. package/dist/host/guides/codec.md +18 -3
  16. package/dist/host/guides/console.md +4 -30
  17. package/dist/host/guides/contract.md +23 -44
  18. package/dist/host/guides/csv.md +86 -93
  19. package/dist/host/guides/database.md +0 -4
  20. package/dist/host/guides/emitter.md +0 -2
  21. package/dist/host/guides/form.md +26 -47
  22. package/dist/host/guides/guide.md +0 -1
  23. package/dist/host/guides/html.md +3 -7
  24. package/dist/host/guides/indexeddb.md +28 -32
  25. package/dist/host/guides/interpret.md +165 -182
  26. package/dist/host/guides/jsonrpc.md +187 -0
  27. package/dist/host/guides/lsp.md +26 -51
  28. package/dist/host/guides/markdown.md +132 -141
  29. package/dist/host/guides/mcp.md +220 -276
  30. package/dist/host/guides/middleware.md +14 -22
  31. package/dist/host/guides/msg.md +47 -63
  32. package/dist/host/guides/ndjson.md +0 -4
  33. package/dist/host/guides/ollama.md +1 -3
  34. package/dist/host/guides/pool.md +0 -4
  35. package/dist/host/guides/probe.md +71 -80
  36. package/dist/host/guides/process.md +71 -79
  37. package/dist/host/guides/program.md +26 -35
  38. package/dist/host/guides/qualifier.md +0 -6
  39. package/dist/host/guides/queue.md +0 -4
  40. package/dist/host/guides/rater.md +6 -12
  41. package/dist/host/guides/reason.md +30 -36
  42. package/dist/host/guides/relation.md +0 -2
  43. package/dist/host/guides/router.md +11 -18
  44. package/dist/host/guides/scaffold.md +148 -144
  45. package/dist/host/guides/sea.md +47 -51
  46. package/dist/host/guides/server.md +15 -19
  47. package/dist/host/guides/sqlite.md +0 -4
  48. package/dist/host/guides/sse.md +6 -10
  49. package/dist/host/guides/table.md +481 -493
  50. package/dist/host/guides/template.md +0 -4
  51. package/dist/host/guides/terminal.md +0 -26
  52. package/dist/host/guides/test.md +46 -66
  53. package/dist/host/guides/timeout.md +0 -6
  54. package/dist/host/guides/tool.md +2 -6
  55. package/dist/host/guides/toolbox.md +0 -10
  56. package/dist/host/guides/websocket.md +0 -4
  57. package/dist/host/guides/worker.md +57 -57
  58. package/dist/host/guides/workflow.md +13 -26
  59. package/dist/host/guides/workspace.md +15 -21
  60. package/dist/host/manifest.json +64 -909
  61. package/dist/src/core/index.cjs +128 -181
  62. package/dist/src/core/index.cjs.map +1 -1
  63. package/dist/src/core/index.d.cts +213 -213
  64. package/dist/src/core/index.d.ts +213 -213
  65. package/dist/src/core/index.js +117 -170
  66. package/dist/src/core/index.js.map +1 -1
  67. package/dist/src/server/index.cjs +35 -34
  68. package/dist/src/server/index.cjs.map +1 -1
  69. package/dist/src/server/index.d.cts +62 -58
  70. package/dist/src/server/index.d.ts +62 -58
  71. package/dist/src/server/index.js +36 -35
  72. package/dist/src/server/index.js.map +1 -1
  73. package/package.json +13 -13
@@ -5,9 +5,9 @@
5
5
 
6
6
  A `Claim`, a `Verdict`, and a `receipt` carry the package. A `Claim` is the question: a case, a
7
7
  control that must break, and the TypeScript project both are judged under. A `Verdict` is the
8
- answer: one `Check` per stage in each phase, the case and the control. A `receipt` is the verdict's
9
- one-line summary of the conditions it was reached under, and it exists only when the claim proved
10
- itself.
8
+ answer: one `StageResult` per stage in each phase, the case and the control. A `receipt` is the
9
+ verdict's one-line summary of the conditions it was reached under, and it exists only when the
10
+ claim proved itself.
11
11
 
12
12
  The type stage runs the workspace's own compiler over a mirror of the tree, and the lint and runtime
13
13
  stages hold resident Oxlint and Vitest engines. Source: [`src/core`](../src/core),
@@ -29,8 +29,6 @@ trust with a shell.
29
29
  The data shapes, from [`types.ts`](../src/core/types.ts). Every property is readonly, and an absent
30
30
  optional field is absent rather than empty.
31
31
 
32
- A `Shape` cell holds an interface's data members as bare names in braces, `?` marking an optional member and `plus` introducing its call-signature members, and a type alias's own type literal with a union's arms escaped as `\|`. An extended interface's name comes before `plus`, with the members it adds after.
33
-
34
32
  | Name | Kind | Signature | Summary |
35
33
  | ------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
36
34
  | `Stage` | type | `(typeof PROBE_STAGES)[number]` | Names an inspection a claim passes through, derived from `PROBE_STAGES`. |
@@ -40,7 +38,7 @@ A `Shape` cell holds an interface's data members as bare names in braces, `?` ma
40
38
  | `Claim` | interface | `{ project, case, control }` | Carries everything the service needs to produce one verdict. |
41
39
  | `Party` | type | `(typeof PROBE_PARTIES)[number]` | Names who must act on an issue or probe failure. |
42
40
  | `Issue` | interface | `{ origin, path, message, range? }` | Carries one message a stage reported, where it reported it, and whose fault it names. |
43
- | `Check` | interface | `{ stage, elapsed, issues }` | Carries one stage's outcome: what it cost and what it reported. |
41
+ | `StageResult` | interface | `{ stage, elapsed, issues }` | Carries one stage's outcome: what it cost and what it reported. |
44
42
  | `Toolchain` | interface | `{ typescript, oxlint, vitest }` | Names the tool versions a verdict was produced with. |
45
43
  | `Project` | interface | `{ path, digest }` | Names the TypeScript project that judged a verdict's candidate drafts. |
46
44
  | `Verdict` | interface | `{ id, digest, toolchain, project, reason?, case, control, elapsed, receipt? }` | Carries the full result of one claim: every stage, for both the case and its control. |
@@ -51,15 +49,13 @@ A `Shape` cell holds an interface's data members as bare names in braces, `?` ma
51
49
  | `ProbeErrorContext` | interface | `{ stage?, path?, project?, name?, deadline?, value? }` | Carries the structured detail one probe failure reports beside its message. |
52
50
  | `ProbeErrorOptions` | interface | `{ origin, code, context?, cause? }` | Configures one probe failure at construction. |
53
51
 
54
- A row whose `Shape` cell names call-signature members after `plus` carries those members in
55
- [`## Methods`](#methods); the data members before `plus` stay here.
52
+ A row whose `Signature` cell names members with parentheses carries those members in
53
+ [`## Methods`](#methods); the data members it names without parentheses stay here.
56
54
 
57
55
  ### Constants
58
56
 
59
57
  From [`constants.ts`](../src/core/constants.ts). Each is frozen.
60
58
 
61
- A `Shape` cell holds the constant's declared type.
62
-
63
59
  | Name | Kind | Signature | Summary |
64
60
  | ---------------------- | ----- | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
65
61
  | `PROBE_STAGES` | const | `readonly ["type", "lint", "runtime"]` | Lists the stages a claim passes through, in the order a verdict reports them: `['type', 'lint', 'runtime']`. |
@@ -96,8 +92,6 @@ Schema. The schema is the wire contract's shape and `isClaim` is the admission r
96
92
  narrower on `Draft.path`: see
97
93
  [The advertised schema is wider than the admission rule](#registering-the-server).
98
94
 
99
- A `Shape` cell holds the constant's declared type.
100
-
101
95
  | Name | Kind | Signature | Summary |
102
96
  | --------------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
103
97
  | `DRAFT_SHAPE` | const | `import("@orkestrel/contract").ObjectShape<{ path: import("@orkestrel/contract").StringShape; text: import("@orkestrel/contract").StringShape; }, false>` | Describes one proposed file a claim carries. |
@@ -110,21 +104,19 @@ A `Shape` cell holds the constant's declared type.
110
104
  Total guards, from [`validators.ts`](../src/core/validators.ts). Each returns a boolean for any
111
105
  input and never throws.
112
106
 
113
- In a guard table a `Shape` cell holds the type the guard narrows to.
114
-
115
- | Name | Kind | Signature | Summary |
116
- | ------------- | ----- | ------------------ | ----------------------------------------------------------------------------------------------- |
117
- | `isStage` | const | `Guard<Stage>` | Checks whether a value names a stage. |
118
- | `isParty` | const | `Guard<Party>` | Checks whether a value names a party an issue carries. |
119
- | `isDraft` | const | `Guard<Draft>` | Checks whether a value carries a proposed file's path and text. |
120
- | `isCase` | const | `Guard<Case>` | Checks whether a value carries a claim's candidate drafts and its test. |
121
- | `isControl` | const | `Guard<Control>` | Checks whether a value carries a case plus the stage and reason it must fail for. |
122
- | `isClaim` | const | `Guard<Claim>` | Checks whether a value carries a project, a case, and a control. |
123
- | `isIssue` | const | `Guard<Issue>` | Checks whether a value carries one message, its location, and the origin of the fault it names. |
124
- | `isCheck` | const | `Guard<Check>` | Checks whether a value carries one stage's outcome. |
125
- | `isToolchain` | const | `Guard<Toolchain>` | Checks whether a value names every resolved tool version. |
126
- | `isProject` | const | `Guard<Project>` | Checks whether a value names one resolved TypeScript project and what it contained. |
127
- | `isVerdict` | const | `Guard<Verdict>` | Checks whether a value carries a complete verdict. |
107
+ | Name | Kind | Signature | Summary |
108
+ | --------------- | ----- | -------------------- | ----------------------------------------------------------------------------------------------- |
109
+ | `isStage` | const | `Guard<Stage>` | Checks whether a value names a stage. |
110
+ | `isParty` | const | `Guard<Party>` | Checks whether a value names a party an issue carries. |
111
+ | `isDraft` | const | `Guard<Draft>` | Checks whether a value carries a proposed file's path and text. |
112
+ | `isCase` | const | `Guard<Case>` | Checks whether a value carries a claim's candidate drafts and its test. |
113
+ | `isControl` | const | `Guard<Control>` | Checks whether a value carries a case plus the stage and reason it must fail for. |
114
+ | `isClaim` | const | `Guard<Claim>` | Checks whether a value carries a project, a case, and a control. |
115
+ | `isIssue` | const | `Guard<Issue>` | Checks whether a value carries one message, its location, and the origin of the fault it names. |
116
+ | `isStageResult` | const | `Guard<StageResult>` | Checks whether a value carries one stage's outcome. |
117
+ | `isToolchain` | const | `Guard<Toolchain>` | Checks whether a value names every resolved tool version. |
118
+ | `isProject` | const | `Guard<Project>` | Checks whether a value names one resolved TypeScript project and what it contained. |
119
+ | `isVerdict` | const | `Guard<Verdict>` | Checks whether a value carries a complete verdict. |
128
120
 
129
121
  ### Formatters and the token
130
122
 
@@ -133,7 +125,7 @@ Pure leaves, from [`helpers.ts`](../src/core/helpers.ts).
133
125
  | Name | Kind | Signature | Summary |
134
126
  | ---------------------- | -------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
135
127
  | `formatIssue` | function | `(issue: Issue) => string` | Renders one tool message as a single line an agent can classify and locate. |
136
- | `formatCheck` | function | `(check: Check) => string` | Renders one stage's outcome as its summary line followed by every message it reported. |
128
+ | `formatStageResult` | function | `(result: StageResult) => string` | Renders one stage's outcome as its summary line followed by every message it reported. |
137
129
  | `formatProof` | function | `(verdict: Verdict) => string` | Renders the closing line a rendered verdict ends with: the receipt it earned, or its absence. |
138
130
  | `formatReceipt` | function | `(verdict: Verdict) => string` | Renders the smallest text a verdict can travel as: what it judged, and how it ended. |
139
131
  | `formatVerdict` | function | `(verdict: Verdict) => string` | Renders a whole verdict as the text an agent reads. |
@@ -145,8 +137,6 @@ Pure leaves, from [`helpers.ts`](../src/core/helpers.ts).
145
137
 
146
138
  From [`types.ts`](../src/server/types.ts).
147
139
 
148
- A `Shape` cell holds an interface's data members as bare names in braces, `?` marking an optional member and `plus` introducing its call-signature members, and a type alias's own type literal with a union's arms escaped as `\|`. An extended interface's name comes before `plus`, with the members it adds after.
149
-
150
140
  | Name | Kind | Signature | Summary |
151
141
  | ---------------------- | --------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
152
142
  | `Inspection` | interface | `{ subject, claim }` | Carries one queued inspection: the case a stage reads and the claim it belongs to. |
@@ -260,7 +250,7 @@ Pure leaves and workspace readers, from [`helpers.ts`](../src/server/helpers.ts)
260
250
  | `guardStage` | function | `<T>(stage: Stage, operation: Promise<T>) => Promise<T>` | Guards one stage operation with the stage failure contract. |
261
251
  | `findRefusedPaths` | function | `(value: unknown) => readonly string[]` | Names every draft member of a claim-shaped value whose `path` this package's guard refuses. |
262
252
  | `normalizeValue` | function | `(workspace: string, value: unknown) => unknown` | Rewrites every workspace-contained absolute path in a value to its workspace-relative form and sorts every record's keys. |
263
- | `computeDigest` | function | `(workspace: string, value: unknown) => string` | Computes the canonical digest of one value as it stands in a target workspace. |
253
+ | `computeWorkspaceDigest` | function | `(workspace: string, value: unknown) => string` | Computes the canonical digest of one value as it stands in a target workspace. |
264
254
  | `captureListeners` | function | `(emitter: EventEmitter, events: readonly string[]) => ListenerCapture` | Records the listeners one emitter carries for a set of events. |
265
255
  | `releaseListeners` | function | `(emitter: EventEmitter, capture: ListenerCapture) => void` | Removes every listener one emitter gained for the captured events since its capture. |
266
256
 
@@ -288,21 +278,21 @@ The public call-signature members of each behavioral interface, one table per in
288
278
 
289
279
  #### `StageInterface`
290
280
 
291
- | Method | Returns | Summary |
292
- | --------- | ---------------- | ---------------------------------------------------------------------- |
293
- | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
294
- | `inspect` | `Promise<Check>` | Inspects one case. |
295
- | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
281
+ | Method | Returns | Summary |
282
+ | --------- | ---------------------- | ---------------------------------------------------------------------- |
283
+ | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
284
+ | `inspect` | `Promise<StageResult>` | Inspects one case. |
285
+ | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
296
286
 
297
287
  #### `RuntimeStage`
298
288
 
299
289
  The stage implements the preceding `StageInterface` contract.
300
290
 
301
- | Method | Returns | Summary |
302
- | --------- | ---------------- | ---------------------------------------------------------------------- |
303
- | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
304
- | `inspect` | `Promise<Check>` | Inspects one case. |
305
- | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
291
+ | Method | Returns | Summary |
292
+ | --------- | ---------------------- | ---------------------------------------------------------------------- |
293
+ | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
294
+ | `inspect` | `Promise<StageResult>` | Inspects one case. |
295
+ | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
306
296
 
307
297
  #### `TypeStageInterface`
308
298
 
@@ -311,20 +301,20 @@ mirror. Each termination utility has the existing `PROBE_DEADLINE` budget of 30,
311
301
  run concurrently. POSIX teardown retains `SIGTERM`. Warming settles before mirror removal on either
312
302
  host. The termination attempt remains best effort if the host utility fails.
313
303
 
314
- | Method | Returns | Summary |
315
- | --------- | ------------------ | ----------------------------------------------------------------------------------------------------------------- |
316
- | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
317
- | `inspect` | `Promise<Check>` | Inspects one case, against a caller-named project where the caller names one. |
318
- | `resolve` | `Promise<Project>` | Resolves one project to the path and digest the stage applies for it. Calls `start()` before reading the project. |
319
- | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
304
+ | Method | Returns | Summary |
305
+ | --------- | ---------------------- | ----------------------------------------------------------------------------------------------------------------- |
306
+ | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
307
+ | `inspect` | `Promise<StageResult>` | Inspects one case, against a caller-named project where the caller names one. |
308
+ | `resolve` | `Promise<Project>` | Resolves one project to the path and digest the stage applies for it. Calls `start()` before reading the project. |
309
+ | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
320
310
 
321
311
  #### `LintStageInterface`
322
312
 
323
- | Method | Returns | Summary |
324
- | --------- | ---------------- | ---------------------------------------------------------------------- |
325
- | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
326
- | `inspect` | `Promise<Check>` | Inspects one case, under the bound the caller supplies. |
327
- | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
313
+ | Method | Returns | Summary |
314
+ | --------- | ---------------------- | ---------------------------------------------------------------------- |
315
+ | `start` | `Promise<void>` | Begins the warm or joins the warm already begun. |
316
+ | `inspect` | `Promise<StageResult>` | Inspects one case, under the bound the caller supplies. |
317
+ | `destroy` | `Promise<void>` | Tears down the resident tool or the mirror and releases its resources. |
328
318
 
329
319
  #### `OverlayInterface`
330
320
 
@@ -377,13 +367,13 @@ keeps one commit checked out at two paths reading as one claim. A claim carrying
377
367
  therefore digests the same in every workspace; a claim that carries one digests per workspace, so
378
368
  compare two such tokens only when both were minted against the same tree.
379
369
 
380
- `prove` runs every stage over the case, then every stage over the control, and returns one `Check`
381
- per stage for each. A stage that cannot start throws rather than returning an empty check, so no
382
- verdict ever reports a stage that did not run.
370
+ `prove` runs every stage over the case, then every stage over the control, and returns one
371
+ `StageResult` per stage for each. A stage that cannot start throws rather than returning an empty
372
+ stage result, so no verdict ever reports a stage that did not run.
383
373
 
384
374
  The receipt is minted on these conditions together:
385
375
 
386
- - both phases report one check per stage; and
376
+ - both phases report one stage result per stage; and
387
377
  - the case produced no issue at any stage; and
388
378
  - the control produced an `origin: 'claimant'` issue at the stage it declared, and neither phase
389
379
  produced an `origin: 'instrument'` issue; and
@@ -394,10 +384,10 @@ receipt is minted for it. An `origin: 'instrument'` issue in either phase says t
394
384
  not complete, so nothing was learned about the code and no receipt is minted either. An
395
385
  `origin: 'workspace'` issue in the control decides neither break condition: it names the target
396
386
  tree rather than the candidate. A case carrying any issue did not run clean and earns no receipt.
397
- The check-per-stage condition binds both phases, because the clean-elsewhere condition reads the
398
- control entries a verdict carries: a control that omits a stage would otherwise read as a stage
399
- that stayed clean. `prove` records every stage for both phases, so that condition refuses only a
400
- verdict you assembled by hand and passed to `computeReceipt` yourself.
387
+ The one-stage-result-per-stage condition binds both phases, because the clean-elsewhere condition
388
+ reads the control entries a verdict carries: a control that omits a stage would otherwise read as a
389
+ stage that stayed clean. `prove` records every stage for both phases, so that condition refuses
390
+ only a verdict you assembled by hand and passed to `computeReceipt` yourself.
401
391
 
402
392
  `Issue.origin` names the party that must act, and the receipt conditions read that value rather
403
393
  than the message beside it. **A `claimant` issue is a tool's diagnostic about a candidate draft,
@@ -414,8 +404,8 @@ message about an inspection that did not complete — a specification it could n
414
404
  directory exists, for a reason the target tree does not own, a module that ran no test, or a covered
415
405
  module probe's own loader received and did not resolve.
416
406
  `formatIssue` renders the value first as `[claimant]`, `[workspace]`, or `[instrument]`, so the
417
- ownership survives `formatVerdict`. A clean runtime check means every collected test passed, not
418
- that the module reported itself passed.
407
+ ownership survives `formatVerdict`. A clean runtime stage result means every collected test
408
+ passed, not that the module reported itself passed.
419
409
 
420
410
  **A diagnostic about a project belongs to the workspace.** The compiler reports a configuration
421
411
  fault — a JSON syntax error, an option it cannot apply, a `types` entry or an extended project it
@@ -497,12 +487,13 @@ A TypeScript project whose JSON the compiler cannot parse reaches you as that `w
497
487
  An `instrument` failure carries the same meaning it carries on `Issue.origin`: the inspection did
498
488
  not complete, so nothing was learned about the code. Do not read it as evidence about a candidate.
499
489
 
500
- **The pure leaves are total over a validated claim and not over every value.** `computeDigest`,
501
- `normalizeValue`, and the other exported leaves are written for the values a `Claim` the guards
502
- admit can carry, so a caller that hands one a value `isClaim` would refuse — a cyclic record, a
503
- `BigInt` — gets the host's own `RangeError` or `TypeError` unchanged rather than a `ProbeError`.
504
- Measured on 2026-08-20: `computeDigest(workspace, cyclic)` raises
505
- `RangeError: Maximum call stack size exceeded`, and `computeDigest(workspace, { n: 1n })` raises
490
+ **The pure leaves are total over a validated claim and not over every value.**
491
+ `computeWorkspaceDigest`, `normalizeValue`, and the other exported leaves are written for the
492
+ values a `Claim` the guards admit can carry, so a caller that hands one a value `isClaim` would
493
+ refuse — a cyclic record, a `BigInt` — gets the host's own `RangeError` or `TypeError` unchanged
494
+ rather than a `ProbeError`. Measured on 2026-08-20: `computeWorkspaceDigest(workspace, cyclic)`
495
+ raises `RangeError: Maximum call stack size exceeded`, and
496
+ `computeWorkspaceDigest(workspace, { n: 1n })` raises
506
497
  `TypeError: Do not know how to serialize a BigInt`. Validate with `isClaim` before you reach past
507
498
  `prove` into a leaf.
508
499
 
@@ -532,7 +523,7 @@ and proof waits for type readiness and the boot controls. See [Lifecycle](#lifec
532
523
  - **That project is composed in the root configuration, not declared as a path string.** The
533
524
  runtime stage installs its own overlay plugin into each project's configuration so the candidate
534
525
  drafts resolve from memory. A project the root configuration names by path carries no such
535
- plugin, so the stage installs no overlay and runs no test. The check reports an
526
+ plugin, so the stage installs no overlay and runs no test. The stage result carries an
536
527
  `origin: 'workspace'` issue, because the party that must act is the workspace owner editing
537
528
  `vite.config.ts`:
538
529
  `The runtime stage cannot instrument the string-declared Vitest project <name> because its configuration carries no runtime overlay plugin`.
@@ -785,9 +776,9 @@ import { RuntimeStage } from '@orkestrel/probe/server'
785
776
 
786
777
  const runtime = new RuntimeStage(process.cwd())
787
778
  try {
788
- const check = await runtime.inspect(claim.case)
789
- check.stage // 'runtime'
790
- check.issues // []
779
+ const result = await runtime.inspect(claim.case)
780
+ result.stage // 'runtime'
781
+ result.issues // []
791
782
  } finally {
792
783
  await runtime.destroy()
793
784
  }
@@ -881,12 +872,12 @@ itself.
881
872
 
882
873
  The project digest is the digest of the `compilerOptions` member of `tsc --showConfig -p <project>`,
883
874
  read against the mirrored copy of the project with the mirror as the current directory, so the
884
- digest and the check read one set of files. `computeDigest` canonicalizes the record: a relative
885
- path the project declares that escapes the workspace root resolves against the mirror's own
886
- ancestors, and the mirror carries nothing such a path names. It still **moves with the TypeScript
887
- version**, because a compiler decides which options it resolves and how it spells them. That is
888
- contained rather than surprising: the token already names `typescript@<version>`, so any policy
889
- pinning a digest already pins the version.
875
+ digest and the check read one set of files. `computeWorkspaceDigest` canonicalizes the record: a
876
+ relative path the project declares that escapes the workspace root resolves against the mirror's
877
+ own ancestors, and the mirror carries nothing such a path names. It still **moves with the
878
+ TypeScript version**, because a compiler decides which options it resolves and how it spells them.
879
+ That is contained rather than surprising: the token already names `typescript@<version>`, so any
880
+ policy pinning a digest already pins the version.
890
881
 
891
882
  Further limits belong beside those:
892
883
 
@@ -991,7 +982,7 @@ already supply test code the runtime stage runs.
991
982
 
992
983
  **A path the workspace's version-control ignore excludes is a path the lint stage reports nothing
993
984
  for.** Oxlint's language server honours `.gitignore`, and it does so for text supplied from memory
994
- exactly as it does for a file on disk. The stage reports a clean check, not a skipped one.
985
+ exactly as it does for a file on disk. The stage reports a clean stage result, not a skipped one.
995
986
 
996
987
  This reaches the flagship claim stated earlier: its test lives at `tmp/probes/greeting.test.ts`, and
997
988
  `tmp` is ignored in this workspace, so the lint stage inspects the candidate `src/core/factories.ts`
@@ -1007,7 +998,7 @@ carries. Put every candidate draft you want linted at a path version control tra
1007
998
  The lint stage owns the workspace, the candidate's identity, and the projection from a diagnostic to
1008
999
  an `Issue`. `@orkestrel/lsp` owns everything between them, and the hookup is fixed:
1009
1000
 
1010
- - **The transport is `createStdioClientTransport` from `@orkestrel/lsp/server`.** Its command vector
1001
+ - **The transport is `createLSPStdioTransport` from `@orkestrel/lsp/server`.** Its command vector
1011
1002
  is the current executable, the entry `resolveWorkspaceBinary` resolves for `oxlint` in the target
1012
1003
  workspace, and `--lsp`; its directory is that workspace. The child is therefore the workspace's
1013
1004
  own installed Oxlint entry rather than a `node_modules/.bin` shim, for the reason the