attic-recalllisted

# Recall from the attic First, in the same shell command as anything below, locate the script: ```bash ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1) ``` Query: `$ARGUMENTS`. ```bash node "$ATTIC_JS" recall "$ARGUMENTS" ``` The script scores slug, index hook and item body, returns the best match, and lists alternatives. 1. No `.attic/` yet, or nothing matches: say so in one line and stop. Do not invent an answer or go read source files unless the user asks. 2. Several plausible matches: report the best one, then list the alternative handles in one line so the user can redirect. 3. Report the item in at most ten lines. Keep code, paths and commands verbatim. End with the handle. Never rewrite or delete items while recalling. ## Freshness Recall prints a trust line above the body, and for anything that is not current, a warning with the reason. Pass it on — an item's staleness is part of the item, and dropping it while quoting the conclusion is the failure this release exists to prevent. | What recall says | What you do | |---|---| | `current` | Use it. Mention the item is current only if asked. | | `possibly-stale` | Quote it, then say which files changed and that it needs checking before it is relied on. | | `needs-review` | A