test/rehearsal-real.test.ts is admitted: ten green flake-hunt runs on the check host, or its red names what did not come up and that is fixed #11169

For: the last box of #11098, so the two real rolls are proven in the gate rather than hoped for.

Done when:

• [ ] bun scripts/flake-hunt.ts admit test/rehearsal-real.test.ts is ten green on the check host, and the pull quotes its summary.
• [ ] Or, when a run is red, the failure message names the process or port that did not come up and how long it waited. That cause is fixed in the rehearsal or the test's setup, not by raising a timeout or skipping the test.
• [x] The test is in the gate's list, or found by its discovery, with no skip.

Files: test/rehearsal-real.test.ts and whatever its red names. Risk: do not touch the release workflow or the chart.

Reviewed pull #11178 at its head: ticked The test is in the gate's list, or found by its discovery, with no skip.. left open: bun scripts/flake-hunt.ts admit test/rehearsal-real.test.ts is ten green on the check host, and the pull quotes its summary. — The ten green runs were in the agent sandbox on loopback ports, not on the check host.; Or, when a run is red, the failure message names the process or port that did not come up and how long it waited. That cause is fixed in the rehearsal or the test's setup, not by raising a timeout or skipping the test. — The message and the retry are in place, but the port-theft cause is a hypothesis not yet seen on a red run, so the box stays open..

Left open after pull #11178 landed: 2 unticked items remain (bun scripts/flake-hunt.ts admit test/rehearsal-real.test.ts is ten green on the check host, and the pull quotes its summary.; Or, when a run is red, the failure message names the process or port that did not come up and how long it waited. That cause is fixed in the rehearsal or the test's setup, not by raising a timeout or skipping the test.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

Split by the planner. The admission landed in e89189b1c. The second box (a red names the forge, its port and how long it waited) is now #11186: today judge() only says "the new forge never became ready". The first box (ten green flake-hunt runs on the check host) is not a builder's run, because the sandbox cannot host it. The forge's check runs the file on every push, and #11186's check log is where it shows green.