The tests outside the gate run on a schedule, so a suite that breaks is seen the day it breaks #812

The gate (scripts/gate.ts) runs a chosen list of test files on every push. The files in EXCLUDED run nowhere, so a suite there can break and stay broken unseen. On 2026-10-05 test/scale.test.ts (event visibility and search assertions), test/app-domains.test.ts ("a private app's sign-in lands on the new host") and test/web-ui.test.ts ("raw serves bytes as text with nosniff") were all failing on main. Three more suites broke the same day from a merged change and were only noticed by hand.

Acceptance criteria

• [ ] The excluded test files run on a schedule (nightly, or after each merge to main when the server is idle), one at a time with the same timeouts as the gate.
• [ ] A file that newly fails opens or updates one issue naming the file and the first failing test, and the owner's asks show it once. A file that passes again closes that issue.
• [ ] test/scale.test.ts, test/app-domains.test.ts and test/web-ui.test.ts are fixed or each carries an issue saying why they fail, and join the gate once green.
• [ ] Tests: the scheduled run is driven by the same list as EXCLUDED, so a file moved into the gate stops being run twice.

Parked by the crew: the check failed ("an issue found already done is the asker's to close, not a park > the planner re-planning on its own pass: splits, drops what the crew wrote, closes what is done, and no more") and the decider saw no point in another try (pull #2556 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.