docs(handoff): record JSON/YAML review cleanup

Advance the PR #123 recovery heads and verification record after its
documentation-only pre-merge cleanup.

docs/active-work.md

@@ -1,6 +1,6 @@
 # Active work — cross-machine resume ledger
 
-**Snapshot: 2026-07-20.** This file records volatile work that has not
+**Snapshot: 2026-07-21.** This file records volatile work that has not
 landed on `main`. Read it after `docs/agent-handoff.md`. Remove completed
 entries when their PR merges; do not let this become a second permanent
 backlog.
@@ -55,18 +55,18 @@ If it does not, stop and repair the remote/fetch configuration.
 
 - PR: <https://github.com/levineuwirth/pmacs/pull/123>
 - Public PR branch: `githubsucks/json-yaml-grammar`
-- Public PR head: `5c202c5`
+- Public PR head: `ffcb903`
 - Original merge base was `56eb67e`; the completed branch is rebased onto
   canonical main `f8096ff`.
 - Portable checkpoint branch:
   `githubsucks/json-yaml-handoff-2026-07-20`
-- Checkpoint head: `5c202c5`
+- Checkpoint head: `ffcb903`
 - The checkpoint is a continuation branch for recovery, not a second
   feature and not a merge target. Its completed head now exactly matches
   `githubsucks/json-yaml-grammar`.
 
-The checkpoint carries the transferred review-fix set plus the completed
-destination-machine continuation:
+The checkpoint carries the transferred review-fix set, completed
+destination-machine continuation, and final review-documentation cleanup:
 
 - push configured settings via
   `workspace/didChangeConfiguration` immediately after `initialized`;
@@ -133,6 +133,11 @@ Verification completed across the source and destination machines:
   `29778967156` completed successfully for that head: all 12 jobs passed
   (format; LuaJIT/Lua 5.4 lint and Linux/macOS tests; headless GPU; and
   M1/M4/M5/M6 gates).
+- Review cleanup `ffcb903` refreshes the stale YAML transfer-task test
+  comment and the framing/handoff checkpoint status. Its targeted
+  `m4_json_yaml_lsp_configs_pin_command_and_sections`, `cargo fmt --check`,
+  and `git diff --check` verification passed; both public and checkpoint
+  refs were fast-forwarded to it.
 
 Still required:
 

docs/agent-handoff.md

@@ -1,6 +1,7 @@
 # Agent handoff — cross-machine continuity
 
-**Last updated: 2026-07-20, after the cross-machine continuity audit;
+**Last updated: 2026-07-21, after the JSON/YAML review-documentation
+cleanup and the cross-machine continuity audit;
 main still reflects GPU font preferences (#124), themes stage 1 (#120),
 and injections (#122).** This file is the
 bridge between development machines. If you are an agent reading
@@ -140,13 +141,14 @@ commands, read `docs/active-work.md` immediately after this file.
   first built-in provider. Approval → implementation → gates → PR.
   Completing stage 3 completes Arc 4.
 - **OPEN: JSON + YAML PR #123.** Public and checkpoint branches both
-  point to fully gated `5c202c5`, rebased onto `f8096ff`. Review fixes
-  include config push delivery, corrected provider/config claims, and
-  both live-provider paths; the real YAML-through-pmacs smoke proves
+  point to review-cleanup `ffcb903`, atop fully gated `5c202c5` rebased
+  onto `f8096ff`. Review fixes include config push delivery, corrected
+  provider/config claims, both live-provider paths, and the final stale
+  checkpoint-text cleanup; the real YAML-through-pmacs smoke proves
   auto-attach, network-free configuration, diagnostics, and continued
   liveness against Red Hat 1.24.0. CI run `29778967156` passed all 12
-  jobs for the exact public head; awaiting user review. Exact recovery
-  is in `docs/active-work.md`.
+  jobs for `5c202c5`; the doc-only cleanup passed its targeted checks and
+  the PR awaits user review. Exact recovery is in `docs/active-work.md`.
 - **PARKED: kill-ring browser + persistence.** Revision 2 framing is
   preserved on branch `kill-ring-browser`, but its `0efb5cd` scout is
   stale and must be repeated before implementation. No PR or