checkpointlisted

## Step 0 — resolve the binary No environment variable carries this plugin's path under Codex. Codex lists each skill with the absolute path of its `SKILL.md`; **this file** is at `<plugin-root>/skills/checkpoint/SKILL.md`, so the binary is two directories above it: ``` <plugin-root>/bin/admin.mjs ``` Resolve that to an absolute path from this file's own location and use it in every command below. Do not write `${CLAUDE_PLUGIN_ROOT}`: Codex sets no plugin-root variable of any spelling, so the shell expands it to nothing and `node /bin/admin.mjs` fails with ENOENT. Run the bundled script with the snapshot on stdin. It posts `POST /v2/control/checkpoint` under this session's run, and nothing else: ```bash node <plugin-root>/bin/admin.mjs checkpoint --label "<short name>" <<'SNAPSHOT' <the snapshot> SNAPSHOT ``` `--label` is required: a short name the user can ask for later. The snapshot is whatever is on stdin (`--file <path>` reads it from a file instead). The script prints the checkpoint id it was given back; relay it. It does not call an MCP tool — `mubit_checkpoint` left the default tool surface so that a session pays nothing to list it, and this script is how the skill reaches the same route. ## What goes in the snapshot It is stored **verbatim and unsummarised**. Nothing rewrites it, shortens it or extracts anything from it, which cuts both ways: whatever you write is exactly what a future reader gets, and a one-line headline restores nothing. Write it for someon