Update stale roadmap references after Doctor v2 and Go/Rust profile completion

[baskduf]

Summary

ROADMAP.md still describes several completed items as future work. Doctor v2, the Go profile, and the Rust profile have all shipped, but the roadmap still says to finish or add them.

Priority: P2

Evidence

• ROADMAP.md still says to finish the Harness Doctor v2 coupling-diagnostic transition.
• ROADMAP.md describes Doctor v2 as future work with wording like Harness Doctor should evolve and The first implementation should....
• docs/decisions/0007-harness-doctor-six-element-coupling-diagnostic.md records the accepted Doctor v2 decision.
• CHANGELOG.md records Doctor v2 as shipped in v0.1.10.
• ROADMAP.md still lists Go and Rust as candidate profiles.
• docs/profiles.md lists go and rust as available profiles, and merged work has already added their fixtures/smoke coverage.

Why this matters

The roadmap is used to prioritize future harness work. Stale completed items make it harder for contributors to identify the next real gaps and can lead to duplicate work or confused issue scoping.

Expected behavior

The roadmap should distinguish completed work from next-step refinement work. Doctor v2 should be framed as implemented and awaiting refinement from real target use, while Go and Rust should be removed from the candidate profile list.

Suggested fix

• Rewrite the Doctor v2 roadmap section as post-implementation refinement work.
• Update the recommended order if Doctor v2 transition is no longer the first blocker.
• Remove Go and Rust from candidate profiles, or move them to a completed-profile note.
• Keep future candidates such as Rails, Laravel, and iOS where appropriate.

Duplicate check

Searched existing issues for roadmap Doctor v2 Go Rust; no duplicate issue was found.