Close out the coordinated suite upgrade

docs/roadmap/features/0022-coordinated-suite-upgrade.md

@@ -1,6 +1,6 @@
 # Feature 0022: Integrate the Reviewed Application Upgrades
 
-Status: in_progress
+Status: done
 
 ## Summary
 
@@ -231,9 +231,9 @@ controls, not additive timeout guarantees.
 
 ## Dependencies and Follow-up Work
 
-Features 0018–0021 provide the reviewed standalone revisions. Implementation
-is recorded in the [implementation plan](../implementation.md) and is complete;
-independent review is pending. Actual deployment,
+Features 0018–0021 provide the reviewed standalone revisions. Implementation,
+independent review, and remediation are complete. Git history preserves the
+completed staged implementation plan. Actual deployment,
 session migration, live processing, and a formal tagged release are separate
 operator actions, not completion gates for this feature.
 
@@ -266,8 +266,8 @@ there was no operational deployment or live inference, transcription, or object
 storage call. Vault values and target access were not needed or verified.
 After the override harness passed, a formatting-only split of its fixture JSON
 line was checked with `bash -n`, JSON parsing, and `git diff --check` without
-rerunning the long integration harness. Independent review remains required
-before marking this feature done. No tagged release was created.
+rerunning the long integration harness. Independent review subsequently found
+the three issues resolved below. No tagged release was created.
 
 ## Remediation Follow-up
 
@@ -279,7 +279,16 @@ snapshot. Shell/whitespace checks, pipeline and installed-collection syntax and
 lint, collection build/install, and real-inventory consumer target/syntax checks
 passed. Full host-mutating convergence was not rerun for these documentation
 and test-only changes. Application versions/defaults and runtime behavior are
-unchanged. Feature closeout remains pending.
+unchanged.
+
+## Closeout
+
+Closed on 2026-09-29 after independent review and resolution of all three
+findings. This completes the agreed application upgrade sequence. The active
+implementation plan is retired; no additional implementation is required for
+this feature. Consumer commits remain local. Operational upgrade, session
+migration, live production/testing checks, and any new tagged release require
+separate operator action and were not performed as part of closeout.
 
 ## Upstream References