This is a comment left during a code review.
Path: src/discord/monitor/native-command.ts
Line: 118-121

Comment:
**Hard-coded command key in generic function**

`forceAutocomplete` embeds command-specific knowledge (`"acp"` / `"action"`) directly inside the generic `buildDiscordCommandOptions` function. Several other commands share the same structure — static choices arrays with fewer than 25 items (e.g. `/subagents action`, `/tts action`, `/session action`) — and would face the same inline-arg regression if Discord's behaviour applies to them too. Adding entries here each time would keep widening this special-case block.

A more extensible approach would be to add a `forceAutocomplete?: boolean` field to `CommandArgDefinition` and set it on the `acp` `action` arg at the definition site in `commands-registry.data.ts`, keeping this function generic:

```typescript
// In commands-registry.data.ts, acp action arg:
{
  name: "action",
  description: "Action to run",
  type: "string",
  forceAutocomplete: true,
  choices: [ "spawn", "cancel", ... ],
}

// In native-command.ts:
const forceAutocomplete = arg.forceAutocomplete === true;
```

This is a design preference for now — the current approach works correctly for the targeted fix — but worth noting if similar issues arise on other commands.

How can I resolve this? If you propose a fix, please make it concise.

This is a comment left during a code review.
Path: src/discord/monitor/native-command.ts
Line: 119-121

Comment:
**`forceAutocomplete` is silently suppressed when choices are absent**

Despite the name implying an unconditional override, `forceAutocomplete` has no effect when `resolvedChoices.length === 0` because of the outer `&&` guard:

```typescript
const shouldAutocomplete =
  resolvedChoices.length > 0 &&   // ← still blocks when choices = []
  (forceAutocomplete || ...);
```

Currently this is safe — the `acp action` arg always carries 15 static choices — but if someone ever refactored those choices away, the flag would silently stop working with no error or warning. Consider restructuring to make the intent explicit:

```suggestion
    const shouldAutocomplete =
      forceAutocomplete
        ? resolvedChoices.length > 0  // need choices to respond with
        : resolvedChoices.length > 0 && (typeof arg.choices === "function" || resolvedChoices.length > 25);
```

This makes the dependency on choices explicit for the forced case while keeping the same runtime semantics.

How can I resolve this? If you propose a fix, please make it concise.