session-loglisted

# When to Use Mid-session, when context is about to be compacted or handed to another agent and the work is not finished. Invoked by a person. **Adapting this skill:** filenames below name roles rather than literal paths. `db` throughout means whatever your durable store is called. Substitute your own filenames freely. `session-close` is expensive on purpose. It sweeps a whole session by category, updates every standing file, and runs mechanical checks. That price is correct once, at the end. It is wrong three times in an afternoon, and a procedure too expensive to run at the moment it is needed is a procedure that does not get run. The gap this fills is the compaction boundary, where reasoning is lost quietly and nothing is on fire. **Running this does not satisfy `session-close`.** It skips the sweep, the standing files, and the checks by design. A session that ends after a `session-log` is a session that was never closed. Say so in the log rather than letting the file's existence imply otherwise. ## What compaction actually destroys Only one thing, and aiming at it is what keeps this cheap. The tree survives compaction. Files written this session are still on disk, and a later session can read them. What does not survive is **why they look like that**: the alternative that was rejected, the constraint that ruled it out, the thing that turned out to be false halfway through. So do not restate what a file says. If a sentence could be recovered by opening the file it