@orkestrel/scaffold 0.0.26 → 0.0.28

package/dist/src/core/index.d.cts

@@ -104,7 +104,7 @@ export declare const ARTIFACT_TEMPLATES: Readonly<{
         readme: "# Guides\n\n## By concept\n\n- Package\n  - Spec: Not created. Create this file when the workspace has a public surface:\n    `guides/{{guide}}.md`\n  - Source:\n{{source}}\n  - Tests:\n{{tests}}\n\n## By directory\n\n{{directories}}\n";
     }>;
     orchestration: Readonly<{
-        service: "#!/usr/bin/env sh\nset -eu\n\nprintf '%s\\n' \\\n{{services}}\n";
+        service: "#!/usr/bin/env sh\nset -eu\n\nprintf '%s\\n' \\\n{{vendors}}\n";
     }>;
 }>;
 
@@ -235,14 +235,22 @@ export declare const BIN_ENTRY_PATH = "src/bin/main.ts";
  * application-only, and mixed workspaces are all first class. `dependencies`
  * and `peers` are runtime `@orkestrel/*` packages; `extras` are
  * package-specific development dependencies and may carry any valid npm name.
- * `bin`, `integration`, `services`, `global`, and `showcase` are structural
- * facts: each is set only when the workspace physically ships the directory or
- * exact-case file that defines it, never because of the workspace's name and
- * never because a sibling fact is set. An axis-dependent fact projects nothing
- * when its required axis is absent: `integration` projects only a published
- * `src`, and `showcase` projects only a browser `app`. The gate answers that case
- * with a non-blocking question, so a caller that set the flag learns it emitted
- * nothing and the compile still completes.
+ * `bin`, `integration`, `conformance`, `service`, `vendors`, `global`, and
+ * `showcase` are structural facts: each is set only when the workspace
+ * physically ships the directory or exact-case file that defines it, never
+ * because of the workspace's name and never because a sibling fact is set. An
+ * axis-dependent fact projects nothing when its required axis is absent:
+ * `integration` projects only a published `src`, and `showcase` projects only a
+ * browser `app`. The gate answers that case with a non-blocking question, so a
+ * caller that set the flag learns it emitted nothing and the compile still
+ * completes.
+ *
+ * `service` says the workspace runs a live-service Vitest project over
+ * `tests/service`, and it alone registers that project. `vendors` names each
+ * external service the workspace drives and emits the provisioner skeleton that
+ * starts them. Neither is derivable from the other: a workspace may declare
+ * vendors before it writes a suite, and a suite may drive a service the skeleton
+ * does not start.
  */
 export declare interface Blueprint {
     readonly name: string;
@@ -258,7 +266,9 @@ export declare interface Blueprint {
     readonly overrides: readonly Override[];
     readonly bin: boolean;
     readonly integration: boolean;
-    readonly services: readonly string[];
+    readonly conformance: boolean;
+    readonly service: boolean;
+    readonly vendors: readonly string[];
     readonly global: boolean;
     readonly showcase: boolean;
 }
@@ -401,10 +411,10 @@ export declare function blueprintToManifest(blueprint: Blueprint): string;
  * Compile the blueprint-dependent orchestration artifacts.
  *
  * @param blueprint - The workspace specification.
- * @returns A service inventory script when services are declared, otherwise none.
+ * @returns A vendor inventory script when vendors are declared, otherwise none.
  *
  * @remarks
- * A service name does not describe startup, readiness, or cleanup. The script
+ * A vendor name does not describe startup, readiness, or cleanup. The script
  * therefore records only the declared inventory and does not invent a service
  * runner or test project.
  */
@@ -499,8 +509,14 @@ export declare function blueprintToRootVite(blueprint: Blueprint): string;
  * to the axes the blueprint declares: a check and a test script per declared
  * environment, an aggregate over each axis, the policy and configuration
  * proofs every workspace can pass before it has a public API, and one build per
- * target that actually builds. The isolated installed-package integration
- * proof stays out of `test` and runs from `prepublishOnly` instead.
+ * target that actually builds.
+ *
+ * A proof leaves `test` when a real service or a real install answers it. The
+ * installed-package integration proof and the live-service proof therefore run
+ * from `prepublishOnly` instead. The conformance proof stays in `test`, because
+ * it measures this package against official tooling and drives nothing external:
+ * a conformance run may start a server, but it starts its own and reaches it
+ * over loopback, so the run stays hermetic.
  *
  * The configuration paths interpolated here are the same ones `SRC_MATRIX` and
  * `APP_MATRIX` list as each environment's configuration files, so a rename in
@@ -556,6 +572,12 @@ export declare function blueprintToSourceArtifacts(blueprint: Blueprint): readon
  * workspace and therefore follows the `src` axis as well as its structural
  * flag.
  *
+ * The conformance proof is not emitted either, for the reason the guide proof
+ * is not: it names an official artifact only the package knows, so a generated
+ * placeholder would read as a proof while measuring nothing. `service` emits its
+ * readiness setup alone, because the root configuration names that module by
+ * path.
+ *
  * @example
  * ```ts
  * import { blueprintToTestArtifacts, createBlueprint } from '@orkestrel/scaffold'
@@ -609,19 +631,61 @@ export declare const CATALOG_AGENT_PATH = ".claude/agents/orkestrel.md";
  * still a row: dropping it would hide a package the organization publishes
  * behind one failed request, and inventing a version would state something
  * upstream never said.
+ *
+ * `dependencies` are the RUNTIME edges the published version declares, which is
+ * what a publish order is computed over: a runtime bump obliges every dependent
+ * to re-pin and republish, while a development bump obliges nothing beyond the
+ * repository that declares it. No layer is recorded here, because a layer is a
+ * deterministic function of these edges across the whole catalog — a stored one
+ * could only disagree with the rows it was derived from. Read it through
+ * {@link catalogToLayers}.
  */
 export declare type CatalogEntry = {
     readonly name: string;
     readonly lookup: 'found';
     readonly version: string;
+    readonly dependencies: readonly Dependency[];
     readonly note?: never;
 } | {
     readonly name: string;
     readonly lookup: 'missing' | 'failed';
     readonly note: string;
     readonly version?: never;
+    readonly dependencies?: never;
 };
 
+/**
+ * Project a catalog into the layers it publishes in.
+ *
+ * @param entries - The catalog rows to order.
+ * @returns One layer per round, each holding the names publishable together,
+ * sorted within the layer; a name whose edges never resolve is omitted.
+ *
+ * @remarks
+ * A layer is a deterministic function of the catalog's own edges, so it is
+ * computed here rather than stored on a row that could disagree with them.
+ * Only RUNTIME edges between catalogued packages count: a development
+ * dependency reaches no consumer, so it constrains nothing about publish order,
+ * and an edge leaving the fleet is a package this catalog does not publish.
+ *
+ * The order matters because these packages are `0.0.x`, where a caret pins one
+ * exact release. Publishing a dependent before its dependency leaves the
+ * dependent pinned to the older release, and two ranges that disagree install
+ * two copies of one package that the compiler reads as two distinct types.
+ *
+ * A cycle cannot be published in rounds, so its members are omitted rather than
+ * placed in an order that would be wrong. An absent name is the report: compare
+ * the returned names against the catalog to find one.
+ *
+ * @example
+ * ```ts
+ * import { catalogToLayers } from '@orkestrel/scaffold'
+ *
+ * catalogToLayers(entries)[0] // the names that depend on nothing in the fleet
+ * ```
+ */
+export declare function catalogToLayers(entries: readonly CatalogEntry[]): ReadonlyArray<readonly string[]>;
+
 /**
  * Snapshot an untrusted value into exact JSON data the caller owns.
  *
@@ -979,6 +1043,8 @@ export declare class Compiler implements CompilerInterface {
               policy: "export const policy = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'policy', color: 'white' },\n\t\t\t\tinclude: ['tests/policy.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               config: "export const config = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'config', color: 'yellow' },\n\t\t\t\tinclude: ['tests/config.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               guides: "export const guides = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'guides', color: 'green' },\n\t\t\t\tinclude: ['tests/guides.test.ts'],\n\t\t\t\texclude: ['tests/src/**/*.test.ts', 'tests/app/**/*.test.ts', 'tests/setup.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
+              conformance: "// Where this package drifts from the official tooling it stays compatible with.\n// The subject is this package, so the proof is hermetic and stays in `npm test`.\nexport const conformance = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'conformance', color: 'magenta' },\n\t\t\t\tinclude: ['tests/conformance.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
+              service: "// The live external services this package drives. It starts nothing itself:\n// `scripts/service.sh` provisions, `tests/setupService.ts` proves readiness, and\n// the project stays out of `npm test` because a real service answers it.\nexport const service = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'service', color: 'red' },\n\t\t\t\tinclude: ['tests/service/**/*.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts', './tests/setupService.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t\ttestTimeout: 120_000,\n\t\t\t\thookTimeout: 120_000,\n\t\t\t\tfileParallelism: false,\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               probe: "// A workbench, not a proof. No gate selects this project.\nexport const probe = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'probe', color: 'gray' },\n\t\t\t\tinclude: ['tmp/probe/**/*.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               integration: "export const integration = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'integration', color: 'blue' },\n\t\t\t\tinclude: ['tests/integration.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n{{global}}\t\t\t\tenvironment: 'node',\n\t\t\t\ttestTimeout: 120_000,\n\t\t\t\thookTimeout: 120_000,\n\t\t\t\tfileParallelism: false,\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
           }>;
@@ -1010,6 +1076,9 @@ export declare class Compiler implements CompilerInterface {
           }>;
       }>;
 
+      /** The official-tooling drift proof whose presence makes a workspace `conformance`. */
+      export declare const CONFORMANCE_TEST_PATH = "tests/conformance.test.ts";
+
       /** A text file produced by the template or computed compilation path. */
       export declare interface ContentArtifact extends ArtifactBase {
           readonly origin: 'template' | 'computed';
@@ -1052,8 +1121,8 @@ export declare class Compiler implements CompilerInterface {
            * blueprint.
            *
            * @remarks
-           * A blueprint is a closed record of sixteen fields, and most of them have one
-           * sensible starting value: an empty list, a cleared flag, `DEFAULT_VERSION`, and
+           * A blueprint is a closed record, and most of its fields have one sensible
+           * starting value: an empty list, a cleared flag, `DEFAULT_VERSION`, and
            * `DEFAULT_ENGINES`. Filling them here is what lets a caller state only what its
            * workspace actually declares.
            *
@@ -2546,6 +2615,12 @@ export declare class Compiler implements CompilerInterface {
         /** The provisioner skeleton a workspace with declared service vendors is given once. */
         export declare const SERVICE_SCRIPT_PATH = "scripts/service.sh";
 
+        /** The live-service readiness module whose presence makes a workspace `service`. */
+        export declare const SERVICE_SETUP_PATH = "tests/setupService.ts";
+
+        /** The include the live-service project covers, which is a directory rather than one proof. */
+        export declare const SERVICE_TEST_INCLUDE = "tests/service/**/*.test.ts";
+
         /** The Vite wrapper whose presence makes a workspace `showcase`. */
         export declare const SHOWCASE_CONFIG_PATH = "configs/app/vite.showcase.config.ts";
 

package/dist/src/core/index.d.ts

@@ -104,7 +104,7 @@ export declare const ARTIFACT_TEMPLATES: Readonly<{
         readme: "# Guides\n\n## By concept\n\n- Package\n  - Spec: Not created. Create this file when the workspace has a public surface:\n    `guides/{{guide}}.md`\n  - Source:\n{{source}}\n  - Tests:\n{{tests}}\n\n## By directory\n\n{{directories}}\n";
     }>;
     orchestration: Readonly<{
-        service: "#!/usr/bin/env sh\nset -eu\n\nprintf '%s\\n' \\\n{{services}}\n";
+        service: "#!/usr/bin/env sh\nset -eu\n\nprintf '%s\\n' \\\n{{vendors}}\n";
     }>;
 }>;
 
@@ -235,14 +235,22 @@ export declare const BIN_ENTRY_PATH = "src/bin/main.ts";
  * application-only, and mixed workspaces are all first class. `dependencies`
  * and `peers` are runtime `@orkestrel/*` packages; `extras` are
  * package-specific development dependencies and may carry any valid npm name.
- * `bin`, `integration`, `services`, `global`, and `showcase` are structural
- * facts: each is set only when the workspace physically ships the directory or
- * exact-case file that defines it, never because of the workspace's name and
- * never because a sibling fact is set. An axis-dependent fact projects nothing
- * when its required axis is absent: `integration` projects only a published
- * `src`, and `showcase` projects only a browser `app`. The gate answers that case
- * with a non-blocking question, so a caller that set the flag learns it emitted
- * nothing and the compile still completes.
+ * `bin`, `integration`, `conformance`, `service`, `vendors`, `global`, and
+ * `showcase` are structural facts: each is set only when the workspace
+ * physically ships the directory or exact-case file that defines it, never
+ * because of the workspace's name and never because a sibling fact is set. An
+ * axis-dependent fact projects nothing when its required axis is absent:
+ * `integration` projects only a published `src`, and `showcase` projects only a
+ * browser `app`. The gate answers that case with a non-blocking question, so a
+ * caller that set the flag learns it emitted nothing and the compile still
+ * completes.
+ *
+ * `service` says the workspace runs a live-service Vitest project over
+ * `tests/service`, and it alone registers that project. `vendors` names each
+ * external service the workspace drives and emits the provisioner skeleton that
+ * starts them. Neither is derivable from the other: a workspace may declare
+ * vendors before it writes a suite, and a suite may drive a service the skeleton
+ * does not start.
  */
 export declare interface Blueprint {
     readonly name: string;
@@ -258,7 +266,9 @@ export declare interface Blueprint {
     readonly overrides: readonly Override[];
     readonly bin: boolean;
     readonly integration: boolean;
-    readonly services: readonly string[];
+    readonly conformance: boolean;
+    readonly service: boolean;
+    readonly vendors: readonly string[];
     readonly global: boolean;
     readonly showcase: boolean;
 }
@@ -401,10 +411,10 @@ export declare function blueprintToManifest(blueprint: Blueprint): string;
  * Compile the blueprint-dependent orchestration artifacts.
  *
  * @param blueprint - The workspace specification.
- * @returns A service inventory script when services are declared, otherwise none.
+ * @returns A vendor inventory script when vendors are declared, otherwise none.
  *
  * @remarks
- * A service name does not describe startup, readiness, or cleanup. The script
+ * A vendor name does not describe startup, readiness, or cleanup. The script
  * therefore records only the declared inventory and does not invent a service
  * runner or test project.
  */
@@ -499,8 +509,14 @@ export declare function blueprintToRootVite(blueprint: Blueprint): string;
  * to the axes the blueprint declares: a check and a test script per declared
  * environment, an aggregate over each axis, the policy and configuration
  * proofs every workspace can pass before it has a public API, and one build per
- * target that actually builds. The isolated installed-package integration
- * proof stays out of `test` and runs from `prepublishOnly` instead.
+ * target that actually builds.
+ *
+ * A proof leaves `test` when a real service or a real install answers it. The
+ * installed-package integration proof and the live-service proof therefore run
+ * from `prepublishOnly` instead. The conformance proof stays in `test`, because
+ * it measures this package against official tooling and drives nothing external:
+ * a conformance run may start a server, but it starts its own and reaches it
+ * over loopback, so the run stays hermetic.
  *
  * The configuration paths interpolated here are the same ones `SRC_MATRIX` and
  * `APP_MATRIX` list as each environment's configuration files, so a rename in
@@ -556,6 +572,12 @@ export declare function blueprintToSourceArtifacts(blueprint: Blueprint): readon
  * workspace and therefore follows the `src` axis as well as its structural
  * flag.
  *
+ * The conformance proof is not emitted either, for the reason the guide proof
+ * is not: it names an official artifact only the package knows, so a generated
+ * placeholder would read as a proof while measuring nothing. `service` emits its
+ * readiness setup alone, because the root configuration names that module by
+ * path.
+ *
  * @example
  * ```ts
  * import { blueprintToTestArtifacts, createBlueprint } from '@orkestrel/scaffold'
@@ -609,19 +631,61 @@ export declare const CATALOG_AGENT_PATH = ".claude/agents/orkestrel.md";
  * still a row: dropping it would hide a package the organization publishes
  * behind one failed request, and inventing a version would state something
  * upstream never said.
+ *
+ * `dependencies` are the RUNTIME edges the published version declares, which is
+ * what a publish order is computed over: a runtime bump obliges every dependent
+ * to re-pin and republish, while a development bump obliges nothing beyond the
+ * repository that declares it. No layer is recorded here, because a layer is a
+ * deterministic function of these edges across the whole catalog — a stored one
+ * could only disagree with the rows it was derived from. Read it through
+ * {@link catalogToLayers}.
  */
 export declare type CatalogEntry = {
     readonly name: string;
     readonly lookup: 'found';
     readonly version: string;
+    readonly dependencies: readonly Dependency[];
     readonly note?: never;
 } | {
     readonly name: string;
     readonly lookup: 'missing' | 'failed';
     readonly note: string;
     readonly version?: never;
+    readonly dependencies?: never;
 };
 
+/**
+ * Project a catalog into the layers it publishes in.
+ *
+ * @param entries - The catalog rows to order.
+ * @returns One layer per round, each holding the names publishable together,
+ * sorted within the layer; a name whose edges never resolve is omitted.
+ *
+ * @remarks
+ * A layer is a deterministic function of the catalog's own edges, so it is
+ * computed here rather than stored on a row that could disagree with them.
+ * Only RUNTIME edges between catalogued packages count: a development
+ * dependency reaches no consumer, so it constrains nothing about publish order,
+ * and an edge leaving the fleet is a package this catalog does not publish.
+ *
+ * The order matters because these packages are `0.0.x`, where a caret pins one
+ * exact release. Publishing a dependent before its dependency leaves the
+ * dependent pinned to the older release, and two ranges that disagree install
+ * two copies of one package that the compiler reads as two distinct types.
+ *
+ * A cycle cannot be published in rounds, so its members are omitted rather than
+ * placed in an order that would be wrong. An absent name is the report: compare
+ * the returned names against the catalog to find one.
+ *
+ * @example
+ * ```ts
+ * import { catalogToLayers } from '@orkestrel/scaffold'
+ *
+ * catalogToLayers(entries)[0] // the names that depend on nothing in the fleet
+ * ```
+ */
+export declare function catalogToLayers(entries: readonly CatalogEntry[]): ReadonlyArray<readonly string[]>;
+
 /**
  * Snapshot an untrusted value into exact JSON data the caller owns.
  *
@@ -979,6 +1043,8 @@ export declare class Compiler implements CompilerInterface {
               policy: "export const policy = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'policy', color: 'white' },\n\t\t\t\tinclude: ['tests/policy.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               config: "export const config = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'config', color: 'yellow' },\n\t\t\t\tinclude: ['tests/config.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               guides: "export const guides = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'guides', color: 'green' },\n\t\t\t\tinclude: ['tests/guides.test.ts'],\n\t\t\t\texclude: ['tests/src/**/*.test.ts', 'tests/app/**/*.test.ts', 'tests/setup.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
+              conformance: "// Where this package drifts from the official tooling it stays compatible with.\n// The subject is this package, so the proof is hermetic and stays in `npm test`.\nexport const conformance = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'conformance', color: 'magenta' },\n\t\t\t\tinclude: ['tests/conformance.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
+              service: "// The live external services this package drives. It starts nothing itself:\n// `scripts/service.sh` provisions, `tests/setupService.ts` proves readiness, and\n// the project stays out of `npm test` because a real service answers it.\nexport const service = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'service', color: 'red' },\n\t\t\t\tinclude: ['tests/service/**/*.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts', './tests/setupService.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t\ttestTimeout: 120_000,\n\t\t\t\thookTimeout: 120_000,\n\t\t\t\tfileParallelism: false,\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               probe: "// A workbench, not a proof. No gate selects this project.\nexport const probe = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'probe', color: 'gray' },\n\t\t\t\tinclude: ['tmp/probe/**/*.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n\t\t\t\tenvironment: 'node',\n\t\t\t\tbrowser: { enabled: false },\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
               integration: "export const integration = (options?: UserConfig): UserConfig =>\n\tmergeConfig(\n\t\t{\n\t\t\tresolve,\n\t\t\ttest: {\n\t\t\t\tname: { label: 'integration', color: 'blue' },\n\t\t\t\tinclude: ['tests/integration.test.ts'],\n\t\t\t\tsetupFiles: ['./tests/setup.ts'],\n{{global}}\t\t\t\tenvironment: 'node',\n\t\t\t\ttestTimeout: 120_000,\n\t\t\t\thookTimeout: 120_000,\n\t\t\t\tfileParallelism: false,\n\t\t\t},\n\t\t},\n\t\toptions ?? {},\n\t)\n";
           }>;
@@ -1010,6 +1076,9 @@ export declare class Compiler implements CompilerInterface {
           }>;
       }>;
 
+      /** The official-tooling drift proof whose presence makes a workspace `conformance`. */
+      export declare const CONFORMANCE_TEST_PATH = "tests/conformance.test.ts";
+
       /** A text file produced by the template or computed compilation path. */
       export declare interface ContentArtifact extends ArtifactBase {
           readonly origin: 'template' | 'computed';
@@ -1052,8 +1121,8 @@ export declare class Compiler implements CompilerInterface {
            * blueprint.
            *
            * @remarks
-           * A blueprint is a closed record of sixteen fields, and most of them have one
-           * sensible starting value: an empty list, a cleared flag, `DEFAULT_VERSION`, and
+           * A blueprint is a closed record, and most of its fields have one sensible
+           * starting value: an empty list, a cleared flag, `DEFAULT_VERSION`, and
            * `DEFAULT_ENGINES`. Filling them here is what lets a caller state only what its
            * workspace actually declares.
            *
@@ -2546,6 +2615,12 @@ export declare class Compiler implements CompilerInterface {
         /** The provisioner skeleton a workspace with declared service vendors is given once. */
         export declare const SERVICE_SCRIPT_PATH = "scripts/service.sh";
 
+        /** The live-service readiness module whose presence makes a workspace `service`. */
+        export declare const SERVICE_SETUP_PATH = "tests/setupService.ts";
+
+        /** The include the live-service project covers, which is a directory rather than one proof. */
+        export declare const SERVICE_TEST_INCLUDE = "tests/service/**/*.test.ts";
+
         /** The Vite wrapper whose presence makes a workspace `showcase`. */
         export declare const SHOWCASE_CONFIG_PATH = "configs/app/vite.showcase.config.ts";