Correct A-303: the reach's watches use the seat form, only the stuck key takes the real bucket

The view's kept reach holds no bucket name, so no kept entry depends on the holder's real bucket.

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md

@@ -480,7 +480,8 @@ the principle that settles it, cited as "design 47 G A-n".
   claimant of mesh-module-assigner read from its own catalog (it holds the catalog seat), so buildrun's 5-second
   holder loop goes for every part.
 - **A-303** (§717, A-302; principles 2 and 7) The status view names its followed pictures in the seat form
-  (`<seat>_<state>`); where a name must be the holder's real bucket (the watchdogs' stuck key, which matches what the
-  watchman writes, and the reach history's bucket names, whose kept entries stay readable), the view takes it at run
-  time from the holder FollowSeat follows, through one accessor of the SDK's process reader; no code names the
-  assigner's module.
+  (`<seat>_<state>`), the reach's watches (`reachBuckets`, its history watch included) too, since they match the names
+  the followed pictures are told; where a name must be the holder's real bucket (only the watchdogs' stuck key, which
+  matches what the watchman writes), the view takes it at run time from the holder FollowSeat follows, through one
+  accessor of the SDK's process reader; no code names the assigner's module. *Corrected 2026-11-12: it first named the
+  reach history's bucket names as real buckets too, for kept entries' sake; the view's kept reach holds no bucket name.*