Problem: the local CONTEST_ACTIONS list in `handle_command` was a manually maintained subset of ACTIONS that could drift — `pick` was already in it incorrectly, requiring a separate hotfix. Solution: encode `requires_context` on `ParsedCommand` at each parse-site in `parse_command`, where the action's semantics are already known. `handle_command` now checks `cmd.requires_context` directly, eliminating the parallel list. |
||
|---|---|---|
| .. | ||
| cp | ||