flybrain/services/flysim/crates
acamilo 66ec2e5c6b session: an unknown launch option is an error, not a no-op
The command line between a launcher and a participant in its own process
was coupled by string convention on both sides and checked by neither: the
parser accepted any --flag it did not know, so a renamed or dropped option
would have become a fault that never fires or a delay that is never
applied, with nothing failing.

Every flag now has one name, in launcher::flags, written by the launcher's
argv and read by the parser. Options::parse takes the sets its command
allows and refuses anything outside them by name, so a mismatch fails the
launch. measure and measure-row use the same constants for their own
flags.

Three tests hold the two sides together: every flag a launch writes is one
its command accepts, every media option is written for a separate process,
and an unknown or wrong-command flag is refused by name. The four media
faults now also run end to end in all three execution modes, each failing
its own transition, so the wiring across a process boundary is proved
rather than assumed.
2026-09-22 16:28:59 +00:00
..
fly-session session: an unknown launch option is an error, not a no-op 2026-09-22 16:28:59 +00:00
fly-session-types Merge main: the per-fly processes, the launcher and the thread budgets 2026-09-22 16:07:30 +00:00
flybrain-core flybrain v0.4.0: public tree (history retained privately) 2026-09-21 15:09:46 +00:00
flybrain-gb traps: rows 51 to 53, the museum's missing rows and a BACK with no box under it 2026-09-22 13:14:47 +00:00
flybus bus: wait for the teardown the disconnect test asserts 2026-09-22 14:29:57 +00:00
flysim tests: ROM-gated, the fly gets out of the museum and into the gym 2026-09-22 13:12:31 +00:00