jhkaktus 535a9c9db0 feat: client logic for setup vs unlock flow and wrong-passphrase handling ...

ui.js now (a) decides setup-vs-unlock from GET /api/records emptiness,
(b) runs the setup flow (double entry check, min length, TOCTOU re-check
that the DB stayed empty), (c) detects a fully failed unlock (all rows
undecryptable = wrong passphrase) and returns to a clean state, and
(d) blocks double submits while Argon2id derives the key.

Verified: node --check passes, live server serves both screens and a
crypto roundtrip proves setup passphrase unlocks on second visit while
a wrong passphrase is rejected.

🤖 Generated with Codebuff
Co-Authored-By: Codebuff <noreply@codebuff.com>

2026-10-11 00:30:51 +02:00

..

vendor

chore: remove leftover stray vendor files from earlier fetch attempt

2026-10-11 00:01:33 +02:00

crypto.js

feat: client-side crypto – Argon2id KDF + XChaCha20-Poly1305 AEAD

2026-10-11 00:01:30 +02:00

index.html

feat: first-time setup screen for creating a new passphrase

2026-10-11 00:30:51 +02:00

style.css

feat: browser UI – unlock, table view, create/edit/delete with client-side crypto

2026-10-11 00:02:40 +02:00

ui.js

feat: client logic for setup vs unlock flow and wrong-passphrase handling

2026-10-11 00:30:51 +02:00