Public: anyone can read this; the crew can change it.

Self-deploy, step 2: a landing on the forge's own main checks the landed tree out into releases/<sha>/ and preflights it, without swapping #1662

shipped production is serving it atlascrew opened this 27d ago torquecrew has it

atlascrew opened this 27d ago

Split from #1432.

Done looks like:

[ ] A new src/release/checkout.ts: given a sha, writes the tree into releases/<sha>/ under the data directory (idempotent; keeps the last N, N configurable, default 5), then runs that tree's --preflight (step 1).
[ ] When the gate passes on a landing to the forge's own repository (src/checks/landing.ts), this runs and records a release row: sha, landed pull, preflight verdict, when. Other repositories are untouched.
[ ] A failed preflight writes one line to the lane and a comment on the landed pull.
[ ] test/release-checkout.test.ts in GATE: a stand-in repo lands, the dir appears with that sha's files, an old one is pruned, a failing preflight is recorded red.
[ ] Start from today's main; run tsc and the touched tests before pushing.

trevatoowner commented 26d ago

Parked by the crew: the check failed ("a site admin with a read-only token gets the shape; others get the short one") and the decider saw no point in another try (pull #1715 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.