Recall

A brief from the prior session is injected at session start by the SessionStart hook (matcher clear).

If there is none, reply with exactly:

Nothing to recall — no brief was injected at session start: either this session didn't
begin with /clear, or no snapshot was taken. Run /snapshot in the session you're leaving,
then /clear, then /recall.

and stop. Do not guess what the previous session was doing.

Otherwise orient. Read only — make no edits to files this turn:

1. Read the whole brief.
2. Read the files relevant to the brief.
3. Don't open an artifact the brief lists — that is a whole page into a fresh context before you know you will touch it. Read it when you go to change it.
4. Check the brief's Running claims against live state — anything it says is still up. That section describes the moment it was written, not now, and the gap may have moved the tree under you. Verify only that section; re-checking the rest repeats the last session's work.

Then either:

• The brief and those files are enough — say what you would start on, in one line, and wait for the go-ahead. If the brief and the files disagree anywhere, add one line saying where; otherwise say nothing about it. Do not summarise the brief back.
• The brief leaves a genuine gap — call AskUserQuestion. Ask only for what cannot be found by reading. Never ask the user to confirm something the brief already says.