Start CUST-WP-0050: T01 allowed-values + validator; classify the-custodian

Activate the workplan and complete T01: add the machine-readable controlled
vocabulary canon/standards/repo-classification.allowed.yaml (categories,
domains, business_stake, business_mechanics, capability families, guidance),
reference it from the standard §12, and add tools/validate_repo_classification.py
(stdlib + PyYAML, --self-test PASS).

Begin T02: author the-custodian/.repo-classification.yaml (research · infotech ·
agents), which validates clean. classified_by: agent, pending human review.

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

workplans/CUST-WP-0050-repo-classification-registration-redesign.md

@@ -4,13 +4,14 @@ type: workplan
 title: "Repo Classification & State Hub Registration Redesign"
 domain: custodian
 repo: the-custodian
-status: proposed
+status: active
 owner: custodian
 topic_slug: custodian
 planning_priority: high
 planning_order: 50
 created: "2026-06-22"
 updated: "2026-06-22"
+started: "2026-06-22"
 state_hub_workstream_id: "9f031f48-8de8-48b6-8e69-d2d83ad70a7a"
 ---
 
@@ -150,7 +151,7 @@ hub remains a read/index model fed by repo-owned files (ADR-001).
 
 ```task
 id: CUST-WP-0050-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "d978b1f3-4eca-4a17-835b-2c25d13cae22"
 ```
@@ -164,13 +165,20 @@ families) into a single machine-readable artefact (e.g.
 Done when a single allowed-values file exists, is referenced by the standard, and
 a small validator can check a `.repo-classification.yaml` against it.
 
+**Delivered (2026-06-22):** `canon/standards/repo-classification.allowed.yaml`
+(categories, domains, business_stake, business_mechanics, capability families,
+guidance bounds); referenced from the standard §12; validator
+`tools/validate_repo_classification.py` (stdlib + PyYAML) with `--self-test`
+(PASS) — checks category/domain enums, secondary-domain rules, kebab-case tags,
+and stake/mechanics enums.
+
 ### Phase 2 — Classify the portfolio (repo-owned source of truth)
 
 ### T02 - Classify custodian-owned repos
 
 ```task
 id: CUST-WP-0050-T02
-status: todo
+status: in_progress
 priority: high
 state_hub_task_id: "b7edfbb5-483f-4600-9356-8f885c78ce58"
 ```
@@ -183,6 +191,12 @@ standard's §16 agent prompt as a first pass.
 Done when each custodian repo has a committed file that validates against T01 and
 has been reviewed by a human.
 
+**Progress (2026-06-22):** `the-custodian/.repo-classification.yaml` authored
+(category: research · domain: infotech · secondary: agents) and validates clean;
+flagged `classified_by: agent` pending human review. Remaining 10 custodian repos
+(state-hub, hub-core, inter-hub, activity-core, issue-core, kaizen-agentic,
+llm-connect, ops-bridge, ops-warden, email-connect) still to classify.
+
 ### T03 - Classify the full Gitea inventory
 
 ```task