Run body and fire phases during scripted control locks
This commit is contained in:
1 parent
5876da112c
commit
c285b57091
35 files changed
+1503
-45
No files matched your search
+9
-3
@@ -74,9 +74,15 @@ plan in verified chunks. Earlier priorities below are a backlog.
|
||||
- [x] Full tutorial gadget re-enable tails and LV1B item1/7 restrictions; replaces
|
||||
previous prefix-only availability. Other level tails/selection remain open.
|
||||
- [x] Companion/shadow reset trace and equal-state AI guard; no blanket AI carry.
|
||||
- [ ] Next: uncontrolled body/controller/fire scheduling, body registration and
|
||||
appended-helper callback timing; then C4 support/response and shared viewport/
|
||||
DEFAULT handoff. C6 source channel allocation/clock/banks remains separate.
|
||||
- [x] Bounded uncontrolled body/fire versus controlled movement, ordered CAM/MCA/
|
||||
AI preparation, no repeated later-shot reset, held input restoration and authored
|
||||
player-transform synchronization; managed/GPU/native Linux checks.
|
||||
- [x] Local REA6.8.0/Ghidra12.1.4/full JDK21 launcher, selected native pseudocode
|
||||
Evidence/snapshot export; client MCP configuration unchanged. See rea.md.
|
||||
- [ ] Next: full Jimmy/base wrapper and body registration/helper timing; C4 support/
|
||||
response/root and shared viewport/DEFAULT handoff. C6 source channel allocation/
|
||||
clock/banks remains separate. Fire's missing Ghidra procedure definition is an
|
||||
analysis limitation; its immutable source-byte contract is already guarded.
|
||||
|
||||
1. Lab regressions are corrected and republished, with user verification of their
|
||||
own Windows build. Keep comprehensive native Windows driver/audio/input
|
||||
|
||||
Reference in new issue
Block a user