end-resumelisted

Resume a cost-quiescent `/end` explicitly. This is the only normal path that reopens the session-scoped launch gate; unrelated messages and timers do not. > **`/go-on` is the primary entry point for resuming.** It classifies the > stoppage from recorded evidence and routes here when the newest record is an > `/end`, forwarding `--resume-refill` verbatim — so nobody has to remember which > stop happened (Issue #1397; ladder: > `.claude/reference/universal-resume.md`). This command keeps working unchanged > and stays the direct path when you already know the session was ended; it > remains the executor, and a routed invocation is still an explicit human > invocation of it. Portable handoff documents keep naming `/end-resume` alone in > their `Resume command:` field — that field is lint-restricted to this command > because its reader may be outside this harness entirely. ## Step 0: Resolve state helpers Resolve `execution-pause.sh`, `background-task-registry.sh`, and `session-state.sh` using the standard stop-command order: skills worktree, then `$HOME/.claude`. Do not execute a current-checkout fallback: this command may be invoked from an unrelated or untrusted repository. Parse only `--resume-refill`. Before clearing the gate, require all three helpers to be resolved and readable. Use the registry to list the current session and use `session-state.sh` to read the repo key/refill state. If either inventory is unavailable or malformed, report a degraded resume and leave the