CUST-WP-0050 T02: classify remaining 10 custodian repos

All 11 custodian-domain repos now carry a committed, validated
.repo-classification.yaml (first-pass classified_by: agent). T02 remains
in_progress pending the human-review step.

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

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

@@ -191,11 +191,16 @@ 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.
+**Progress (2026-06-22):** all 11 custodian-domain repos now carry a committed,
+validated `.repo-classification.yaml` (first-pass `classified_by: agent`):
+the-custodian (research·infotech), state-hub (product·infotech), hub-core
+(product·infotech), inter-hub (research·infotech), activity-core
+(project·infotech), issue-core (product·infotech), kaizen-agentic
+(product·agents), llm-connect (product·agents), ops-bridge (product·infotech),
+ops-warden (product·infotech), email-connect (product·infotech). Commits are
+**local-only** in each repo (not yet pushed to Gitea). Task stays `in_progress`
+pending the **human review** step (done-criterion); review the `research` vs
+`project`/`product` calls and the agents-vs-infotech primary-domain choices.
 
 ### T03 - Classify the full Gitea inventory