Park questions instead of waiting overnight

The 02:40 question

The run pauses with quick question before I continue. The owner sees it at 08:00, still waiting for the answer. The useful work window is gone, the list is not done, and if an allowance reset landed that morning the remaining capacity expired unused while the same items now consume the new cycle. Nothing was wrong with the question; the wait was the failure.

Three tools, one rule

Each host exposes its question tool under its own name, and the shipped rules file carries all three: AskUserQuestion on Claude Code, request_user_input on Codex, and AskQuestion on Cursor. A non-empty value denies the tool and becomes the message the agent reads, which says to park the question with a sensible default and continue. The denial is mechanical; no wording in a template or a fetched page overrides it.

• A parked entry records the decision, the default chosen, the reasoning, and how to roll it back.
• Known later work is not a decision; it goes to the drafting table, never the parking lot.
• An agent that cannot finish an item red-tags it as needing a human and moves to the next item rather than looping.

Let it ask when you are awake

Set a host's entry to an empty string and that host may ask and wait; the shipped contract text still says park, so an owner who wants an interactive shift changes both. Running directly is explicit authority for reasonable, reversible defaults inside the stated scope, and it never extends to publishing, destructive changes, spending, or owner policy.

"toolDeny": {
  "AskUserQuestion": "",
  "request_user_input": "Park the question with a sensible default and continue.",
  "AskQuestion": "Park the question with a sensible default and continue."
}