Record coordinated suite upgrade validation
This commit is contained in:
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user