onlisted

# squirrel-mode on /squirrel:on reverses `/squirrel:off` for the current session. It is a no-op, confirmed the same way, if the session was never turned off. ## Why this cannot flip a flag directly (ADR-0005) Exactly the same problem `/squirrel:off` has: this skill has no way to learn this session's own session id, so it cannot name the one file it would need to remove. It leaves a note for the `UserPromptSubmit` hook - which does see the real session id on the next prompt - and lets that hook clear the flag. ## Find the session off-token and working directory first Your context already contains two lines, injected at the start of this session: - `Session off-token: <token>` - the opaque token this skill embeds in the sentinel filename. Copy that exact string. Do not invent a token, do not shorten it, do not substitute a random suffix of your own: the `UserPromptSubmit` hook recomputes the same value from the session id it receives on stdin, and a token you invent is one it cannot match. - `Session working directory: <value>` - the exact value written into the sentinel's contents (legacy dual-match / cwd path). Never determine this yourself by running a command, inspecting your own state, or any other means: a value you determine yourself can disagree with the one the claiming hook compares against on the legacy path (a symlinked project path, a trailing slash, a different shell context), and the mismatch is silent. If the off-token line is missing entirely, or present