Problem
Every WP-CLI invocation with Data Machine active emits nine unrelated registration warnings because command-owned options redeclare WP-CLI global arguments. This was reproduced with a read-only wp intelligence --help invocation.
The affected commands are datamachine memory compose (--quiet), datamachine auth revoke (--user), datamachine email send-queued (--context), and datamachine chat list/get/create/delete (--user and/or --context).
Evidence
The CLI bootstrap registers every CommandRegistry entry on startup. The command documentation declares these conflicting option names. In particular, the command-owned --user and --context values have distinct application meanings: per-user credential or chat-session targeting, email template data, and chat execution mode, while WP-CLI reserves those names for bootstrap user and load context.
Acceptance criteria
- Each command preserves its documented application behavior with non-conflicting option names or an explicit, documented use of the corresponding WP-CLI global behavior.
- A generic WP-CLI command with Data Machine active registers without these nine warnings.
- Help and examples distinguish Data Machine command options from WP-CLI global options.
- Add an automated registration-level check that catches global-option collisions across the CommandRegistry surface.
AI assistance
OpenAI gpt-5.6-terra via OpenCode reproduced sanitized bootstrap warnings, inspected the installed runtime and current command registry, checked existing Data Machine trackers, and drafted this report under Chris Huber direction.
Problem
Every WP-CLI invocation with Data Machine active emits nine unrelated registration warnings because command-owned options redeclare WP-CLI global arguments. This was reproduced with a read-only wp intelligence --help invocation.
The affected commands are datamachine memory compose (--quiet), datamachine auth revoke (--user), datamachine email send-queued (--context), and datamachine chat list/get/create/delete (--user and/or --context).
Evidence
The CLI bootstrap registers every CommandRegistry entry on startup. The command documentation declares these conflicting option names. In particular, the command-owned --user and --context values have distinct application meanings: per-user credential or chat-session targeting, email template data, and chat execution mode, while WP-CLI reserves those names for bootstrap user and load context.
Acceptance criteria
AI assistance
OpenAI gpt-5.6-terra via OpenCode reproduced sanitized bootstrap warnings, inspected the installed runtime and current command registry, checked existing Data Machine trackers, and drafted this report under Chris Huber direction.