feat(code): configure Auto goal criteria acceptance

[Mason Daugherty (mdrxy)]

Auto mode now reviews generated goal acceptance criteria by default, while users who prefer uninterrupted goal setup can opt into applying them automatically. Manual mode always reviews and YOLO remains automatic.

---

Users who have not already configured a preference see a one-time selector the first time they create or amend a goal in Auto mode:

• Review before applying is recommended and preselected.
• Apply automatically in Auto mode enables the uninterrupted flow.

A Manual or YOLO user is prompted the first time they create or amend a goal after switching to Auto. Explicit environment or TOML settings suppress the selector, and a versioned state marker prevents it from reappearing once answered.

Configure the Auto-mode preference in ~/.deepagents/config.toml:

[goals]
auto_accept_criteria = true

Or set DEEPAGENTS_CODE_GOAL_AUTO_ACCEPT_CRITERIA=true. The environment variable takes precedence over TOML, invalid environment values fall through to TOML and then the safe false default, and the preference is resolved live on each proposal decision—so file or environment edits apply the next time a goal proposal is created, amended, regenerated, restored, or mode-resolved, not only after relaunch. If the preference cannot be resolved, it fails closed to review and logs.

New, amended, regenerated, restored, and mode-transitioned goal proposals all resolve through the same live policy so the selected behavior is consistent throughout the session.

Example: Manual user later switches to Auto

1. Mason works in Manual and runs /goal ship OAuth. No preference selector appears, because the setting only affects Auto.
2. Later he enables Auto, then runs /goal add refresh tokens or /goal amend include passkeys.
3. Because Auto still has the built-in default and no marker, he gets the one-time selector with Review before applying preselected.
4. His choice is saved to config.toml and the versioned marker is set so the prompt does not return.

Example: File edit takes effect on the next proposal decision

1. Mason is already in Auto with review selected.
2. In another editor he sets auto_accept_criteria = true in ~/.deepagents/config.toml.
3. Nothing changes immediately.
4. On the next create, amend, regenerate, restore, or mode-resolution of a goal proposal, dcode re-reads the preference and auto-applies.

Example: Same live policy across proposal paths

• New: /goal ship login drafts criteria and either reviews or auto-applies under the current Auto/YOLO policy.
• Amended: /goal amend also require passkeys regenerates the checklist and resolves it the same way.
• Regenerated: feedback on an open review produces a new proposal that uses the policy in effect when it arrives.
• Restored: resuming a thread with a pending proposal resolves that pending state through the same gate.
• Mode-transitioned: enabling Auto or YOLO with a mounted review re-resolves that pending proposal immediately under the live policy.

---

Other nits:

• Removed /goal accept and /goal edit subcommands. These were redirect-only handlers that pointed users to the inline review prompt; the review prompt's own keybindings are the real actions, so the subcommands were a discoverability dead end.
• Simplified the /goal usage text to describe what /goal does rather than enumerating per-mode behavior. The mode-specific behavior is discoverable through the app and the first-run preference screen.
• Removed the "Goal criteria automatically accepted without manual review." toast that fired on auto-accepted proposals. YOLO's contract is no prompts, and opted-in Auto users already know they opted in, so the toast was noise for both.