AIMEAT 3.5.0

AIMEAT 3.5.0 — the node grows a front door.

Nearly 1 800 commits since 2.3.0. The arcs:

The chat is how you arrive. Every node can now carry its own chat agent (powered by
goose): a new account lands in a conversation, not on a form.
Three starters, live tool log under every answer, result cards for pages and files the agent
makes, image and file attachments, a real Stop, and a first-conversation flow that builds the
person's own webpage before asking them for anything. The EU AI Act interaction notice is on the
page, with a plain-words dialog behind it.

Consent screens speak human. One shared vocabulary drives the app-grant page, the MCP
connector consent and the device-authorization page: plain-language sentences instead of raw
scope tokens, and on every screen the boundary a person actually fears about — this touches only
your AIMEAT account here, never your computer, your files on disk, or your accounts elsewhere.
The connector consent now describes the selected agent's real permissions instead of a static
"Full access" line, and the two consent doors grant the same preset sets from one source.

The home is a status dashboard. Mailbox with its flag up, the agent fleet as one line, what
you have made by name (starred favourites always visible, the rest folded), your favourite
apps, a colour-coded event timeline, achievements derived from the account's real state, and
your GHII address on the nameplate with its meaning one hover away.

Plain language, enforced by machine. "node" is gone from every screen a normal person
meets, and a ratchet in the locale gate keeps it out — alongside the existing plain-language
baseline for API messages. English, Finnish and Spanish, each composed rather than translated.

Metering, not currencies. The economy reframed as meters (RFC v4.0): one-off AI allowance,
own OpenRouter key or your existing AI subscription over MCP as the two roads on, honest payer
lines in the UI, and operator-side money visibility.

Security. The August audit's invariants enforced and gated: 14 guard suites (407
assertions) that block every merge, live scope checks on the consent surfaces, and the
three-surface MCP tool parity checks.

Full history: v2.3.0...v3.5.0