fix(skills): read positionals declared with .addArgument() - #13009

check:agent-skills-sync fails on every branch, and regenerating with --apply does not fix it — it makes it worse:

-### `tunnel create [type]`
+### `tunnel create`

Why

Commander takes a positional two ways: inline in .command("stop <type>"), or through .addArgument(new Argument("[type]")). cliRegistryParser matched only the first:

const COMMAND_RE = /\.command\(\s*["']([^"']+)["']/g;
const OPTION_RE  = /\.option\(\s*["']([^"']+)["']/g;
// nothing for .addArgument

So tunnel create came out bare, disagreed with the committed page, and the gate reported drift that it could only "resolve" by deleting a real argument.

Two commands use that form, and the second is worse than cosmetic:

An agent reading the second page was told to run omniroute resilience set with no argument.

Result

Agent Skills Generator [dry-run]
Generated: 0 · Unchanged: 46 · Pruned: 0 · Orphans: 0 · Errors: 0

Exit 0, with tunnel create [type] reproduced rather than removed. The only regenerated content is the two resilience lines that gain <name>.

What this deliberately does not do

The parser flattens subcommands onto the family name, so resilience profile set still publishes as resilience set. Resolving the receiver chain looks like a small addition. It is not — and I tried it before deciding:

cloud.mjs builds its task commands under cloud.command(agent) inside for (const agent of AGENTS), so the real path is cloud codex task create and no regex can reach a name held in a loop variable. A parent-chain pass rewrote 12 files and turned cloud create into task create — differently wrong rather than less wrong — so it is not in this change. The file's own header already records that limitation ("uses regex, not a full AST").

Verification

tests/unit/agentSkills-cliRegistryParser.test.ts — 13 passed, including one fixture test and one that asserts against the real bin/cli/commands/tunnel.mjs.

Reverting the change (fullName = base) fails exactly those two new tests and puts the gate back to exit 2 — the same check both ways.