checkpointlisted

# Save an iroha Checkpoint Do NOT run a CLI command for this. Call the iroha MCP tool **`create_checkpoint`** exposed by the `iroha` MCP server. **Keep it short, and spend the length where it is read back.** Only three fields reach a later session, so those are the ones worth writing carefully: | Field | Who reads it | What to put there | |---|---|---| | `unresolved` | `get_context` **and** `get_session_state` — the only field two consumers read | What a later session must pick up: the open question, the blocked step, the decision still owed. Specific enough to act on without this conversation. | | `summary` | `get_session_state` | What changed, what it verified, what is still open. A few sentences, not a report. | | `references` | Two different paths — see below | The issue/PR this belongs to, plus any canonical entity it builds on. | | `objective`, `implementation`, `validation` | Nothing reads these back | A terse record — the changed file and a one-line what, the command and its result. | | `proposals` | A human, in the dashboard | Reusable knowledge worth keeping past this session. The one field a reviewer actually sees. | `outcome` (`completed` / `partial` / `blocked` / `no_change`) is read back too — set it honestly; `partial` with a clear `unresolved` is more useful than `completed` on unfinished work. `references` is worth recording for both of its consumers. An `issue` or `pull_request` entry is extracted by `get_session_state`. Separately, **any** entry whose