docs(mvp1): close MVP-1-08 after baseline tag

[Alexendros]

Summary

• Mark MVP-1-08 closed after annotated tag implementation-baseline-mvp1 on 97045f5.
• Update plan-status, roadmap, backlog and go-no-go to the new baseline (mvp0.1 untouched).

Test plan

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

---

Note

Low Risk
Documentation and issue-status updates only; no application logic, auth, or release pipeline changes in this diff.

Overview
Aligns governance and delivery docs with the emitted implementation-baseline-mvp1 baseline after closing release issue MVP-1-08.

plan-status.md and go-no-go.md now treat implementation-baseline-mvp1 as the active baseline and state that implementation-baseline-mvp0.1 was not moved. backlog.md and next-issues.md mark MVP-1-08 as closed (was planned) and update the plan-closure note so MVP-1-01..08 are all closed with the baseline emitted. roadmap.md reframes MVP-1 from “in progress toward the tag” to stabilized on that baseline.

No code, CI, or runtime behavior changes—documentation and tracking only.

^{Reviewed by Cursor Bugbot for commit 2379b7c. 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: 9c18aca0-0859-4853-b264-4b7add37105b)