Centralize resource display naming

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

@@ -156,6 +156,9 @@ at each resolved mention site rather than going through an AI-local wrapper.
 Chat knowledge extraction and resource-context rendering now also consume the
 shared unified-resource label helpers directly, so governed labels and
 redacted values stay consistent without AI-local presentation shims.
+Those same paths also use the shared resource display-name helper, so the
+name-or-ID fallback stays aligned across chat extraction, resource context,
+and unified adapter presentation.
 That shared presentation layer also owns the elapsed-time and "ago" wording
 utilities, so the same "time ago" phrasing stays consistent across resource,
 incident, and fallback memory summaries instead of being reformatted

docs/release-control/v6/internal/subsystems/unified-resources.md

@@ -192,6 +192,9 @@ shared unified-resource contract, and their governed labels now flow through
 shared `ResourcePolicyLabel(...)` and `ResourcePolicyRedactedValue(...)`
 helpers instead of through AI-local presentation shims, so policy copying and
 policy-bound labels both stay centralized in the resource model.
+That same contract also owns the canonical resource display-name fallback, so
+name-or-ID presentation stays consistent between the unified AI adapter and
+the AI resource context instead of being recomputed locally.
 
 That same shared store now also persists append-only action lifecycle, action
 audit, and export audit records, giving the control-plane verbs a durable home