@patronage/factory-ci 1.0.0-alpha.36 → 1.0.0-alpha.37

package/README.md

@@ -14,7 +14,7 @@ It is a **pure library**. There is no `bin`: anything invocable belongs to `psf`
 
 Three repositories independently built the same scaffolding and then drifted: three wordings of the same setup block, the same `@v4` action tags pinned to different commits because they were generated months apart, two esbuild pre-bundles, two Alchemy CLI wrappers, and one disposable-stage grammar invented twice.
 
-The admission rule is **upstream on repetition**: nothing enters this package until it already repeats across at least two projects. Experiments live in one repository first. The public surface is made of four deep modules, not a workflow framework.
+The admission rule is **experiment, prove, fan out** (ADR 0036). A mechanism starts as an experiment in one project. When the experiment proves it and the intent is fleet-wide, it moves into the factory: into this package, or into `psf` when it is invocable. Then it fans out to the other projects. A single consumer is a risk to record, not a gate. The public surface is made of deep modules, not a workflow framework.
 
 ## Exports
 
@@ -684,7 +684,7 @@ const result = await runAlchemyLifecycle({
 });
 ```
 
-`runAlchemyLifecycle` is the one operation over an Alchemy plan, deploy, or destroy. It owns the order; a consumer cannot get the order wrong because it does not call the steps. Paitronage and HQ each reconstructed this sequence from the guards below and got different parts wrong (paitronage#1917), which is the repetition that admits it here.
+`runAlchemyLifecycle` is the one operation over an Alchemy plan, deploy, or destroy. It owns the order; a consumer cannot get the order wrong because it does not call the steps. Paitronage and HQ each reconstructed this sequence from the guards below and got different parts wrong (paitronage#1917), which was the evidence that admitted it here.
 
 The consumer passes typed policy and two capabilities. `state` is the store from `@patronage/alchemy-d1-state`: `snapshotStage`, `get`, and `acquireStageOwnership`, whose lease carries `renew`, `release`, `deleteEmptyStage` and `childEnvironment`, matched structurally, so this package learns no table, account, or SQL. `entry` is what `executeAlchemyEntry` needs minus what the lifecycle decides: the arguments are the lifecycle's, stdio is always piped so the plan can be read, and a `bundle` is built once up front, with every child launched in `cwd`, then the bundle root, then this process's directory — the same chain `executeAlchemyEntry` resolves. A bundle that cannot build is `PREPARATION_FAILED` and nothing else: the bundler's own diagnostics are silenced at the source. There is no `redact` and no echo because there is no sink: each child's captured output is parsed and dropped, written nowhere, so nothing in it can reach a job log or an evidence file through this operation. Every child's environment carries the stage lease; see ownership below.
 

package/dist/.build-fingerprint.json

@@ -1,3 +1,3 @@
 {
-  "fingerprint": "b74ad36f28a800fdec15f84e7711704b2b79305d6207efd55f663040f40fe034"
+  "fingerprint": "d4ebf8af4787cc4426a8c73b8f84098d818fc0f34fab36f6afc21e49e0b619a5"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@patronage/factory-ci",
-  "version": "1.0.0-alpha.36",
+  "version": "1.0.0-alpha.37",
   "description": "Deep CI and deploy building blocks for Patronage factory projects: workflow source artifacts, hosted diff classification, Alchemy entry execution, and disposable-stage semantics",
   "keywords": [
     "alchemy",