docs(audit-workspace): rebaseline remaining work to the multi-plane telemetry contract

[wryenmeek]

Summary

The audit-workspace-improve-flow plan now depends on a corrected multi-plane telemetry contract learned from the sibling vscode-genai reset work: VS Code Copilot Chat OTel, Copilot CLI local OTel, and session-history/session-store data are distinct evidence planes with different field coverage.

Today the knowledgebase plan documents friction mining and cross-surface validation as though "telemetry" were one uniform datasource. That framing is now too weak. We need one focused issue that rewrites the remaining datasource assumptions before the remaining HITL validation slices are closed.

Why this issue exists

Open HITL slices such as #196 and #212 still need guidance on:

1. which findings are expected to come from session-history/session-store inputs,
2. which are expected to come from VS Code OTel,
3. which cannot currently be justified from local CLI OTel alone, and
4. how to record datasource provenance in validation artifacts.

Without this rewrite, Phase 4 / Phase 7 work can pass while still mixing incompatible evidence planes.

Acceptance criteria

• Update docs/ideas/audit-workspace-improve-flow.md with an explicit plane matrix for remaining friction-query and validation work
• Define which remaining query families are session-history-backed vs OTel-backed
• Mark any classifier expectations that currently over-assume local CLI OTel richness
• Add datasource-provenance expectations for Phase 7 validation artifacts so CLI and VS Code results are compared as outcome parity, not raw-plane equivalence
• Comment on dependent open HITL issues (Compliance-rate measurement spike (Phase 1.5) (slice 7) #196, QA gate: read-only classifier real-repo + hallucination audit (qa-f) #207, First real-use exercise (Phase 7 validation) — cross-surface set-equivalence (slice 10) #212) with the re-scope guidance

Related

• knowledgebase plan: docs/ideas/audit-workspace-improve-flow.md
• sibling contract reset: wryenmeek/vscode-genai#1631 through #1636
• likely dependent knowledgebase issues: Compliance-rate measurement spike (Phase 1.5) (slice 7) #196, QA gate: read-only classifier real-repo + hallucination audit (qa-f) #207, First real-use exercise (Phase 7 validation) — cross-surface set-equivalence (slice 10) #212