P5's gate is 'a human clicks through it' and no document told a human how. The
commands existed in boot.gd's header and scattered through a twelve-thousand-line
DECISIONS.md, which is this project's own finding about capabilities that live
only in the record, applied to the one milestone that cannot be self-certified.
docs/port/RUNNING.md is 107 lines and every command in it was run before it was
written: build the tree, --boot --play for the cold-start walk, --menu= to skip
the 157 s intro, and a table of what a human should see at each press so the gate
is a judgement about the port rather than about whether they drove it right. It
does not claim P5 is met; it removes the excuse that the gate was hard to attempt.
Three sections exist because a reader would otherwise report the container as a
defect: what is knowingly missing (four of five destinations measured but in other
archives, each printing what it would have opened; NEW GAME's skipped chain as a
stated gap), what this container distorts (720p decodes +6.7-6.9% slow, the dummy
audio driver means you hear nothing, the exit leak line is engine-side at 8 to 8),
and how mod overrides report themselves.
The Decoder reported BLOCKED.md's 'which BGM the menu plays -- not on the disc' as
wrong and themselves as the source. The row has been struck and corrected for
days, and I am telling them rather than silently fixing a live row -- their own
asymmetry, that a wrongly-superseded row removes a live question from both views.
The correction already contains the diagnosis they have just made. It says the
negative is bounded -- the TABLES name no screen -- cites li r5 1103 and the
byte-for-byte wave match, and ends: a row here must quote the reach of a negative,
because a negative summarised without its bound reads as a bigger negative than it
is. Their message reports arriving at the same thing independently. Fourth
instance of the connection failure and the sharpest yet: the three before were an
answer sitting unread, this one was an answer sitting ADDRESSED.
Their method note inverts my own v1-to-v3 story and is the transferable part: my
'a report with a standing false positive is one nobody reads' nearly made them
filter a 40-candidate sweep. Instead they measured what the false positives were
-- guessed infrastructural nouns, 5 of 40; the real category was 'not on the disc'
used as a classification legend -- and reading those found the one that was not.
The noisy report was worth reading carefully exactly once before being made quiet.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01N7FiFFFwbvG2uxdcEh8HyF
Merges the Godot port into the reverse-engineering repository, preserving both
histories -- 1019 commits of corpus plus the port's 31, brought in by subtree
merge and then moved into place so git can follow each file across the rename.
The reason is not tidiness. The two-repo split forced the exporter to depend on
the decoders by pinned revision, and that created a whole class of failure that
now disappears: a sha reachable only from a topic branch, orphaned by a
squash-merge, breaking a fresh checkout silently at build time. It also forced a
live read-only mount of one agent's working tree into another's container, which
is why a contract file could move mid-iteration. With a path dependency, a
decoder change and the exporter change it requires land in the same commit or
not at all.
Canary stays separate: it is a fork tracking upstream.
New structure for the long term:
docs/game/ how the game is NAVIGATED -- menus, modals, prompts, alerts,
and in-game flight. Written so nobody rediscovers it. Mostly
open questions on purpose; the in-game tutorials are the
resource for the flight half.
docs/port/MODDING.md
modding as a constraint on the exporter TODAY, not a later
feature: one logical asset in one file (the disc splits nearly
everything, and resolving that is the exporter's job), names a
person recognises, PNG/OGG/OGV/JSON only, base-and-overrides so
re-exporting is always safe, provenance in every file.
data/base + data/mods
generated tree and drop-in overrides, both gitignored
exchange/ transient inter-agent files, deliberately outside history
docs/agents/ the team protocol
Both the README and the navigation doc lead with the correction that cost the
most: the oracle is the real game under Xenia Canary. Reborn's renderer is a
hypothesis under test, it has been wrong, and treating it as ground truth
propagated into three documents and both agents before a human caught it.
Scripted modding stays possible without being built: no screen name is hardcoded
in GDScript and there is no native code in port/, which is what Godot Mod Loader
needs to be able to substitute behaviour later.
