docs: record dirty source resolution

docs/workflow/develop-workflow-record.md

@@ -2,9 +2,9 @@
 
 ## Status
 
-- Status: blocked
-- Current phase: local integration
-- Next safe action: resolve the pre-existing dirty source-checkout change through an explicit user decision before fast-forward integration.
+- Status: active
+- Current phase: source synchronization
+- Next safe action: commit the exact pre-existing artifact-presenter YAML quoting change separately on `main`, then rebase, reverify, and review the feature again.
 
 ## Request and scope
 
@@ -210,5 +210,6 @@ Rebase the feature branch onto the latest remote/local `main` when available, re
 - Review cycle 2: specification approved; standards requested removal of two dead-code items. Both reviewers remained read-only.
 - Remediation cycle 2: parent removed both items; focused tests, `bun run typecheck`, and `bun run test` exited 0.
 - Review cycle 3: standards and specification approved the exact fingerprint with no findings; both reviewers remained read-only.
-- Integration blocker: primary checkout `main` still contains the pre-existing uncommitted YAML quoting change in `skills/document/artifact-presenter/SKILL.md`. The reviewed feature does not touch that path, but the approved workflow requires a clean source checkout.
-- Next safe action: commit this approval evidence, ask the user to preserve, discard, or leave the source change blocked, then integrate only after the source checkout is clean.
+- Source-checkout decision: on 04SEP2026 the user explicitly chose to preserve the exact pre-existing YAML quoting change in a separate `main` commit. This authorizes only that one-file commit; it does not broaden feature scope.
+- Consequence: after `main` advances, rebase the feature, rerun full verification, regenerate the fingerprint, and obtain fresh independent approval before integration.
+- Next safe action: commit this gate decision, then create the exact separate source commit.