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>

docker/agent/AGENT.md

@@ -55,28 +55,6 @@ python3 tools/re-capture/gmem.py find hex:820af844 400
 * A Bevy system-parameter conflict is invisible to the type checker and panics
   at startup. If you touch viewer systems, *run the binary*, don't just build it.
 
-## The Godot port
-
-The primary objective — see `docs/port/MISSION.md`. Two binaries are installed:
-
-```bash
-godot-headless --path port/ --script res://tools/check.gd   # no display needed
-DISPLAY=:99 godot --path port/                              # windowed, under Xvfb
-screenshot ~/shots/godot.png                                # then capture it
-```
-
-* **Godot is pinned to one version** in the Dockerfile. An engine bump changes
-  rendering, and this project diffs Godot's output against a reference renderer —
-  so do not upgrade it to fix a bug without saying that is what you did.
-* **`sylpheed-cli screen render` is the reference.** When Godot draws a screen,
-  render the same build with the CLI and compare. Where they disagree, one of
-  them is wrong; say which, and why, rather than tuning until they match.
-* **ffmpeg has libtheora**, which is the transcode target for video. Keep the
-  exact command in the exporter config — a modder who dislikes the quality should
-  be able to re-run it, not reverse-engineer what you did.
-* **Never commit anything under `export/`.** It is generated from the user's own
-  disc and gitignored. Code, schemas, `authored/` mappings and docs only.
-
 ## Reporting
 
 State what you measured, what you assumed, and what you could not settle. If a