docs: approve focused lock remediation

docs/workflow/develop-workflow-record.md

@@ -2,9 +2,9 @@
 
 ## Status
 
-- Status: blocked
+- Status: active
-- Current phase: remediation escalation gate
+- Current phase: exceptional focused remediation
-- Next safe action: obtain an explicit user decision on the newly discovered lock-ownership finding before any further remediation.
+- Next safe action: verify lock pathname identity before cleanup, add the replacement-lock regression test, then reverify and obtain fresh independent review.
 
 ## Request and scope
 
@@ -221,5 +221,6 @@ Rebase the feature branch onto the latest remote/local `main` when available, re
 - Rebase result: feature rebased cleanly onto `b4373113a404bb523bef306a66fb8a22fc706223`; focused checkpoint/link tests, `bun run typecheck`, and `bun run test` all exited 0.
 - Post-rebase review brief: product `b4e71b47db4af3455ab665050f51b96c0bed3959`, tree `1efcde6ccbd81063a44c46a3b75b34d50d3af4b0`, digest `3fd063ad1a4591e776ef2a29c26f31482bbcb5329a6541126fd991c72a0d247f`.
 - Post-rebase review outcome: standards approved; specification requested a focused lock-ownership fix. Both reviewers reported unchanged clean Git state.
-- Escalation: two earlier remediation cycles were already consumed. The parent will not start another automatically; explicit user approval is required.
+- Escalation decision: after two earlier remediation cycles, the user explicitly authorized one exceptional focused remediation cycle for this lock-ownership finding.
-- Next safe action: commit this finding evidence and ask whether to authorize one exceptional focused remediation cycle or stop blocked.
+- Approved remediation scope: capture the acquired lock identity, unlink only when the pathname still resolves to that identity, and add a regression test that replaces the pathname during an active checkpoint.
+- Next safe action: commit this gate decision before the parent-owned code mutation.