Confirm maintainer coverage and complete seven-day operational handover

[imran-siddique]

The maintainer policy rollout is merged across 11 repositories, but accepted capacity, specialist access and operation without Imran still need evidence. Track the remaining handover here.

Sources: canonical roster, handover procedure, coverage workflow run, and release safeguards follow-up #54. The procedure contains historical rollout/cutover status that needs reconciliation; current issue evidence should distinguish completed deployment from pending handover.

Proposed routing for existing maintainers:

Repository	Primary	Backup
.github	Qiang-Xu	pforest
agent-manifest	rajnisht7	zohebk8s
cmcp	carloshvp	zohebk8s
ca2a	carloshvp	zohebk8s
trace-spec	lywinged	rajnisht7
trace-registry	Qiang-Xu	pforest
weight-custody-manifest	Qiang-Xu	pforest
integrations	carloshvp	Qiang-Xu
agentrust-telemetry	Qiang-Xu	pforest
awesome-ai-governance	pforest	Qiang-Xu
agentrust-io.github.io	pforest	Qiang-Xu

Repository write/admin access was verified for all 22 routing assignments on October 2, 2026. This does not establish team membership, package ownership, organization ownership or accepted capacity. Approval of a rollout PR is not acceptance of an operational role.

Completion criteria:

• Obtain dated primary/backup acceptance for each scope, including availability and fallback routing; revise pairs if capacity is unavailable.
• Verify two active authorized members for the required Agent Manifest/WCM spec-editor and SDK-maintainer teams, and registry code-owner coverage. Preserve appointment and governance requirements.
• Privately verify organization-owner and recovery coverage for two people; record a dated summary without sensitive recovery information.
• Verify package/operator and environment access in coordination with Audit and enforce package release safeguards across AgenTrust #54, including a working backup path.
• Reconcile the canonical handover record with completed consolidation and current verification evidence.
• Start a seven-day handover only after capacity and required access are confirmed; record actual start/end dates.
• During that week, demonstrate routine independent review and merges by at least two non-Imran maintainers across their scopes. Link current-head approvals, checks and actual merge operators. Auto-merges attributed to Imran do not count as non-Imran merge evidence.
• Demonstrate package build/install validation by a non-Imran release operator and a permitted backup path by a second operator. Production publication is optional and requires the normal release policy.
• Record review response times, blocked work, access/routing fixes and any intervention by Imran. Close only when the evidence supports sustained coverage.

The handover has not started. Listing routing pairs does not appoint new maintainers or grant access.