docs: update the roadmap

[leandrodamascena]

Update the roadmap.

Closes #732

Changes

replace with a description of the changes

User experience

Please share what the user experience looks like before and after this change

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have reviewed the contributing guidelines
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented

Test Plan

replace with instructions or a checklist for reviewers to verify

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

[apackeer]

Leandro, this PR replaces the stale July roadmap with an August 10 snapshot of
the v2.5.62 branch, including GA status, shipped Copilot support, current
in-flight work, and the longer-term delivery themes. I checked the status and
version claims against the live v2 tip, merge history, open PRs/issues, releases,
and the published documentation site.

Direction: sound. The stale-roadmap problem is real, docs/roadmap.md is the
right authored layer, there is no existing updater being duplicated, and the
one-file scope is proportionate.

I found no blocking issues. Three nonblocking notes:

1. docs/roadmap.md:93 reads like a complete inventory, but several open v2 PRs
   are intentionally absent, including #613, #711, and #729. Calling this
   "Selected open work," or saying the table is selective, would prevent readers
   from treating it as exhaustive.

2. docs/roadmap.md:95 calls the PR references linked, but bare #NNN text is
   not linked by the published Zensical site. Markdown links for the In flight
   and directional references would make the roadmap's evidence easier to
   inspect.

3. The other item reported in #732 remains on the default branch:
   .github/ISSUE_TEMPLATE/documentation.yml:18 still says v2 (alpha).
   This v2-targeted PR cannot fix that template, and its closing keyword will not
   close the issue automatically, so that correction should stay tracked
   separately.

UX-wise this is otherwise a documentation-only improvement: no commands, flags,
prompts, stages, defaults, or runtime behavior change. The revised shipped and
directional status is consistent with the current v2 branch.

[leandrodamascena]

Arden, thanks for the review. I addressed the two roadmap comments in 3f202fd8:

• clarified that the In flight table contains selected open work;
• added direct links for the PR and issue references in In flight and Directional themes.

I left the v2 (alpha) issue-template correction separate, since it is outside this v2-targeted PR.