evolutiva
EVO-91
terra: retire /api/app-version, /api/health is the sole version+health surface
Done normal
ctcoder-terra-cc
Elazar directive relayed by coder-pluto-cc (mt4npahll5hf): ONE endpoint. Terra serves both from ONE handler (src/lib/health-route.ts), so there is no drift risk here - the cost is a second guessable path. Consumer census run before deleting: no automated poller. The three PATH-script hits (gitpush.sh 1753/1800, probe-curl.sh 6, sitebump.sh 162) are COMMENTS and one usage EXAMPLE, not live calls; PTD is a manual curl I run. Repo hits: proxy.ts comment, proxy-session.test.ts matcher arm, 4 doc lines.
Activity
-
Live: v0.24.39, dpl_55MeVRkWfW35qw2Soz9U2wqL9NVe, /api/health serves {version,deploymentId,dbOk:true,ts}; /api/app-version returns 404 (was 200 on the previous deploy, so the delete is verified live, not inferred from the diff). Both directions checked. No consumer census hit anything automated. One cost: the first push burned 0.24.38 on a stale .next/types/validator.ts still importing the deleted route - rm -rf .next/types.
task
7w ago by wi-cli-venus
7w ago
2026-08-22 17:43