web-code, web-origins and ssh-site join the gate, each green in the check and under the test budget #1278

For the P0 Trust pillar: the last three files #291 kept out of the gate get in, held to the owner's bar from 2026-10-13: fast (#1242) and not flaky (#1243).

Where it stands. scripts/gate.ts still lists test/web-code.test.ts, test/web-origins.test.ts and test/ssh-site.test.ts in EXCLUDED under #291, with the reason "red: asserts the dashboard and studio pages as they were before the redesign". Pull #557 found that this is no longer true. All seven old assertions match today's pages, and /search?q=vault as alice names alice/vault while a stranger's search does not. Both earlier tries (#499, #557) went red only in gated files they never touched. Those races are now fixed (#1076, #1077, #1120).

Heads-up for the builder. A crew sandbox refuses listen on a unix socket (EPERM), so these three files cannot run locally (#1163, #1107). The pull's check is the proof. Don't change assertions blind to make them pass locally.

Done looks like

• [ ] The three files move from EXCLUDED to GATE in scripts/gate.ts. No other line of either list changes.
• [ ] The pull's check is green, and its summary or scripts/test-times.json shows each of the three under the #1242 budget: no file over 20 s and no test over 2 s. A file over budget is fixed by shape (one server per file, no sleep), or it stays in EXCLUDED with the reason "over budget" and a new issue for it.
• [ ] A file that is red in the check stays in EXCLUDED. Its reason gets the failing test's name, it gets a new issue, and the other files still move.
• [ ] test/check-list.test.ts passes.
• [ ] If the check goes red in a file this pull did not touch, the pull names that file and test and does not edit it.

Files: scripts/gate.ts. Only if the check shows they need it: test/web-code.test.ts, test/web-origins.test.ts, test/ssh-site.test.ts.

Risks: a race in another gated file can turn this pull red, as it did twice before. Name it and leave it alone. Search visibility is a security claim: if the private-repo case goes red, it is an app bug to file, not an assertion to loosen.

Brief: a builder (scout or mason), one short run.