LoopCheck 0.5.2
The first screen now separates live Strands planning from the disclosed keyless walkthrough. The live path connects an unchanged public MDN shopping-list sample and accepts a natural-language goal; it does not supply preset browser checks. Once requirements exist, checking the current change is the primary action. Contextual guidance explains whether to approve, generate missing checks, inspect evidence or recheck.
A read-only readiness check reports source access, preview reachability, model configuration and remaining recorded budget. It makes no provider request and does not approve a change. Public preview links resolve against the deployed host instead of a judge's own localhost.
The actual browser exercise exposed blocked inline JavaScript in the newly mounted MDN samples. Only the exact inline assets of the two pinned samples receive CSP hashes; the main application policy is unchanged. A real browser regression test verifies addition, cleared input and deletion through the production middleware.
Planner improvements simplify the initial observation and keep full evidence in the run while avoiding duplicated provider context. Tool validation failures are retained for diagnosis. Provider errors use bounded categories without response bodies or credentials. Planning drafts are not mislabeled as historical checks; they still cannot approve a change.
Verification and all unsuccessful live attempts are recorded in the 0.5.2 report. Release readiness, AWS access, public video and Devpost submission are independent gates. Read the exact commit's Actions results before deployment.
Upgrade: back up your existing data directory, update the source, retain the private .env and restart. No database migration beyond 0.5.0 is introduced. Existing requirements, evidence and recorded budget remain available. No human-efficiency percentage or prize outcome is claimed.