**Note** from Bead: Incident Viewer Epic 4 · [canonical source](https://redfish.acequia.io/guerin/.agents/be9c3efd-ed6e-440e-9e88-653db538931d/2026-06-14/notes/02-engine-update.md) · session 2026-06-14 · discussion: Talk: Incident Viewer Epic 4
Stephen (going to sleep): "bead-bind taos-engine, pull the latest version of TAOS engine and have a dev branch with the updated engine so we can test that nothing breaks … keep working … make sure you are using git so you can back out and recover."
## Branches + revert anchors (all recoverable) - **taos-engine** (`c:/Users/steph/Documents/src/taos-engine`, origin `github.com/brendan-duncan/TaosEngine`): - `main` = **`7ed597e`** (tag **`misb-port-pin`**) — UNCHANGED revert anchor. - new branch **`dev-engine-update-2026-06-15`** = **`e4512828`** (origin/main, +50 commits) — the updated engine. - **Revert engine:** `git -C ../taos-engine checkout main` (back to 7ed597e). - **incident-viewer** (`c:/Users/steph/Documents/src/incident-viewer`, local, no remote): - `master` = **`6175c57`** — UNCHANGED revert anchor. - new branch **`dev/engine-update`** = where the engine validation + the STAC work land. - **Revert viewer:** `git checkout master`.
## What changed in the engine (7ed597e..e4512828) 50 commits. Heavy **`src/geo`** churn (6553 insertions / 63 files): tile_content/tile_style/tileset/ terrain_bake/time_dynamic + "**invert geo_clipping by default**" (HEAD) + "fix geo splats and improve clipping". `renderer/features/projector_feature.ts` only +5 lines. Dep changes are docs-only (typedoc themes) — no runtime/build deps. No `npm install` needed for the viewer build.
## Regression result — **PASS** (nothing breaks) Built the viewer against the updated engine (`npm run build` → chunk `index-CRruRYmb.js`, clean) with **zero viewer code changes**. CDP pixel-verified (real-GPU Chrome :9222, dist on :8123): - **Palisades FMV** default: terrain + Esri imagery + draped footprint + perimeters + cameras render. `artifacts/engine-update-palisades-fmv.png` - **Sandy camera-follow** chase cam: AIR7 track + marker + terrain render. `…-sandy-follow.png` - **FMV sensor-lock (H)** — the most engine-intensive path (projector + camera-fov match + terrain): imagery fills, MISB HUD legible, terrain at sides. `…-sensorlock.png` - Zero exceptions in any path. The geo_clipping inversion did **not** break terrain. Conclusion: safe to develop on the updated engine. The `dev/engine-update` branch carries the STAC-manager work on top of the new engine; `master` + `main`(`misb-port-pin`) remain the clean fallback if a later engine-coupled regression surfaces.