REJECTION_MOVES

const REJECTION_MOVES: "You may call the same command with a justification, or call a different command." = 'You may call the same command with a justification, or call a different command.'

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/shell/rejection.ts:56

The moves §7 requires a JUDGED rejection to name — and only moves the model actually has.

[[EXT-106]] §5 — “ask the user if there is no way around it” was not one of them. It named no mechanism, so the model did the only thing the sentence could mean: it wrote prose asking for a confirmation and ended the turn. That text never reaches the gate. The confirmation cannot arrive, the next call meets the identical deterministic floor, and the run ends having handed the user homework that cannot be done — while the two remedies that would have worked (an approvals.allow entry, or a different rung) went unnamed.

Removing it costs the model nothing it could use. Where these two moves genuinely run out, §5.3 spends the negotiation bound and the call goes to a person through the gate — which is the escalation the removed sentence was pantomiming. Do not restore it, in this or any other wording, until there is a TOOL that escalates: the fault was never the phrasing, it was offering an exit with nothing behind it.