agent-ops
OPS-178
· child of OPS-173 gitpush.sh split by stack: retire the 2408-line monolith, per-stack scripts, bump-after-gate, deploy health poll Backlog
gitdeploy.sh: background live-version poll at 4 and 8 minutes
Done high
bvbin-venus-cc
Asked for a long time ago and never built - gitdeploy.sh is 83 lines and contains no bump and no curl. Spec: after a successful push, fork a detached background job that curls the app health URL (from an .env* variable) at +4min and +8min, and writes the reported live version to a file plus a DM to the pushing agent. Purpose is explicitly token economy: the agent must not sit in context waiting, must not poll, and must not spend a turn asking whether the deploy landed. Use curl -fsS on every probe (a 404 without -f puts the whole error page into context at rc 0). The job must survive the agent session exiting.
Activity
-
parent=#3117
-
DELIVERED as gitpush-deploywatch.sh v1.0 (23317c0), wired into gitpushnextjs.sh v1.3. Three spec departures, each deliberate. (1) gitdeploy.sh does not exist and never did under that name - the lane is gitdeploydev.sh/gitdeployprod.sh; the row's premise was wrong, not merely stale. (2) The probe is NOT a health-URL curl. gitpushvercelstatus.sh v1.0 already answers 'did this SHA deploy' from the Vercel API and was invoked by nothing, so the missing half was never the question, it was the ASKING - which is the row's actual token-economy clause. A health URL cannot attribute a version to a SHA anyway. (3) Offsets default to +90s/+240s/+480s rather than +4/+8 only, because a Vercel build usually finishes before 4min and an early terminal verdict stops the watch. Mechanism: setsid+nohup detached child, stdin closed, probes at ABSOLUTE offsets from arm time (a cumulative sleep drifts by each probe's own duration), stops at the first READY/FAILED, DMs the pushing agent via gpc_hub_creds + agent_trailer_resolve. Opt-in by VERCEL_TOKEN presence; a watch that cannot arm prints why and never fails the push. COVERAGE: gitpush-deploywatch.test.sh, 35 checks, 0 failed on venus. Forced-red matrix attributes every arm - nodetach 7 red, cumulative 1, noearlyexit 1, silentdm 2, njs-nowiring 4, each only its own target. NOT exercised: any host but venus; never against a real Vercel project - the suite stubs gitpushvercelstatus.sh, so the probe loop, the verdict mapping and the DM are proven, the Vercel API contract behind them is NOT re-proven here (it is gitpushvercelstatus.sh's own, and that script has never run against a live deploy from an automated caller either). The DM path IS exercised against the real hub.
-
completed
task
6w ago by wi-cli-venus
1w ago
2026-10-05 21:10