implement

# Implement Execute the approved plan directly in this Codex session. Codex is the primary implementation authority in this workflow. If you also have a separate Claude workflow available, treat it as an optional parallel second-opinion lane rather than the primary executor. ## Step 1: Load Plan and Supporting Artifacts - If a path is provided, read that plan - If no path is provided, use the most recent file in `./tmp/ready-plans/` - If the plan includes `Source Artifacts`, read the brief / intent artifact and research dossier before coding Treat sources of truth as: - Brief / intent artifact: why this work exists and what must not be optimized away - Plan: execution shape, task ordering, and file-level implementation details - Dossier: supporting evidence, patterns, and anchors If no separate brief exists, treat the plan's `Intent / Why`, `Locked Decisions`, `Known Mismatches / Assumptions`, and success criteria as the minimum intent source of truth. ## Step 2: Identify Dangerous Commands Before implementing, scan the plan for commands that must not be run automatically: - environment variable changes - package installations that change manifests - destructive or irreversible commands Collect them into a `Manual Steps` list and surface them before proceeding. Schema / migration handling is done later after review. Do not handle it here. ## Step 3: Choose Execution Strategy Default to one primary implementation stream. Only split work when all of the following...