closed-blueprint walkforward --axis prints the UnknownKnob rejection twice #177

New Issue

2026-07-01T17:02:16+02:00

Brummel commented

2026-07-01 17:02:16 +02:00

aura walkforward <closed bp> --axis <name>=<v> emits the same rejection
diagnostic twice (exit 2, no panic):

aura: UnknownKnob("graph.fast.length")
aura: UnknownKnob("graph.fast.length")

Exit code is correct; the diagnostic is just duplicated (the sweep / mc paths emit
their rejection once). Likely the per-window walk-forward closure re-raises the
same top-level bind error. Low severity — dedupe the emit.

Surfaced by the World/C21 milestone fieldtest. Detail in
docs/specs/fieldtest-milestone-world-c21-blueprint-data-families.md.

refs #170

`aura walkforward <closed bp> --axis <name>=<v>` emits the same rejection diagnostic **twice** (exit 2, no panic): ``` aura: UnknownKnob("graph.fast.length") aura: UnknownKnob("graph.fast.length") ``` Exit code is correct; the diagnostic is just duplicated (the sweep / mc paths emit their rejection once). Likely the per-window walk-forward closure re-raises the same top-level bind error. Low severity — dedupe the emit. Surfaced by the World/C21 milestone fieldtest. Detail in docs/specs/fieldtest-milestone-world-c21-blueprint-data-families.md. refs #170

Brummel added the bug label 2026-07-01 17:02:16 +02:00

Brummel referenced this issue from a commit

2026-07-01 17:47:37 +02:00

fix(cli): walkforward validates its --axis grid once, not once per window

Brummel closed this issue

2026-07-01 17:47:37 +02:00

Brummel referenced this issue

2026-07-01 17:51:04 +02:00

Monte-Carlo and walk-forward over a loaded blueprint #170

Brummel referenced this issue from a commit

2026-07-02 09:37:09 +02:00

Merge main into the clap-adoption cycle — re-integrate the two parallel CLI fixes