docs(19.7): defer the remaining lane A re-review items

.planning/phases/19.7-generic-mcp-module/deferred-items.md

@@ -263,3 +263,22 @@ was changed by the plan that recorded it.
   module cache holding every dependency; a run that coincides with a cache
   change may miss one. Not caused by this phase's code; watch for a
   recurrence.
+- RA-IN-04: the cap of the non-reserving store fallback is still check-then-act (found in the gap-closure re-review, deferred by its lane A fixes)
+  status: open
+  **What:** 034aa19 makes `serveNew`'s fallback for a store without
+  `Reserve` write the record before the server is built, so a reaper pass
+  can no longer close a session that has no record yet. The Count-then-Put
+  cap of that fallback remains racy. Closing it means making `Reserve` part
+  of the exported `pier.Store` interface or refusing a store without it at
+  mount, which changes pier's exported API for a branch only a test wrapper
+  (`WrapStore`) reaches; both shipped stores reserve atomically.
+- RA-WR-06 optional: the demo pin check does not require unreleased commits to be on the canonical checkout's upstream (found in the gap-closure re-review)
+  status: open
+  **What:** 2fdda99 qualifies the gate's verdict ("Phase 19.7 gate passed
+  WITH UNRELEASED PINS: the release pins are not yet proven") while demo
+  submodules carry unreleased non-test commits; the exit status stays 0 so
+  the pre-release verification can run. The review's optional
+  `git branch -r --contains` check was not added: the gap-closure commits
+  are deliberately unpushed until the release order runs, so it would
+  refuse every pre-release run. `PHASE197_RELEASED=1` after the tags is
+  the release proof.