Phase 8.12 — Fleet and application stack update

The platform now runs well over a hundred GitOps-managed application repositories. Each one moves on its own schedule as its upstream ships new releases, so the fleet naturally drifts: some apps sit a minor version behind, some several, and a few are still tracking a release line that upstream itself has stopped supporting.

This phase is a deliberate, fleet-wide pass rather than a per-app afterthought: every application, and the shared chart/CI templates they are built from, gets brought up to its current stable upstream release in one coordinated sweep.

What this phase does

• Updates every app in the fleet to its latest stable upstream version.
• Closes the version gap before it becomes a security or compatibility problem instead of a routine bump.
• Verifies each update against its ArgoCD health check before moving to the next.

No downtime expected — updates roll out one app at a time, with each one confirmed healthy before the next starts.