Centralize memory summary formatting

docs/release-control/v6/internal/subsystems/ai-runtime.md

@@ -159,6 +159,10 @@ The same runtime boundary now also owns durable action execution auditing.
 startup, and the write-action tool paths under `internal/ai/tools/` persist
 append-only action lifecycle and action audit records through that shared
 store instead of leaving command execution state in memory-only tool helpers.
+The patrol-local `memory.ChangeDetector.GetChangesSummary` path now also
+delegates to the shared memory recent-change presentation helper, so any
+future fallback summary entry point inherits the same heading, resource
+prefixing, and change-type labels without re-implementing the markdown shape.
 Those unified-resource action and export audit records are now also exposed
 through the enterprise audit read surface so operators can inspect the
 execution trail without reaching into storage internals.

docs/release-control/v6/internal/subsystems/patrol-intelligence.md

@@ -85,6 +85,9 @@ When that detector fallback is used, the Patrol runtime must render recent
 changes through the shared memory presentation helper so the same heading,
 resource prefixing, and change labels are reused across the Patrol and AI
 fallback paths.
+`memory.ChangeDetector.GetChangesSummary` now also delegates to that shared
+helper, so the detector-owned summary API and the Patrol fallback prompt path
+stay aligned on the same markdown shape.
 Those same Patrol-owned prompt contexts now also surface a canonical
 resource-graph section from unified-resource relationships, so edge labels,
 directionality, and provenance stay aligned with the shared graph model