Refine stewardship evidence and specify owner preparation handoffs

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e782-9f45-7382-afff-77ad665b88ec

history/2026-09-28-coordination-followup.md

@@ -0,0 +1,54 @@
+# Preparation coordination follow-up — 2026-09-28
+
+User instruction: proceed with the remaining preparation coordination.
+
+## What advanced
+
+- Reviewed the 35 previously unresolved repositories against their local purpose
+  and scope records. Four now have evidence-backed proposals: disaster-control
+  → coulomb; ops-hub → helixforge; whynot-control and whynot-design → candidate
+  whynot. The current matrix has 122 proposed and 31 unresolved assignments.
+  None is marked approved; named maintainers and effective grants remain unknown.
+- Prepared the exact rollback-gate sequencing amendment in
+  `decisions/rollback-gate-amendment.md`. Explicit approval was requested, but
+  none has been received. AGENTS.md and the all-four gate are unchanged.
+- Specified a sanitized authenticated owner export contract. Linked the existing
+  credential caller-identity and PAT-lane work by stable IDs; did not retry the
+  denied credential request or use another principal.
+- Linked coverage and GitOps owner records, produced a 52-row workload diagnostic
+  queue, and enumerated all 326 excluded source/archive items for disposition.
+  These are review contacts/context records, not accepted new owner task grants.
+- Inspected all four markitect-main gitlinks and recorded their exact revisions.
+  They still point to the old forge endpoint. Attached wiki and issue-facade
+  identities require reconciliation beyond the standalone assignment matrix.
+- Repeated the inventory consecutively. Reference sets remained equal, but
+  hub-core content changed, so condition 3 still fails. The retry receipt is
+  diagnostic only; the earlier full snapshots are retained unchanged.
+
+## Decisions still required
+
+Existing State Hub decisions were updated in place, not duplicated:
+
+- `60c5767c-d510-4d13-9a24-d5d58485b7e5`: candidate whynot naming, 31 unresolved
+  stewards, acceptance of all proposed targets and named teams.
+- `5f3680fc-0cd5-4d27-ba39-59fbdd13313c`: authorized authenticated export/access,
+  exclusion disposition and complete consumer census.
+- `e9aca79b-f167-4326-94cd-037dcea34cd2`: proposed disposable-only exception to
+  the sequencing rule. Accepting it would not permit execution today because
+  conditions 2/3 and the scoped owner rehearsal record are still missing.
+
+The candidate whynot addition is grounded in its existing organizational intent,
+not the lifecycle of every experimental repo. The requested naming preference
+remains unanswered; the matrix explicitly marks it as unaccepted.
+
+Factory integration of Vergabe Teilnahme remains insufficient evidence to infer
+its product steward. Likewise canon ownership is not an organization/team grant.
+No new maintainers, server IDs or accepted remediation tasks were invented.
+
+## Validation and readiness
+
+JSON/CSV populations, proposal counts, 52 coverage rows, 326 exclusion rows,
+source evidence paths/hashes and preserved AGENTS.md were checked. No production
+implementation or T03–T05 work started. No messages were sent to other agents.
+T01/T02 remain waiting on the concrete acceptance gaps; the four-condition entry
+gate is still not met.