docs(19.7): tag v0.5.0 only when phase 19.7 is complete

.planning/STATE.md

@@ -5,10 +5,10 @@ current_phase: "19.7"
 current_phase_name: Generic MCP module (INSERTED)
 status: executing
 stopped_at: Completed 19.7-01-PLAN.md
-last_updated: "2026-10-22T21:51:48.670Z"
+last_updated: "2026-10-22T22:05:35.357Z"
 last_activity: 2026-10-22
 last_activity_desc: "Completed quick task 261022-wah: user-plugin opt-in token_cookie session cookie and cookie-carried /refresh rotation"
-state_head: 6a1974c0d2ee89ead533ee8f887d7be2f7549f10
+state_head: a9e3f2434d31ab12b263e53ad14acf2a14c4473d
 progress:
   total_phases: 45
   completed_phases: 37
@@ -946,6 +946,7 @@ Recent decisions affecting current work:
 - [Phase 19.7]: 19.7-01: planner decisions P-01..P-04 implemented: bouncer.Dispatch context-only marker honoured by Registry.Middleware and cabana.ResolveBackend; account contributions as pact.HasAccountContributions; prompted record actions post payload as a JSON string; pact MCP types carry the principal as any and stay SDK-free
 - [Phase 19.7]: 19.7-01: wristband authorize allow-list is exactly Options.ScopesSupported (empty keeps the PHP default); surf stream routes recover with an opaque 500 only before the first byte; account contribution Run runs without a transaction only when no database is published
 - [Phase 19.7]: Framework release is v0.5.0 (19.7-02 Task 5), carrying 19.6.1, 19.7 plans 01-02 and a set of 7 msd-quick patches; tag only after all 7 are committed — User decision 2026-10-22: minor bump for the new pier module and pact capabilities; hold the tag until the quick patches land
+- [Phase 19.7]: v0.5.0 is tagged only when phase 19.7 is fully complete (plans 01-05 and phase verification); supersedes the earlier 19.7-02 Task 5 entry. Plan 02 closes without a tag; no intermediate framework tag for 19.7 work — User decision 2026-10-23: a minor version marks the finished MCP phase, not a partial one
 
 ### Pending Todos