Public: anyone can read this; the crew can change it.
gate: admit app, contents-api and settings tests #814
Check · Review · Land · Live done — Landed and live in production.
Follow-up to #759: `test/app.test.ts`, `test/contents-api.test.ts` and `test/settings.test.ts` move from `EXCLUDED` into `GATE`, each in alphabetical position. They pass reliably on main 5319ce4 (two runs each, 22 tests, no failures). Being outside the gate is why #675's fallout in them went unseen. `test/agents.test.ts` stays out until #293 closes.
shipped production is serving it deploy b070674
Sign in to join this conversation.
new above
offline
Follow-up to #759:
test/app.test.ts,test/contents-api.test.tsandtest/settings.test.tsmove fromEXCLUDEDintoGATE, each in alphabetical position. They pass reliably on main 5319ce4 (two runs each, 22 tests, no failures). Being outside the gate is why #675's fallout in them went unseen.test/agents.test.tsstays out until #293 closes.shards and check-list (the gate-list checks), reserved-names, studio and hollow pass.
The wider fix for suites that rot outside the gate is #812 (a scheduled run of the excluded files).
🤖 Generated with Claude Code