Approved refined F-14 integration

Execution identity: t_154ab492. Status: IN_PROGRESS. Target release: unassigned. No release wave allocation.

This task-scoped record is authoritative for this explicitly release-unassigned exception; it does not admit TASK-0166 or alter its portfolio status.

Authority and claim

RootAtSkic approved the exact onboarding in UI/UX decision 1554866963119865869. Decision 1554928333916078161 explicitly instructs proceeding without a target release, using this execution identity and task-based branches. Hermes records that supplied decision now, not a fabricated historical event.

Claim: application PR328, branch task/t_154ab492-refined-f14-1, base test. Both application PR328 and record PR421 were visible with matching branch/head/title/base before repository edits.

Exact scope

Replace only the existing canonical fighter-collection-f14 visual asset in flight and Hangar. Preserve selection/persistence, scale/axes/origin, semantic nodes and camera/collision anchors. Do not change physics, flight envelope, controls, unrelated UI, other aircraft or terrain; no wing animation, cockpit interiors or landing gear.

Use documentation PR415, revision 6c04510842aadb30d8d25aa24cae8b66ad8e5e50, path static/model-review/assets/fighter-collection-f14.glb, never PR413. Independently verified SHA256: 76b55e51958695d5c1ad259571b9618345246a1dbe6cc5bb8c330b1ad7cb77ca; 109816 bytes, 2440 indexed triangles, four primitives/materials and no textures. Four draws is a source primitive estimate, not a runtime measurement.

Preserve independently authored MIT provenance with immutable links to generator and model sources.

Required evidence before Delivery completion

• Unit-first canonical wiring and narrowly scoped asset-contract regressions, preserving enforcement for other assets.
• Full unit/static/build checks, independent exact-head review and required CI.
• Immutable image publication tied to integrated application commit.
• Reviewed development GitOps revision, Argo reconciliation, deployed runtime identity and independently matching asset readback.
• Frozen tuple and rollback instructions handed to UAT. Functional/browser/non-unit acceptance remains UAT-owned.

The preparation record above does not itself claim delivery completion. The verified implementation/deployment checkpoint below supersedes its initial no-change state. Existing application PR299 overlaps this manifest and GLB family; the approved refined bytes remain authoritative.

Verified development checkpoint — 2026-09-30

This reference is for UAT and Delivery to identify the exact deployed candidate. Status remains IN_PROGRESS; GATE_005_TASK_POST_MERGE is pending the actual UAT and Releases channel handoffs. This worker has neither a Discord operation nor an injected Discord credential. No channel message or UAT verdict is claimed. Hermes main session owns completing those posts and recording their readback IDs; no new model approval or release allocation is needed.

Machine-readable frozen evidence includes exact CI jobs, runtime identities, annotations and served-asset readback.

Identity	Verified value
Application integration	f59327751115d3b935eb3afc0de91664683d6c2e
Application PR reviewed head	710090a30735ead8522e77f5c853e3bcde3eab08 — independent review PASS; PR328
Web image	harbor-v1.apps.lego-cloud.eu/library/nebula@sha256:cdf3f18cde554ffdd20b3e4372d562a42502ccc3f6a43043daafc1063276cc4a
API image	harbor-v1.apps.lego-cloud.eu/library/singularity@sha256:c4f337923e3360f3da198ba6ff302d7bc37566e2c83186bd434fd8e82e796064
Chart version	1.0.0+build.3.f59327751115d3b935eb3afc0de91664683d6c2e
Chart OCI digest	sha256:dbae6a613e6fb265f3883fb7bbcb1252f87f8b250a4cfe0c0beb820a626b23a0
Chart archive SHA256	f0249d3bd2bff17bdf09eb65a38b1a38c3ee7787a814e63914fa64645baac4dc
Template integration	34002ad9df0e46b2541845021defe13d43786cb0 — PR84
Development GitOps integration	c88485878e9119557082726316b65702c97e6df7 — PR61
Root Argo	0000-aerosim-dev-app-of-apps — Synced / Healthy at the development GitOps integration above
Runtime Argo	0600-aerosim-dev — Synced / Healthy at the exact chart version above; source/chart annotations match
Ready web pod	aerosim-dev-web-c97864bf4-2stcd — runtime imageID equals the web digest above
Ready API pod	aerosim-dev-api-664868c56c-q6f5x — runtime imageID equals the API digest above
Deployed asset	Public development GLB readback — HTTP 200, 109816 bytes, SHA256 76b55e51958695d5c1ad259571b9618345246a1dbe6cc5bb8c330b1ad7cb77ca

Development: https://aerosim-dev.apps.lego-cloud.eu/ . Production: https://aerosim.apps.lego-cloud.eu/ — not changed by this task. Artifact/chart product-version labels do not allocate this task to a target release.

Validation and provenance evidence

• Independently acquired committed GLB bytes with git show 6c04510842aadb30d8d25aa24cae8b66ad8e5e50:static/model-review/assets/fighter-collection-f14.glb; parsed GLB headers/JSON/accessors using Python struct/json, hashed using hashlib.sha256. Verified four mesh nodes, 2520 vertices, 2440 triangles, four material-backed primitives and no textures. No source discrepancy was found.
• packages/assets/src/refined-f14.test.ts: RED before replacement, then GREEN; asserts pinned approval hash, measured manifest, preserved presentation envelope/origin/axes/anchors, narrow budget acceptance and rejection under other-asset limits. Catalogue unit coverage asserts one canonical F14. The existing shared flight/Hangar lookup remains unchanged.
• Full application pnpm validate and pnpm audit --prod --audit-level high passed on the candidate and exact integration revision. Production build inputs were supplied explicitly; no runtime services or functional non-unit suites were started.
• Application PR validation run6632: all three required checks passed on the reviewed head. Trusted integrated publication run6636: all five jobs passed in attempt 1. Independent Harbor API and OCI readback confirmed both image labels/source revisions, manifest digests, chart identity and archive checksum.
• Template candidate a9fa56db25767b43992ead985ee59e0ce09a0484 and rendered candidate fb75d90361173fb2cd4ce4592c5ec9a8d069a3f1 passed independent review and exact-head CI. Local python -m unittest discover -s tests -v passed in both repositories. The template's production answers were unchanged. Its existing generic scaffold exclusions were retained, not deployed.
• Read-only microk8s kubectl ... -o json over authenticated Gondor SSH verified the exact root/runtime Applications, namespace, Ready pods and imageIDs. A separate HTTPS GET retrieved and hashed the actual deployed GLB. These checks establish deployment identity, not functional acceptance.

Functional validation reserved for UAT

UAT must verify this frozen tuple in its owned E2E repository and record its own results:

1. Select F14 in Setup/Hangar and verify the refined model in Hangar and flight with no duplicate selection; confirm saved selection survives navigation/reload.
2. Compare the approved silhouette/materials, orientation, scale, origin and semantic-node expectations in real rendering. The flight presentation envelope remains unchanged to avoid physics/anchor drift; visual mesh height differs within that envelope.
3. Exercise cameras, flight controls, near-ground/collision presentation and unaffected aircraft; identify any visual regression without interpreting unit results as behavioral acceptance.
4. Measure actual loading/resource/draw behavior, fallback/error handling and applicable performance budgets. Four draws above is an authored-primitive estimate, not a measured live-frame count.
5. Run applicable browser, integration, runtime, smoke, security-boundary and acceptance suites owned by UAT. No such suite was run by Delivery.

Rollback procedure for authorized Delivery

Open reviewed task-based branches/PRs; never patch live Deployments or use direct Helm deployment. Restore the prior template development answer tuple from template integration 229b72fe0ccf0b5ff933ec10048ea9d13a42d147, rerender, and restore matching development desired state from revision 7a528e116c6420bfcf3fc2fbeb96d29159a2a863 without overwriting unrelated later work. Prior application is 5edfc59a596a406dd62de17a7bb6fdb19195112c, chart 1.0.0+build.3.5edfc59a596a406dd62de17a7bb6fdb19195112c, chart OCI digest sha256:457ea282075f4ad0d8357a0828c8f5d3bb0cca644aa37abcdb40e2190e00675c, web digest sha256:ed3b0a344f64847e0c4741b21fae8015f57a92e1d05b0fe1f2fb687e6ea651ee, API digest sha256:57ebc3d97cd9321dee23d732069f246e318a349a4784afcd0783040e603d9b9e.

Run local validation, independent exact-head review and CI before merging. Then require Argo Synced / Healthy, Ready pods on those imageIDs and a fresh deployed asset readback. If rolling the source change forward instead, restore the prior F14 manifest and source/runtime assets together in a reviewed application PR, reconcile its pinned regression expectations explicitly, publish new immutable artifacts and repeat the development GitOps flow. Do not reset branches, overwrite existing immutable tags, change other aircraft or touch production.