chore: reconcile roadmap claims with verified runtime state

[parthrohit22]

Task

Reconcile the public roadmap and strategy documents with the capabilities that are actually implemented and verified on dev, then publish one canonical version.

Rationale

The latest Phase 0 audit found strategy drift: the v2.1 roadmap describes the evidence store as the system of record even though ingestion still writes the legacy mutable intelligence field and the query/consumer path is not complete. Leaving that claim published makes an unfinished capability look production-ready and undermines the product-honesty gate.

References

• Current roadmap/strategy documents in the repository.
• The Phase 0 audit dated 2026-07-18 (audited dev at 4395e8e1383d56297803302d161feb1d437e9961).
• Related implementation work: feat: add versioned Repository Intelligence snapshot and query endpoints #92, chore: move repository analysis to a durable cancellable job lifecycle #93, chore: deliver evidence-backed authentication architecture explanation #95, security: enforce outbound AI provider egress policy (P0-03) #109, feat: expose tamper-evident revision manifests for evidence-backed explanations #113, and chore: establish clean-clone self-hosted release gate and operational readiness #115.

Implementation Notes

• Diff the roadmap versions and identify claims that are not backed by a shipped API, durable job lifecycle, evidence chain, or verified acceptance test.
• Correct the evidence-store/system-of-record wording and any other overstated Phase 0 status.
• Decide which document is canonical; archive, remove, or clearly mark superseded copies so contributors do not follow conflicting plans.
• Preserve links to the implementation issues and record the owner decision in the canonical document. This issue is documentation/strategy ownership work; it does not implement the evidence store.

Acceptance Criteria

• A single roadmap/strategy document is explicitly marked canonical.
• Every Phase 0 capability claim is traceable to an implemented endpoint/flow and a verification method, or is clearly marked planned/deferred.
• The evidence-store system-of-record claim is corrected until feat: add versioned Repository Intelligence snapshot and query endpoints #92/chore: move repository analysis to a durable cancellable job lifecycle #93/chore: deliver evidence-backed authentication architecture explanation #95/feat: expose tamper-evident revision manifests for evidence-backed explanations #113 provide the required path.
• Superseded documents are archived, removed, or prominently marked with a link to the canonical version.
• A maintainer signs off on the final wording and linked issue status.

Priority: P2 - Medium