journallisted

Write the journal entry for this session per Part 4 of the committed edition (the `journal/` section). This command is a thin binding: on any conflict between this file and the edition, the edition wins. When in doubt, load the Part: `bash "${CLAUDE_PLUGIN_ROOT}/scripts/part.sh" 4` ## When an entry is owed One numbered file per substantive session: a multi-hour build, a non-trivial planning decision, a QA pass that found real issues, a migration or gate transition. Not a five-minute chore. Substantive work done on another surface (the design project, Part 5c) lands as a companion entry, numbered in the same sequence, written from that surface's own record. Any deliberate deviation from the declared working mode (a model experiment, a process trial) gets one line stating the intent: the repo cannot tell drift from experiment; that line can. ## The entry - Next sequential number in `journal/` (`NNNN-<slug>.md`), same namespace as the existing entries; a bare number is never a valid reference, so cite as `journal/NNNN` elsewhere. - Role split, kept strict: STATUS.md is canonical current state; the journal is the diary. What happened, what surprised you, what dead ends you tried, what you would change about the spec with hindsight. Nothing in the entry substitutes for the STATUS.md, Closing-report, or ADR updates the session already owes. - Style: raw notes, no narrative smoothing, no em-dashes (as everywhere). Sections like "the actual session," "what surprised