On a new forge a finished change goes live by itself: today it waits forever for a review that never comes
Evidence (production 0.7.547+, 2026-11-12, forge probe-obfd, 4 CPUs, $2 included credit). First good run end to end: the ask "A page that says hello and shows today's date." had an app in 2 s and a pull with a passed check inside 77 s, for $0.22. Then nothing for eight minutes. The pull read, unchanged from 77 s to 552 s: "Check · Review · Land · Live — No review yet. Next: reviewer, no review yet." and "waiting for reviewer's review". The reviewer never ran. The tester pressed Ship on the pull at 552 s; two seconds later it was "Landed and live in production" and the app's own address showed "Hello, probe! Today is Thursday, November 12, 2026." The pull's page also said "This app does not wait on the check to ship… then ship it or say what is off", so the forge already knew this app may ship without a review; and its Look panel said "No picture… net::ERR_INTERNET_DISCONNECTED".
So the build works and costs cents. The only thing between a stranger and a live change is a review nobody performs and a Ship button they are not told about.
What.
Find why the reviewer never ran on a new forge (no reviewer agent seeded, one crew slot held, no model access for the reviewer role, or review simply not queued for a forge on included credit) and fix that cause.
For an app whose owner has not asked for reviews: a pull whose check passed lands by itself (the page's own words say it need not wait). Reviews are something an owner turns on, per app, when they want a second look; a new forge's first app has it off.
Whenever a pull is waiting on something only the person can do, the forge's home and the app's page say so in one line with the button right there: "Your change is ready. Ship it" with the preview link beside it. Never a status that reads as if someone else is about to act when nobody is.
A preview link for the pull is shown to the person (none was).
The look of a child forge's own app must not fail with ERR_INTERNET_DISCONNECTED: the browser taking it has no route to the app's address from inside the cell (see #11651); fix or stop showing an error panel to a new owner.
One cost figure: the pull said $0.22, the app page "$0.45 of $20" and "$0.45 per shipped pull request", the home "$2 of $2 included credit" seven minutes in. Same number everywhere, updated as it is spent.
Acceptance. The stranger journey (#11158) on a new forge: ask → app's own address shows the change with no click after the ask, under five minutes, with zero "waiting for reviewer" states. A production probe after release does the same; paste the timeline. Do not close this until that probe passes.
On a new forge a finished change goes live by itself: today it waits forever for a review that never comes
Evidence (production 0.7.547+, 2026-11-12, forge probe-obfd, 4 CPUs, $2 included credit). First good run end to end: the ask "A page that says hello and shows today's date." had an app in 2 s and a pull with a passed check inside 77 s, for $0.22. Then nothing for eight minutes. The pull read, unchanged from 77 s to 552 s: "Check · Review · Land · Live — No review yet. Next: reviewer, no review yet." and "waiting for reviewer's review". The reviewer never ran. The tester pressed Ship on the pull at 552 s; two seconds later it was "Landed and live in production" and the app's own address showed "Hello, probe! Today is Thursday, November 12, 2026." The pull's page also said "This app does not wait on the check to ship… then ship it or say what is off", so the forge already knew this app may ship without a review; and its Look panel said "No picture… net::ERR_INTERNET_DISCONNECTED".
So the build works and costs cents. The only thing between a stranger and a live change is a review nobody performs and a Ship button they are not told about.
What.
ERR_INTERNET_DISCONNECTED: the browser taking it has no route to the app's address from inside the cell (see #11651); fix or stop showing an error panel to a new owner.Acceptance. The stranger journey (#11158) on a new forge: ask → app's own address shows the change with no click after the ask, under five minutes, with zero "waiting for reviewer" states. A production probe after release does the same; paste the timeline. Do not close this until that probe passes.