# AeroSim lessons review — Releases ## Immutable sources AeroSim Releases source SHA: `3c4b4788915bae3d89303959c46a8854c9a141bc`. Central baseline: `2844c4a5f7231ab597519a59f5f11cfe1c858b9f`. - [SKILL.md](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-releases-aerosim/src/commit/3c4b4788915bae3d89303959c46a8854c9a141bc/SKILL.md) - [references/recurring-readiness-pr-refresh.md](https://gitea.lego-cloud.eu/corp-v1-aerosim-skills-code-agent/corp-v1-channel-releases-aerosim/src/commit/3c4b4788915bae3d89303959c46a8854c9a141bc/references/recurring-readiness-pr-refresh.md) Read the full source skill and readiness reference against their central counterparts. Relevant sections: **Release Readiness**, **Gate 1 — explicit request**, **UAT promotion gate**, **Release Completion Gate**, and **Synchronization Workflow**. ## Promoted lessons - Consume a complete, exact-tuple UAT pass independently of release authorization. Record a separate production desired-state revision and verify it live rather than relabeling development evidence. - Preserve immutable rejected-release evidence and require a new corrective release; containment remains separately authorized. - Separate technical health, automated acceptance, and explicit human acceptance. Use ordinary visible interactions, not diagnostic bypasses. - Include UAT and UI/UX in readiness collection; remove stale six-channel coverage. Respect auto-delivered reports and require receipts for message-delivery claims. - Keep existing readiness race guards, PR reuse, latest exact-head CI, and self-reference avoidance in their reference rather than duplicating the long AeroSim synchronization procedure. ## Runtime drift reviewed Installed Releases `SKILL.md` SHA-256: `feac09e2515486abc35a5b127525ec3a13ca97d47f12b32cf68e434c50df9ece`. Its **Post-Approval and Deployment Evidence**, **Production Rejection and Replacement**, and **Release Completion Gate** add the acceptance and rejected-release lessons above. These are supplementary local snapshot evidence, not text attributed to the pinned source SHA. Runtime is not uniformly newer: its deployment repository wording and Gate 1 omit safeguards present in the Git source; those regressions are excluded. Hard-coded app-of-apps identities, flight-specific dwell instructions, standing merge authority, and Copier environment repair are not transplanted. ## 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.