docs(changelog): fold #892 + #770 into 3.4.1; record #730/#768 deferrals

Jargon baseline +1 artifact_name (legit ROADMAP.md mention in the #892 entry).

Author: jnuyens

CHANGELOG.md

@@ -32,6 +32,10 @@ Background: the plugin previously only auto-wrote memory at planned-phase comple
 - **`agents/` (14 agents)** (upstream #771, `3aed0282`): `color:` frontmatter values changed from hex/`magenta` to the 8 documented Claude Code named colors, so per-agent TUI coloring actually renders.
 - **`agents/gsd-verifier.md`** (upstream #25, `ad1203f9`): Step 7b now proves a test EXISTS by enumeration (`--list` / `--collect-only`) and one PASSES by name, and forbids more than one full-suite run per verification, stopping the cross-language full-suite re-runs (`cargo`/`pytest`/`go`) that wasted minutes per must-have.
 - **`workflows/plan-phase.md`** (upstream #913, `bb27263d`): adds a `<runtime_compatibility>` block (the Agent tool is available top-level; never collapse researcher/planner/checker roles inline; `--chain`/`--auto` suppress prompts only) and relabels all 7 orchestrator-rule markers from `CODEX RUNTIME` to `ALL RUNTIMES`. The `execute-phase` background-dispatch scoping is deferred (it crosses a plugin divergence).
+- **`bin/lib/verify.cjs`** (upstream #892, `fe5c9c05`): `cmdValidateConsistency` and the W006 health check now also match checklist-style roadmap phases (`- [x] **Phase N:**`), not just headings, so a checklist-format ROADMAP no longer false-warns "Phase X exists on disk but not in ROADMAP.md" for every realized phase. Ported as an inline second regex pass (the plugin has no `buildRoadmapPhaseVariants` helper).
+- **`hooks/hooks.json`** (upstream #770, `1b6bd66f`, SubagentStop slice): registers `gsd-context-monitor.js` on the new `SubagentStop` lifecycle event in the plugin's stale-path resolver-shim form, so context-headroom warnings also fire when a subagent finalizes. `Stop`/`PreCompact` were already registered; the `FileChanged` + `gsd-config-reload` slice is deferred.
+
+Two further CC-relevant v1.4.x fixes were evaluated and intentionally deferred: #730 (multi-milestone `extractCurrentMilestone`) is a 97-line rewrite on a divergent, patched `core.cjs` base and needs its own focused task with a two-milestone test fixture; #768 (CC permissions prepopulation) lives in upstream's npm installer with no confirmed plugin-manifest equivalent. The multi-runtime emitters and release/CI infra that dominate the v1.3.1->v1.4.1 delta remain out of scope by design, so `3.4.x` tracks the gsd-core 1.4.x line as a selective cherry-pick, not byte-parity.
 
 ## [2.45.10] - 2026-06-08  (based on upstream GSD 1.42.3, with 5 cherry-picks from upstream v1.3.1)
 

tests/drift-baseline.json

@@ -8,7 +8,7 @@
   },
   "user_docs_jargon": {
     "planning_paths": 38,
-    "artifact_names": 47,
+    "artifact_names": 48,
     "plan_files": 3,
     "generic_phase_num": 17,
     "generated_at": "2026-06-09",