write_goal cannot draft goals in auto permission mode

Apologies if this is a naive report, but it felt related to the user experience. This can currently be worked around by manually exiting auto (or yolo) mode before invoking write_goal.

After a goal finishes in auto permission mode, invoking write_goal to plan the next goal fails to collect user
input:

  Could not collect your input
  AskUserQuestion is disabled while auto permission mode is active. Make a reasonable decision and continue
without asking the user.

This is an intentional design conflict:

• write_goal is defined as an interactive skill that drafts a /goal objective together with the user via
AskUserQuestion.
• auto mode explicitly tells the model not to call AskUserQuestion and to continue without asking.
• The permission policy enforces this by denying AskUserQuestion in auto mode, and tests confirm the block.

Because auto is the intended mode for unattended goal work, this creates a rough hand-off: the user returns to
write_goal after one goal ends, but the remaining auto state prevents the skill from functioning.

Proposal
When write_goal is invoked in auto/yolo mode, ask whether to exit auto so the goal can be drafted interactively.
For example:

• "Exit auto/yolo mode and draft the goal"

After the goal is drafted, CreateGoal can use the existing goal-start menu to let the user pick the mode for
the actual run.

Scope
Focus on the write_goal → next goal flow under auto permission mode.

Start at the write_goal → next goal flow and trace how AskUserQuestion is handled while auto/yolo permission mode is active. Review the permission-policy tests that confirm the block and the existing CreateGoal goal-start menu. Done means invoking write_goal in auto/yolo mode can transition to interactive drafting, while the actual run still lets the user choose its mode.