Add CUST-WP-0053 coordination hygiene workplan

Unblock sweep for blocked workplans vs inbox, inbox triage discipline
(thread_id + unread-age alerts), workplan ID prefix lint with cross-repo
collision detection, SCOPE Current State freshness. Findings from the
2026-07-01 railiance-cluster review (RAILIANCE-WP-0014 sat blocked 13 days
after the unblocking inbox message arrived).

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

workplans/CUST-WP-0053-coordination-hygiene-improvements.md

@@ -0,0 +1,82 @@
+---
+id: CUST-WP-0053
+type: workplan
+title: "Coordination hygiene: unblock sweep, inbox triage, workplan lint"
+domain: infotech
+repo: the-custodian
+status: proposed
+owner: the-custodian
+topic_slug: custodian
+created: "2026-07-01"
+updated: "2026-07-01"
+---
+
+# Coordination hygiene: unblock sweep, inbox triage, workplan lint
+
+## Context
+
+A railiance-cluster review (2026-07-01) found systemic coordination gaps
+across the railiance and net-kingdom repo sets. Concrete incident:
+RAILIANCE-WP-0014 sat `blocked` for 13 days after llm-connect posted the
+unblocking message (inbox `7c05dde1`, 2026-06-18) — nobody cross-checked
+blocked workplans against the inbox. Other findings: 8+ unread inbox messages
+dating back weeks with no thread_ids, workplan ID collisions across repos
+(`RAILIANCE-WP-0005` is two different plans in railiance-platform and
+railiance-apps), non-canonical statuses (`completed`, `done`), and stale
+SCOPE "Current State" lines contradicting live workplan status.
+
+These fixes belong in state-hub / fix-consistency tooling, so this plan is
+anchored here rather than in any single railiance repo.
+
+## Unblock sweep for blocked workplans
+
+```task
+id: CUST-WP-0053-T01
+status: todo
+priority: high
+```
+
+When a workplan goes `blocked`, record the unblock condition and counterpart
+agent in frontmatter (e.g. `blocked_on: message-from:llm-connect`). Add a
+sweep (fix-consistency check or scheduled agent) that cross-references
+`blocked` workplans against unread inbox messages from the counterpart agent
+and raises a warning ("blocker may have cleared") in the repo brief.
+
+## Inbox triage discipline
+
+```task
+id: CUST-WP-0053-T02
+status: todo
+priority: medium
+```
+
+- Agents set `thread_id` on follow-up messages so supersession is visible.
+- Add an "unread messages older than N days" warning to `get_domain_summary`
+  output and `.custodian-brief.md` generation.
+- Inbound asks that require multi-step work get promoted to a workplan file
+  in the receiving repo (convention exists; make the sweep flag violations).
+
+## Workplan ID prefix lint
+
+```task
+id: CUST-WP-0053-T03
+status: todo
+priority: medium
+```
+
+fix-consistency check: workplan frontmatter `id` must start with the repo's
+canonical prefix (e.g. `RAIL-BS-WP-` for railiance-cluster). Warn on strays
+(existing `RAILIANCE-WP-*` files keep their ids — the convention forbids id
+renames — but new plans must conform) and detect cross-repo id collisions.
+
+## SCOPE Current State freshness
+
+```task
+id: CUST-WP-0053-T04
+status: todo
+priority: low
+```
+
+fix-consistency already syncs task status; teach the brief writer to refresh
+(or flag as stale) the SCOPE.md "Current State" section when it contradicts
+live workplan statuses, so agents don't orient on wrong facts.