Files
channel-uat-skic/references/aerosim-lessons-review.md
T

3.8 KiB

AeroSim lessons review — UAT

Immutable sources

AeroSim UAT source SHA: f07f457bf6debeb16cdf79ab10dac193d0f6d69c. Central baseline: 8e6547659cd7019a445c8b4b061e61a3a7b79b8b.

Read the full source skill and all four references against the central skill and its four references. Relevant sections: Entry gate from Delivery, E2E Gitea Actions contract, Handoff packet, Exact deployment evidence, and Defect return and retest.

Promoted lessons

  • A template commit is provenance, not proof of the rendered deployment. Require timestamped pre/post live identity and health; distinguish root/runtime sources and invalidate mixed-deployment results.
  • Reconcile the complete required journey/browser matrix rather than accepting a partial run; keep E2E revision and verified receipt in reporting.
  • Accept only ordinary-user-path evidence, with meaningful runtime outcomes. Infrastructure health and bypass-assisted navigation cannot prove product acceptance.
  • Existing two-workflow, secret-handling, retest, and lifecycle separation contracts already cover the source; preserve rather than duplicate them.

Runtime drift reviewed

Installed UAT SKILL.md SHA-256: 0167e17bf5f254c359ea311b21b0b94a8a24db9d33b0635afa3e6a2b0b311d9b; installed references/journey-repository-and-execution.md SHA-256: 0fef75fdd1d6eaa861f40810fbcbe1f0a3e75d16e7c76d1ad91da8f8e556e291. Runtime board reassignment and standing authority are local overlays, not central defaults. The runtime journey reference omits artifact-validation exclusions present in Git; preserve the newer source boundary.

Ordinary-interaction acceptance is a cross-channel lesson from installed AeroSim Releases Post-Approval and Deployment Evidence, SHA-256 feac09e2515486abc35a5b127525ec3a13ca97d47f12b32cf68e434c50df9ece. This supplementary local content is not attributed to the pinned source; the related immutable Releases baseline is:

Exclusions

No project rollout, runtime overwrite, owner reassignment, branch naming change, Jira mandate, standing merge/deploy delegation, account recovery, board/channel IDs, endpoint, scheduler cadence, or deployment configuration is promoted. Central authority and project overlays remain unchanged. The newer central functional-non-unit versus build-time artifact-validation split is retained; runtime references that send Helm artifact validation to UAT are stale and are not imported.

Verification

Run python3 -B -m unittest discover -s tests -v from this repository, plus git diff --check. Tests validate the published documentation contract and links offline; they do not prove a deployment or live acceptance run.