## Fix: support unquoted --flags in wrap commands for effect/unstable/cli

[jfet97]

The new effect/unstable/cli lexer tokenizes all --flags as LongOption tokens upfront, at the lexer level, before any command routing happens. When a subcommand like packagejson or index-multi receives args like tsc --build, the lexer classifies --build as a LongOption. The subcommand parser then discards it as an unrecognized flag — unlike the old @effect/cli which treated unrecognized flags as positional args.

Why -- doesn't work: the lexer splits on -- at the top level, putting everything after it into trailingOperands. But these operands stay at the parent command level and don't propagate down to the subcommand's argument parser.

Solution: an argv pre-processor joins all args after a wrap-enabled subcommand (index-multi, packagejson, packagejson-packages) into a single string element before the CLI parser runs. The lexer sees one Value token (e.g. "tsc --build") instead of Value("tsc") + LongOption("build"). The wrap handler already passes this string to sh -c, so the shell handles the splitting correctly.

No changes needed in consumer projects (macs-scanner, configurator, signalznow).

Tests

• 18 unit tests for the argv patch function (wrap/non-wrap subcommands, edge cases)
• 5 e2e tests that spawn the actual CLI binary and verify the wrap command is executed, output is correct, and exit codes propagate