Skip to main content

AEROSIM-TS-52

Project task

Verify Argo CD reconciliation of the selected release artifacts

A governed GitOps change reconciles through Argo CD to healthy Web and API workloads whose running image revisions match the reviewed selection.

AEROSIM-TS-52Canonical ID TASK-0052
Verified flow state
Done
Owner
AeroSim Architecture and Delivery
Component
Gondor runtime — Argo CD reconciliation verification
Repository
corp-v1-aerosim/gondor-v1-aerosim

Delivery scope

Verify a reviewed Gondor Git commit reaches Argo CD Synced/Healthy, both workloads become Available, ingress routes /,/api,/socket.io correctly, running imageIDs equal selected digests, and a reviewed revert restores the prior digests; serialize evidence without declaring Feature acceptance. Primary files: apps/aerosim/tests/reconcile-release.sh, apps/aerosim/tests/assert-runtime-revision.sh, tests/gitops/argo-reconciliation.test.mjs, evidence/aerosim-release-evidence.schema.json.

Implementation contract

Implementation artifacts

  • apps/aerosim/tests/reconcile-release.sh
  • apps/aerosim/tests/assert-runtime-revision.sh
  • tests/gitops/argo-reconciliation.test.mjs
  • evidence/aerosim-release-evidence.schema.json

Inputs

  • Reviewed Gondor commit SHA and Argo CD Application aerosim
  • Expected Nebula/Singularity digests, namespace, ingress host, and previous reviewed commit for revert

Outputs

  • ReleaseEvidence document containing GitOps SHA, Argo sync revision/status/health, workload readiness, route checks, and observed imageIDs
  • Rollback evidence tying the revert commit to restored prior image digests

Failure boundaries

  • Fail evidence capture on Argo OutOfSync/Degraded, timeout, unavailable replica, route error, or any observed imageID mismatch.
  • Do not mark reconciliation verified when evidence fields are missing, commands target another namespace/application, or rollback used an imperative runtime mutation.

Excluded scope

  • Successful reconciliation is deployment evidence only; it does not approve the Feature, allocate a release, validate business scenarios, or authorize an unreviewed rollback.

Verification steps

  • bash apps/aerosim/tests/reconcile-release.sh --app aerosim --revision "$GITOPS_SHA" --timeout 10m
  • bash apps/aerosim/tests/assert-runtime-revision.sh --namespace aerosim --web-digest "$NEBULA_DIGEST" --api-digest "$SINGULARITY_DIGEST" && node --test tests/gitops/argo-reconciliation.test.mjs

Traceability

Requirements

Dependencies

UI/UX applicability

non_visual

This Task owns technical or behavioral acceptance and does not claim direct visual conformance to the approved UI/UX package.

Acceptance evidence

Verified delivery: Gondor PR #8 introduced fail-closed Argo reconciliation and runtime image/route verification with ReleaseEvidence schema; PRs #9-#12 reconciled the reviewed digest-pinned release and resolved live selector, readiness, and resource-discovery compatibility; PR #13 restored the prior reviewed runtime at Synced/Healthy with both prior imageIDs and all routes verified; PR #14 reapplied the selected release. Final Argo revision 51cc5384728a804874acc75032b9a8bf5c50418c is Synced/Healthy, aerosim-web and aerosim-api are Available 1/1, /, /api/health, and /socket.io return HTTP 200, observed imageIDs exactly equal the selected Nebula and Singularity digests, local GitOps tests pass 13/13, policy checks pass 250/250, and exact-head CI passed for every reviewed PR. Release completion verified on product 1.0.0.0 at GitOps revision 5d3712d89dfbf7dacd993348e55f497d126c7bf9 with Argo Synced/Healthy, exact image digests, authenticated API/database access, and three-world configured-flight acceptance.

Current evidence boundary

No current implementation, acceptance, release, or deployment evidence is claimed for this planned Task. Any prior implementation may be used only as prototype and discovery evidence.