@mstar-harness/engine 3.9.3 → 3.10.0

package/dist/audit.d.ts

@@ -1,4 +1,5 @@
 import type { GateResult } from "./core.js";
+import { type WorkflowDeliveryKind } from "./workflow.js";
 /** Priority values (mstar-audit SKILL.md § Plan output (all variants) Status block). */
 export declare const AUDIT_PRIORITIES: readonly ["P1", "P2", "P3"];
 export type AuditPriority = (typeof AUDIT_PRIORITIES)[number];
@@ -226,6 +227,20 @@ export type PromoteAuditPlansOptions = {
     harnessDir: string;
     /** Default: basename of `outDir` (e.g. `audit-2026-08-22`). */
     workflowId?: string;
+    /**
+     * Delivery kind declared for the promoted plans (contract §1/§4a). Required —
+     * the promoted lifecycle is a `type: plan` workflow, so its delivery kind is
+     * declared at registration, never inferred and never defaulted in code (an
+     * audit promotion that left it unset minted an active snapshot no close path
+     * could complete).
+     */
+    deliveryKind: WorkflowDeliveryKind;
+    /** Delivery source branch, recorded as `branch.source`. Required for `development`. */
+    branchSource?: string;
+    /** Delivery target branch, recorded as `branch.target`. Required for `development`. */
+    branchTarget?: string;
+    /** Completion policy for `verification/report-only` promotions. Required for that kind. */
+    completionPolicy?: string;
 };
 /**
  * Promote selected audit plans into the v2 workflow lifecycle as a
@@ -246,16 +261,17 @@ export type PromoteAuditPlansOptions = {
  * same root lock `registerWorkflow` uses — so the guard is check-then-act
  * safe: two concurrent same-id promotes cannot both pass it (one writes
  * and registers; the other re-checks under the lock and refuses). The
- * snapshot is written directly with `writeJson` under the root lock (never
- * a nested `writeWorkflowSnapshot` — its own snapshot-dir lock would be a
- * second serialization point; the root lock must be THE serialization
- * point). The root upsert replicates `registerWorkflow` semantics inline
+ * snapshot is written create-only through the routed
+ * `writeWorkflowSnapshot(snapshot, dir, { createOnly: true })`, whose own
+ * snapshot-dir lock nests inside the root lock (root → snapshot is the
+ * documented acquisition order). The root upsert replicates
+ * `registerWorkflow` semantics inline
  * via the shared `registerWorkflowEntryLocked` helper (calling
  * `registerWorkflow` itself would re-enter the non-reentrant root lock).
  *
- * On any failure inside the lock, the partial snapshot + now-empty
- * workflow dir are rolled back so a retry converges after the root
- * conflict is resolved.
+ * On any failure inside the lock, the snapshot this call created (and only
+ * that exact byte version) plus the now-empty workflow dir are rolled back so
+ * a retry converges after the root conflict is resolved.
  */
 export declare function promoteAuditPlans(outDir: string, selected: readonly string[], options: PromoteAuditPlansOptions): Promise<{
     workflowId: string;