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. ## 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 invent history when no vault data exists. ## Workflow ### Pre-Check: Vault Health Before running the recall helper, do a quick health check: 1. Resolve vault path from config 2. Check if `{vault}/raw/weeks/` has any `{slug}.json` files 3. If no raw entries exist at all: suggest `/tracework:capture` and stop 4. If raw entries exist but are older than 14 days: note staleness in output 5. If `recall_context.py` is missing: warn and suggest re-install If the pre-check passes, continu