Disambiguate "auto" permission mode from Claude Code auto mode (label as "accept edits")

[bborn]

What & why

Kyle reported that the word "auto" is overloaded in TaskYou's permission
settings (#tmp-taskyou-feedback):

I think Claude got confused on the auto mode because you might have used the
word "auto" originally to refer to the "accept edits" mode (before CC auto
mode was a thing). So in this case there's actually 4 permission sets.
--enable-auto-mode makes it available in CC.

TaskYou's auto permission set predates Claude Code's own auto mode (the
agentic flow gated by --enable-auto-mode). Our auto actually maps to
Claude's acceptEdits (--permission-mode acceptEdits): auto-accept file
edits while still prompting for risky actions. Reusing the word "auto" for that
made both agents and users conflate it with CC's separate auto mode.

This PR keeps the three permission sets TaskYou exposes (prompt / accept-edits /
dangerous) but renames the user- and agent-facing label from "auto" to
"accept edits" everywhere, and documents in code why CC's --enable-auto-mode
is a distinct fourth mode we do not surface.

Changes

• UI: settings form option Auto → Accept Edits, detail badge AUTO → ACCEPT EDITS,
  queue/confirm prompt "execute in accept-edits mode".
• CLI: --permission-mode help + queue notifications use accept-edits
  (with auto noted as a legacy alias).
• MCP: permission_mode schema advertises accept-edits and the description
  explicitly states it is NOT Claude Code's --enable-auto-mode; enum is
  ["default", "accept-edits", "dangerous"].
• Back-compat (no migration): NormalizePermissionMode now accepts
  accept-edits / accept_edits / acceptEdits (case- and space-insensitive),
  all mapping to the canonical stored value "auto". Existing DB rows, scripts,
  and --permission-mode auto keep working.
• Code comments on PermissionModeAuto / NormalizePermissionMode spell out the
  history so this doesn't get re-confused.

Tests

• internal/db: NormalizePermissionMode covers the new aliases + trimming/case.
• internal/executor: accept-edits resolves to --permission-mode acceptEdits.
• go build ./..., go vet, and all affected package tests pass.

QA evidence

Rendered against an isolated ty instance (VHS, real TUI).

Settings → Default Permission Mode — "Accept Edits" replaces the overloaded "Auto":

Detail header badge — active accept-edits task now shows ACCEPT EDITS (was AUTO):

_{(The "Claude failed to start" line in the full-screen capture is just the
isolated QA harness having no live tmux agent — unrelated to this change.)}

🤖 Generated with Claude Code