Your board knows when there's a newer one. At boot, a board with a saved WiFi network joins it for about a second, asks squachwatch.com for the latest version of its own build, and lets go again, all before Bluetooth starts and before anything else that wants memory. Measured at 1.4 seconds on the Phantom. It tells, it never installs: Squachy says "v1.8.1 is out. SYSTEM > UPDATE." once, the SYSTEM row reads UPDATE, and UPDATE FIRMWARE names the version until you install it. UPDATE CHECK on the SYSTEM page turns it off. Out in the field with no WiFi, the squad does the same job: every board's hello now carries its version, so a board that hears a member running something newer knows, and says who. The first version of this used HTTPS and took ten seconds; the manifest is public and the install still checks the signature, so the check asks plainly.
Two Squachys talk about something now. Forty-six situational exchanges beside the forty-eight about nothing: the snow, the synthwave sun, the stars, the rain of code, the toasters, the fish; what was caught earlier; each other's outfits ("Is that a VOID EYE?" "You know it is." "Bold."); how many times this visitor has turned up, straight off the roster; the squad's size; the visitor's name; a quiet day, a busy one, and how long the board has been up. One exchange in three when there's something to say, never the same one twice running.
The LOG looks like Settings. Every entry is a tile now, the same panel the menus use, with a solid ground under the text and four rows of backdrop between neighbours. Every other list got the same air. The tap targets didn't move.
Five small things. NEARBY shows a green up-arrow beside a device that has come closer since its last reading and a red down-arrow for one that has moved away. The first time this board ever catches a type, the card says FIRST OF ITS KIND and Squachy marks the occasion when you're back with him. FILL on the message screen swaps the lines for eight openings that end in a blank, MEET AT, I'M AT, BACK IN and the rest, and picking one opens the keyboard with it typed. When a squad member opens your message, their board says so and yours shows READ with their name for three seconds, and Squachy says it too. SNOOZE 1H on an alert mutes the type for an hour, not the device, with the minutes left on the type filter.
Toasts show on the main screen. They only ever drew on LOG and NEARBY, which meant SNOOZED and READ went unseen exactly where you'd be standing.
The release workflow stopped racing itself. The v1.7.7 tag started it twice in the same second; one run built and published, the other built and then failed creating a release that already existed. Runs on the same tag now queue, and the second one finds the release and stops before the build.
Getting this version: from v1.7.4 or later, UPDATE OVER WIFI, Bluetooth, or a squad member's UPDATE SQUAD. From anything older, the USB flasher. This is the release that proves the squad update's report-back: one board updated by hand, UPDATE SQUAD from it, and the others answer by name.
The actually-useful part
- Added: an update check at boot over saved WiFi, with UPDATE CHECK on the SYSTEM page
- Added: the version in every squad hello, so a newer member is enough to know
- Added: forty-six situational banter exchanges between two Squachys
- Added: closer/further arrows on NEARBY
- Added: FIRST OF ITS KIND on the alert card
- Added: FILL, message openings that end in a blank
- Added: read receipts, with a READ toast and Squachy's line
- Added: SNOOZE 1H on the alert card
- Changed: LOG entries are tiles; every list has more air between tiles
- Changed: toasts draw on the main screen; READ holds three seconds
- Fixed: the release workflow no longer runs twice on one tag