[FEATURE] Subtractive exclude-list for spinner verbs (remove one verb, keep the curated defaults)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

spinnerVerbs already lets me replace the verb list or append to it (shipped via #6814). What's missing is the opposite, subtractive operation: keep the curated default verbs but remove one specific word from the rotation.

This is not the same ask as "let me customize the spinner" (done) or "let me disable the spinner entirely" (#62392). It is specifically a blocklist / exclude-list, and it has been requested before in #27727 ("exclude some words when claude is thinking") — but that issue was auto-closed as a duplicate and is now locked, so there is no live home for it.

Why spinnerVerbs (replace) doesn't solve this: to drop a single word via replacement I have to hardcode and maintain the entire ~225-word list minus that one word — forever. I then lose the curated defaults and never receive any verbs the team adds upstream. tweakcc has the same limitation (it collapses everything to a single static verb). There is no way to say "defaults, minus this one word."

Proposed Solution

Add a subtractive setting that is applied after the default + append list is assembled, so it composes with the existing behavior:

{
  // existing, unchanged:
  "spinnerVerbs": ["Cogitating", "Noodling"], // replace or append
  // new — case-insensitive exact-match removal from the *active* list:
  "excludeSpinnerVerbs": ["Wandering"],
}

Resolution order: defaults (+ append / or replace) → then subtract excludeSpinnerVerbs. With this, a user keeps the full curated experience and any future additions, and simply never sees the one word they want gone.

Alternative Solutions

• A --prefix convention inside the existing spinnerVerbs array (e.g. "-Wandering") to mark a removal, avoiding a new top-level key.
• Either works; the key requirement is that it is subtractive over the maintained defaults, not a full replace.

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

A user finds one particular verb distracting or personally upsetting (the exact motivation in the now-locked #27727 — a verb that collided with a name tied to a difficult personal event). They love the rest of the verbs and want to keep them fresh from upstream; they just need that single word to never appear. Today their only option is to throw away the entire list, which is a poor trade for removing one word.

Additional Context

• Shipped, related but distinct: #6814 (replace/append spinnerVerbs).
• Open, related but distinct: #62392 (disable the rotation entirely / "Working…").
• Locked precise prior art: #27727 (exact same subtractive ask, auto-closed as duplicate → no live tracking issue exists for it).

Filing fresh because none of the above is both open and scoped to the subtractive/exclude operation.