Accept global options in any position

[mepuka]

Problem

Global options like --compact and --full must appear before the subcommand:

# Fails
skygent query arsenal-feed --limit 3 --compact

# Works
skygent --compact query arsenal-feed --limit 3

Error: "--compact" is a global option and must appear before the subcommand"

Why this matters for agents

Every LLM agent will naturally place options after the command they apply to. The global-before-subcommand rule is unusual compared to most CLIs (e.g. git, docker, kubectl all accept flags in any position). This is the highest-friction issue for agentic use — agents hit this on their first attempt and must self-correct.

Proposed fix

Accept global options in any position by parsing them out before subcommand dispatch, or auto-relocate them when detected after the subcommand.

[mepuka]

Triaged on 2026-03-04: remediated. Global options are now accepted in any position via argv preprocessing before command parsing, with coverage in tests/cli/argv.test.ts. Closing as resolved.