The everyday account: a new owner is led to an account apart from admin, told why in two sentences, and can still choose otherwise #596

Pillar: P0 Trust (umbrella #586). One run, started fresh from today's main.

Outcome (what a person sees). A forge owner who signs in as the admin account is led, kindly and directly, to make a separate everyday account for daily work. Using AI with admin stays possible, but only on purpose.

Today. One account is both. On this forge trevato is site admin and the daily account (trevato2 exists, unused). Nothing in src names an everyday account.

Acceptance.

• [ ] Signed in as a site admin with no everyday account and no recorded choice, the home shows one card: "Make your everyday account", two sentences of why (for example: "Admin can change everything, including who can see what. Use it when you mean to; day to day, use an account that cannot break the forge."), and two buttons: Make it (username prefilled, editable) and Keep using admin (recorded; the card goes; settings keeps one line to change your mind).
• [ ] Make it creates an ordinary user linked to the admin (a user setting), signs you in as it, and both account pages name the pair.
• [ ] Minting a token for a site admin at /settings/tokens or through the API needs an explicit "I mean to give AI admin" confirmation; without it the token is minted for nobody and the page says why.
• [ ] MCP: the forge tool, called with an admin's token, returns a note that this token acts as admin and names the everyday account.

Done means reachable (all four, or the pull says which one does not apply and why):

• Page: the card on the home, two taps to a new account
• MCP: forge returns the admin note
• Test: create, link, decline, and the token confirmation
• Look: the home as a fresh admin, phone and desk, on the pull

Start from: src/web/pages/site.ts (home), src/web/pages/account.ts, src/web/pages/settings.ts (tokens), src/core/users.ts, src/core/settings.ts, src/http/mcp.ts (forge).

Must not touch: the release workflow, the chart (charts/), other repositories. Do not change any existing account's admin flag, sessions or sign-in beyond what the switch needs.

Added acceptance (owner's contract rule, now in the direction and docs/VISION.md):

• [ ] Contract: one interface per job. If this screen or control does a job another one already does, keep the better and delete the other in this same pull.
• [ ] Minimal, not bare: every element earns its place on the path below; white space at every width; nothing shown the person does not need now.
• [ ] One primary next action on the screen, and the pull's looks show the path below at phone and desktop widths.
• [ ] The pull says what it removes for every screen or control it adds.

The path: a new admin arrives at the home after first sign-in, to start using the forge; the card's one action is Make it; they leave signed in as the everyday account, on the feed.

Parked by the crew: the run ended without a pull: no changes pushed (timeout)