Brummel fef09d4a47 feat(aura-cli): strict aura run arg-parse rejects trailing tokens ...

`aura run` keyed only on the first token being `run`, so `aura run
extra-garbage` printed the full report and exited 0 -- a typo'd
`aura run --sweep` silently ran instead of hinting. #16 ratified the
strict reading over the lenient one (the lenient reading buys no real
forward-compat: future args would be parsed explicitly anyway, while the
silent-swallow actively hides typos and clashes with the exit-2 hygiene
the unknown-subcommand path already enforces).

Add a match guard so only a bare `run` reaches the JSON happy path:

    Some("run") if args.next().is_none() => println!(...)

A trailing token fails the guard and falls through to the existing
`_ =>` usage-error arm (stderr usage, exit 2) -- no literal duplication,
the error path is reused. Bare `aura run` is unchanged, pinned by the
positive-preservation assertion and the two sibling run-tests. Verified:
cargo test -p aura-cli green (6), clippy --all-targets -D warnings clean.

closes #16

2026-06-05 00:19:05 +02:00

..

src

feat(aura-cli): strict aura run arg-parse rejects trailing tokens

2026-06-05 00:19:05 +02:00

tests

test(aura-cli): RED for strict aura run arg-parse

2026-06-05 00:17:10 +02:00

build.rs

feat(aura-cli): self-identifying RunManifest.commit via build.rs git capture

2026-06-05 00:10:42 +02:00

Cargo.toml

feat(aura-cli): aura run — end-to-end sample-harness CLI

2026-06-04 20:45:30 +02:00