mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-09-24 06:55:20 +00:00
Kaj SchittecatandClaude Opus 5
a80a48988e
Settings, About gains "Report this build": works or a problem, five tick boxes for what you actually exercised, how long you have run it, an optional line. It posts to the report service and lands on wadamesh.com/beta, which is what the next promote is decided on. Ticking matters: "it works" from somebody who watched it boot and "it works" from somebody who messaged on it all week are not the same claim, and a board only goes green on two of the second kind. "Report a bug" draws a QR for a prefilled GitHub issue form. The issue is filed from the reporter's phone under their own account, so no write token has to exist in a public firmware image and the reporter gets the replies. "Count this device" is off by default. It lets the update check say which board and version it is running, so a board with no reports can be told apart from a board nobody owns. Those need opposite responses and nothing could tell them apart before. Mechanics: the POST rides the existing core-0 tile/update worker and its WiFiClient/HTTPClient, like the version check, because a second pair on that ~8 KB stack overflows it. The device id is a salted SHA-256 of the public key truncated to 64 bits, so a second report replaces the first without saying who sent it. Sending is two taps and the second lists every field that leaves. Prefs v64 appends report_ping + report_done_n at the tail, which the schema's trailing static_assert now checks. Also here: scripts/build/matrix-check.sh prints what testers reported for a tag, and release.sh runs it before a --promote. It never blocks; a board nobody owns can never go green. With no reports at all it now says so rather than reporting a clean bill of health, which is the habit this is meant to replace. Built on all eleven S3 envs and the T-Display P4. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>