Canonicalize export redaction labels

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

@@ -145,6 +145,10 @@ That export decision must come from the shared unified-resource privacy
 helpers, so sensitivity floors and redaction-triggered routing stay aligned
 with the canonical policy contract instead of being recomputed in AI-local
 code.
+The export audit should also record canonical human-readable redaction labels
+from the shared policy presentation helper, so the audit trail and the
+resource-context surfaces speak the same governed redaction language instead
+of reformatting hint names locally.
 The same AI runtime boundary now also consumes the canonical unified-resource
 timeline when it assembles rich resource or incident context. Recent-change
 context should come from the shared resource store first so AI prompts reflect

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

@@ -448,6 +448,10 @@ Shared privacy helpers also own the export sensitivity floor and route
 decision derived from those canonical policy counts, so AI export audits and
 route decisions reuse the same governed boundary logic instead of rebuilding
 it in consumer packages.
+That same export path now records canonical human-readable redaction labels
+through the shared policy presentation helper, so audit records and prompt
+context stay aligned on the same redaction vocabulary instead of duplicating
+hint-to-label conversion in AI-local code.
 The AI runtime now also uses the canonical policy presentation helpers to
 surface those routing and redaction labels in shared context output, so the
 same policy model is reflected in prompt summaries instead of being