@patronage/software-factory 1.0.0-alpha.30 → 1.0.0-alpha.31

package/README.md

@@ -8,7 +8,7 @@ Admission is fail closed. A clean-session review and required verification produ
 
 ## Develop the package
 
-This section and the two below describe the source repository; the paths they mention are not part of the installed npm package. The package lives in the repository pnpm workspace and requires Node 24. From the repository root:
+This section and the two below describe the source repository; the paths they mention are not part of the installed npm package. The package lives in the repository pnpm workspace and requires Node 24.20.0 from `.nvmrc`. Published `engines.node` remains `^24.0.0`. From the repository root:
 
 ```bash
 bash scripts/bootstrap-worktree.sh .
@@ -24,7 +24,7 @@ The package publishes to public npm as `@patronage/software-factory` under MIT.
 
 Internal architectural packages live under `src/packages/`. Read the package root's `README.md` before editing one. Import only entry points explicitly declared by `dependency-cruiser.config.mjs`; package implementation and fixtures are private. See ADR 0007 (`docs/adr/0007-factory-internal-deep-packages-enforce-module-seams.md` in the source repository).
 
-A public export leaves this package only with a named supported-consumer account, under the criteria in that ADR's 2026-09-04 amendment. `api:check` reports declaration drift, and it passes a breaking removal through whenever the version opens a break window, so it is a notice rather than the control. The control is that amendment plus `src/public-consumer-surface.test.ts`, which names every export the audited consumers import and fails when one goes. The amendment also lists the retained surface — the exports that stay without a current importer — and the reason each group stays.
+A public export leaves this package only with the supported-consumer, migration and release account in [ADR 0007](https://github.com/patronage/software-factory/blob/main/software-factory/docs/adr/0007-factory-internal-deep-packages-enforce-module-seams.md#public-export-removals). `api:check` reports declaration drift; an open version break window is not removal approval. `src/public-consumer-surface.test.ts` protects the known consumed exports, while a fresh consumer audit and per-export rationale remain review obligations.
 
 ## Releases
 

package/dist/index.d.ts

@@ -869,7 +869,7 @@ interface CheckoutRepository {
 //#endregion
 //#region src/profile.d.ts
 declare const DEFAULT_FACTORY_REPOSITORY = "unknown/unknown";
-/** The one profile shape this build accepts (ADR 0023, #318, #351, #742). */
+/** The one profile shape this build accepts (ADR 0021, #318, #351, #742). */
 declare const PROFILE_SCHEMA_VERSION = 6;
 declare const factoryProjectProfileSchema: z.ZodObject<{
   $schema: z.ZodOptional<z.ZodString>;
@@ -1309,8 +1309,8 @@ declare const mergeFreezeStateSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
   generationId: z.ZodNumber;
   headSha: z.ZodString;
   outcome: z.ZodEnum<{
-    stale: "stale";
     active: "active";
+    stale: "stale";
   }>;
   reason: z.ZodString;
   recordedAt: z.ZodISODateTime;
@@ -1328,7 +1328,7 @@ declare const mergeFreezeStateSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
 type MergeFreezeState = z.infer<typeof mergeFreezeStateSchema>;
 /**
  * The write side of this contract lives in the generated merge-target push
- * Verify workflow (#356, ADR 0016 as amended; #429): it is the ONLY producer of
+ * Verify workflow (#356, ADR 0016; #429): it is the ONLY producer of
  * `patronage-factory/merge-freeze` generations. Its emitted `output.text`
  * payload must parse under this exact reader schema, which is what the
  * workflow's own tests assert through this export.
@@ -1558,9 +1558,9 @@ declare const managedReadinessLedgerSchema: z.ZodObject<{
       reviewedPatchId: z.ZodOptional<z.ZodString>;
       status: z.ZodEnum<{
         "not-required": "not-required";
+        stale: "stale";
         blocked: "blocked";
         current: "current";
-        stale: "stale";
         missing: "missing";
       }>;
     }, z.core.$strip>;
@@ -1570,9 +1570,9 @@ declare const managedReadinessLedgerSchema: z.ZodObject<{
       reviewedPatchId: z.ZodOptional<z.ZodString>;
       status: z.ZodEnum<{
         "not-required": "not-required";
+        stale: "stale";
         blocked: "blocked";
         current: "current";
-        stale: "stale";
         missing: "missing";
       }>;
     }, z.core.$strip>>;
@@ -1625,7 +1625,7 @@ declare const isFactoryReadyCheck: (check: StatusCheckRollup) => boolean;
  * The hosted verification gate's context name — the branch ruleset's other
  * source-pinned required check, alongside `patronage-factory/pr-ready`. One
  * name across the fleet because one generator emits the workflow that posts
- * it (ADR 0016, 2026-07-31 amendment).
+ * it (ADR 0016).
  */
 declare const HOSTED_VERIFY_CHECK_NAME = "verify";
 /**
@@ -2681,9 +2681,9 @@ declare const loadEvidenceEnvelopes: (cwd: string) => LoadedEvidenceEnvelope[];
 declare const REVIEW_STATUS_VALUES: readonly ["not-required", "current", "stale", "missing", "blocked"];
 declare const reviewStatusSchema: z.ZodEnum<{
   "not-required": "not-required";
+  stale: "stale";
   blocked: "blocked";
   current: "current";
-  stale: "stale";
   missing: "missing";
 }>;
 type ReviewStatus = z.infer<typeof reviewStatusSchema>;
@@ -4510,13 +4510,13 @@ declare const evaluateReadiness: (input: EvaluationInput) => {
     reviews: {
       correctness: {
         required: boolean;
-        status: "not-required" | "blocked" | "current" | "stale" | "missing";
+        status: "not-required" | "stale" | "blocked" | "current" | "missing";
         reviewedHeadSha?: string | undefined;
         reviewedPatchId?: string | undefined;
       };
       security?: {
         required: boolean;
-        status: "not-required" | "blocked" | "current" | "stale" | "missing";
+        status: "not-required" | "stale" | "blocked" | "current" | "missing";
         reviewedHeadSha?: string | undefined;
         reviewedPatchId?: string | undefined;
       } | undefined;
@@ -4664,7 +4664,7 @@ interface CloudflareAccessServiceToken {
 declare const EPIC_STRUCTURE_SCHEMA_VERSION = 1;
 /**
  * DAG-node PLANNING statuses — the planning-plane vocabulary a planner authors
- * on a `dag.yml` node. Carried forward by ADR 0018 §4 and defined by the epic
+ * on a `dag.yml` node. Carried forward by ADR 0018 and defined by the epic
  * skill (`reference/epic-artifacts.md`) and both `CONTEXT.md` glossaries.
  *
  * A DAG node is a unit of *plan*; an HQ lane is a unit of *runtime execution*.