@orkestrel/scaffold 0.0.125 → 0.0.127

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 (35) hide show
  1. package/dist/bin/main.js +50 -14
  2. package/dist/bin/main.js.map +1 -1
  3. package/dist/host/AGENTS.md +1 -1
  4. package/dist/host/agents/orchestration.md +5 -4
  5. package/dist/host/agents/skills/orkestrel-falsify/SKILL.md +1 -1
  6. package/dist/host/agents/skills/orkestrel-harden/references/methods.md +2 -2
  7. package/dist/host/agents/skills/orkestrel-journey/SKILL.md +18 -19
  8. package/dist/host/agents/skills/orkestrel-parallel/references/codex.md +2 -1
  9. package/dist/host/claude/AGENTS.md +2 -2
  10. package/dist/host/claude/agents/orkestrel.md +18 -18
  11. package/dist/host/claude/agents/planner.md +2 -2
  12. package/dist/host/claude/rules/quality.md +3 -0
  13. package/dist/host/claude/rules/tests.md +3 -0
  14. package/dist/host/claude/rules/workspace.md +11 -5
  15. package/dist/host/codex/agents/planner.toml +2 -2
  16. package/dist/host/guides/agent.md +285 -161
  17. package/dist/host/guides/capture.md +123 -123
  18. package/dist/host/guides/database.md +18 -7
  19. package/dist/host/guides/ndjson.md +4 -3
  20. package/dist/host/guides/ollama.md +2 -2
  21. package/dist/host/guides/program.md +3 -3
  22. package/dist/host/guides/qualifier.md +1 -1
  23. package/dist/host/guides/relation.md +71 -31
  24. package/dist/host/guides/scaffold.md +101 -64
  25. package/dist/host/guides/study.md +22 -12
  26. package/dist/host/guides/toolbox.md +9 -2
  27. package/dist/host/manifest.json +26 -26
  28. package/dist/host/tests/config.test.ts +24 -6
  29. package/dist/src/core/index.cjs +134 -79
  30. package/dist/src/core/index.cjs.map +1 -1
  31. package/dist/src/core/index.d.cts +30 -7
  32. package/dist/src/core/index.d.ts +30 -7
  33. package/dist/src/core/index.js +134 -80
  34. package/dist/src/core/index.js.map +1 -1
  35. package/package.json +4 -4
@@ -82,39 +82,39 @@ Exported from `@orkestrel/scaffold`, and reachable from
82
82
 
83
83
  #### Interfaces
84
84
 
85
- | Name | Kind | Signature | Summary |
86
- | ----------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
87
- | `AppDefinition` | interface | `{ configs, project, entry? }` | Describes the configuration and runtime-entry settings one private `app` environment contributes. |
88
- | `ArtifactBase` | interface | `{ path, group, ownership, environment? }` | Describes the fields every planned file carries. |
89
- | `ArtifactTemplateSet` | interface | `{ source, tests, docs, guides, orchestration }` | Represents the source, test, document, guide, and service template text. |
90
- | `Audit` | interface | `{ findings, questions }` | Represents the whole comparison of a plan against a target's current content. |
91
- | `Blueprint` | interface | `{ name, description?, keywords, src, app, extensions, styles, themes, dependencies, peers, extras, version, engines, overrides, bin, setup, guides, integration, conformance, tree, service, vendors, studies, global, showcase, journey, skills }` | Represents the closed, JSON-serializable workspace specification. |
92
- | `BrowserExtension` | interface | `{ surface, name, axes }` | Represents a browser framework and its physically occupied axes. |
93
- | `CompileFailure` | interface | `{ code, message }` | Represents the coded reason one compile stage failed. |
94
- | `CompileRecord` | interface | `{ stage, input, output, failure? }` | Holds the input and output snapshot of one compile stage. |
95
- | `CompilerInterface` | interface | `{ emitter, compile(), audit(), destroy() }` | Describes the compilation contract: pure, synchronous, and host-independent. |
96
- | `CompilerOptions` | interface | `{ on?, error? }` | Represents the options for the compiler. |
97
- | `ConfigTemplateSet` | interface | `{ root, factories, tsconfigs, vites, browsers, commands }` | Represents the configuration template text, grouped by the artifact each template builds. |
98
- | `ContentArtifact` | interface | `{ origin, content, hex?, source? }` | Represents a text file produced by the template or computed compilation path. |
99
- | `Dependency` | interface | `{ name, range, optional? }` | Represents one runtime `@orkestrel/*` dependency of a generated workspace. |
100
- | `DependencyPinSet` | interface | `{ runtime, development }` | Describes the runtime and development sections a range-writing operation may change. |
101
- | `FrameworkDefinition` | interface | `{ plugin, checker, suffixes, refused, dependencies }` | Describes the tooling and package boundaries a browser framework contributes. |
102
- | `HostArtifact` | interface | `{ origin, ownership, source?, pointer?, hex?, content? }` | Represents a file byte-copied from the vendored data root, planned before its bytes are read. |
103
- | `HydratedArtifact` | interface | `{ origin, ownership, source?, hex, content? }` | Represents a vendored file whose exact bytes have been read, so its content can be compared. |
104
- | `ManifestDependencySet` | interface | `{ runtime, development, peer }` | Describes the runtime, development, and peer sections read from an existing package manifest. |
105
- | `ManifestEdit` | interface | `{ start, end, text }` | Represents one in-place replacement of manifest text. |
106
- | `ManifestRegionSet` | interface | `{ pins, scripts, additions?, overrides? }` | Describes the manifest regions a writing operation may change. |
107
- | `ManifestScript` | interface | `{ name, command, accepted }` | Represents one manifest script a region-writing operation may replace. |
108
- | `ManifestToken` | interface | `{ text, index, depth, value }` | Represents one string or object brace found in manifest text. |
109
- | `Override` | interface | `{ path, content }` | Represents one artifact override. |
110
- | `Plan` | interface | `{ blueprint, groups, artifacts, hash? }` | Holds the compiled, ordered artifact list and the selection it covers. |
111
- | `PlanSummary` | interface | `{ name, src, app, groups, host, template, computed }` | Represents the tally of one plan by artifact origin. |
112
- | `Question` | interface | `{ field, message, blocking, candidates? }` | Represents one validation issue raised against a blueprint or a plan. |
113
- | `CompileResult` | interface | `{ plan?, questions, stages }` | Represents the replayable outcome of one compile. |
114
- | `SrcDefinition` | interface | `{ configs, project, path, formats }` | Describes the build and export settings one published `src` environment contributes. |
115
- | `StylesExtension` | interface | `{ surface, name }` | Represents a named sheet face under `src/<name>`. |
116
- | `ToolchainHold` | interface | `{ framework, range, reason }` | Represents one foreign tool range required by a browser framework. |
117
- | `ViteMachinery` | interface | `{ browser, frameworks, output, showcase }` | Names which host-specific pipelines a generated root Vite configuration carries. |
85
+ | Name | Kind | Signature | Summary |
86
+ | ----------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
87
+ | `AppDefinition` | interface | `{ configs, project, entry? }` | Describes the configuration and runtime-entry settings one private `app` environment contributes. |
88
+ | `ArtifactBase` | interface | `{ path, group, ownership, environment? }` | Describes the fields every planned file carries. |
89
+ | `ArtifactTemplateSet` | interface | `{ source, tests, docs, guides, orchestration }` | Represents the source, test, document, guide, and service template text. |
90
+ | `Audit` | interface | `{ findings, questions }` | Represents the whole comparison of a plan against a target's current content. |
91
+ | `Blueprint` | interface | `{ name, description?, keywords, src, app, extensions, styles, themes, dependencies, peers, extras, version, engines, overrides, bin, setup, guides, integration, conformance, tree, service, vendors, studies, global, showcase, journey, base, skills }` | Represents the closed, JSON-serializable workspace specification. |
92
+ | `BrowserExtension` | interface | `{ surface, name, axes }` | Represents a browser framework and its physically occupied axes. |
93
+ | `CompileFailure` | interface | `{ code, message }` | Represents the coded reason one compile stage failed. |
94
+ | `CompileRecord` | interface | `{ stage, input, output, failure? }` | Holds the input and output snapshot of one compile stage. |
95
+ | `CompilerInterface` | interface | `{ emitter, compile(), audit(), destroy() }` | Describes the compilation contract: pure, synchronous, and host-independent. |
96
+ | `CompilerOptions` | interface | `{ on?, error? }` | Represents the options for the compiler. |
97
+ | `ConfigTemplateSet` | interface | `{ root, factories, tsconfigs, vites, browsers, commands }` | Represents the configuration template text, grouped by the artifact each template builds. |
98
+ | `ContentArtifact` | interface | `{ origin, content, hex?, source? }` | Represents a text file produced by the template or computed compilation path. |
99
+ | `Dependency` | interface | `{ name, range, optional? }` | Represents one runtime `@orkestrel/*` dependency of a generated workspace. |
100
+ | `DependencyPinSet` | interface | `{ runtime, development }` | Describes the runtime and development sections a range-writing operation may change. |
101
+ | `FrameworkDefinition` | interface | `{ plugin, checker, suffixes, refused, dependencies }` | Describes the tooling and package boundaries a browser framework contributes. |
102
+ | `HostArtifact` | interface | `{ origin, ownership, source?, pointer?, hex?, content? }` | Represents a file byte-copied from the vendored data root, planned before its bytes are read. |
103
+ | `HydratedArtifact` | interface | `{ origin, ownership, source?, hex, content? }` | Represents a vendored file whose exact bytes have been read, so its content can be compared. |
104
+ | `ManifestDependencySet` | interface | `{ runtime, development, peer }` | Describes the runtime, development, and peer sections read from an existing package manifest. |
105
+ | `ManifestEdit` | interface | `{ start, end, text }` | Represents one in-place replacement of manifest text. |
106
+ | `ManifestRegionSet` | interface | `{ pins, scripts, additions?, overrides? }` | Describes the manifest regions a writing operation may change. |
107
+ | `ManifestScript` | interface | `{ name, command, accepted }` | Represents one manifest script a region-writing operation may replace. |
108
+ | `ManifestToken` | interface | `{ text, index, depth, value }` | Represents one string or object brace found in manifest text. |
109
+ | `Override` | interface | `{ path, content }` | Represents one artifact override. |
110
+ | `Plan` | interface | `{ blueprint, groups, artifacts, hash? }` | Holds the compiled, ordered artifact list and the selection it covers. |
111
+ | `PlanSummary` | interface | `{ name, src, app, groups, host, template, computed }` | Represents the tally of one plan by artifact origin. |
112
+ | `Question` | interface | `{ field, message, blocking, candidates? }` | Represents one validation issue raised against a blueprint or a plan. |
113
+ | `CompileResult` | interface | `{ plan?, questions, stages }` | Represents the replayable outcome of one compile. |
114
+ | `SrcDefinition` | interface | `{ configs, project, path, formats }` | Describes the build and export settings one published `src` environment contributes. |
115
+ | `StylesExtension` | interface | `{ surface, name }` | Represents a named sheet face under `src/<name>`. |
116
+ | `ToolchainHold` | interface | `{ framework, range, reason }` | Represents one foreign tool range required by a browser framework. |
117
+ | `ViteMachinery` | interface | `{ browser, frameworks, output, showcase }` | Names which host-specific pipelines a generated root Vite configuration carries. |
118
118
 
119
119
  | Name | Kind | Signature | Summary |
120
120
  | ------------------- | --------- | --------------------------------------------- | -------------------------------------------------------------------------------------------------- |
@@ -146,6 +146,7 @@ Exported from `@orkestrel/scaffold`, and reachable from
146
146
  | `BROWSE_DEV_DEPENDENCIES` | const | `Readonly<Record<string, string>>` | Names the development dependency a browser or styles surface adds. |
147
147
  | `BROWSE_UPSTREAM` | const | `readonly string[]` | Lists the packages `@orkestrel/browser` depends on at runtime, directly or transitively, frozen. |
148
148
  | `CAPTURE_DEV_DEPENDENCIES` | const | `Readonly<Record<string, string>>` | Names the development dependency a browser application's journey axis adds. |
149
+ | `BROWSER_ENTRIES` | const | `readonly string[]` | Lists the Orkestrel packages that publish a `/browser` entry, frozen. |
149
150
  | `CAPTURE_UPSTREAM` | const | `readonly string[]` | Lists the capture package and its fleet runtime dependency closure, frozen. |
150
151
  | `CANON_PATHS` | const | `readonly string[]` | Lists the instruction-canon paths staged for reading rather than for a target, frozen. |
151
152
  | `CATALOG_AGENT_PATH` | const | `".claude/agents/orkestrel.md"` | Names the agent file whose marker-bounded package table the catalog verb alone owns. |
@@ -697,8 +698,9 @@ answers a read and grant no verb write authority that it did not already have.
697
698
  `new --bin` creates the executable entry, its test, and its scoped Vite and TypeScript wrappers. The
698
699
  `new --app browser` command selects the journey axis, creates its birth-owned wrapper, defines
699
700
  `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
701
+ `app:browser`. Its manifest declares `test:journey`. A `private: true` workspace invokes it after
702
+ `npm run test:app` in `test`; a publishing workspace runs application and journey suites on demand,
703
+ outside release gates and chains. It also declares `journey: capture journey` and `capture: capture frames` for explicit
702
704
  scoped selections. A selection without a browser application emits no journey axis. `--styles`, `--themes`,
703
705
  `--showcase`, and `--extend` select the structural facts and the extensions, and Surfaces and extensions
704
706
  states what each emits and what each refuses. Creation leaves `setup` empty, and the remaining
@@ -940,11 +942,17 @@ in command order. A configuration value containing an unresolved shell expansion
940
942
  When a `test:*` script whose text names `vitest` names a configuration that the plan does not emit
941
943
  and the target does not hold, the non-blocking `projects` question names the script and configuration
942
944
  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
945
+ invocation from the `test` chain. In a `private: true` workspace, when the plan emits `test:journey` and no chain from `test` reaches
944
946
  `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
947
+ after `npm run test:app`. A publishing workspace requires neither application nor journey suites
948
+ in its gate chains. When a chain from `test` or `prepublishOnly` reaches their script names, names
949
+ their Vitest projects, or runs their planned application or journey wrappers through literal
950
+ `vitest run --config` calls, the question asks you to remove those invocations and run the suites on demand.
951
+ For reached projects and wrappers, the question includes the caller and its command.
952
+ These advisories belong to `configs`. `repair` and `overwrite` replace a byte-exact former generated
953
+ publishing `test` chain with the planned chain. An authored chain, including one with an extra step,
954
+ stays report-only; the commands preserve that chain and any unplanned script.
955
+ A configuration emitted by the plan or present in the target does not raise
948
956
  the absent configuration advisory.
949
957
 
950
958
  `audit` still completes the comparison and reports one non-blocking `projects` question when its
@@ -984,11 +992,16 @@ Each occupied framework face adds `check:<axis>:vue` and `build:<axis>:vue`; the
984
992
  Selected showcase pages add `showcase`, `showcase:<framework>`, `build:showcase`, and `build:showcase:<framework>`; application journeys add `test:journey:<framework>`.
985
993
  Its `test:src:<face>` script accepts, as its generated predecessor, the command that ran the project
986
994
  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
995
+ predecessor of the chain that builds themes after it. A publishing `test` chain joins the region when
996
+ it matches byte for byte the planned chain with the generated `test:app`, `test:journey`, and framework
997
+ journey invocations inserted after `test:src`, where that blueprint emitted them before.
998
+ `repair` and `overwrite` remove those helper invocations from that exact predecessor.
999
+ The `test` chain also joins the region as a generated predecessor when it runs fewer steps than
1000
+ the planned chain and every step it runs is a planned step in the planned
989
1001
  order, `repair` and `overwrite` write the planned chain in its place. That write lands only when
990
1002
  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
1003
+ `test:src` and `test:app` aggregates sit outside the region. Only a private workspace's planned
1004
+ chain invokes `test:app`. A chain whose planned form adds an
992
1005
  aggregate the manifest lacks stays with the package, and the `projects` question keeps its remedy.
993
1006
  `audit` reports this chain write only through the `projects` question, so a planned step that
994
1007
  registers no Vitest project, such as `npm run test:guides`, lands on the next `repair` without an
@@ -1004,11 +1017,12 @@ section. A name carrying no colon has no family, and a family the section declar
1004
1017
  nothing to follow, so each of those is appended after the last declared script instead. `catalog`
1005
1018
  writes no script region; it names the ranges alone.
1006
1019
 
1007
- The browser application's journey axis adds `journey` and `capture`. Their generated commands,
1020
+ The base browser application's journey axis adds `journey` and `capture`, and each app-side browser face adds `journey:<name>` and `capture:<name>`. Their generated commands,
1008
1021
  `capture journey` and `capture frames`, have no predecessor forms in the accepted set. Missing
1009
- commands append; generated values remain writable; `replaceManifestScripts` preserves customized
1022
+ commands append, each face's `journey:<name>` and `capture:<name>` among them; generated values remain writable; `replaceManifestScripts` preserves customized
1010
1023
  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.
1024
+ repair. Neither scoped command replaces `test:journey` in a private workspace's gate chain.
1025
+ Publishing workspaces keep application and journey suites outside release gates and chains.
1012
1026
 
1013
1027
  The range region and the script region are not groups. `package.json` is birth-owned, so the
1014
1028
  `manifest` group creates it when a workspace is first materialized and never rewrites it afterwards,
@@ -1253,7 +1267,7 @@ because the shape is chosen once and read afterwards: `new` refuses the advisory
1253
1267
  caller creating a workspace holds the same refusal, and the Compile section states it.
1254
1268
 
1255
1269
  `bin`, `setup`, `guides`, `integration`, `conformance`, `tree`, `service`, `vendors`, `studies`,
1256
- `global`, `styles`, `themes`, `showcase`, `journey`, and `skills` are structural facts, and `extensions` lists the
1270
+ `global`, `styles`, `themes`, `showcase`, `journey`, `base`, and `skills` are structural facts, and `extensions` lists the
1257
1271
  extension faces. Reading verbs set each fact and list each extension only when the workspace
1258
1272
  physically ships the directory or exact-case file that defines it, never because of the workspace's
1259
1273
  name and never because a sibling fact is set.
@@ -1283,6 +1297,9 @@ can import and render the extension's components. A browser application without
1283
1297
  extension keeps the non-Vue pipeline, and a `src/browser` selection adds no Vue plugin or
1284
1298
  dependency.
1285
1299
 
1300
+ Every browser project also pre-bundles each declared `@orkestrel` package's `/browser` entry when
1301
+ that package publishes one. Node projects keep no `optimizeDeps` setting.
1302
+
1286
1303
  A structural fact is read when a verb runs, not when the file appears. Writing
1287
1304
  `tests/integration.test.ts` into a workspace sets the fact, but the root configuration on disk was
1288
1305
  generated before that file existed and still registers no `integration` project, so `test:config`
@@ -1355,11 +1372,19 @@ no artifact, configuration, script, or dependency, and the gate reports a non-bl
1355
1372
  that field so the caller who set it learns it emitted nothing.
1356
1373
 
1357
1374
  The library's `journey` flag defaults to `false`; `new` sets it when its `app` selection includes
1358
- `browser`. Reading verbs infer it from the wrapper's presence. The flag requires a browser application. Without that
1359
- application, it emits no journey configuration or script and raises a non-blocking `journey`
1360
- question. With that application, the content-owned root configuration defines the `appJourney`
1361
- factory and excludes `tests/app/browser/integration.test.ts` from the ordinary `app:browser`
1362
- project. Surfaces and extensions states the journey of each further application mode.
1375
+ `browser`. Reading verbs infer it from the wrapper's presence. The `base` fact selects the exact-case
1376
+ `app/browser/main.ts` entry. `new` sets `base` when the browser environment is selected, while a
1377
+ target without that entry, including one with only `app/browser/Main.ts`, has `base: false`. A
1378
+ face-only workspace retains the browser environment and its `appBrowser` project without planning
1379
+ the base entry, scripts, application record member, or arrival journey. When the browser environment
1380
+ has no base entry or app-side browser face, the plan raises one non-blocking question on `base`.
1381
+
1382
+ With a journey and a declared browser application, the content-owned root configuration defines
1383
+ the `appJourney` factory. It selects the suite for the exact Vite mode and refuses a mode the generated `applications`
1384
+ record omits. The base record member follows `base`, which follows the exact-case `app/browser/main.ts`
1385
+ entry, and a face's member follows its extension, which the reader sets from the `app/<name>` directory. The ordinary `app:browser` project
1386
+ excludes the base arrival suite only when `base` is true. Surfaces and extensions states the journey
1387
+ of each further application mode.
1363
1388
 
1364
1389
  Edit the variant list in `configs/app/vite.journey.config.ts`. This wrapper is birth-owned:
1365
1390
  scaffold creates it when absent and preserves your edits during `repair`. It imports
@@ -1367,17 +1392,22 @@ scaffold creates it when absent and preserves your edits during `repair`. It imp
1367
1392
  at 1280 × 800 and `compact` at 390 × 844 without a theme. Rename and extend those variants for
1368
1393
  your application; apply themes through the application's interface in your tests.
1369
1394
 
1370
- The wrapper registers `journey:<name>` for each variant through the root factory. Each project
1395
+ The wrapper registers `journey:<name>` for each variant through the root factory. Each app-side
1396
+ browser face also receives `journey:<name>` as `capture journey --mode <name>` and `capture:<name>`
1397
+ as `capture frames --mode <name>`. Each project
1371
1398
  collects the integration suite of the application the Vite mode selects, sets the variant
1372
1399
  viewport, and provides `variant`
1373
1400
  as its name, `variants` as the declared list, and `capture` as a boolean. The root configuration
1374
1401
  reads `process.env.CAPTURE === '1'` for that boolean. The generated `test:journey` script runs
1375
1402
  `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
1403
+ `test` chain runs it after the application projects only in a private workspace. In a publishing
1404
+ workspace, application and journey suites run on demand outside release gates and chains.
1405
+ With the journey axis off, the ordinary
1377
1406
  browser project retains its integration suite.
1378
1407
 
1379
- The same axis adds `journey: capture journey` and `capture: capture frames`, using the executable
1380
- from `node_modules/@orkestrel/capture`. Run `npm run journey -- <selector>` for behavior with
1408
+ With `base`, the same axis adds `journey: capture journey` and `capture: capture frames`, using the
1409
+ executable from `node_modules/@orkestrel/capture`. Each app-side browser face adds
1410
+ `journey:<name>` and `capture:<name>`, the same commands with `--mode <name>`. Run `npm run journey -- <selector>` for behavior with
1381
1411
  capture off and `npm run capture -- <selector>` for frames with `CAPTURE=1`. A selector is `all`
1382
1412
  or a colon-delimited owner path declared by the wrapper. Narrow with `--variant <name>` and
1383
1413
  `--case <exact-full-name>`; frames also accept `--state <name>`. Replace the selector with
@@ -1480,6 +1510,7 @@ no selection is stored anywhere. Each fact and each extension has its own marker
1480
1510
  | `themes` | The exact-case `THEMES_BARREL_PATH` and `THEMES_ENTRY_PATH` files under `src/styles/themes` |
1481
1511
  | `showcase` | The exact-case `configs/app/vite.showcase.config.ts` wrapper, or a `showcase` directory |
1482
1512
  | `journey` | The exact-case `configs/app/vite.journey.config.ts` wrapper |
1513
+ | `base` | The exact-case `app/browser/main.ts` entry |
1483
1514
  | `vue` | A `src/vue` or `app/vue` directory, and `axes` lists each one present |
1484
1515
  | A styles extension | A direct `src/<name>` directory holding the exact-case `index.scss` and `sheet.ts` files |
1485
1516
 
@@ -1594,7 +1625,7 @@ leaves every sibling page in place. It stamps the final inlined page through `st
1594
1625
  the page `showcase/<application>.html`. The manifest declares `showcase` and `build:showcase` for
1595
1626
  the base mode and `showcase:<framework>` and `build:showcase:<framework>` for each extension mode,
1596
1627
  and a publishing workspace rebuilds every page from `prepublishOnly` after `npm run build` and
1597
- before `npm test`. The vendored `.prettierignore` lists `showcase/`, so formatting never rewrites a
1628
+ before `npm test`, the base page only when `base` is set. The vendored `.prettierignore` lists `showcase/`, so formatting never rewrites a
1598
1629
  committed page.
1599
1630
 
1600
1631
  `stampPage` writes one `<meta name="build-id" content="DIGEST" />` line before the line that closes
@@ -1611,7 +1642,10 @@ keeps your variant list and passes the Vite mode to the root
1611
1642
  through `mergeOverride`, so a wrapper changes only the fields it names and the project keeps its
1612
1643
  include and exclude replacement, viewport, commands, and plugin rules. The manifest runs `test:journey` for the base
1613
1644
  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`.
1645
+ app-side browser extension. A private workspace runs them after `npm run test:app` in `test`.
1646
+ A publishing workspace keeps those scripts available on demand and invokes neither application
1647
+ nor journey suites from its release gates and chains. With `base` unset, the plan omits `test:journey`
1648
+ and its `npm run test:journey` chain entry, and the base arrival journey below.
1615
1649
 
1616
1650
  Scaffold seeds one birth-owned arrival journey per application at
1617
1651
  `tests/app/<application>/integration.test.ts`. The base journey imports `app/browser/main.ts`, and
@@ -2153,7 +2187,7 @@ extras pass through unchanged except for the selected showcase pair. Extras foll
2153
2187
  `ORKESTREL_RANGE_PATTERN`; foreign peers follow `FLOOR_RANGE_PATTERN`.
2154
2188
 
2155
2189
  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
2190
+ `vite-plugin-singlefile: 2.3.3`, Vite `^8.3.7` from scaffold's manifest, and the npm override
2157
2191
  `"vite-plugin-singlefile@2.3.3": { "micromatch": "npm:picomatch@2.3.2" }`. This policy applies
2158
2192
  after extras. Online resolution excludes this pair from ordinary foreign-major updates; other
2159
2193
  dependencies retain their usual resolution. Repair preserves each package's runtime or development
@@ -2187,8 +2221,9 @@ row entering or leaving the manifest moves a test rather than passing unnoticed.
2187
2221
  of `STYLES_DEV_DEPENDENCIES`, is a seed as well: it carries the `^1.105.1` range the
2188
2222
  `@orkestrel/veneer` checkout declared on 2026-09-30, and that test names it in the seeded set.
2189
2223
 
2190
- `CAPTURE_DEV_DEPENDENCIES` seeds `@orkestrel/capture` at `^0.0.1` only when the blueprint's
2191
- `journey` axis is enabled and its `app` includes `browser`. `CAPTURE_UPSTREAM` withholds that
2224
+ `CAPTURE_DEV_DEPENDENCIES` seeds `@orkestrel/capture` at `^0.0.5`, the first release whose commands
2225
+ take `--mode`, only when the blueprint plans a journey: the `journey` axis with the base entry or
2226
+ an app-side browser face. `CAPTURE_UPSTREAM` withholds that
2192
2227
  seed from capture itself and its fleet runtime closure: `@orkestrel/contract`,
2193
2228
  `@orkestrel/emitter`, `@orkestrel/process`, and `@orkestrel/timeout`. The frozen, sorted list
2194
2229
  follows dependencies and peers from capture's installed manifests and moves with the capture
@@ -2226,11 +2261,11 @@ The dependency tables select these floors:
2226
2261
  | TypeScript | `^6.0.3` | A selected `src/vue` or `app/vue` face |
2227
2262
  | Vitest | `^5.1.0` | Every workspace |
2228
2263
  | `@vitest/browser-playwright` | `^5.1.0` | Browser tooling |
2229
- | `oxlint` | `^1.91.0` | Every workspace |
2230
- | `oxfmt` | `^0.76.0` | Every workspace |
2264
+ | `oxlint` | `^1.93.0` | Every workspace |
2265
+ | `oxfmt` | `^0.78.0` | Every workspace |
2231
2266
  | `@microsoft/api-extractor` | `^7.60.1` | Declaration builds; uses its bundled TypeScript 6.0.3 engine |
2232
2267
  | `playwright` | `^1.64.1` | Browser tooling |
2233
- | Vite | `^8.3.6` | Every workspace |
2268
+ | Vite | `^8.3.7` | Every workspace |
2234
2269
  | `@types/node` | `^24.19.2` | Every workspace; generated workspaces support Node `>=22.18.0` |
2235
2270
 
2236
2271
  Node 26 types admit APIs that the supported runtime lacks. Inside the declared major the verbs
@@ -2984,7 +3019,9 @@ publishes at least one `src` environment or sheet face. In a publishing workspac
2984
3019
  and `service` run from `prepublishOnly`, and `conformance` and `tree` stay in `test`. In a
2985
3020
  `private: true` workspace, `distribution` is absent, `service` runs from `test`, and there is no
2986
3021
  `prepublishOnly`. In both kinds of workspace, `studies` runs on demand through `npm run test:studies`
2987
- 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`.
3022
+ alone, outside every gate and chain. Application and journey suites run on demand outside release
3023
+ gates and chains in a publishing workspace, and remain in `test` in a private workspace.
3024
+ The `policy` project reports an exporting root setup module that lacks its sibling proof or an import from `tests/setup.test.ts`.
2988
3025
  Separately, a filled, exporting `tests/setup*.ts` module that no `tests/setup*.test.ts`
2989
3026
  proof covers raises the non-blocking `setup` question in `audit`, which names the modules and the proof to add.
2990
3027
  For setup modules the workspace authors, the workspace supplies the behavior proof; the setup modules scaffold seeds arrive with their sibling proofs.