Step 6 done on both deployments. CARLOSTEMPORARYAPPS=1 is on, delivered as the drop-in /etc/systemd/system/console.service.d/temporary-apps.conf.
- Dev console (carlos-dev-ie, console sha 5af6127a) restarted 2026-10-24 23:09:05Z. healthz 200, NRestarts 0, no panic, and the running env carries the switch.
- Flagship console (carlos-flagship-ie, console sha cc95be6d) restarted 23:11:10Z, with the same results. The journal lines
parse ses eventandinvalid account "woodstar-*"that appeared after the restart are older than this change: 75 occurrences in the three days before the switch.
End to end:
- Dev (account bab):
deploy --temporary --ttl 1hcreated tmp-f6qaqp and it went live.listshowed "expires in 59m",keepmade it permanent, anddeletegave a 29-day purge date. - Flagship (account bdj): the same sequence on tmp-sphykz, with the same results.
- Flagship (account bdj): tmp-heknv2, a 7-day site Paul asked for (the CARLOS app spec draft), is live with x-carlos-version draft0.
- Left-alone expiry: tmp-rlttvo on dev (1h, due 2026-10-25 00:09Z). The result will be posted here.
Correction to the table above: carlos-flagship-au has 47 routes and carlos-flagship-us has 44. The two counts were swapped. Both had zero tmp- routes.
Off switch: remove temporary-apps.conf, then systemctl daemon-reload && systemctl restart console.service.