Run body and fire phases during scripted control locks

This commit is contained in:
UnixNight committed 2026-10-26 12:21:25 -04:00
1 parent 5876da112c
commit c285b57091
35 files changed
+1503 -45

No files matched your search

+49
View File
@@ -1,5 +1,54 @@
# Progress — 2026-10-26
## Uncontrolled-player implementation and REA
Continued C3 into source control/body/fire boundaries. Original475CA0/frame/body
eligibility is separate from controlled pointer5099E4. Movement437940 has an
identity gate after base/timer work;421FB0 fire has no raw-control gate. CAM,
initial MCA and AI preparation order differ; later MCA shots do not repeat it.
Source-byte reports/helpers/tests: uncontrolled-player.md, uncontrolled-physics.md
and cutscene-preparation.md under checkpoint/. Investigators supplied independent
player/control traces; primary completed physics and preparation work when agent
capacity ended. All file ownership is now primary.
Implemented LabSimulation controlled-input/controller gates while existing body
physics and owned fire continue. Preparation clears speed/velocity only; queued
impulse/acceleration and mode/jump/hold/fire are independent. Ordinary grounded
radius60 is outside the movement gate. PlayerSceneBinding connects ordered raw
preparations and authored AI root/yaw; STOP observation follows physical clear.
An initial MCA with first target none returns instead of executing completion.
Force Control stays an effective override; preparations use authored ownership.
Headless story pre-roll uses the same phases; F1/practice/inspect still pause them.
Full wrapper/base transforms/ceiling response, other gadget/class effects and
registry/cadence remain explicit gaps in control-phase-implementation.md.
Targeted movement24 groups, coupled director tests and the32-frame airborne
control fixture pass. Native Linux GTX1070 at1280x720 passes Carl/control phases,
F1 menu/Force Control and F3/tools/checkpoint reload, with zero enabled Vulkan
validation errors. The input-only lab replay now uses the actual binding; its
old coasting turn missed the narrow exit. Down braking before large turns reaches
outside with score150, one practice No, owned jetpack, zero jumps and6 wall hits.
No physical response/task gate was changed for that replay. A corner snapshot
is retained for C4. Logs: artifacts/uncontrolled-phases/.
REA MCP connected but lacked native providers. Installed the verified official
Ghidra12.1.4 ZIP locally and extracted matching full Ubuntu JDK21 packages under
.tools (system Java21 was runtime-only). Existing Node24/public REA6.8.0 launcher
is selected by ignored .tools/rea.env and scripts/rea.sh. Client registration was
not changed. Local Unix IPC needed the approved execution allowance. Five source
procedures were decompiled and byte-cross-checked; complete Evidence/snapshots are
on disk.421FB0 maps correctly but has no recognized Ghidra procedure in this
profile; existing byte/vtable evidence remains authoritative. See docs/rea.md and
the control-phase report's Evidence IDs. No original game execution or new native
Windows runtime comparison is claimed by this setup.
Final C3 validation: full scripts/test.sh passes (integration-final.log):93
Python checks, all managed groups including24 movement, updated input-only route,
27 GPU render completions with zero enabled Vulkan validation errors, SDL dummy
lifecycle and539 unchanged originals. Coupled director tests include body-before-
STOP observation and the initial empty-MCA return. Four native window commands
pass (five scene renders) in native/*.log. No native Windows runtime is added.
## Retained-state implementation continuation
Read prompt.MD in full and resumed C3/C7. Three independent investigators owned