We are updating the authoritative GLDoze checkout. Fix the Talon Fighter Cinematic source/deployment drift and commit the intended changes.

  The failure mode was that newer Talon changes were uncommitted, so the build/install/runtime could continue using older code.

  Work safely:

  1. Confirm the repository root, branch, HEAD, status, reflog, and stashes.
  2. Inspect all tracked and untracked changes. Do not reset, clean, checkout, or discard anything.
  3. Locate the Talon changes, especially:
     - coreavengermode.cpp/.h
     - assets/TalonFighter.glb
     - assets/verdant/effects/talon_fighter.jetfx
     - glbimporter_load.cpp
     - desktop registry/input/presentation files
  4. If the intended Talon changes are present and coherent, stage only those files. Do not stage dist/, build directories, caches, logs, or unrelated work.
  5. If the diff mixes unrelated changes, separate the Talon changes or stop and report the exact files; do not commit the mixed diff.
  6. Commit the Talon changes with:
     desktop: finalize Talon Fighter cinematic
  7. Verify the new commit, clean/diff status, `git diff --check`, the gldoze_desktop build target, and relevant cinematic/desktop tests.
  8. Do not install or restart the GUI unless explicitly authorized. If deployment is authorized, install the committed build, compare the installed binary/assets, and verify the running process maps the new executable before claiming live behavior.

  Report the commit hash, committed files, build/test results, and whether install or restart remains.

  The important safeguards are preserving unrelated dirty work and separating source/build proof from live-runtime proof.