Refresh RC5 packet validation range for plain-JSON tool-call sanitisation

docs/releases/RELEASE_NOTES_v6_RC5_DRAFT.md

@@ -38,15 +38,16 @@ work into a retestable v6 candidate:
   Proxmox VE, PBS, PMG, and Unraid agent hosts
 - a sizable alerts-manager refactor (decomposition only, no API change)
 
-This packet was audited against `426` commits in the exact code-backed
+This packet was audited against `428` commits in the exact code-backed
 `rc.4` to `rc.5` pre-publication validation range, from the published
 `v6.0.0-rc.4` tag commit `4aa91f6af37be08c93ff19e44f307735d1b9cb70` through
-validation-risk commit `52416cec6fdb42c0bf753d52ad870f4dfede5e1e`. That
-range covers 687 files changed, 84642 insertions, 16632 deletions, and
+validation-risk commit `e36945741e1db5d763ab63eeeda18a58acda23c5`. That
+range covers 694 files changed, 85715 insertions, 16639 deletions, and
 includes the agent-substrate, Patrol intelligence, operator-state,
 action-governance, AI reporting, availability-probe, accessibility,
 DeepSeek V4, platform-identity, and alerts-decomposition work, plus the
-RC5 packet and release-validation commits.
+RC5 packet and release-validation commits including the plain-JSON
+tool-call sanitisation for weak local models.
 
 ## Support Stance
 

docs/releases/V6_CHANGELOG_RC5_DRAFT.md

@@ -25,10 +25,10 @@ The changelog was audited against every feature/runtime commit in the exact
 code-backed release-validation range for the current candidate:
 
 - `v6.0.0-rc.4`: `4aa91f6af37be08c93ff19e44f307735d1b9cb70`
-- validation-risk commit: `52416cec6fdb42c0bf753d52ad870f4dfede5e1e`
-- range: `v6.0.0-rc.4..52416cec6fdb42c0bf753d52ad870f4dfede5e1e`
-- commit count: `426`
-- changed scope: `687` files, `84642` insertions, `16632` deletions
+- validation-risk commit: `e36945741e1db5d763ab63eeeda18a58acda23c5`
+- range: `v6.0.0-rc.4..e36945741e1db5d763ab63eeeda18a58acda23c5`
+- commit count: `428`
+- changed scope: `694` files, `85715` insertions, `16639` deletions
 
 Those commits are grouped in this changelog rather than listed one by one.
 The range carries: the agent-substrate HTTP contract and `cmd/pulse-mcp` /
@@ -267,6 +267,13 @@ public alerts API is unchanged.
 - SSHSIG is verified on in-app update artifacts
 - patrol-main session bounded at 200 messages to stop unbounded disk growth
 - AGENT-side update signer trust migration guidance carries through
+- weak local Ollama models (qwen2.5:11b, qwen2.5:14b, similar) that emit
+  Pulse tool invocations as plain JSON inside content instead of through
+  the structured `tool_calls` channel are now sanitised by extending
+  `cleanToolCallArtifacts` and `containsToolCallMarker` with a registry-
+  sourced canonical-tool allowlist pass; users no longer see raw
+  `{"name": "pulse_query", ...}` payloads as the assistant's final
+  response
 
 ## What existing v5 users should re-test in `rc.5`
 

scripts/release_control/render_release_body_test.py

@@ -180,8 +180,8 @@ Old metadata section.
             repo_root / "docs/releases/V6_RC5_OPERATOR_SUPPORT_PACK_DRAFT.md"
         ).read_text(encoding="utf-8")
 
-        self.assertIn("52416cec6fdb42c0bf753d52ad870f4dfede5e1e", release_notes)
-        self.assertIn("commit count: `426`", changelog)
+        self.assertIn("e36945741e1db5d763ab63eeeda18a58acda23c5", release_notes)
+        self.assertIn("commit count: `428`", changelog)
         self.assertIn("agent-substrate HTTP contract", release_notes)
         self.assertIn("/api/agent/capabilities", changelog)
         self.assertIn("Pulse Intelligence", support_pack)