STATE-WP-0093-T08: reader-aware mark-read and notice ack in the instruction templates; first standing notice live.

No fleet regeneration: standing notices are already visible to agents on
old instructions, and the notice carries its own ack command.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703

scripts/project_rules/agents-codex.template

@@ -59,8 +59,10 @@ curl -s "http://127.0.0.1:8000/messages/?to_agent={REPO_SLUG}&unread_only=true"
 
 Mark a message read:
 ```bash
-curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
+curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read?reader={REPO_SLUG}" \
   -H "Content-Type: application/json" -d '{}'
+# Standing notices (to_agent "broadcast", kind "standing") stay until acknowledged:
+# curl -s -X POST "http://127.0.0.1:8000/messages/<id>/ack" -H "Content-Type: application/json" -d '{"agent":"{REPO_SLUG}"}'
 ```
 
 ### Log progress (required at session close)

scripts/project_rules/session-protocol.template

@@ -31,8 +31,10 @@ Without MCP tools:
 ```bash
 curl -s "http://127.0.0.1:8000/messages/?to_agent={REPO_SLUG}&unread_only=true" \
   | python3 -m json.tool
-curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
+curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read?reader={REPO_SLUG}" \
   -H "Content-Type: application/json" -d '{}'
+# Standing notices (to_agent "broadcast", kind "standing") stay until acknowledged:
+# curl -s -X POST "http://127.0.0.1:8000/messages/<id>/ack" -H "Content-Type: application/json" -d '{"agent":"{REPO_SLUG}"}'
 ```
 
 **Step 3 — Scan workplans**

workplans/STATE-WP-0093-broadcast-receipts-and-standing-notices.md

@@ -273,7 +273,7 @@ then bump the pinned hub-core here.
 
 ```task
 id: STATE-WP-0093-T05
-status: progress
+status: done
 priority: medium
 state_hub_task_id: "fdb44fd9-ab44-5e26-86b3-a4f0f8a4e701"
 ```
@@ -342,7 +342,7 @@ agents, and archives it.
 
 ```task
 id: STATE-WP-0093-T08
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "7866d802-eaed-5a7d-be74-eda3185f55d0"
 ```
@@ -365,3 +365,14 @@ templates carry the reader/ack line, and gate-house has answered.
 - **Release (T07):** `helm upgrade --atomic --set image.tag=main-ef541f5` gave **revision 65**, deployed. API and MCP both run `main-ef541f5`, 1/1. The migrate hook completed.
 - **Verified live:** `/state/health` ok with schema `d7e8f9a0b1c2`; `GET /messages/notices` 200 (empty); `standing_notices` in `/state/summary`; the 5 old broadcasts archived and out of inboxes; direct-message mark-read unchanged.
 - **Still open:** T04 hub-core (handoff `69fc387c` plus addendum). T05 check against a live notice, which comes with T08. T08: the first standing notice, the template line, and the gate-house question.
+
+## T08 record, 2026-09-22 (founder go-ahead; custodian session)
+
+- **First standing notice published:** `4ff51ffa-2b95-49da-a5a9-2c1965d5fcbe`, from the-custodian to broadcast, kind `standing`, expires 2027-03-20. It points every coding agent to `the-custodian/docs/agent-environment-orientation.md` (revision 2026-09-21), and its body carries the ack command.
+- **Live end-to-end check (closes T05):**
+  - the notice appears in the-custodian's and gate-house's unread inbox;
+  - `POST /ack` as the-custodian clears it for the-custodian only, and gate-house still sees it;
+  - `GET /messages/notices` reported 1 acknowledged, 1 delivered-only and 135 unreached. The delivered-only entry was gate-house, recorded by the custodian's own test query.
+- **Template line:** `session-protocol.template` and `agents-codex.template` now mark read with `?reader={REPO_SLUG}` and document `POST /messages/<id>/ack`.
+- **Fleet propagation NOT run, deliberately.** `update_agent_instruction_files.py` regenerates each repository's whole CLAUDE.md, rules and AGENTS.md without committing. Across the fleet it would overwrite local customisations and leave ~120 dirty working trees. It is also unnecessary: agents on the old instructions already *see* standing notices at every inbox check, and the notice body tells them how to acknowledge. The template change reaches each repository whenever it is next regenerated for its own reasons.
+- The gate-house question (republish the archived v0.7 "start here" note as a standing notice?) was sent to gate-house.