Make product checks additive

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # ReleaseKit audit implementation plan
 
-Status: Stages 1 and 2 complete; Stage 3 not started.
+Status: Stages 1–3 complete; Stage 4 not started.
 Baseline: `e4be7fa` (2026-10-06). The [audit](audit.md) records the evidence,
 product goals, and selected direction. This document owns implementation order
 and completion criteria for that work.
@@ -201,6 +201,15 @@ its captured candidate. Reuse existing mutation/recheck tests with the new
 callback. One CLI profile test covers ordered extra commands. Keep callback
 unit coverage and end-to-end suite-count coverage at distinct boundaries.
 
+**Completed:** `AdditionalChecks` now runs after the standard offline suite in
+the public check and publish flows; selected builds remain after both. The CLI
+keeps ordered JSON `checks` as additional commands, and the bundled profiles no
+longer repeat the standard suite. Facade tests prove suite failure stops checks
+and publication, additional-check errors retain identity, and successful
+publication runs both once for its captured candidate. CLI coverage verifies
+ordered checks. The full offline suite, API boundary check, and documentation
+whitespace checks pass.
+
 ## Stage 4 — Consolidate artifact identity and declaration rules
 
 **Covers:** artifact portion of F8. **Primary owners:** `internal/build/`,