@mstar-harness/engine 3.9.2 → 3.9.4

package/dist/audit.d.ts

@@ -246,16 +246,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;