Record round 14: audit-core 5f3d01c8 pin reviewed by all five owners.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 236506@bnt-lap001
Assistant-Session: 09087018-91e1-48c5-ab2f-acfbb62c92e4

workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md

@@ -623,3 +623,13 @@ readiness, the accept/duplicate path and lease/readiness behaviour are
 unchanged. The scope-file `secret_policy` tightening and the independent-reader
 reconciliation do not touch the reviewed procedures. The founder posts the
 hash-bound receipts with the usual `approve` loop under `AUDIT_KUBECONFIG`.
+
+Round 14 (contract `950f54af`, base `edc6bf4`). The round-13 approvals could
+not be posted: audit-core released again minutes later (`4fcf7c6`,
+AUDIT-WP-0018-T03, receiver `sha256:5f3d01c8…` built from `2b8c909`). The
+preflight pins that release. All five owners approve. audit-core diffed
+`8185893..2b8c909`: one read-only stream-finding kind and an optional
+`closing_classes` registry field (only on `nk-bounded-executor`). Health and
+readiness, accept/duplicate, lease/readiness and migrations are unchanged. Each
+audit-core release breaks this exact-digest pin and costs an owner round; that
+recurring cost is a known limitation.