Connect invocation execution to one reporter

docs/roadmap/implementation.md

@@ -1,6 +1,6 @@
 # Invocation reporting implementation plan
 
-Status: Stages 1–6 complete. Stage 7 is next.
+Status: Stages 1–7 complete. Stage 8 is next.
 
 ## Objective and authority
 
@@ -275,7 +275,7 @@ buildability.
 
 ## Stage 7: Connect invocation execution to one reporter
 
-Status: pending.
+Status: complete.
 
 Primary files: [identity.go](../../identity.go),
 [execute.go](../../execute.go), [route.go](../../route.go),
@@ -307,6 +307,14 @@ cleanup writes, ignored writer failures, repeated invocations, alias identity,
 and usage guidance in quiet. Preserve factory-free help/preflight behavior and
 existing input conversion/cause tests under the new API.
 
+The invocation now owns one reporter, applies ordered reporting selection before
+preparation and handler execution, and finalizes normal outcomes through the
+reporter. Focused internal suites pass. Root-package execution remains blocked
+by the planned help/version migration and remaining legacy test callers; the
+root test command was run and its compile errors are recorded for those later
+steps. Focused invocation coverage has been added for reporter freshness,
+selection, quiet usage guidance, early errors, and ignored output failures.
+
 ## Stage 8: Migrate help and version presentation
 
 Status: pending.