Docs: convert roadmap to non-dated capability progression and tidy compliance TOC anchors

[Shards-inc]

Motivation

• Remove explicit calendar dates and timeline claims from the roadmap to avoid unsupported scheduling assertions and to present a capability-based progression.
• Improve clarity of headings and anchors in the compliance mapping document for more precise references.

Description

• Replace the roadmap Last Updated date with a non-dated Capability progression (non-dated) label and rename Release Timeline to Capability Progression.
• Convert the ASCII timeline from quarter-based dates to phase-based labels and change timeline fields (e.g., Timeline → Progression Slot) and milestone dates to ordinal sequencing language.
• Rename several roadmap section headings for clarity (e.g., Changelog → Methodology, 2026 and Beyond → Long Horizon) and replace dated revision rows with neutral numbered entries.
• Adjust docs/COMPLIANCE_MAPPING.md table-of-contents anchor labels for clearer, longer anchor names.

Testing

• No automated tests were required because this is a documentation-only change.
• Repository CI was not modified by this PR and no code tests were run as part of these edits.

---

Codex Task

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.