igneum/docs/plans/relay-deploy-2026-10-07.md

Relay deploy, 7 October 2026 (the X23 tree, MF-11)

What	Value
Deployed	2026-10-07 15:38 BST, from branch update-return bd9b4f4e, relay/
Production deployment	https://igneum-relay-iabqarnby-igneum.vercel.app (inspect KHyscUSVKueXueqxvZBRKkaUHwJR), aliased https://relay.igneum.network
Previous production	https://igneum-relay-bgy767z40-igneum.vercel.app
Env added	RELAY_RUN_PUB (the public half of ~/.config/igneum/relay-run-key, made by node tools/relay.mjs keygen the same hour); RELAY_INTAKE_COMPAT unset
Read-backs	/wake answers; fn=machines carries the bound field; the console page answers 200 and c/machines carries poll fields; a v1-shaped register by hostname (key tier) answers named:false bound:false; a signed start-app from the Mac answers 200 (item 394); an unsigned run from master's old tool is refused

Rollback

cd relay && npx --yes vercel@latest --global-config ~/.config/igneum/vercel --scope igneum rollback https://igneum-relay-bgy767z40-igneum.vercel.app (or vercel promote https://igneum-relay-bgy767z40-igneum.vercel.app). Seconds; nothing to undo in the database: the X23 code adds relay_machines.secret_hash and the table relay_wake_seen, both ignored by the old code. What a rollback loses: signed run verification (the old relay never had it), the start-app kind, the ping; PC 2's new agent registers by hostname on either.