Let the decider: a card that needs a person can be handed to a decision model with curated context, per card or by a standing rule per app #1151

From the owner, 2026-10-12, on seeing two shelved apps' hand-overs on his board: "The option to defer to a decision model that has curated context could be interesting. I don't want to waste work, but I want to keep things unblocked without wasting time on things that do not matter."

The forge already has a decider: the retry decider answers stop or retry in the decision ledger, and the next-issue decider ranks the ready list. What the owner wants is the same thing one level up: a card that needs him can be handed to the decider instead, and a repository or app can say once that the decider decides for it.

Done looks like:

• [ ] On every card that needs a person — a hand-over, a green pull waiting, a conflict, a review — a third tap beside the two decisions: "Let the decider". It answers now, in the ledger, with its reason and its confidence, and the card leaves the board. Undo for a day, like a bulk decision.
• [ ] A standing rule per repository or app (Settings, one select): "decisions here: me / the decider / the decider, and tell me the ones it was unsure of". Shelved apps get the decider; the realtor's apps get the owner.
• [ ] The decider's context is curated, not the whole forge: the direction text, which apps are pinned, muted or archived, the day's spend against the ceiling, the owner's last ten decisions on this repository, and the card's own evidence (the park notes, the check summary, the review). Nothing else, and the context is shown on the ledger row so a person can see why.
• [ ] Cost: one small-model call per card, and none when a rule already answers (an archived app's hand-over closes without a call).
• [ ] Today's card (#1083/#1125) carries one line: "the decider closed 4, deferred 2, asked you about 1".
• [ ] Tests: a hand-over on a repository ruled "decider" is answered without a person; an unsure answer reaches the owner; undo restores the card; the ledger row carries the context used.

Files I expect: src/core/decisions.ts, src/crew/decide.ts (new, beside the existing deciders), src/web/pages/site.ts (the third tap), src/web/pages/settings.ts (the rule), src/http/mcp.ts (decide takes by: "decider").

Parked by the crew: the check stayed red through 2 automatic tries (pull #1360 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check failed ("the decider's doors > the ledger of a public app does not name another app, and the board says what the decider did") and the decider saw no point in another try (pull #1547 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check stayed red through 2 automatic tries (pull #1360 closed)
2. the check failed ("the decider's doors > the ledger of a public app does not name another app, and the board says what the decider did") and the decider saw no point in another try (pull #1547 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Split into #1604 (Let the decider on a hand-over card, with curated context in the ledger), #1605 (a standing rule per repository) and #1606 (the day's card says what the decider did).