Steps 10–12 — Manifest-Bound Implementation and Acceptance

Implement approved tasks only inside manifest source_roots.
Confirm every changed behavior and test maps to a requirement ID.
Review architecture boundaries, validation, authorization, data integrity, safe logging/errors, dependency policy, test depth, and golden drift.
Run all matching manifest verification rules.
Run manifest build commands, then test commands, as argv without shell interpolation.
On failure, roll back the approved patch and return to plan/implementation with evidence.
Write implementation acceptance only after every deterministic gate passes.