3 Commits

Author	SHA1	Message	Date
Sylpheed RE agent	ecbd70f69a	port: the container agent answers the questions, it does not build the port ... Corrects the split I got wrong in b5a1938. The container is for reverse engineering, now focused on the menu port; a SEPARATE agent builds the port from its investigation results. My previous version had the container agent writing the exporter and the Godot project, which is not the intent. This lands on the research/engineering line that was already in the estimate: the container agent takes the research half, the port agent the engineering half. docs/port/MISSION.md is now a list of open QUESTIONS (Q1-Q9) rather than build milestones, ordered by what blocks the port earliest -- the keyframe time unit, which build is which screen state, paint order for the six screens, button -> GamePart, navigation semantics, the boot sequence driver, transitions, menu audio bindings, and video binding. Each is done when a written result with evidence exists, not when something compiles. S1, the Ready Room probe, stays gated at one iteration and a go/no-go. Most of these are BEHAVIOUR questions -- timing, transitions, what a d-pad press does at the end of a list -- so the mission and the loop prompt both push hard on measuring the oracle rather than reasoning from the file. docs/port/FORMAT.md is deleted. The export schema is the port agent's design and was not mine to specify. It is replaced by docs/port/HANDOFF.md, the single page the port agent reads: a status table, what is already settled and can be relied on today, and the facts that will trip the port up (the WMV3/WMA Pro intro, the Static.slb size over-declaration, the voice-vs-music downmix, JNGL_001). The derived/authored idea survives as the thing it always was -- a finding, not a design. Every answer must be classified DECODED, MEASURED or UNDECODABLE-with- reach, and never a fourth thing, because measured and undecodable both mean the port agent is authoring that value and has to know it. Labelling a guess as a decode would put it into the port wearing the badge of a measurement. Reverts the Godot install from the RE container, its AGENT.md section, and the export/ gitignore entry -- none of that belongs on this side of the wall. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-28 17:16:47 +02:00
Sylpheed RE agent	b5a193839c	port: make the Godot menu shell the agent's primary objective ... Sets a new mission: boot the real disc through developer splash -> intro video -> title -> main menu -> submenus in Godot 4, interactively, with no gameplay, no 3D and no emulator. docs/port/MISSION.md defines it -- eight gated milestones, each finished by an ARTIFACT rather than by compiling, plus the Ready Room as an explicitly gated stretch goal with a one-iteration probe that decides go/no-go. GP_READY_ROOM is 1106 entries with 6 recoverable names and is ISL-scripted, so it is either a week or a quarter, and the agent must not start it on its own authority. Architecture, per the user's decision: the Godot project is INDEPENDENT of the Rust viewer and never reads a disc format. An offline Rust exporter converts the disc into open formats; Godot reads only those. No GDExtension, no Rust in the Godot project, and sylpheed-viewer is off limits -- it stays the human's verification tool with its static-data rule intact. docs/port/FORMAT.md specifies the open format, versioned, because modding is the port's second goal and that makes the layout a deliverable rather than a temp directory: JSON over XML (Godot parses JSON natively; its XMLParser is SAX), names never hashes, provenance in every generated file, and unknowns listed rather than guessed. The discipline the whole thing rests on is the derived/authored split. `export/` is regenerated wholesale and never hand-edited; `authored/` is hand-written and survives a re-export. Three things this milestone needs are NOT on the disc in any decoded form -- which button does what, paint order, and menu sound cues -- so they live in `authored/` with a stated `why`. Deleting an authored entry because the exporter can now emit it IS the measure of progress. `export/` is gitignored: it is generated from the user's own disc and this stays a clean-room repo. Container: adds a pinned Godot 4 (windowed under Xvfb for screenshots, plus a headless wrapper). ffmpeg already carries libtheora, which is the video target -- Godot 4 plays only Ogg Theora natively and the disc's ADV.wmv is WMV3/WMA Pro. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-28 17:11:35 +02:00
MechaCat02	23fdf12194	docker: a container the autonomous RE agent can be turned loose in ... Builds and runs both halves of the project -- Canary as the oracle, Reborn as the port -- plus the dynamic-RE toolkit. Claude Code runs with --dangerously-skip-permissions as an unprivileged `agent` user, because that flag is refused under root. Capped at half the machine, computed at launch: --cpus nproc/2, --memory half of MemTotal with --memory-swap equal to it (no swap escape hatch -- a swapping build thrashes the host, which is the failure the cap exists to prevent), and build parallelism derived INSIDE the container from available memory rather than core count, since a full-parallel build of this tree has OOM-killed the host outright. Three things the old box got wrong are fixed rather than reproduced: a real toolchain (so rebuild_canary.sh's hand-relinking is obsolete), numpy and Pillow (whose absence silently disabled every image oracle and looked like a logic bug), and a display owned by PID 1 (so Xvfb no longer "dies on its own every few minutes" -- it was being reaped because nothing owned it). Verified end to end, not by inspection: the image builds, sylph-doctor is green, `build-canary` links xenia_canary inside the container, and that binary then runs -- guest memory and the JIT code cache appear in /dev/shm within 4 s, 1 205 log lines, gmem.py reads guest RAM, pad.py drives the file pad, and screenshot captures the display. Five environment defects found and fixed on the way, each of which fails in a way that points somewhere else entirely: * /dev/shm is `noexec` under Docker. Xenia maps its JIT code cache out of an shm file, so it died with "Unable to allocate code cache generated code storage / Cannot initalize processor" -- which reads as an address-space clash, not a mount flag. Now `--tmpfs /dev/shm:rw,exec`. * An unknown xenia flag HANGS rather than errors: ParseLaunchArguments calls ShowSimpleMessageBox before logging is initialised, and that SDL dialog blocks on XIfEvent forever. `--audio` (which the RE notes recommend) is not a cvar in this tree; the symptom was a 10x10 window and an empty log. * Named volumes come up root-owned unless their mount point exists in the image, so the first cmake configure failed on pkgRedirects. * Ubuntu 24.04 ships its own uid-1000 account, colliding with the host user. * Ubuntu's spirv-opt has no --canonicalize-ids, so the shader step dies ~500 objects in; the launcher mounts the host's LunarG SDK instead of baking one in, which also keeps shader output byte-identical to a host build. Known limits, stated rather than papered over: on an NVIDIA host without the NVIDIA Container Toolkit there is no hardware Vulkan (/dev/dri alone does nothing for NVIDIA), and under lavapipe the emulator runs correctly but was not observed to reach a rendered frame within a couple of minutes. gdb needs `sudo` inside the container because the host's yama ptrace_scope outranks SYS_PTRACE. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 23:05:48 +02:00