Record publish-scope request to activity-core (REINAH-WP-0003-T04)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 269692@bnt-lap001
Assistant-Session: 8077e68a-0985-4b41-898c-2dc602b0d6be

.custodian-brief.md

@@ -2,7 +2,7 @@
 # Custodian Brief — rein-aharness
 
 **Domain:** agents  
-**Last synced:** 2026-10-08 10:31 UTC  
+**Last synced:** 2026-10-13 18:43 UTC  
 **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
 
 ## Active Workstreams
@@ -21,7 +21,7 @@ Progress: 3/6 done  |  workplan_id: `eba2eff1-10a7-50a3-a70b-14e7d398f27f`
 ## Inbox Hygiene
 
 **Stale unread:** 2 message(s) older than 3 day(s) — triage at session start.
-**Missing thread_id:** 2 unread message(s) lack supersession chains.
+**Missing thread_id:** 3 unread message(s) lack supersession chains.
 
 ---
 ## MCP Orientation (when available)

workplans/REINAH-WP-0003-governed-runtime-integrity.md

@@ -523,6 +523,8 @@ the step 6 removal condition counts five definitions. The owner's declaration
 is founder-approved (inbox `76d28b97`, `6e4eb9cc`). Two items are still open:
 the owner and location of the path-scoped publish grant, and the move to a
 tenant-owned blueprint. The owner targets 2026-12-15.
+Activity Core was asked for a publish scope on the repository grant
+(message `3eb4fa11`); a tenant-declared grant is the fallback until 2026-12-31.
 
 ## Align deployment, recovery, and conformance with the supported runtime