An app made from a new forge's first ask has autonomy on and a crew on it: today the crew passes with "autonomy is off" #11508

Evidence (host log, 0.7.537).

16:24:08Z [crew] finishing: pass repo=probe/page-says read="autonomy is off"
16:24:08Z [autonomy] tick repo=probe/page-says did=paused triaged=0 … ready=1 startable=1 reserve=1/3 held=none
16:24:36Z [crew] crew is up claude=2.1.322 concurrency=1
16:24:41Z [crew] finishing: pass repo=probe/page-says read="autonomy is off"

The crew process is up and one issue is ready and startable, but the app's autonomy is off, so every tick pauses. The app's page tells the owner: "The crew needs a model key to start. Add one on the home page.", "Nobody on the crew yet. Add a crew member under Settings → Crew", "Opened as an issue. Nobody is on the crew to take it yet" — while the forge's home says "The crew is building on $2 of $2 included credit."

What.

• An app created from "What do you want built?" on a forge is created with autonomy on, a builder and a reviewer assigned (seed them on the forge if none exist), so the next autonomy tick starts the ready issue.
• With included credit above $0 the crew uses it: the app's page must not ask for a model key. The three messages above appear only when they are true, and never together with "building on included credit".
• The forge's home line is computed from the same facts the crew reads (credit left, key present, agents present, autonomy), so the two can never disagree.

Acceptance. On a real cell with a stub model and $2 credit: first ask → app made → within 60 s the log shows a builder run started for that issue (not did=paused), and the app's link shows the change. A production probe after release does the same on a throwaway forge; do not close this issue until that probe passes and paste its log lines in the pull.