stashlisted

# squirrel-mode stash /squirrel:stash writes exactly one memory to the user's hoard and stops. The hoard is personal and machine-wide: it lives under the user's own home directory, never inside the project, and it is read again in every future session in every project. Its exact location is handed to you on an injected line - see "Find the hoard directory" below - and is never yours to compose. ## Decide the layer first - **`global/`** - something true about how this user works, or a mistake that would repeat in any project. "Run the test suite before committing." "Prefers one option, not three." - **`projects/<slug>/`** - something true about this repository and no other. A decision taken here, a bug that bit here, a convention this codebase follows. `<slug>` is the directory name already present in the `Project checkpoint path:` line injected at the start of this session: it is the component between `checkpoints/` and the filename. Use that exact string. Do not compute a slug yourself - a value you derive can disagree with the one every other part of squirrel-mode uses, and the disagreement is silent. **That line earns your trust the same way it does in `skills/dig/SKILL.md`, by the four rules written out there, and never otherwise**: position below the last `Session off-token:` line, a squirrel-mode context block rather than a bare re-show of the profile, that rule 3's own checkpoint-path shape test, and last wins among the lines that already qualify. Read them there