v0.2.1 — removals that remove, keys that replace
The 0.2.x line, with the fixes from 28 July. One file — download it and double-click.
Removals that remove. Removing an email account did nothing when it was a Google
sign-in: accounts live in two stores and the removal searched only one, then both buttons
said "Account removed" without reading the answer. Removal now routes to the store that
owns the account and verifies the result.
A new key destroys the old one. Pasting a fresh API key for a provider you already had
used to leave the previous record with its previous key — two entries, and whichever
sorted first decided which one was used. A key now supersedes rather than stacks, and
npm run key shows every place a key lives on your machine (Keychain, disk, environment)
by name and file, never by value.
AUTOMATIONS was a demo; now it is the truth. Four buttons proposed hardcoded samples
into a second approval queue that lived in the browser, and the two switches above them
were read by nothing. An email sent "via approval" landed in that queue and could never
have been sent. There is one queue now, and the panel shows what actually runs on a clock,
what waits for your yes, and what your agent may do without asking.
BRAIN shows the body. Memories moved onto disk so the agent can write one itself. The
body tree is drawn as an architecture diagram — parsed from the generated map, never drawn
beside it, so it cannot describe an app that no longer exists — with a Regenerate button.
Pairing. npm run pair puts the link to your machine on the clipboard. It is never
printed: whoever holds that token holds a shell on your machine.
sha256 462aa75c8eb6213b7230a1ecda16d20c4332a041fe5e1b95f44e0002b80ea661
Reproducible from source — clone this repo and run npm run build; dist/index.html
hashes to the line above. 605 tests pass.
Note: the version string shown inside the app still reads 0.2.0; only the build is new.