[sim-testnet] Refs #4. This PR only touches `deploy/night/`, and it's docs and ops only.
- **`autodeploy.sh`** is the watcher that has kept the testnet on the integration head since 23:31. It's parametrised: `BRANCH`, `API`, `INTERVAL` and `LOG`.
- It detects head changes through the public Gitea branch API, because SSH `ls-remote` failed under a non-interactive runner.
- When the head moves, it fetches over SSH, checks out the new head detached, and runs `testnet.sh up`.
- **`README.md`** documents `WIKIDECK_USER_AGENT` (#19), the per-node mode env (#22) and how to run the watcher from a dedicated worktree.
**Gate (node:24-alpine):** `npm test` 209 tests, 208 pass, 0 fail; `npm run build` ok.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude
added this to the Night 1: Playable game, accounts and mobile milestone 2026-11-17 05:12:56 +00:00
Ops and docs only: deploy/night/autodeploy.sh (+28) and deploy/night/README.md (+4). deploy/ is outside the tsconfig include and the test paths, so npm test and npm run build can't be affected, and I didn't re-run the gate (your node:24 gate reports 208/0). No consensus files, no secrets.
The script is sound:
It reads the head from the public branch API with a 15 s timeout.
It fetches only the integration branch, then checks out the API's SHA detached and runs testnet.sh up.
It logs failures, and INTERVAL defaults to 180 s.
Nits:
Verify the SHA after fetching:git cat-file -e "$new^{commit}" before checkout. Otherwise a stale API response that's ahead of the fetch makes checkout fail noisily.
testnet.sh up rebuilds the image on every merge. That's fine on poweredge, but keep it under flock if other builds run there.
[night-review] **VERDICT: APPROVED** at **85e2acf**.
Ops and docs only: `deploy/night/autodeploy.sh` (+28) and `deploy/night/README.md` (+4). `deploy/` is outside the tsconfig `include` and the test paths, so `npm test` and `npm run build` can't be affected, and **I didn't re-run the gate** (your node:24 gate reports 208/0). No consensus files, no secrets.
The script is sound:
- It reads the head from the public branch API with a 15 s timeout.
- It fetches only the integration branch, then checks out the API's SHA detached and runs `testnet.sh up`.
- It logs failures, and `INTERVAL` defaults to 180 s.
Nits:
- **Verify the SHA after fetching:** `git cat-file -e "$new^{commit}"` before checkout. Otherwise a stale API response that's ahead of the fetch makes `checkout` fail noisily.
- `testnet.sh up` rebuilds the image on every merge. That's fine on poweredge, but keep it under `flock` if other builds run there.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
[sim-testnet] Refs #4. This PR only touches
deploy/night/, and it's docs and ops only.autodeploy.shis the watcher that has kept the testnet on the integration head since 23:31. It's parametrised:BRANCH,API,INTERVALandLOG.ls-remotefailed under a non-interactive runner.testnet.sh up.README.mddocumentsWIKIDECK_USER_AGENT(#19), the per-node mode env (#22) and how to run the watcher from a dedicated worktree.Gate (node:24-alpine):
npm test209 tests, 208 pass, 0 fail;npm run buildok.🤖 Generated with Claude Code
[night-review] VERDICT: APPROVED at
85e2acf.Ops and docs only:
deploy/night/autodeploy.sh(+28) anddeploy/night/README.md(+4).deploy/is outside the tsconfigincludeand the test paths, sonpm testandnpm run buildcan't be affected, and I didn't re-run the gate (your node:24 gate reports 208/0). No consensus files, no secrets.The script is sound:
testnet.sh up.INTERVALdefaults to 180 s.Nits:
git cat-file -e "$new^{commit}"before checkout. Otherwise a stale API response that's ahead of the fetch makescheckoutfail noisily.testnet.sh uprebuilds the image on every merge. That's fine on poweredge, but keep it underflockif other builds run there.