Accept bare --select plateau (default the aggregation to mean) #227
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Brummel/Aura#227
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Surfaced by the triage-harvest milestone fieldtest (2026-07-10).
--select plateauis refused (needs plateau:mean|plateau:worst); the error self-corrects the user, so this is low friction. A bareplateaucould default toplateau:mean(the documented default aggregation), mirroring how the stop flags default since #217.context: milestone-fieldtest friction finding, severity low; droppable.
This issue targeted a CLI flag-parsing ergonomics gap: parse_select in crates/aura-cli/src/main.rs (~lines 490-497) refuses a bare 'plateau' token and requires the fully-qualified 'plateau:mean' or 'plateau:worst'. That behavior is unchanged as of the #295 shell-boundary extraction (2026-07-21) — #295 relocated the Selection/DataChoice types to aura_runner::family (Task 8) but left the argument-parsing function itself in aura-cli/src/main.rs.
Issue #300 (2026-07-21, document-first completion) has since decided that --select is one of the run quintet's residual flags migrating into document vocabulary, with the CLI converging on a small executor verb set. The document-side representation of select (SelectRule in crates/aura-research/src/lib.rs, ~lines 94-102) currently mirrors the same strict grammar (argmax | plateau:mean | plateau:worst, no bare-plateau default) and has the same gap, but its field shape is explicitly named as unsettled design work belonging to #300, not this issue.
Closing as superseded by #300: patching the soon-to-shrink CLI parser is no longer the right venue for a bare-plateau default. If a default-aggregation convenience is still wanted once #300 settles the select field's document shape, it should be re-raised there or as a fresh issue scoped to that design, rather than as a CLI-parser patch. (The original report already flagged this as low-severity and droppable.)