CYBERPUNK_MOD_TODO.md

Lilith Cyberpunk Mod Build: 1-10 Execution Ledger

Updated: 2026-07-11

1. Establish the authoritative source and deployment roots. Source is this repository; deployment is ~/.local/share/Steam/steamapps/common/Cyberpunk 2077.
2. Audit the existing source without overwriting the dirty worktree. The core full-stack validator passes: 17 engines, 12 data manifests, two quest chains, 96 generated weapons, 1,000,000 hats, 500 hell items, and 69 bios.
3. Repair stale staging paths. launch_verify.sh now defaults to the current Steam install, and reconciliation no longer treats the deployed rebuild as its own source.
4. Rebuild the Akashic/cerebellum context snapshot. The RAM snapshot contains 426 MB and 506 indexed source files under /dev/shm/gtc_cerebellum.
5. Unify the memory index schema. Bootstrap and verification now agree on the repository manifest, ripgrep index, deployment map, and freshness contract; all 10 cerebellum checks pass against 507 indexed files.
6. Finish core source release blockers. Lucifer and mirror spawns now use entity records, ley nodes use deterministic Night City anchors, manifest coverage is complete, and the core gate treats the planned Blender model pack as optional.
7. Compile and validate the REDmod archive with WolvenKit 8.19.0. The installed archive matches the build at SHA-256 4b7f1af8cb165f4fbbbac76cda467ff9847b943ad8f16b80dbdbf80a22a02324.
8. Reconcile packages with authoritative sources. MSN Integration and MSNWeaponOverhaul are synchronized; the installed legacy GTC rebuild was retained because no authoritative source checkout exists. Installed MSN coverage is 123/123 scripts with no root scripts, extras, missing files, or stale Star Wars tree.
9. Restore and verify runtime services and load order. RED4ext, CET, redscript, Codeware, TweakXL, and ArchiveXL are installed. The 29-agent router, NGD, cerebellum bridge, and Cyberpunk NGD are active and healthy on ports 8007, 8006, 8008, and 8009 respectively.
10. Complete the interactive in-game smoke test. Proton and NTSYNC launched the REDprelauncher with the deployed mod, but the bounded run produced no game process or RED4ext/redscript logs. A user must advance the graphical prelauncher, enter a save, invoke msn.lucifer.spawn, and exit once to produce test evidence.

Release Rule

The core build is compiled and deployed. Do not label the release in-game verified until step 10 produces a clean redscript/RED4ext log and observed gameplay evidence.