@orkestrel/scaffold 0.0.134 → 0.0.136

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 (53) hide show
  1. package/dist/agents/skills/orkestrel-parallel/scripts/lane.js +777 -83
  2. package/dist/agents/skills/orkestrel-publish/scripts/wave.js +327 -21
  3. package/dist/bin/main.js +254 -36
  4. package/dist/bin/main.js.map +1 -1
  5. package/dist/host/AGENTS.md +2 -2
  6. package/dist/host/agents/orchestration.md +2 -2
  7. package/dist/host/agents/skills/orkestrel-parallel/SKILL.md +1 -1
  8. package/dist/host/agents/skills/orkestrel-parallel/scripts/lane.ts +983 -123
  9. package/dist/host/agents/skills/orkestrel-publish/references/release.md +1 -0
  10. package/dist/host/agents/skills/orkestrel-publish/references/wave.md +22 -5
  11. package/dist/host/agents/skills/orkestrel-publish/scripts/wave.ts +403 -32
  12. package/dist/host/claude/agents/orkestrel.md +17 -17
  13. package/dist/host/claude/agents/reviewer.md +1 -1
  14. package/dist/host/claude/rules/architecture.md +1 -1
  15. package/dist/host/claude/rules/documentation.md +1 -1
  16. package/dist/host/claude/rules/patterns.md +4 -2
  17. package/dist/host/claude/rules/workspace.md +73 -67
  18. package/dist/host/configs/helpers.ts +109 -73
  19. package/dist/host/dotfiles/oxlintrc.json +1 -57
  20. package/dist/host/guides/agent.md +989 -395
  21. package/dist/host/guides/contract.md +198 -163
  22. package/dist/host/guides/database.md +978 -503
  23. package/dist/host/guides/indexeddb.md +80 -66
  24. package/dist/host/guides/middleware.md +5 -5
  25. package/dist/host/guides/ollama.md +41 -42
  26. package/dist/host/guides/relation.md +56 -32
  27. package/dist/host/guides/scaffold.md +185 -107
  28. package/dist/host/guides/sqlite.md +44 -23
  29. package/dist/host/guides/study.md +12 -12
  30. package/dist/host/guides/test.md +163 -47
  31. package/dist/host/guides/toolbox.md +127 -81
  32. package/dist/host/guides/workspace.md +21 -14
  33. package/dist/host/manifest.json +30 -30
  34. package/dist/host/scripts/browsers.sh +0 -0
  35. package/dist/host/scripts/codex.sh +0 -0
  36. package/dist/host/scripts/cursor.sh +0 -0
  37. package/dist/host/scripts/deps.sh +0 -0
  38. package/dist/host/scripts/npm.sh +0 -0
  39. package/dist/host/scripts/ollama.sh +0 -0
  40. package/dist/host/tests/config.test.ts +237 -115
  41. package/dist/src/core/index.cjs +591 -218
  42. package/dist/src/core/index.cjs.map +1 -1
  43. package/dist/src/core/index.d.cts +248 -29
  44. package/dist/src/core/index.d.ts +248 -29
  45. package/dist/src/core/index.js +581 -216
  46. package/dist/src/core/index.js.map +1 -1
  47. package/dist/src/server/index.cjs +18 -8
  48. package/dist/src/server/index.cjs.map +1 -1
  49. package/dist/src/server/index.d.cts +4 -3
  50. package/dist/src/server/index.d.ts +4 -3
  51. package/dist/src/server/index.js +19 -9
  52. package/dist/src/server/index.js.map +1 -1
  53. package/package.json +3 -3
@@ -63,7 +63,7 @@ configs/ thin target wrappers around root Vite/TypeScript configuration
63
63
  - **No nested functions**, except a callback passed as an argument or returned as the result; `.claude/rules/architecture.md` § Functions and orchestration bounds the literal positions it climbs.
64
64
  - **Functional core, imperative shell.** Pure exported leaves; stateful orchestration as class methods. A method never forwards 1:1 to a helper.
65
65
  - **No superfluous wrappers.** A wrapper adds a boundary, invariant, composition, translation, lifecycle, or materially narrower contract, or it goes.
66
- - **Minimal public API.** Create or substantively expand a capability with its first real consumer; this gate applies at creation, never later. Expose an existing reusable capability through its environment barrel regardless of consumer count. Remove a symbol only when the capability itself must not exist. Prefer one minimal interface and one shared engine, with a native backend override only for a faster path.
66
+ - **Minimal public API.** Create or substantively expand a capability with its first real consumer; this gate applies at creation, never later. Expose an existing reusable capability through its environment barrel regardless of consumer count. Remove a symbol only when the capability itself must not exist. Prefer one minimal interface over every backend, answered natively wherever a backend's engine can; `.claude/rules/architecture.md` § System constraints owns where the shared engine runs.
67
67
  - **No compatibility shims.** Update every consumer in the same change. Fleet packages and applications are greenfield: write no alias, wrapper, or migration for a shape or for data an earlier release produced.
68
68
  - **Mechanism, not product policy.** Framework code stops before application decisions.
69
69
  - **No polling architecture.** Park idle work on events and abort signals. Yield long work cooperatively.
@@ -91,7 +91,7 @@ Within the size, in order:
91
91
  3. **Implement.** Conform to the types. Place each declaration in its kind file. Update the barrel.
92
92
  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.
93
93
  5. **Consolidate.** Remove duplication, nested functions, and superfluous wrappers without widening the API.
94
- 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.
94
+ 6. **Document.** After the implementation is final, update the matching guide, comments, and TSDoc in one minimal pass: what `tests/guides.test.ts` asserts, plus each sentence the change made false. Before then, write, revise, and review no prose: a brief carries no wording row, a review reports no wording finding, and no fix round opens for wording. A line that states something false is the one exception, and it changes in the round that made it false.
95
95
 
96
96
  Test ladder, narrowest first; stop at the boundary the change size names:
97
97
 
@@ -45,7 +45,7 @@ The harness's own engine orchestrates: Claude Fable 5.2 or Claude Opus 5.5 in Cl
45
45
 
46
46
  - Name the role and its engine in every dispatch. Reach a role by its own name. When a hosting harness offers both columns, the dispatch names the column each lane runs on.
47
47
  - The capability column names the lane a role holds by default and the one a dispatch may assign (`reviewer`: subjective by default, objective when assigned; `orkestrel`: reader).
48
- - A role holding the subjective lane judges whether the requested shape and voice are present, names and boundaries are coherent, the work sits at the right layer, each concept earns its place, and the guide matches the code. A role holding the objective lane judges correctness under adverse orderings, what the contracts and installed declarations permit, dependency and range truth, the missing seam or the assertion that cannot fail, and the letter of the rules. A charter points here for both lenses.
48
+ - A role holding the subjective lane judges whether the requested shape is present, names and boundaries are coherent, the work sits at the right layer, each concept earns its place, and the guide matches the code. A role holding the objective lane judges correctness under adverse orderings, what the contracts and installed declarations permit, dependency and range truth, the missing seam or the assertion that cannot fail, and the letter of the rules. A charter points here for both lenses.
49
49
  - In a falsify round, where a claim about a name or a comment is no claim, both lanes hold the same claims and differ by posture: the subjective lane drives the subject as a real caller would and reports what that caller meets, and the objective lane tests the contract's letter across adverse orderings.
50
50
  - Read the word `lane` by its qualifier: a subjective or an objective lane is the lens a role holds, a writer, runner, or review lane is a unit at work, and the execution lane is the host resource `.agents/skills/orkestrel-parallel/SKILL.md` § Share an execution lane between sessions orders. Read the word `census` the same way: the `map.ts --census` flag counts a term, the `discovery.ts` script lists test collection, `.agents/skills/orkestrel-harden/references/bindings.md` sweeps a binding key, and a class census under § Depth, breadth, and machinery lists one defect class across packages.
51
51
  - `planner` also carries the read-only consultation § Engines admits for Claude Fable 5.2, on the engine the dispatch names.
@@ -135,7 +135,7 @@ The harness's own engine orchestrates: Claude Fable 5.2 or Claude Opus 5.5 in Cl
135
135
  | large | one independent round: `planner` and `analyst`, same brief, clean contexts, blind to each other | disjoint units in parallel | one `orkestrel-falsify` round on the integrated result | `verifier` tree-wide, once |
136
136
 
137
137
  - Never run a review on a small change. Never run a second design round on the same brief. A design question a repair round opens is its own brief, not a second design round on the campaign's brief.
138
- - 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.
138
+ - A review judges types, tests, and implementation; `AGENTS.md` § Work loop step 6 rules what it reports about wording.
139
139
  - 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.
140
140
  - 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.
141
141
  - 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.
@@ -21,7 +21,7 @@ description: >-
21
21
  Run from the checkout root. The script's opening comment owns its behavior.
22
22
 
23
23
  - `scripts/cases.ts --report FILE.json [--passed NAME ...] [--failed NAME ...]` reads a Vitest `--reporter=json` report and requires every case a `--passed` name matches to have passed and every case a `--failed` name matches to have failed. A name matches a case's full name or its own title exactly; both flags repeat. A name that matches no case is missing, and a failed case no name matches is refused, as is a test file that failed with no failed case (it did not collect, or a hook threw) and a report whose `success` is false while nothing in it failed. It prints one summary line, each difference, and `ok` or `differences=N`. Exit 0 when the report matches, 3 when it does not, 2 when the report cannot be read as a Vitest report, 64 usage.
24
- - `scripts/lane.ts --label NAME --journal PATH --errors PATH --cap SECONDS [--root DIR] [--solo] -- COMMAND [ARGS...]` runs process-running commands on this host in one heavy lane and several light lanes, each in arrival order, across every checkout and shell of one user account: it takes a ticket, waits with no timer, runs the command through `.agents/skills/orkestrel-dispatch/scripts/launch.ts`, kills and reads the command's process tree until no member remains, and releases. A ticket runs light only while `limits.json` exists under the lane root and the command's kind or its own run records read it light; every other ticket runs heavy, one at a time. `--solo` runs heavy with no light run beside it. `scripts/lane.ts --status [--root DIR] [--json]` prints each ticket in arrival order with its label, `live`, `dead`, or `unread`, its lane, and whether it holds, and names the heavy holder and every light holder; it writes nothing, and an absent root reads as an empty queue. The two forms are two modes, and `--status` with a run's flag is refused. Exit: the launcher's code, 1 when a signal ended the launcher, 64 usage, 69 when a light run passed its threshold and the lane ended it, 75 when the lane refused before the command ran, 70 when the command ran and its tree still reads as present or its ticket could not be removed; `--status` exits 0 on a read and 75 when the root cannot be listed. A command that itself exits 64, 69, 70, or 75 reads like the lane's own code. The opening comment owns the lane rules, the limits, and the migration stop.
24
+ - `scripts/lane.ts --label NAME --journal PATH --errors PATH --cap SECONDS [--root DIR] [--solo] -- COMMAND [ARGS...]` runs process-running commands on this host in one heavy lane and several light lanes, each in arrival order, across every checkout and shell of one user account: it takes a ticket, waits with no timer, runs the command through `.agents/skills/orkestrel-dispatch/scripts/launch.ts`, kills and reads the command's process tree until no member remains, and releases. A ticket runs light only while `limits.json` exists under the lane root and the command's kind or its own run records read it light; every other ticket runs heavy, one at a time. `npx` and `npm exec` read as the tool they run, and a `mutate` run of the falsify skill reads as the command it wraps, keyed without its edits file, and a `mutate --restore` run reads heavy; each waits on the earlier tickets of its working directory, and every later ticket of that directory waits on it. A run's record counts a command shorter than the sample interval when the command outlives one process query; a shorter command can record zero, per the opening comment's Sampling limit. A record that opens a history key prunes the history to the age and count bounds the opening comment names. `--solo` runs heavy with no light run beside it. `scripts/lane.ts --status [--root DIR] [--json]` prints each ticket in arrival order with its label, `live`, `dead`, or `unread`, its lane, and whether it holds, and names the heavy holder and every light holder; it writes nothing, and an absent root reads as an empty queue. The two forms are two modes, and `--status` with a run's flag is refused. Exit: the launcher's code, 1 when a signal ended the launcher, 64 usage, 69 when a light run passed its threshold and the lane ended it, 75 when the lane refused before the command ran, 70 when the command ran and its tree still reads as present or its ticket could not be removed; `--status` exits 0 on a read and 75 when the root cannot be listed. A command that itself exits 64, 69, 70, or 75 reads like the lane's own code. The opening comment owns the lane rules, the limits, and the migration stop.
25
25
 
26
26
  ## Bound the host
27
27