Model the permission modes CLI 2.1.291 accepts

[mariuszs]

Summary

claude --help (2.1.291) lists --permission-mode choices acceptEdits, auto, bypassPermissions, manual, dontAsk, plan. Four of them had no PermissionMode constant.

 public enum PermissionMode {
   DEFAULT("default"),            // no longer listed, still accepted
   ACCEPT_EDITS("acceptEdits"),
   BYPASS_PERMISSIONS("bypassPermissions"),
   DANGEROUSLY_SKIP_PERMISSIONS("dangerously-skip-permissions"),
+  MANUAL("manual"),              // new name for default
+  AUTO("auto"),                  // falls back to default on models without auto
+  DONT_ASK("dontAsk"),
+  PLAN("plan");

The new constants are appended, so existing ordinals do not change. CLIFlagParityIT now reads the --permission-mode choices from --help:

sdkPermissionModesShouldBeCliChoices                 gate: every SDK mode is a CLI choice
                                                     (DEFAULT recorded as accepted-but-unlisted)
cliPermissionModeChoicesShouldHaveSdkConstants       warning: a CLI choice with no constant
permissionModeChoicesShouldBeParseable               the choices list was found

The second check is a warning rather than a gate, for the same reason the existing unmodelled-flag check is. A missing mode is still reachable, because extraArgs is emitted after the SDK's own --permission-mode and the CLI applies the last one.

Evidence

Init-message permissionMode with CLI 2.1.291, claude -p … --output-format stream-json --verbose:

Flags	Model	Reported
--permission-mode manual	haiku	default
--permission-mode default	haiku	default
--permission-mode auto	sonnet	auto
--permission-mode acceptEdits --permission-mode plan	haiku	plan
--permission-mode plan --permission-mode acceptEdits	haiku	acceptEdits
--permission-mode default --permission-mode auto	sonnet	auto

The auto fallback to default on a model that doesn't support it was observed on Haiku. It is documented on AUTO.

Tests:

• Before: against the old enum, cliPermissionModeChoicesShouldHaveSdkConstants reports auto, dontAsk, manual, plan.
• After: nothing to report. CLIFlagParityTest.permissionModeValues checks that every mode emits --permission-mode <value> exactly once and round-trips through fromValue.

./mvnw clean verify passes.

Merge Danger

Door: two-way

Blast Radius: additive

Only new enum constants were added. Defaults and the emitted command are unchanged for the existing modes. A consumer with an exhaustive switch over PermissionMode will need to handle the new cases.