nextlisted

# Running the next node This skill holds no state in the conversation. Everything comes from the chain artifact and the state records, which is what makes it survive a `/clear`. ## 1. Read the state python3 "$CLAUDE_PLUGIN_ROOT/kl.py" state --chain-id <id> Every command in this skill takes `--chain-id`. Omit it only when you know this directory holds one chain. If a verb exits saying there is more than one unfinished chain, show the human the list it printed and ask which - do not pick. You get `node`, `hooks`, `gate`, `attempt`, `cap`, `status` and `note`. - `status: unstarted` - there is no chain here. Invoke the `start` skill, or say so if you were not asked to start one. Do not report this as finished. - `status: done` - the chain is finished. Say so and stop. - `status: blocked` - a gate is waiting. Invoke the `gate` skill. Do not proceed. - `note` non-empty - the node was rejected. That note leads this attempt. ## 2. Run the node's hooks, in order For each hook in `hooks`, look it up in `.kraft-lite/registry.yaml` and dispatch: - `kind: skill` - invoke that skill. If it is not installed, follow the entry's `prompt` instead and say you fell back. - `kind: prompt` - follow the instruction inline. - `kind: subprocess` - run the command, show its output. - `kind: agent` or `kind: builtin` - these are Kraft's, not Lite's. Stop and tell the human which hook is bound to one; do not improvise a substitute. - not in the registry at all - stop and say which hoo