A forge's owner sets their own model key and their own budgets, and the crew picks the work back up without anyone else's help #11515

Why. A hosted forge is its own thing. Its owner brings a key and decides what to spend. Today a forge without a host grant fails every run with "This repository has no model account: ask an admin to grant one" (glint-agency: 9 of 9), parks the issues after two failures and never retries; and a run's spend limit (grokbot-agency: every run ends max_budget_reached near $0.45) is not something its owner can see or change in one place.

What.

• When the forge has its own model key (the first-screen field from #11154), every repository on it uses that key. No grant, account or setting on any other forge is consulted, and no message tells the owner to ask an admin elsewhere.
• Settings → Crew on the forge shows the owner three numbers they can change: spend per run, per day and per month, with what was spent against each. Defaults are sensible for a key the owner pays for (a run is not cut off under a dollar). A run stopped by a limit says which limit and links to that setting.
• Adding or replacing a key, or raising a limit, wakes the work: issues parked for "no model account", "no key" or a budget stop are un-parked and tried again once, and the owner sees "3 issues picked back up".
• A forge that still runs on its host's included credit keeps working as in #11154; the moment its own key is set, the host's credit is no longer drawn on, and the forge's home says which one is paying.
• The words "ask an admin to grant" do not appear on a forge whose reader is its admin.

Acceptance. Tests on a cell with no host grant: (1) no key → the run stops with the add-a-key message and the issue is parked; add a key → it is un-parked and a run starts within a minute, with no call to the host for model access (asserted). (2) A per-run limit of $0.10 stops a run naming that limit; raising it re-runs the issue. (3) With its own key set, the forge's spend never appears against the host's credit.