mirror of
https://github.com/ALLFATHER-BV/wadamesh.git
synced 2026-10-06 03:27:23 +00:00
Kaj SchittecatandClaude Opus 5
66e1f37d2c
Two things made a full harness run untrustworthy, and together they produced a false accusation against a community app. wada.fs was stubs. append threw the data away, remove always said true, and read, write and list were not there at all — although the firmware registers all five (LuaAppHost.cpp). Any app that writes a file and reads it back therefore failed here while working perfectly on device. wardrive 1.2 is exactly that app: it errors on a nil fs.read at its first log flush, long before it renders anything, and the emoji scenario then reported the repeater name as unrendered. Read as "1.2 regressed the beta_70 emoji fix", which it did not. It passes untouched once fs is real. wada.fs is now an in-memory filesystem following LuaAppHost's semantics: read returns the data plus the file's TOTAL size so a caller can window a growing log, an offset at or past the end gives an empty string rather than nil, a missing file gives nil, and list is sorted so a hash order cannot make a test flaky. The second: the gpscompass scenario list was acting as the dispatch default, so an app with no branch of its own was run against tests written for a different app. Six store apps have no branch (2048, airtime, monitor, nearby, sdktest, snake), so a full sweep came back with six red apps as its normal state — and a real regression would not have stood out against that. Those apps now say they have no scenarios and run none. They are untested, which is worth saying out loud, but that is not the same as broken. A sweep of every store app is now 8 apps passing their own scenarios, 6 reported untested, 0 failures. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>