docs(19.7): add pattern map, mark D-36 informational, drop session path from plan 02

.planning/phases/19.7-generic-mcp-module/19.7-02-PLAN.md

@@ -345,7 +345,7 @@ Output: `modules/pier` with README, the tagged `pier_on.go`, root README row, `d
     - .planning/phases/19.6.1-backend-administrators-screen/19.6.1-0{1,2,3,4}-SUMMARY.md (for the tag message's 19.6.1 highlights)
   </read_first>
   <action>
-    Run the pre-checks named in the checkpoint context once more on the exact HEAD to be tagged. Write an annotated tag message that lists, in this order: Phase 19.6.1 (Settings → System → Administrators and Roles, the cross-controller record action seam, field triggers and per-record permission locks, the two production fixes), Phase 19.7 plan 01 (dispatch marker, streaming routes and the Handler lookup, the pact MCP and account contribution contracts, the prompted record action, wristband's scope set), Phase 19.7 plan 02 (the `pier` module behind `summercms_mcp`, the `mcp.*` keys, the go-sdk decision note). `git tag -a <version> -m "<message>"` then `git push origin master --tags` (this push is the go-ahead the checkpoint gave; no other branch). Then from `../sm-summercmsio-app`: `scripts/changelog-post.py source <version>` to print the tag message and commits, write user-facing notes under `## Highlights`, `## Added`, `## Changed`, `## Fixed` (no planning IDs, no `quick-*` codes, no H1, framework and plugin names only, never a consuming application), save them to the scratchpad (`/tmp/claude-1000/-media-nvme-dev-golem15-summercms-io-summercms-summercms-go/b7afd5d4-5e95-4c0a-95e4-b30be6da7b19/scratchpad/changelog-<version>.md`) and run `scripts/changelog-post.py publish <version> <that file> --excerpt "<one sentence>"`. Append a "Released in <version>" line to the Consequences section of the decision note (planning docs commit). Record the version in the SUMMARY so plans 03 and 04 pin it.
+    Run the pre-checks named in the checkpoint context once more on the exact HEAD to be tagged. Write an annotated tag message that lists, in this order: Phase 19.6.1 (Settings → System → Administrators and Roles, the cross-controller record action seam, field triggers and per-record permission locks, the two production fixes), Phase 19.7 plan 01 (dispatch marker, streaming routes and the Handler lookup, the pact MCP and account contribution contracts, the prompted record action, wristband's scope set), Phase 19.7 plan 02 (the `pier` module behind `summercms_mcp`, the `mcp.*` keys, the go-sdk decision note). `git tag -a <version> -m "<message>"` then `git push origin master --tags` (this push is the go-ahead the checkpoint gave; no other branch). Then from `../sm-summercmsio-app`: `scripts/changelog-post.py source <version>` to print the tag message and commits, write user-facing notes under `## Highlights`, `## Added`, `## Changed`, `## Fixed` (no planning IDs, no `quick-*` codes, no H1, framework and plugin names only, never a consuming application), save them to the scratchpad (`<your session scratchpad directory>/changelog-<version>.md`) and run `scripts/changelog-post.py publish <version> <that file> --excerpt "<one sentence>"`. Append a "Released in <version>" line to the Consequences section of the decision note (planning docs commit). Record the version in the SUMMARY so plans 03 and 04 pin it.
   </action>
   <verify>
     <automated>TAG=$(git describe --tags --exact-match HEAD) && git ls-remote --exit-code --tags origin "refs/tags/$TAG" >/dev/null</automated>

.planning/phases/19.7-generic-mcp-module/19.7-CONTEXT.md

@@ -118,7 +118,7 @@ Out of scope: MCP resources (the capability is designed for them, but they ship
   - the `ai` scope plays no part in the read/write ceiling;
   - consent is served as JSON endpoints in sm-oauthserver-plugin, with a `/connect` page in vue-demo-app;
   - the permission code is `golem15.users.manage_backend_links`.
-- **D-36:** **Plan split, 5 plans** (user-confirmed):
+- **D-36 [informational]:** **Plan split, 5 plans** (user-confirmed):
   1. framework seams;
   2. the pier module and framework release;
   3. sm-user-plugin;