From acb160ecce50ec30b9f8689e7e14210a93a99c66 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Wed, 20 May 2026 07:53:23 -0400 Subject: [PATCH] docs(audit): fix plan reference to existing CachedCallTelemetry message Task 2's spec reviewer flagged that the plan used a non-existent name 'CachedOperationTelemetry' when describing the additively-evolved cached telemetry message. The existing message is 'CachedCallTelemetry'; renaming would violate Commons REQ-COM-5a (additive-only). Plan now reflects the in-place additive evolution and warns against rename. --- docs/plans/2026-05-20-centralized-audit-log.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/plans/2026-05-20-centralized-audit-log.md b/docs/plans/2026-05-20-centralized-audit-log.md index a6becf7..afa71bc 100644 --- a/docs/plans/2026-05-20-centralized-audit-log.md +++ b/docs/plans/2026-05-20-centralized-audit-log.md @@ -203,7 +203,7 @@ Under the Types section, add: **Step 4: Add to `Messages/`** - `AuditTelemetryEnvelope` — gRPC message wrapping a batch of `AuditEvent` rows for telemetry forwarding. -- `CachedOperationTelemetry` — additively-evolved version of the existing SiteCalls telemetry message: now also carries `AuditEvent` content alongside the operational `SiteCalls` upsert fields. Note additive-only evolution rule (per existing project convention). +- `CachedCallTelemetry` — the existing SiteCalls telemetry message, additively extended in place to also carry `AuditEvent` content alongside the operational `SiteCalls` upsert fields. Do NOT rename; per `Component-Commons.md` REQ-COM-5a, message renames are breaking changes. Extend the existing entry's description. **Step 5: Verify**