docs(json-yaml): refresh final review state

Remove stale transfer-task wording and record the rebased, fully gated
JSON/YAML provider validation in the framing and handoff.

docs/agent-handoff.md

@@ -329,11 +329,12 @@ byte-accurate multibyte cursor placement in `move_active_cursor_to`
 OPEN** (grammar-gap style, `tree-sitter-json`/`-yaml`; LSP configs
 `vscode-json-language-server` with provider pin
 `@t1ckbase/vscode-langservers-extracted@2.0.2`, plus
-`yaml-language-server`). Review fixes are preserved on
-`json-yaml-handoff-2026-07-20`; the real YAML-through-pmacs smoke,
-rebase, and full gates remain. Once merged, YAML `---` and TOML `+++`
-markdown frontmatter highlight via the #122 engine and the Jupyter
-reader → editable → kernel arc has both grammar prerequisites.
+`yaml-language-server`). The public and checkpoint branches are both at
+fully gated `5c202c5`, rebased onto `f8096ff`; the JSON and YAML
+PATH-gated pmacs smokes both passed, and the PR awaits user review.
+Once merged, YAML `---` and TOML `+++` markdown frontmatter highlight via
+the #122 engine and the Jupyter reader → editable → kernel arc has both
+grammar prerequisites.
 GPU: auto-reconnect after daemon restart, splits/multi-buffer, gutter
 riders (whitespace guides, folding, git markers).
 Themes (full list in theme-faces framing rev 9 "Deferred (named)"):

docs/json-yaml-framing.md

@@ -1,12 +1,11 @@
 # JSON + YAML grammars — framing (side quest, highlight family)
 
-**Revision 3 — 2026-07-20. Status: PR #123 open; review-fix
-checkpoint preserved on branch `json-yaml-handoff-2026-07-20`.**
-The public PR branch still pointed to the original implementation
-`4be2a65` when this checkpoint was created. JSON provider resolution
-and its real pmacs smoke are complete; the YAML 1.24.0 standalone
-protocol smoke and real YAML-through-pmacs acceptance are complete;
-rebase onto current main and full gates remain.
+**Revision 4 — 2026-07-21. Status: PR #123 open and awaiting review;
+the public and checkpoint branches are at fully gated `5c202c5`, rebased
+onto `main` `f8096ff`.**
+The JSON provider and Red Hat YAML 1.24.0 have each passed their
+PATH-gated pmacs acceptance, in addition to the deterministic fake-server
+config-push proof and the YAML standalone protocol smoke.
 
 **Intent.** Add `tree-sitter-json` and `tree-sitter-yaml` grammars (plus
 their language servers) to the bundle. Two config formats that pmacs
@@ -125,10 +124,10 @@ also installed in an isolated prefix and live-smoked over stdio: its
 initial configuration pull was exactly `yaml`, `http`, `[yaml]`,
 `editor`, `files`; opening the document caused a second scoped
 `[yaml]` pull; invalid YAML produced a parser diagnostic; shutdown was
-clean. The remaining gap is the same provider through pmacs.
-Config-push delivery is also proven deterministically through the fake
-server's config sink. Servers activate only if installed; the grammar
-is the always-on value.
+clean. Both providers have also passed their PATH-gated pmacs acceptance.
+Config-push delivery is proven deterministically through the fake server's
+config sink. Servers activate only if installed; the grammar is the
+always-on value.
 
 ### Q#JY3 — Filetype fallback + alias entries
 

tests/m4_acceptance.rs

@@ -6292,10 +6292,8 @@ fn m4_gap_grammars_align_with_lsp_configs() {
 
 /// JSON/YAML LSP configs pin the server commands and the settings shape
 /// each consumes (framing Q#JY2): JSON receives a pushed full object;
-/// YAML pulls five named sections. The pinned JSON provider has a separate
-/// PATH-gated live smoke below. YAML 1.24.0's five-section pull was
-/// observed over a standalone protocol smoke; its PATH-gated pmacs
-/// integration test remains a transfer task. The point is to pin the
+/// YAML pulls five named sections. The pinned JSON and YAML providers each
+/// have a separate PATH-gated live smoke below. The point is to pin the
 /// contract, not merely assert that some settings table exists.
 #[test]
 fn m4_json_yaml_lsp_configs_pin_command_and_sections() {