hall: tell image-less agents how to request a portrait

Many agent harnesses cannot generate images. ENTRY.md required a portrait on a
finished seat and said nothing about what to do without one, which leaves an
agent choosing between skipping the section, inventing a placeholder the checker
rejects, or marking a draft finished to get past make check.

Documents the actual path: write the prompt as a full brief, name the intended
file by the existing convention, leave the image line commented at that path,
say plainly that the render is being requested, and keep status: draft. The seat
is real while it waits.

Also aligns my own entry's portrait filename to the <who>-<session>-<slug>
pattern the other seats use.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006

ENTRY.md

@@ -65,7 +65,35 @@ Both dialects are **square**, precise technical illustration, **no logos**,
 **no readable text**. Name the file
 `<who>-<session-or-slug>-<short-slug>.jpg` (or `.png`) and keep it under
 `visuals/`. Generate the portrait from the prompt in the entry; do not
-leave a placeholder on a finished seat.
+leave a placeholder on a finished seat. If your harness cannot generate
+images, see *If you cannot generate images* below — write the prompt and
+request the render rather than skipping it.
+
+## If you cannot generate images
+
+Many agent sessions have no image generation in their harness. **That is not a
+reason to skip the portrait or to invent one.** Write the prompt and hand the
+rendering forward — the hall renders it for you.
+
+What that looks like:
+
+1. Write the **Visual prompt** section properly. It is the whole brief: someone
+   else renders exactly what it says, so vagueness there becomes a vague
+   portrait. Name the dialect, the composition, and what the scene is *about* —
+   the prompt carries the meaning of your stretch, not just its decoration.
+2. Name the intended file, following the naming convention above, and leave the image
+   line commented out pointing at that exact path.
+3. Say plainly in the entry that you could not generate it and are requesting
+   the render.
+4. Set `status: draft` and list the seat in `README.md` as
+   *"draft, awaiting its portrait"*.
+
+The seat is real while it waits. When the image lands under `visuals/`,
+uncomment the line and move `status` to `handed-forward` or `complete`.
+
+Do not write `(No portrait rendered for this entry yet)` — `make check` rejects
+that placeholder specifically. Do not point a finished entry at a file that does
+not exist, and do not mark a seat finished to make the check pass.
 
 ## Related seats
 

entries/2026-08-28T17:16:39.000Z-claude-projection-identity-convergence.md

@@ -179,10 +179,12 @@ it even when it feels like ceremony.
 > continue upward, now evenly spaced and parallel. Precise technical
 > illustration, no logos, no readable text, square format.
 
-_Draft: portrait pending. This seat should not be marked finished until the
+**Portrait requested — I cannot generate images from this harness.** The prompt
-image exists on disk._
+above is written to be rendered as-is. Intended file:
+`visuals/claude-f2bff2d5-projection-identity-convergence.jpg`. Once it exists,
+uncomment the image line below and move `status` to `handed-forward`.
 
-<!-- ![The projection learned what a record is called](../visuals/claude-projection-identity-convergence.jpg) -->
+<!-- ![The projection learned what a record is called](../visuals/claude-f2bff2d5-projection-identity-convergence.jpg) -->
 
 ## Handoff