docs: publish the active issue-backed roadmap

[Daniel Meppiel (danielmeppiel)]

document(roadmap): publish the active issue-backed roadmap

TL;DR

Point the repository's roadmap entry points at Project 2304 instead of the closed v0.29.0 milestone. Replace pending-rollout prose with the active planning surface while preserving issue-owned scope approval and milestone-owned release targets.

Note

Bounded scope and merge authorization: maintainer closeout record on #2960. The maintainer confirmed native auto-add is completed. Daily Docs remains disabled pending separate disposal.

Problem (WHY)

• README's two roadmap links still target closed milestone 0.29.0.
• CONTRIBUTING, GOVERNANCE and the development guide still describe rollout as pending, although the maintainer has confirmed completion and authorized publication.
• The setup checklist duplicates the rollout tracker. Keep the operating guidance and link the history instead: "Add what the agent lacks, omit what it knows".

Approach (WHAT)

• Link the active Roadmap and contributor-discovery views directly.
• Replace setup-only prose, retaining the human-approval and release-target boundaries.
• Keep rollout history in [FEATURE] Complete governance rollout and issue-backed contribution eligibility #2960 instead of maintaining a second progress checklist.

Implementation (HOW)

File	Change
README.md	Replace both version-specific roadmap links.
CONTRIBUTING.md	Link active priorities and supported, unassigned contribution opportunities.
GOVERNANCE.md	Identify the active Project, link all four views and remove the obsolete rollout checklist.
Development guide	Replace its pending-rollout statement with the active Roadmap link.

Public Project metadata and discussion #116 were updated separately under the same authorization. The discussion was already closed and locked; both states are preserved.

Trade-offs

• Keep one issue-backed Project rather than publish another roadmap document or a version-specific link that will expire.
• Docs-only change: no runtime behavior, scenario-test mapping, changelog entry or architecture diagram is needed. Daily Docs file removal and unrelated backlog decisions remain outside this PR.

Benefits

1. Both README roadmap links reach current priorities.
2. Contributor entry points expose the active Roadmap and Ready to contribute views.
3. No pending-rollout wording or v0.29 roadmap pointer remains in these entry points.

Validation

Canonical pre-push lint and architecture/auth checks passed against current main; all four changed files are documentation.

uv run --extra dev ruff check src/ tests/ scripts/lint_architecture_boundaries.py scripts/architecture_linter/:

All checks passed!

uv run --extra dev ruff format --check src/ tests/ scripts/lint_architecture_boundaries.py scripts/architecture_linter/:

1866 files already formatted

YAML I/O, portable-path and file-length guards:

YAML I/O, portable-path and file-length guards passed

npm --prefix docs run test:links:

ℹ tests 14
ℹ suites 0
ℹ pass 14
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0

Warning

Local full docs build remains unverified: Astro was missing, and restoring dependencies failed because the configured package feed returned HTTP 404 for astro-7.3.2.tgz. No dependency manifest or lockfile is changed. Hosted docs and required checks must pass before merge.

How to test

• Follow both README Roadmap links; confirm Project 2304 opens on Now / Next / Later.
• Follow the four GOVERNANCE view links and the CONTRIBUTING discovery links; confirm their names and filters match the prose.
• Confirm human issue-scope approval remains distinct from Project placement and release targets.
• Confirm hosted docs build and required checks pass; merge before closing [FEATURE] Complete governance rollout and issue-backed contribution eligibility #2960.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[Daniel Meppiel (danielmeppiel)]

Docs sync advisory

Verdict: no_change * Pages affected: 0 additional * LLM calls: 1/15 * Took: not measured

Summary

No additional documentation changes are needed. All four changed files match the index’s documentation-only paths; no runtime user-surface path changed. The contribution-guide pointer is already updated in this PR. No new page or TOC change is needed.

How this advisory was produced

L0 deterministic path classification against .apm/docs-index.yml, checked against the live PR file list and validated with the Draft 7 classifier schema. The attempted classifier persona could not access its tools, so classification was completed locally without another model call. No downstream panel or CDO redraft was needed. This advisory does not grant scope approval or code-review approval.

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved review issues remain.

Review tier: Lite
Findings: None

What changed in this PR

This documentation-only PR publishes Project 2304 as the active issue-backed roadmap.

Changes:

• Updates README roadmap links.
• Removes obsolete rollout wording.
• Documents active roadmap views and contributor guidance.

File	Summary
README.md	Points roadmap links to Project 2304.
GOVERNANCE.md	Documents active project settings and views.
docs/​src/​content/​docs/​contributing/​development-guide.md	Links to the active roadmap.
CONTRIBUTING.md	Links current priorities and contribution opportunities.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.