@orkestrel/scaffold 0.0.74 → 0.0.75

package/dist/host/agents/skills/orkestrel-prove-journey/SKILL.md

@@ -95,11 +95,8 @@ start, and let it choose the capture destination, the matrix row, and the statec
   repair.
 - Name each variant for the theme and the viewport it renders, such as `dark-390`. Never split the
   theme from the viewport; a split writes a filename naming a combination the run did not render.
-- Compose each variant's theme `apply` inside the test, from the variant's name. Vitest `provide`
-  carries serializable values, so `name`, `width`, and `height` cross that channel and a function
-  does not.
-- Apply the theme through the application's own interface wherever the application ships a theme
-  control, and through the attribute the surface reads where it does not.
+- Keep the provided variants as serializable `JourneyVariant` data: `name`, `width`, and `height`.
+  Compose no callback merely to pass that data to a capture.
 - Run the axis with `npm run test:journey`, which runs that wrapper and joins the `test` chain. Set
   `CAPTURE` to `1` in your own shell and run `npm run test:journey` again to write the frames; the
   root configuration reads that variable and provides it as `capture`.
@@ -124,12 +121,28 @@ Settle the one it reports before trusting a green run.
 intermediate script raises none. It reports the configuration question only for a `test:*` script
 whose text names `vitest`, so a script naming another runner's configuration raises none either.
 
+### Prepare the capture theme
+
+- Where the application ships a theme control, await the theme action through that interface
+  before driving the state the journey captures. Pass the provided `JourneyVariant` list directly
+  to `createPortfolio` when capture needs no additional synchronous document change. Never attach
+  an asynchronous action to `CaptureVariant.apply` or re-resolve a covered theme control at capture
+  time.
+- Where the surface has no theme control, prepare the theme through the attribute the surface
+  reads. Use the optional `CaptureVariant.apply` hook only for a synchronous document change,
+  such as setting that attribute. Treat its `() => void` contract as synchronous: `createPortfolio`
+  invokes the hook without awaiting a returned promise.
+- Keep `applyTheme` as the workspace's own browser setup helper. Make it drive the theme control
+  through the published journey verbs and await the announced theme state and settled paint.
+- Put the provided-context declaration in the browser test setup module, and consume the injected
+  data in `tests/app/browser/integration.test.ts` through the following portfolio configuration.
+  Mount the shipped application entry with its real provisions before the acceptance journey runs.
+- From `tests/app/browser/integration.test.ts`, pass `../../../tmp/capture/states` as the capture
+  directory to write into the workspace's `tmp/capture/states` directory. The browser provider
+  resolves a custom screenshot path relative to the test file's directory.
+
 ```ts
 import type { JourneyVariant } from '@orkestrel/test'
-import type { CaptureVariant } from '@orkestrel/test/browser'
-import { inject } from 'vitest'
-// `applyTheme` is the workspace's own setup-module export, named for the act it performs.
-import { applyTheme } from '../../setupBrowser.js'
 
 declare module 'vitest' {
 	interface ProvidedContext {
@@ -138,13 +151,37 @@ declare module 'vitest' {
 		readonly capture: boolean
 	}
 }
+```
+
+```ts
+import { createPortfolio } from '@orkestrel/test/browser'
+import { inject } from 'vitest'
+import { applyTheme } from '../../setupBrowser.js'
 
 const VARIANT = inject('variant')
 const CAPTURE = inject('capture')
-const VARIANTS: readonly CaptureVariant[] = inject('variants').map((variant) => ({
-	...variant,
-	apply: () => applyTheme(variant.name),
-}))
+const VARIANTS = inject('variants')
+const PORTFOLIO = createPortfolio({
+	states: ['home'],
+	variants: VARIANTS,
+	variant: VARIANT,
+	directory: '../../../tmp/capture/states',
+	enabled: CAPTURE,
+})
+```
+
+At the start of the existing home acceptance journey, insert the following theme preparation before
+that journey's actions.
+
+```ts
+await applyTheme(VARIANT)
+```
+
+Immediately after that journey's actual rendered-home assertion, insert the following placement.
+Keep the existing journey and its assertions as the consumer; add no screenshot-only test.
+
+```ts
+await PORTFOLIO.place('home')
 ```
 
 ## Apply the journey laws

package/dist/host/agents/skills/orkestrel-prove-journey/references/captures.md

@@ -68,14 +68,12 @@ these.
 - Declare the viewport list in the birth-owned `configs/app/vite.journey.config.ts` wrapper, as
   `readonly JourneyVariant[]`. That file is the adopter's, so its names and its viewports are the
   application's to set, and the presence of that file is the journey axis.
-- Compose each variant's `apply` inside the test, from the name the project provided, and hand the
-  composed `CaptureVariant` list to `createPortfolio`. `JourneyVariant` carries the `name`, the
-  `width`, and the `height` that cross Vitest's `provide` channel; `CaptureVariant` adds the `apply`
-  that does not.
+- Prepare the theme under [SKILL.md](../SKILL.md#prepare-the-capture-theme) before driving the
+  captured state, and use the variant list that preparation requires.
 - Name each variant for the theme and the viewport it renders, such as `dark-390`. The name is the
   second half of every filename the run writes, so a variant named for one alone produces a
   portfolio nobody can tell apart.
-- Pass the whole composed list as `variants` and `inject('variant')` as `variant`.
+- Pass the whole declared list as `variants` and `inject('variant')` as `variant`.
   `createPortfolio` refuses a `variant` no declared variant carries, and `files` expands the
   registry across the whole list rather than across the one being rendered.
 - Produce the portfolio — the registry times the variants — by running the axis once per variant,

package/dist/host/codex/config.toml

@@ -1,15 +1,8 @@
-# Codex bridge. AGENTS.md governs code. .agents/orchestration.md governs agent operation and is
-# shared by every harness. This layer adds only what a Codex session does differently.
-#
-# One-time machine setup, so this session can reach Opus 5 as an MCP tool:
-#   codex mcp add claude -- claude mcp serve
-
 approval_policy = "never"
 sandbox_mode = "danger-full-access"
 model = "gpt-5.6-sol"
 model_reasoning_effort = "high"
 review_model = "gpt-5.6-sol"
-
 developer_instructions = """
 Read AGENTS.md, .agents/orchestration.md, every applicable .claude/rules/*.md file, the
 dispatch-named .agents/skills workflow and its required references, and the governing
@@ -41,3 +34,7 @@ interrupt_message = true
 [mcp_servers.probe]
 command = "node"
 args = ["node_modules/@orkestrel/probe/dist/bin/main.js"]
+
+[mcp_servers.codex]
+command = "codex"
+args = ["mcp-server"]

package/dist/host/guides/scaffold.md

@@ -408,7 +408,7 @@ The inventory contracts carry these data members.
 | `listCanonPaths`          | function | Lists the canon paths a target holds, filtered to a plan's groups.                     |
 | `listDirectories`         | function | Lists a directory's descendant directories as sorted root-relative paths.              |
 | `listFiles`               | function | Lists a directory's files as sorted root-relative paths.                               |
-| `matchesAnchor`           | function | Tests whether a captured directory is still the same directory.                        |
+| `matchesAnchor`           | function | Tests whether a path still holds the captured directory identity.                      |
 | `matchesExecutablePath`   | function | Tests whether a vendored path is one a target receives executable.                     |
 | `matchesExpectation`      | function | Tests whether a destination still holds what was captured of it.                       |
 | `matchesGitPath`          | function | Tests whether a path addresses a target's own repository metadata.                     |
@@ -921,6 +921,11 @@ only that browser proof and loads `tests/setup.ts` and `tests/setupBrowser.ts` t
 Chromium. The generated manifest emits the selected `test:setup` and `test:setup:browser` scripts
 and invokes them from `test`. Scaffold generates no setup proof for an empty setup seed.
 
+When the `app` axis selects `browser`, the browser setup project also applies the Vue
+single-file-component transform. Your `tests/setupBrowser.ts` module and its paired proof can
+import and render application Vue components. A browser setup proof without `app/browser` keeps
+the non-Vue pipeline; selecting `src/browser` alone adds no Vue plugin or dependency.
+
 A structural fact is read when a verb runs, not when the file appears. Writing
 `tests/integration.test.ts` into a workspace sets the fact, but the root configuration on disk was
 generated before that file existed and still registers no `integration` project, so `test:config`
@@ -1856,6 +1861,7 @@ A transaction owns a private root beside the target on the same volume, so every
 rename rather than a copy. A failure part way through commit restores every destination it already
 promoted and removes every directory it created. No destination ever receives half-written bytes.
 It is not a journal: a process killed between promotions leaves a mixed target.
+Directory anchors capture native bigint device and inode values without numeric rounding.
 The transaction binds each directory's location rather than its lifetime, so an ancestor swapped
 for another path, a file, a symlink, or nothing is refused, and one deleted and recreated in place
 may not be.

package/dist/host/manifest.json

@@ -232,7 +232,7 @@
 			"storage": "agents/skills/orkestrel-prove-journey/SKILL.md",
 			"destination": ".agents/skills/orkestrel-prove-journey/SKILL.md",
 			"executable": false,
-			"digest": "2e18a1917b1b6ab4a523c14c9c00f5aad3d553f6c9f4b34b4cac43692c3efe55"
+			"digest": "c558fb0abcbad2b264c509fc6f82edba4fd9a1cede95a6185eec89056df4361e"
 		},
 		{
 			"storage": "agents/skills/orkestrel-prove-journey/agents/openai.yaml",
@@ -244,7 +244,7 @@
 			"storage": "agents/skills/orkestrel-prove-journey/references/captures.md",
 			"destination": ".agents/skills/orkestrel-prove-journey/references/captures.md",
 			"executable": false,
-			"digest": "a9fcd48be6a92dd717fc69fbb2a90e0406aa1d5b238cde7c2a760d345c0c3315"
+			"digest": "e36b56406d3e8643f253196d915ea1f265aae3169e810769171f75a8ab4461f5"
 		},
 		{
 			"storage": "agents/skills/orkestrel-prove-journey/references/decide.md",
@@ -628,7 +628,7 @@
 			"storage": "codex/config.toml",
 			"destination": ".codex/config.toml",
 			"executable": false,
-			"digest": "d37ab5cd40864ba5667f1e942979a7f0bc641aa8b9636d34a3bb93abffb6c729"
+			"digest": "c8364a20fca401e65f3c092968b1f6b4d4e025a1efd91e22beb01b3fcd39e076"
 		},
 		{
 			"storage": "configs/helpers.ts",
@@ -910,7 +910,7 @@
 			"storage": "guides/scaffold.md",
 			"destination": "guides/scaffold.md",
 			"executable": false,
-			"digest": "3254d49f9878de5e68423a0b052cd2c8be4ba021e41b28ad725a9a0a76b6dc2f"
+			"digest": "7c89a20cba178e493d6cb46e517742cf31d12836eb24481a0eb7c96a2f20acad"
 		},
 		{
 			"storage": "guides/sea.md",
@@ -2001,5 +2001,5 @@
 			]
 		}
 	],
-	"digest": "f339bb7ef137bbfe5e85acab6e93a02cb79491922ba27febf3329dbcec7c9423"
+	"digest": "6e8e2b0524717bfc2b648acba0de5901c7c267a9c189155b45e3cb681b14bf6d"
 }

package/dist/src/core/index.cjs

@@ -4,7 +4,7 @@ let _orkestrel_template = require("@orkestrel/template");
 let _orkestrel_emitter = require("@orkestrel/emitter");
 var package_default = {
 	name: "@orkestrel/scaffold",
-	version: "0.0.74",
+	version: "0.0.75",
 	description: "Scaffold workspaces with commands: new, audit, repair, catalog, and overwrite.",
 	keywords: [
 		"audit",
@@ -102,7 +102,7 @@ var package_default = {
 		"@orkestrel/guide": "^0.0.20",
 		"@orkestrel/html": "^0.0.10",
 		"@orkestrel/probe": "^0.0.16",
-		"@orkestrel/test": "^0.0.17",
+		"@orkestrel/test": "^0.0.18",
 		"@types/node": "^26.5.1",
 		"@vitest/browser-playwright": "^4.1.11",
 		"oxfmt": "^0.68.0",
@@ -962,7 +962,10 @@ function isNamedPlugin(plugin: PluginOption): plugin is { name: string } {
 			journey: `
 // Replace the journey fields directly: merging would concatenate the ordinary include
 // and retain the exclusion of the journey suite.
-export function appJourney(variant: JourneyVariant, variants: readonly JourneyVariant[]): UserConfig {
+export function appJourney(
+	variant: JourneyVariant,
+	variants: readonly JourneyVariant[],
+): UserConfig {
 	const browser = appBrowser()
 	return {
 		...browser,
@@ -1104,7 +1107,7 @@ export function appShowcase(override?: UserConfig): UserConfig {
 		browser: `export function setupBrowser(override?: UserConfig): UserConfig {
 	const project: UserConfig = {
 		resolve,
-		test: {
+{{plugins}}		test: {
 			name: { label: 'setup:browser', color: 'blue' },
 			include: ['tests/setupBrowser.test.ts'],
 			setupFiles: ['./tests/setup.ts', './tests/setupBrowser.ts'],
@@ -5283,7 +5286,7 @@ function blueprintToRootVite(blueprint) {
 		projects.push("setup");
 	}
 	if (blueprint.setup.includes("browser")) {
-		factories.push(CONFIG_TEMPLATES.factories.browser);
+		factories.push((0, _orkestrel_template.fillTemplate)(CONFIG_TEMPLATES.factories.browser, { plugins: machinery.vue ? "		plugins: [vue()],\n" : "" }));
 		projects.push("setupBrowser");
 	}
 	if (blueprint.guides) {