atlas-resumelisted

# atlas-resume — on-disk run resumption (F1 / P11) **Invoke this skill directly (`/atlas-orchestrator:atlas-resume`) whenever you suspect an unfinished run — this manual invocation is the MANDATORY, load-bearing recovery path, never merely a backup to an assumed-working hook.** A `SessionStart` hook (`hooks/session-resume.sh`) also exists and prints a pointer when it finds an unfinished `.atlas/*/state.json`; a live probe against a real Claude Code CLI empirically confirmed that hook's stdout does land in a started session's context (see `probe/probe_cc_sessionstart_injection.sh`), but only for the `startup` source, on one CLI version, via one throwaway scratch plugin — not a guarantee across every build, every one of the hook's five registered sources, or every real user's plugin-loading configuration. Do not wait for that pointer to appear before resuming by hand; run this skill on suspicion alone. This is a **pure instruction**. It injects **no live state** — it only tells you *where the durable ledger lives on disk* so you can find it yourself. atlas-orchestrator keeps its authoritative run state on disk (never in context), because the full orchestrator prompt is **not guaranteed to survive compaction**. This skill body IS re-injected at session start and after compaction, so it is the reliable pointer back to that on-disk state. On the 256K models a multi-node run compacts often (the root reads every node's return into its own context), but **on the 1M `k3`/Kimi-3 mode