recalllisted

# Session Start Recall This skill prepares a bounded project context at the start of a session so the developer and AI do not restart from zero. It is useful when durable Tracework memory exists; it is not required before daily, weekly, monthly, or query can produce their best available output. Recall is a durable-memory surface, not a report fallback. Unlike daily or weekly reports, it must not use git history to invent missing memory. ## Effective Facts Use the bundled helper's effective facts, correction_history, states and diagnostics. `--as-of` selects an explicit knowledge cutoff; `--end` bounds lifecycle state by work date. Query/Roadmap also accept `--start`. Do not restore retracted facts or close questions from similar wording. Accepted risks remain separate from mitigated risks. Missing captured_at limits exact as-of replay. Old reports are not rewritten; refresh a requested report through its writer. ## Scope - Intra-project only. - Raw entries are the semantic source of truth. - Artifact dossier entries are optional source navigation plus recorded context. - Decision context entries are optional synthesized decision-replay hints from `{vault}/raw/decisions/{project-slug}.json`. - If the saved decision index is missing, invalid, empty, or older than the raw entries, the helper refreshes the derived decision index from raw entries as a best-effort side effect, then uses that fresh Decision Context. - Do not use git commits as fallback in v1. - Do not in