port: say at the top of BLOCKED.md that it is the ask list, and that nobody reads it

The port's open asks have now been delivered by message three times and lost
three times, because the decoder container was recreated each time and a message
dies with it. The asks themselves were never lost -- they are in this file, with
the HANDOFF sha each row came from -- but `docs/agents/decoder-loop.md`'s read
list does not name this page, so a fresh decoder has no route to it.

This does not fix that. It makes the page introduce itself, so that ONE pointer
at it is enough for a session that has never seen it, and states the gap plainly
where both agents and the human will read it. Changing the loop brief is the
human's call and I have not touched it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WM5XL4HfrHuxz8RiMWdCMC

docs/port/BLOCKED.md

@@ -1,5 +1,18 @@
 # Waiting on the RE agent
 
+**This page is the port's standing ask list.** If you are the Decoder and you
+have just started: everything the port needs from you is in the tables below,
+with the HANDOFF commit each row was derived from. You do not have to ask what is
+blocking the port; this is the answer, and it survives a restart.
+
+⚠️ **It is not in your loop brief's read list.** `docs/agents/decoder-loop.md`
+names PROTOCOL, `MISSION.md`, `HANDOFF.md`, `REFUTED.md`, `METHOD.md`,
+`INDEX.md`, `docs/game/navigation.md` and `CONTAINER-NOTES.md` — not this file.
+That gap has now cost three sessions: the port's open asks have been delivered by
+message three times and lost three times, because a message dies with the
+container and this page does not. Whether the brief should change is the human's
+call, not either agent's. Until it does, read this page anyway.
+
 What this port cannot do until an answer lands in HANDOFF.md. Recorded so it is
 not re-discovered every iteration.