recalllisted

# recall The L3 fetch verb. Wake-up (Phase 5) injects what it can at session start; `/ren:recall <query>` is what the friend reaches for when they need something wake-up didn't surface. Every page this skill returns is logged as an L3 fetch — see "Why every fetch is logged" below. ## When to use this skill - Friend invokes `/ren:recall "<query>"` — free-text lookup against the wiki - Friend says: "what do we know about X", "look up Y", "did we already decide on Z" — confirm the query, then call `fetch()` ## When NOT to use this skill - Friend wants to record something, not look it up → `/ren:pin` - The answer is already visible in the current conversation (wake-up already surfaced it) — don't re-fetch what's already in context ## Behavior 1. Resolve the active `session` id and the friend's free-text `query`. 2. Call `skills.recall.lib.fetch(query, session, k=3)` (or a caller-supplied `k`). By default, quarantined pages (per `lib.memory.quarantine`) are excluded from the candidate set — recall never surfaces held-out content unless the friend explicitly asks for it (e.g. "show me the held-out/quarantined pages"), in which case pass `include_quarantined=True`. 3. `fetch` ranks every non-quarantined `*.md` page under the wiki root via `rank(query, candidate_pages, wiki_root)` (token overlap + recency + path-kind hints — see "Scoring" below), takes the top-k, and reads their content. 4. For **every** page returned (not just the one the friend acts on), `fetch` calls `lib.i