mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-10-06 20:47:25 +00:00
Kaj SchittecatandClaude Opus 5
2ee888c2c0
Three things Jade reported, the first of which is blocking an app submission. Missing keys on the T-Deck. A Lua app there never received A, P, Q, Enter or Backspace. The rule that withholds them exists so an app can never swallow its own exit, which is right on a board where a reserved key IS the only way out. On the T-Deck it is not: an app page is closed by tapping the back bar, and the app host is not in the popup registry, so those keys closed nothing while an app was running. They were simply dead inside every app. They are now forwarded. The M9 keeps its reservation, because its reserved keys are sentinel bytes for Back and Home that are never typed text and it has no touch to tap out with, and the Pager already reserved nothing. That is why this was T-Deck-only. The trackball click. With an app open the trackball branch forwarded motion and explicitly discarded the button, so an app could be steered but never clicked. It now delivers the same synthetic centre tap the touchless boards' select key sends, on the press edge: the flag is a per-frame "held" level, so forwarding it raw would have fired a tap every frame the button stayed down. Repeat counts. The firmware already counts repeaters heard rebroadcasting an outgoing flood, keyed on a fingerprint taken at transmit time; it is the refresh glyph on a sent bubble. wada.mesh.send() now returns that fingerprint as its second value on success, and wada.mesh.repeats(fp) reads the count back. Additive, so an app reading only the first return is unaffected. The count grows as repeats arrive, so it is polled rather than read once, and a direct message has none because it is not flooded. Documented on the SDK page. Built on all nine S3 envs and both ESP32-P4 targets. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
