Normalize agent instructions and workplan frontmatter (STATE-WP-0067)

- Align agent files with on-disk workplan prefixes (infer from workplan ids)
- Set workplan domain to registered domain_slug; add topic_slug where applicable
- Repair frontmatter delimiter formatting; migrate legacy task status literals
- Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates

AGENTS.md

@@ -2,41 +2,15 @@
 
 ## Repo Identity
 
-**Purpose:** Headless, provider-neutral email communication and evidence service
-for sending, tracking, diagnosing, and normalizing email-channel events without
-overclaiming delivery, awareness, or result satisfaction.
+**Purpose:** Headless provider-neutral email communication and evidence service for sending, tracking, diagnosing, and normalizing email-channel events.
 
-**Domain:** custodian
+**Domain:** infotech
 **Repo slug:** email-connect
 **Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
 **Workplan prefix:** `EMAIL-WP-`
 
 ---
 
-## Repo Orientation
-
-This repository is currently in planning/specification shape. Treat
-`INTENT.md` as the canonical product intent and
-`spec/ProductRequirementsDocument.md` as the detailed requirements source until
-implementation architecture is added.
-
-Preserve the core principle: email events are evidence, not result
-satisfaction. Provider acceptance, MX acceptance, inbox placement, opens,
-clicks, replies, complaints, suppressions, and bounces must remain distinct.
-Do not collapse them into "delivered", "read", "accepted", or any similar
-business conclusion.
-
-Keep the product provider-neutral and adapter-friendly. It should be useful as
-a standalone email communication/evidence service and as the reference
-`coordination-engine` adapter. It should not drift into newsletter campaign
-management, broad marketing automation, or legal/business outcome adjudication.
-
-There is no runtime stack committed yet. Any stack, API, storage, or provider
-choice should be introduced through a workplan and anchored in the current
-intent/PRD.
-
----
-
 ## State Hub Integration
 
 The Custodian State Hub tracks work across all domains. Interact via HTTP REST —
@@ -50,8 +24,8 @@ there is no MCP server for Codex agents.
 ### Orient at session start
 
 ```bash
-# Offline brief, when present
-test -f .custodian-brief.md && cat .custodian-brief.md
+# Offline brief — works without hub connection
+cat .custodian-brief.md
 
 # Active workstreams for this domain
 curl -s "http://127.0.0.1:8000/workstreams/?topic_id=cee7bedf-2b48-46ef-8601-006474f2ad7a&status=active" \
@@ -106,7 +80,7 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 ## Session Protocol
 
 **Start:**
-1. `test -f .custodian-brief.md && cat .custodian-brief.md` — domain goal and open workstreams, when present
+1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
 2. Check inbox: `GET /messages/?to_agent=email-connect&unread_only=true`; mark read
 3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks
 4. Check human-needed tasks: `GET /tasks/?needs_human=true`
@@ -177,6 +151,11 @@ every repo's agent instructions because it is high-frequency, high-risk, and eas
 get wrong.
 
 **Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml`
+
+<!-- REPO-AGENTS-EXTENSIONS -->
+<!-- Append repo-specific agent instructions below this marker.
+     The state-hub template sync preserves content after this line. -->
+
 ---
 
 ## Workplan Convention (ADR-001)
@@ -202,7 +181,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 id: EMAIL-WP-NNNN
 type: workplan
 title: "..."
-domain: custodian
+domain: infotech
 repo: email-connect
 status: proposed | ready | active | blocked | backlog | finished | archived
 owner: codex