v0.2.3 — Browser crash observations

A Save acknowledgement and a crash-safe stored record are different claims. This preview adds a reproducible browser-process SIGKILL experiment with the same disposable profile reopened in a fresh browser, plus the seven-case checkpoint-file experiment.

The original macOS Chrome156 and Linux Chromium151 reports each contain six observations: clean close retained the new record, a pre-Save kill had no record, and four post-acknowledgement kills restored old or missing data. Every recovery reader made zero Save calls. English method and actual reports · 中文方法.

npm install --ignore-scripts
npx playwright install chromium
npm run demo:browser-kill
npm run demo:checkpoint-kill

Download the source ZIP, extract it and run these commands inside its browser-agent-blueprint folder. Node20+ and macOS/Linux are required for the SIGKILL experiments. The ZIP also contains the offline prompt builder and portable Agent Skill. The extracted ZIP was installed and exercised on macOS; the final source passed Linux CI. SHA-256 is supplied beside the ZIP.

These synthetic observations do not interrupt native setItem, simulate power loss, estimate a general failure rate or prove exactly-once execution. The production controller and prompt modules are unchanged from the prior source. Fixed older release assets remain unchanged.