docs(mvp2): close MVP-2-07 after baseline tag

[Alexendros]

Summary

• Mark MVP-2-07 closed after annotated tag implementation-baseline-mvp2 on 7aa1831.
• Update plan-status, roadmap, backlog and go-no-go to the new baseline.

Test plan

• python3 tools/gates.py Clear
• docs-validate green

---

Note

Low Risk
Documentation and planning-status updates only; no code, auth, or runtime behavior changes.

Overview
Records closure of MVP-2-07 after the annotated tag implementation-baseline-mvp2, aligning governance and delivery docs with the new implementation baseline (prior mvp0.1 / mvp1 tags unchanged).

plan-status.md now names implementation-baseline-mvp2 as the active baseline instead of treating mvp1 as current with mvp2 pending. go-no-go.md, next-issues.md (plan closure rule), and roadmap.md switch from “target / emit when CI green” language to baseline emitted and MVP-2-01..07 closed. Scope and CONDITIONAL-CLEAR verdict (walking skeleton + MVP-1/MVP-2 slices, no runner) are unchanged.

^{Reviewed by Cursor Bugbot for commit 1ef7a2c. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: a1157b19-cfb5-4aa3-baa4-60c7f47e0ecf)