session-searchlisted

# Session Search Use Session Index to move from a user’s vague reference to past work into scoped, inspectable evidence. The canonical LLM-facing surface is this skill plus CLI `--help`; the README is not required for operation. ## Choosing a path Most lookup tasks are either: - `find` → choose a candidate by `session.summary` and `match` → `inspect --ref ...` - `query --schema` → SQL aggregate/custom rows → construct refs → `inspect --ref ...` Evidence escalates in tiers: scoped `inspect` packets first; whole generated artifacts (Clean Transcript, Tool Log, Subagent Run transcripts) when a packet is insufficient; raw Source JSONL only when generated artifacts are insufficient. Stop once you have enough evidence to answer the user's question — usually one or two `inspect` calls on the best candidates. Widen the search only when the evidence in hand is insufficient or contradictory. ## Commands Examples use the Pi install path; substitute your install's skill root (for example `~/.claude/skills/session-search`) or run `uv run cli.py <command>` from the repo. Wrappers resolve the repo through their own symlink. ### current — identify this active session ```bash uv run ~/.pi/agent/skills/session-search/scripts/current.py # Canonical Session ID uv run ~/.pi/agent/skills/session-search/scripts/current.py --path # Clean Transcript path; warns if missing uv run ~/.pi/agent/skills/session-search/scripts/current.py --cleaned-paths # Clean Transcript + Tool Log pat