SIM001 0.2.0

What's Changed

• cargo run from the root starts the launcher by @ptescher in #3
• Docs audit: tutorials as walks, right-sized topics, a new layout, real screenshots by @ptescher in #5
• State map: 63 MB to 2 MB (expectation#4) by @ptescher in #6
• State map: screenshots for the states a move from each start by @ptescher in #7
• Towers: the valley map with lanes, low flying, and the drones' cameras by @ptescher in #8
• Launcher: start a game of Towers by @ptescher in #9
• Drop unused dependencies; one version of each shared crate by @ptescher in #10
• Towers commander: RTS controls by @ptescher in #11
• Heavy T2 Cruza and light Seeker 3 planes; Towers teams of 5 by @ptescher in #12
• Station ports per worker; expectation at ba5a6d0 by @ptescher in #13
• Manual: VTOL tutorial screenshots, stable fingerprint, fast-fail docs run by @ptescher in #14
• SITL: isolate parallel runs (scoped cleanup, per-worker test service) by @ptescher in #15
• Commander UI: size cameras and number keys by the team's drones by @ptescher in #16
• GPUI layouts: scroll what does not fit, fold button rows behind MORE by @ptescher in #17
• Manual: Your first hover passes again, with screenshots by @ptescher in #18
• State map: map the launcher's prerequisites, so fewer starts by @ptescher in #19
• Launcher hand-overs: VTOL station, Towers variants; expectation off the branch by @ptescher in #20
• State map: Backgrounds follow the setup they are reached from (13 → 7 starts) by @ptescher in #21
• Towers: fix B4/B5 drones, and one map for the game, 3D view and ground station by @ptescher in #22
• Launcher: one start (no controls.cfg on a fresh launcher); refresh nested lockfiles by @ptescher in #24
• Draw the Seeker 3 as a quadcopter by @ptescher in #25
• Minimum window size for the GPUI apps by @ptescher in #26
• CI: fmt, check and clippy on PRs by @ptescher in #23
• Seeker 3: fix the yaw reaction torque sign by @ptescher in #27
• Seeker 3: stable hover; hover expectations run on both planes by @ptescher in #28
• Towers: radio-blocking towers, lost-link failsafe, and mountains round the field by @ptescher in #30
• Seeker 3: fly AUTO missions as a multicopter (Q_ENABLE 2) by @ptescher in #31
• Towers commander: unit panel with icon and basic stats for the selected drone by @ptescher in #29
• Towers v2: kinds, battery, mesh, drift, a measured ruleset, and a replay you can open by @ptescher in #33
• Towers server: take free ports when the usual ones are in use; the app tells its clients which by @ptescher in #32
• Towers: UNIT panel expectations, and a commander test driver that fails fast by @ptescher in #34
• Towers v2: kinds, battery, mesh, drift, a measured ruleset, and a replay you can open by @ptescher in #35
• Expectation suites: a 120 s budget per suite by @ptescher in #36
• One workspace: the GPUI apps and mapbuild join the root workspace, one Cargo.lock and one target/ by @ptescher in #37
• Expectations: the mountains apply only to a game of Towers, and a Towers game flies ten drones by @ptescher in #38
• Towers commander: the layout no longer outgrows the window on a selection; scroll zooms the map, with a minimap when zoomed in by @ptescher in #40
• tasks docs: the league gets its own suite budget by @ptescher in #39
• Towers server: before GO the drones still hear their orders by @ptescher in #41
• Towers: the mesh relays hop by hop, so a chain of drones carries the radio into a shadow by @ptescher in #42
• Towers: an advisor speaks to a person who commands, when something matters by @ptescher in #43
• Seeker 3: real speed, no VTOL delay, stays low in Towers by @ptescher in #46
• Towers: the spec has two platforms, sim and field (unified link, step 1) by @ptescher in #47
• Towers: the ground reaches each drone through a simulated air (unified link, step 2) by @ptescher in #48
• Towers: a drone flies its standing order itself (unified link, step 3) by @ptescher in #49
• Towers: the commander app is the ground station of its team (unified link, step 4) by @ptescher in #50
• Towers: the team map is made from what the drones reported (unified link, step 5) by @ptescher in #51
• Towers: the game server is the umpire of the app (unified link, step 6) by @ptescher in #52
• Towers: the field bench (unified link, step 7) by @ptescher in #53
• Expectation at its latest, and CI runs the spec, clippy and the tests on Linux by @ptescher in #62
• League: each Claude run has a time limit, and is written down by @ptescher in #63
• tasks: the console's suite is a task of its own (tasks console) by @ptescher in #61
• Towers server: the computer teams take towers together, not each by @ptescher in #59
• Towers: the spec and the app suite follow v2 (five drones, slow 3D view) by @ptescher in #57
• Ground station: the console driver runs 110 of 115 plans, and five planning features it lacked by @ptescher in #60
• Sim: the tests get the time they need (100 s a test, 240 s a run) by @ptescher in #58
• League: the captain whose code changes is judged, not refused by @ptescher in #56
• Cognition: expectations pass on the latest framework; T1-S cruise 18 m/s by @ptescher in #55
• league: fix the Claude tuner's tool rules by @ptescher in #64
• plans: Towers v3 design by @ptescher in #65
• towers: EdgeObs, what a drone knows on board by @ptescher in #66
• towers: Edge policies and the headroom measurement by @ptescher in #67
• towers: spire 1.5, layouts as data, the chain (11 towers), allocation matrices by @ptescher in #68
• towers: a belief about where unseen enemy drones are (particle filter) by @ptescher in #71
• Towers: the commander app as a 3D real-time strategy screen by @ptescher in #70
• towers: allocation by time to win (from an Opus league run) by @ptescher in #69
• towers: the commander thinks ahead (model rollouts from the belief), on by default by @ptescher in #74
• Battlefield view in the ground station, shared with the commander app by @ptescher in #72
• Orders: CIRCLE and routes in both the ground station and the commander app by @ptescher in #75
• Visualization: a more photo-like valley by @ptescher in #76
• Towers: only a drone below the treetops takes a tower by @ptescher in #79
• Visualization: houses, the FPV sensor, relief and cliffs by @ptescher in #77
• Towers: a valley with no ruled lines by @ptescher in #78
• Towers: all five drones of a team circle low under the treetops by @ptescher in #81
• Station: a fresh plane gets a fresh pack by @ptescher in #83
• Manual: a start page with three paths, and a clearer setup by @ptescher in #82
• Replay, phase 1: snapshots, a tape, and Backspace to rewind by @ptescher in #85
• Towers tutorials pass again, and the platform manuals are deployed by @ptescher in #86
• Site: the Towers tutorials' screenshots (expectation at 9a1ecbf) by @ptescher in #87
• Towers in the app bundle by @ptescher in #88
• Version 0.2.0 by @ptescher in #89
• Executor: link ArduPlane with the plan executor on Linux by @ptescher in #90

Full Changelog: v0.1.0...v0.2.0