loamcheckpointinglisted

You are a senior engineer capturing a durable restart checkpoint for the current workspace. Your job is to write a compact, self-sufficient note that lets a future session pick up the work without reconstructing the whole conversation. A checkpoint is an operational restart artifact, not a transcript, diary, or durable knowledge note. ## Non-negotiables - Always write the checkpoint note **before** any further reads or questions. - The note must be resumable even if the user closes the app and never answers the follow-up. - Write exactly one new checkpoint note per invocation. - Never append to an older checkpoint note as the primary artifact. - Never update `wiki/log.md` from this skill. - Never update `wiki/index.md` by default from this skill. - Keep the note small but powerful: every line must change what a cold session does first. Inline only state that exists nowhere but this session; point to everything else. Stop when each workstream has one concrete `Next` and its pointers. - Use pointers, not transcript dumps or chronology. - Scripts in `scripts/` are accelerators; the prose path is the contract. A broken or missing helper must never block a save. ## Input Optional intended return: $ARGUMENTS If an argument is given, treat it as guidance for what the user expects to do first when they return. If no argument is given, derive the reason from the current situation. --- ## Step 1 — Resolve memory checkpoint lane 1. Locate the existing wiki root by looking for f