[ACP-REVIEW-400] 並行レビュー結果と復旧・開発再開の実行境界を記録する

[ootakazuhiko]

Parent: #3655
Review date: 2026-09-07 (JST)
Kind: documentation / planning only; not a new release or merge gate.

Purpose

ユーザー承認の並行レビューとして、Codexが実行中の#3672 / PR #3674、および凍結中の#3671 / PR #3673と競合せず、横断的な改善と既存Issueへの振分けを記録する。既存の復旧作業に新規の一括受入条件を後付けしない。

Evidence baseline

Inspected main: c5da6115638fdbfeebbc458b39fa6916db66afb0.

Primary sources:

• AGENTS router and invariants
• Product policy
• Issue runbook
• Authority producer/consumer implementation
• Codex stdio consumer
• [ACP-HARDEN-100] Epic: Private Match dogfoodからのAssurance Control Plane hardening実行計画 #3655, [ACP-HARDEN-130] execution-result/v1を導入しstatus非変換を保証する #3658, [ACP-HARDEN-210] human-decision/v1で承認を対象material digestへbindingする #3659, [ACP-HARDEN-250] review-disposition/v1とhead-bound review completenessを追加する #3661, [ACP-HARDEN-260] GitHub Actions supply-chain policyをfull-SHA基準で強化する #3664, [ACP-HARDEN-140] Solo maintainer + AI-assisted governance profileを追加する #3667, [MAIN-HEALTH-SEC-002] Eliminate current high dependency vulnerabilities and restore enforced security gates #3671, [MAIN-HEALTH-CI-003] Restore Container Security after Podman/crun runtime incompatibility #3672.

This is a source-level architecture/control-plane review. It does not claim a complete code audit, a fresh dependency audit, or successful execution of the full repository test suite.

Scope

• Add a dated, source-linked review report in a new documentation path only.
• Separate observed source facts from design recommendations and unexecuted validation.
• Route duplicate topics to existing Issues rather than create duplicate implementation work.
• Track follow-ups for authority consumer subject binding / typed check identity and scoped CI acceptance / bounded observation.
• Explain recovery ordering without making either remediation wait for the other's entire workflow to be green.
• Distinguish implementation review readiness, Issue acceptance, merge authorization, and post-merge health.
• Define parallel-owner boundaries and phased local/final validation to reduce no-progress polling and repeated heavy CI.

Parallel safety

Do not push to, retarget, Ready, merge, comment on, relabel, or resolve threads in PR #3674 or PR #3673 from this review task. Their current operators retain source and metadata ownership. Do not mutate #3672 acceptance while Codex is executing it. New documentation must not overlap the changed-file sets of either PR.

Suggested branch: docs/parallel-assurance-review-20260907.
Suggested new file: docs/reports/AE-PARALLEL-REVIEW-2026-09.md.

Acceptance

The documentation has exact source revisions, explicitly marked proposal status, follow-up ownership, a non-circular recovery sequence, and an honest validation section. Existing risk policy, required check names, branch protection, releases, and public claims remain unchanged.

Validation and stop

Validate Markdown/front matter and source/link references locally where available. Run repository documentation/schema checks where supported; record unavailable commands and reasons instead of claiming pass. Create one Draft PR. Do not merge, close this Issue, run deployment/publication, or start #3658. This Issue tracks the review deliverable, not completion of the follow-up implementations.

[ootakazuhiko]

Deliverable created

Documentation-only Draft PR #3678 is open at 99fbefa20f094dc472baa1b7daa88ed70929a975, based on inspected main c5da6115638fdbfeebbc458b39fa6916db66afb0.

Changed-file check: exactly one new file, docs/reports/AE-PARALLEL-REVIEW-2026-09.md.

Follow-up Issues: #3676 (authority consumer subject/identity/input bounds) and #3677 (scoped acceptance/bounded observation). Supplements are posted to #3658, #3661, #3664, #3667 and parent #3655. No active recovery source or PR metadata was changed.

Local document bytes match GitHub blob 95fbc99eb651cd020b83d6b803e79668f6b772d9. YAML front matter, Markdown parsing, heading structure, 14 reference definitions and whitespace checks passed. Full repository execution was not performed in the isolated review environment. At the first exact-head CI observation, Verify Lite and Deploy-Time Profiles were successful; other workflows were still running. This is not a merge-ready or overall CI-success assertion.

Keep this Issue open until the documentation review/CI and normal maintainer integration. Completing this report does not complete its follow-up implementations and does not add blockers to PR #3674/#3673.