@orkestrel/scaffold 0.0.124 → 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.
Files changed (53) hide show
  1. package/dist/agents/skills/orkestrel-publish/scripts/steps.js +523 -0
  2. package/dist/agents/skills/orkestrel-publish/scripts/wave.js +70 -11
  3. package/dist/bin/main.js +51 -18
  4. package/dist/bin/main.js.map +1 -1
  5. package/dist/host/agents/orchestration.md +7 -2
  6. package/dist/host/agents/platforms/windows.md +9 -1
  7. package/dist/host/agents/skills/orkestrel-dispatch/SKILL.md +1 -1
  8. package/dist/host/agents/skills/orkestrel-falsify/SKILL.md +1 -1
  9. package/dist/host/agents/skills/orkestrel-falsify/references/brief.md +1 -0
  10. package/dist/host/agents/skills/orkestrel-harden/references/methods.md +32 -4
  11. package/dist/host/agents/skills/orkestrel-journey/SKILL.md +18 -19
  12. package/dist/host/agents/skills/orkestrel-parallel/SKILL.md +1 -0
  13. package/dist/host/agents/skills/orkestrel-parallel/references/codex.md +2 -1
  14. package/dist/host/agents/skills/orkestrel-parallel/references/t3.md +5 -1
  15. package/dist/host/agents/skills/orkestrel-publish/SKILL.md +1 -0
  16. package/dist/host/agents/skills/orkestrel-publish/references/release.md +2 -2
  17. package/dist/host/agents/skills/orkestrel-publish/references/wave.md +23 -6
  18. package/dist/host/agents/skills/orkestrel-publish/scripts/steps.ts +654 -0
  19. package/dist/host/agents/skills/orkestrel-publish/scripts/wave.ts +79 -14
  20. package/dist/host/claude/agents/orkestrel.md +28 -28
  21. package/dist/host/claude/rules/patterns.md +1 -1
  22. package/dist/host/claude/rules/portability.md +2 -0
  23. package/dist/host/claude/rules/quality.md +6 -1
  24. package/dist/host/claude/rules/tests.md +6 -1
  25. package/dist/host/claude/rules/workspace.md +8 -3
  26. package/dist/host/guides/agent.md +575 -346
  27. package/dist/host/guides/brief.md +52 -48
  28. package/dist/host/guides/browser.md +2 -2
  29. package/dist/host/guides/interpret.md +531 -155
  30. package/dist/host/guides/mcp.md +183 -61
  31. package/dist/host/guides/ndjson.md +4 -3
  32. package/dist/host/guides/ollama.md +125 -68
  33. package/dist/host/guides/program.md +117 -39
  34. package/dist/host/guides/qualifier.md +110 -59
  35. package/dist/host/guides/rater.md +85 -32
  36. package/dist/host/guides/scaffold.md +49 -22
  37. package/dist/host/guides/study.md +596 -489
  38. package/dist/host/guides/toolbox.md +159 -80
  39. package/dist/host/guides/workflow.md +44 -25
  40. package/dist/host/manifest.json +41 -35
  41. package/dist/src/core/index.cjs +12 -10
  42. package/dist/src/core/index.cjs.map +1 -1
  43. package/dist/src/core/index.d.cts +3 -1
  44. package/dist/src/core/index.d.ts +3 -1
  45. package/dist/src/core/index.js +12 -10
  46. package/dist/src/core/index.js.map +1 -1
  47. package/dist/src/server/index.cjs +23 -11
  48. package/dist/src/server/index.cjs.map +1 -1
  49. package/dist/src/server/index.d.cts +10 -6
  50. package/dist/src/server/index.d.ts +10 -6
  51. package/dist/src/server/index.js +23 -11
  52. package/dist/src/server/index.js.map +1 -1
  53. package/package.json +7 -7
@@ -571,7 +571,7 @@ publishes no interface and is documented directly.
571
571
 
572
572
  | Method | Summary |
573
573
  | ----------- | ------------------------------------------------------------------------------------------- |
574
- | `lookup` | Looks up the highest release each declared range admits. |
574
+ | `lookup` | Looks up the highest eligible release each declared range admits. |
575
575
  | `fetch` | Fetches each named package's guide, beside the local mirror it answers for. |
576
576
  | `read` | Reads each named vendored file from the repository, beside the target bytes it answers for. |
577
577
  | `catalog` | Catalogs the published fleet from the registry's organization package list. |
@@ -697,8 +697,9 @@ answers a read and grant no verb write authority that it did not already have.
697
697
  `new --bin` creates the executable entry, its test, and its scoped Vite and TypeScript wrappers. The
698
698
  `new --app browser` command selects the journey axis, creates its birth-owned wrapper, defines
699
699
  `appJourney` in the root configuration, and excludes the browser integration suite from
700
- `app:browser`. Its manifest declares `test:journey` and invokes it after `npm run test:app` in
701
- `test`. It also declares `journey: capture journey` and `capture: capture frames` for explicit
700
+ `app:browser`. Its manifest declares `test:journey`. A `private: true` workspace invokes it after
701
+ `npm run test:app` in `test`; a publishing workspace runs application and journey suites on demand,
702
+ outside release gates and chains. It also declares `journey: capture journey` and `capture: capture frames` for explicit
702
703
  scoped selections. A selection without a browser application emits no journey axis. `--styles`, `--themes`,
703
704
  `--showcase`, and `--extend` select the structural facts and the extensions, and Surfaces and extensions
704
705
  states what each emits and what each refuses. Creation leaves `setup` empty, and the remaining
@@ -940,11 +941,17 @@ in command order. A configuration value containing an unresolved shell expansion
940
941
  When a `test:*` script whose text names `vitest` names a configuration that the plan does not emit
941
942
  and the target does not hold, the non-blocking `projects` question names the script and configuration
942
943
  path. Its remedy asks you to add the configuration, or remove the script that names it and its
943
- invocation from the `test` chain. When the plan emits `test:journey` and no chain from `test` reaches
944
+ invocation from the `test` chain. In a `private: true` workspace, when the plan emits `test:journey` and no chain from `test` reaches
944
945
  `npm run test:journey` through literal `npm run` calls, that question asks you to insert the invocation
945
- after `npm run test:app`. These advisories belong to `configs`
946
- and remain report-only during `repair`: the command preserves a `test` chain the package owns and
947
- an unplanned script. A configuration emitted by the plan or present in the target does not raise
946
+ after `npm run test:app`. A publishing workspace requires neither application nor journey suites
947
+ in its gate chains. When a chain from `test` or `prepublishOnly` reaches their script names, names
948
+ their Vitest projects, or runs their planned application or journey wrappers through literal
949
+ `vitest run --config` calls, the question asks you to remove those invocations and run the suites on demand.
950
+ For reached projects and wrappers, the question includes the caller and its command.
951
+ These advisories belong to `configs`. `repair` and `overwrite` replace a byte-exact former generated
952
+ publishing `test` chain with the planned chain. An authored chain, including one with an extra step,
953
+ stays report-only; the commands preserve that chain and any unplanned script.
954
+ A configuration emitted by the plan or present in the target does not raise
948
955
  the absent configuration advisory.
949
956
 
950
957
  `audit` still completes the comparison and reports one non-blocking `projects` question when its
@@ -984,11 +991,16 @@ Each occupied framework face adds `check:<axis>:vue` and `build:<axis>:vue`; the
984
991
  Selected showcase pages add `showcase`, `showcase:<framework>`, `build:showcase`, and `build:showcase:<framework>`; application journeys add `test:journey:<framework>`.
985
992
  Its `test:src:<face>` script accepts, as its generated predecessor, the command that ran the project
986
993
  without building the face first, and `build:src:styles` accepts the styles-only build as the
987
- predecessor of the chain that builds themes after it. The `test` chain joins the region only as a
988
- generated predecessor: when it runs fewer steps than the planned chain and every step it runs is a planned step in the planned
994
+ predecessor of the chain that builds themes after it. A publishing `test` chain joins the region when
995
+ it matches byte for byte the planned chain with the generated `test:app`, `test:journey`, and framework
996
+ journey invocations inserted after `test:src`, where that blueprint emitted them before.
997
+ `repair` and `overwrite` remove those helper invocations from that exact predecessor.
998
+ The `test` chain also joins the region as a generated predecessor when it runs fewer steps than
999
+ the planned chain and every step it runs is a planned step in the planned
989
1000
  order, `repair` and `overwrite` write the planned chain in its place. That write lands only when
990
1001
  every step the planned chain adds runs a script the manifest declares or the region writes. The
991
- `test:src` and `test:app` aggregates sit outside the region, so a chain whose planned form adds an
1002
+ `test:src` and `test:app` aggregates sit outside the region. Only a private workspace's planned
1003
+ chain invokes `test:app`. A chain whose planned form adds an
992
1004
  aggregate the manifest lacks stays with the package, and the `projects` question keeps its remedy.
993
1005
  `audit` reports this chain write only through the `projects` question, so a planned step that
994
1006
  registers no Vitest project, such as `npm run test:guides`, lands on the next `repair` without an
@@ -1008,7 +1020,8 @@ The browser application's journey axis adds `journey` and `capture`. Their gener
1008
1020
  `capture journey` and `capture frames`, have no predecessor forms in the accepted set. Missing
1009
1021
  commands append; generated values remain writable; `replaceManifestScripts` preserves customized
1010
1022
  values while repairing siblings independently, so a selected or wrapped `journey` command survives
1011
- repair. Neither scoped command replaces `test:journey` in the gate chain.
1023
+ repair. Neither scoped command replaces `test:journey` in a private workspace's gate chain.
1024
+ Publishing workspaces keep application and journey suites outside release gates and chains.
1012
1025
 
1013
1026
  The range region and the script region are not groups. `package.json` is birth-owned, so the
1014
1027
  `manifest` group creates it when a workspace is first materialized and never rewrites it afterwards,
@@ -1373,7 +1386,9 @@ viewport, and provides `variant`
1373
1386
  as its name, `variants` as the declared list, and `capture` as a boolean. The root configuration
1374
1387
  reads `process.env.CAPTURE === '1'` for that boolean. The generated `test:journey` script runs
1375
1388
  `vitest run --config configs/app/vite.journey.config.ts --no-cache --reporter=dot`, and the generated
1376
- `test` chain runs it after the application projects. With the journey axis off, the ordinary
1389
+ `test` chain runs it after the application projects only in a private workspace. In a publishing
1390
+ workspace, application and journey suites run on demand outside release gates and chains.
1391
+ With the journey axis off, the ordinary
1377
1392
  browser project retains its integration suite.
1378
1393
 
1379
1394
  The same axis adds `journey: capture journey` and `capture: capture frames`, using the executable
@@ -1611,7 +1626,9 @@ keeps your variant list and passes the Vite mode to the root
1611
1626
  through `mergeOverride`, so a wrapper changes only the fields it names and the project keeps its
1612
1627
  include and exclude replacement, viewport, commands, and plugin rules. The manifest runs `test:journey` for the base
1613
1628
  application and `test:journey:<framework>`, the same command with `--mode <framework>`, for each
1614
- app-side browser extension, after `npm run test:app` in `test`.
1629
+ app-side browser extension. A private workspace runs them after `npm run test:app` in `test`.
1630
+ A publishing workspace keeps those scripts available on demand and invokes neither application
1631
+ nor journey suites from its release gates and chains.
1615
1632
 
1616
1633
  Scaffold seeds one birth-owned arrival journey per application at
1617
1634
  `tests/app/<application>/integration.test.ts`. The base journey imports `app/browser/main.ts`, and
@@ -2153,7 +2170,7 @@ extras pass through unchanged except for the selected showcase pair. Extras foll
2153
2170
  `ORKESTREL_RANGE_PATTERN`; foreign peers follow `FLOOR_RANGE_PATTERN`.
2154
2171
 
2155
2172
  A browser application with `showcase: true`, including its Vue face, selects exact
2156
- `vite-plugin-singlefile: 2.3.3`, Vite `^8.3.6` from scaffold's manifest, and the npm override
2173
+ `vite-plugin-singlefile: 2.3.3`, Vite `^8.3.7` from scaffold's manifest, and the npm override
2157
2174
  `"vite-plugin-singlefile@2.3.3": { "micromatch": "npm:picomatch@2.3.2" }`. This policy applies
2158
2175
  after extras. Online resolution excludes this pair from ordinary foreign-major updates; other
2159
2176
  dependencies retain their usual resolution. Repair preserves each package's runtime or development
@@ -2226,11 +2243,11 @@ The dependency tables select these floors:
2226
2243
  | TypeScript | `^6.0.3` | A selected `src/vue` or `app/vue` face |
2227
2244
  | Vitest | `^5.1.0` | Every workspace |
2228
2245
  | `@vitest/browser-playwright` | `^5.1.0` | Browser tooling |
2229
- | `oxlint` | `^1.91.0` | Every workspace |
2230
- | `oxfmt` | `^0.76.0` | Every workspace |
2246
+ | `oxlint` | `^1.93.0` | Every workspace |
2247
+ | `oxfmt` | `^0.77.0` | Every workspace |
2231
2248
  | `@microsoft/api-extractor` | `^7.60.1` | Declaration builds; uses its bundled TypeScript 6.0.3 engine |
2232
2249
  | `playwright` | `^1.64.1` | Browser tooling |
2233
- | Vite | `^8.3.6` | Every workspace |
2250
+ | Vite | `^8.3.7` | Every workspace |
2234
2251
  | `@types/node` | `^24.19.2` | Every workspace; generated workspaces support Node `>=22.18.0` |
2235
2252
 
2236
2253
  Node 26 types admit APIs that the supported runtime lacks. Inside the declared major the verbs
@@ -2774,10 +2791,18 @@ verdict carrying its cause rather than thrown, so one unreachable package never
2774
2791
  rest of the answer. The organization package list is the exception, because without it there is no
2775
2792
  fleet to report.
2776
2793
 
2777
- A found verdict carries the highest version the declared range admits, not whatever `dist-tags.latest`
2778
- names. `lookup` reads the packument's version map, selects across it before any collection bound can
2779
- truncate the map, and falls back to the `latest` tag only when that tag is itself admitted. A range of
2780
- `*` admits every version, which is how a caller asks for the highest release outright.
2794
+ A found verdict carries the highest eligible version the declared range admits. `lookup` reads the
2795
+ packument's version map and selects across it before any collection bound can truncate the map. A
2796
+ version whose entry carries a non-empty string `deprecated` field is never eligible, under any range;
2797
+ an empty string, `false`, and an absent field do not mark a version deprecated.
2798
+
2799
+ When `dist-tags.latest` reads as a version, it caps a range of `*` and every range in its own major,
2800
+ so a release published above the tag is not selected. A range on another major is not capped: with
2801
+ `latest` at `6.0.0` or at `4.2.0`, `^5` reads the top of major 5.
2802
+
2803
+ A map that holds an admitted version but no eligible one reads `unmatched`, with a note naming that
2804
+ cause, and never falls back to the tag. A missing map, or a map that holds no admitted version, falls
2805
+ back to the `latest` tag only when the range admits that tag.
2781
2806
 
2782
2807
  Each bound counts decoded bytes, and a version lookup asks the registry for the abbreviated
2783
2808
  packument — `dist-tags` and a trimmed version map, rather than the full per-version metadata no
@@ -2976,7 +3001,9 @@ publishes at least one `src` environment or sheet face. In a publishing workspac
2976
3001
  and `service` run from `prepublishOnly`, and `conformance` and `tree` stay in `test`. In a
2977
3002
  `private: true` workspace, `distribution` is absent, `service` runs from `test`, and there is no
2978
3003
  `prepublishOnly`. In both kinds of workspace, `studies` runs on demand through `npm run test:studies`
2979
- alone, outside every gate and chain. The `policy` project reports an exporting root setup module that lacks its sibling proof or an import from `tests/setup.test.ts`.
3004
+ alone, outside every gate and chain. Application and journey suites run on demand outside release
3005
+ gates and chains in a publishing workspace, and remain in `test` in a private workspace.
3006
+ The `policy` project reports an exporting root setup module that lacks its sibling proof or an import from `tests/setup.test.ts`.
2980
3007
  Separately, a filled, exporting `tests/setup*.ts` module that no `tests/setup*.test.ts`
2981
3008
  proof covers raises the non-blocking `setup` question in `audit`, which names the modules and the proof to add.
2982
3009
  For setup modules the workspace authors, the workspace supplies the behavior proof; the setup modules scaffold seeds arrive with their sibling proofs.