v0.2.0 - Read before replaying a write

Your browser saved the draft. Its worker died before recording success. Should recovery click Save again?

This preview adds a persisted host controller and a reproducible worker-kill demo to the original prompt modules.

• Flush DISPATCHED before execution; stop on persistence failure.
• Bind a stable operation ID to the exact payload hash, origin, account, action kind and count.
• Recover with a fresh browser read, then persist CONFIRMED or ABSENT.
• Keep failed reads unresolved; retry ABSENT only in a separate explicit phase.
• Retain intermediate checkpoints, destination snapshots and real screenshots.

Actual final results: 41 unit/contract checks passed. Both CI jobs passed at commit 630d773. Two actual SIGKILL cases read back 0 before Save / 1 after Save in distinct new processes. A deliberate unguarded two-Save control created 2 rows. Injected HTTP 503 did not become ABSENT.

Final CI and environment · English method · 中文方法

Extract the source ZIP, enter its browser-agent-blueprint folder:

npm install
npx playwright install chromium
npm test
npm run demo:write-ahead

Node 20+, macOS/Linux. On Linux use Playwright's --with-deps option when needed. No model key or existing browser profile is required.

The source ZIP contains all 104 tracked files, independently compared byte for byte to the commit. The evidence ZIP contains the final synthetic checkpoints, target snapshots and screenshots. The JSON report is also available separately. SHA256SUMS.txt covers all three downloads. Old release assets remain unchanged.

This is one task owner with sequential workers against a local target that has no deduplication. It is not server-side idempotency, exactly-once delivery, concurrent-host validation or a power-loss test. The target survives worker death, not its own death. File fsync is used; the parent directory is not fsynced.

中文版：新增写前状态保存、操作与载荷绑定、独立读回核对和失败即停；附中英文说明及真实证据。受控场景读回 0/1 条，不受控两次保存为 2 条。属于合成宿主测试，不宣称生产环境可靠性或 Star 增长。