Record coordinated suite upgrade validation

docs/roadmap/application-upgrade-sequence.md

@@ -32,15 +32,14 @@ Seriatim is unchanged by this sequence.
 
 Release-summary and migration-guidance triage is complete. Standalone
 Scriptorium, Audita, Notarius, and Narratio adoption are complete after independent
-review; coordinated suite integration is next. Add the numbered
-feature link beside each item when its roadmap is created; check it off after
-independent review and closeout.
+review. Coordinated suite integration is implemented and awaits independent
+review; check it off only after review and closeout.
 
 - [x] [Feature 0018: Scriptorium adoption](features/0018-scriptorium-v0-15-adoption.md) — complete through role `b174c8c`; independent review found no remediation issues.
 - [x] [Feature 0019: Audita adoption](features/0019-audita-v2-adoption.md) — complete through role `c3dd59f`; independent review found no remediation issues.
 - [x] [Feature 0020: Notarius adoption](features/0020-notarius-v0-8-adoption.md) — complete through role `6aef48b`; independent review found no remediation issues; suite unchanged.
 - [x] [Feature 0021: Narratio adoption](features/0021-narratio-v3-adoption.md) — complete through role `3c0700b`; independent review found no remediation issues; suite unchanged.
-- [ ] [Feature 0022: Coordinated suite integration](features/0022-coordinated-suite-upgrade.md) — roadmap, default-inheritance policy, and staged plan approved; ready for implementation.
+- [ ] [Feature 0022: Coordinated suite integration](features/0022-coordinated-suite-upgrade.md) — implementation complete at public pipeline `ea8b09e`, public collection `3d77eb3`, and local consumer `f694dad`; independent review pending.
 
 ## Adoption Boundaries
 

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

@@ -1,6 +1,6 @@
 # Feature 0022: Integrate the Reviewed Application Upgrades
 
-Status: ready
+Status: in_progress
 
 ## Summary
 
@@ -231,12 +231,44 @@ controls, not additive timeout guarantees.
 
 ## Dependencies and Follow-up Work
 
-Features 0018–0021 provide the reviewed standalone revisions. This roadmap is
-approved; execution is defined in the [implementation plan](../implementation.md).
-Final review precedes feature closeout. Actual deployment,
+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,
 session migration, live processing, and a formal tagged release are separate
 operator actions, not completion gates for this feature.
 
+## Implementation Evidence and Review Handoff
+
+On 2026-09-29, the four reviewed standalone role revisions were published to
+their existing public Gitea `origin/main` branches and verified after fetch:
+Scriptorium `b174c8c2990bb79f8149d8f288c5e06ccb42bd73`, Audita
+`c3dd59f5ac9b942306ffe540ae9e71d493998137`, Notarius
+`6aef48b7e12e3651971444b8c224d96ff1879e6c`, and Narratio
+`3c0700b5323293d44e3b1e67a50074d82d7a3bff`.
+
+The pipeline role at public revision
+`ea8b09e190419586ede6df3815d1ea999a0f4391` passed `bash -n`, its full
+`tests/integration` harness twice (configuration migration and representative
+override coverage), and `git diff --check`. The collection imported that exact
+public revision by subtree; public collection revision
+`3d77eb382bcb4c1742015d3c32e23630bb8c73bf` passed `bash -n`, its full
+artifact-based `tests/integration`, and `git diff --check`. Both harnesses used
+synthetic credentials and offline native application validation, with clean
+repeats. The consumer's local commit
+`f694dad9426ee21138b175e44a3855d42be99d4b` passed public dependency
+installation into disposable paths, real-inventory `--list-hosts` limited to
+`pipeline-dnd`, `--syntax-check`, and `git diff --check`. Its commit was not
+pushed. Seriatim and native collection pins remain unchanged, and manifests
+across the three repositories agree.
+
+The local integration harnesses converged only the development installation;
+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.
+
 ## Upstream References
 
 - [Audita v2 migration](https://gitea.maximumdirect.net/eric/audita/src/tag/v2.0.1/docs/migrations/v2.md)

docs/roadmap/implementation.md

@@ -352,6 +352,8 @@ commit local unless separately asked to push; it is not a downstream dependency.
 
 ## Stage 6: Record Evidence and Hand Off for Independent Review
 
+Completion: complete (2026-09-29).
+
 ### Required Policy Review
 
 Read `AGENTS.md`, `docs/orientation.md`, `docs/conventions.md`,
@@ -389,7 +391,7 @@ mark F0022 done, begin another feature, or push unrelated workspace history.
 
 ## Progress Notes
 
-Plan approved. Stage 1 publication is blocked. On 2026-09-29, all four exact
+Plan approved. Stage 1 publication was initially blocked. On 2026-09-29, all four exact
 reviewed revisions were present locally; clean worktrees and expected Gitea
 origins were confirmed. After fetching, each `origin/main` was three reviewed
 feature commits behind the selected revision and could fast-forward. The first
@@ -402,6 +404,25 @@ had started.
   `3c0700b` revisions to their existing Gitea `origin/main` branches succeeded.
   A fresh fetch and ancestor check verified all four public references. No
   standalone code or dependency pin changed in this stage.
+- Stage 2: pipeline migration and existing integration cases passed `bash -n`,
+  the full role harness, and `git diff --check`; role commit `8ea8621`.
+- Stage 3: representative override, nullable omission, native effective views,
+  and clean repeats passed the full role harness; public assembly revision
+  `ea8b09e190419586ede6df3815d1ea999a0f4391`. A subsequent fixture-JSON
+  line formatting change passed shell syntax, JSON parsing, and whitespace
+  checks without another full harness run.
+- Stage 4: the exact public pipeline revision was subtree-imported. The
+  collection artifact harness passed with public dependencies, native base and
+  testing validation, and a clean repeat; public collection revision
+  `3d77eb382bcb4c1742015d3c32e23630bb8c73bf`.
+- Stage 5: public consumer dependencies installed into disposable paths;
+  real-inventory `--list-hosts` selected `pipeline-dnd`, and `--syntax-check`
+  and `git diff --check` passed without Vault decryption or deployment. Consumer
+  revision `f694dad9426ee21138b175e44a3855d42be99d4b` remains local.
+- Stage 6: cross-repository pins and owning repository worktrees were checked;
+  implementation is complete, independent review pending. Operational
+  deployment, live processing, session migration, and tagged release remain
+  deferred.
 
 ## Open Questions