atlas-resume
atlas-resume — on-disk run resumption (F1 / P11)
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. kimi-atlas 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 model compaction is
RARE — this resumption then covers turn-kills and crashes more than compaction. It stays
load-bearing (correctness must survive it either way), just no longer the common path at 1M.
What to do at session start
Script-call convention — every script call in this file (both paths below) runs as
PYTHONSAFEPATH=1 PYTHONPATH="${KIMI_SKILL_DIR}/../.." python3 -c "from scripts import <mod>; …".
PYTHONSAFEPATH=1 is mandatory: the working directory here is the user's own project.
Without PYTHONSAFEPATH that directory outranks PYTHONPATH, letting the project replace scripts/ctxstore.py or
scripts/resume.py with its own. This skill runs at session start — before the atlas SKILL
and its interpreter floor guard — so nothing else will catch a bare invocation here.