Repository navigation
V19: Add a /ready route to the built server - #692
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LinuxDevil
force-pushed
the
v19-ready-route
branch
from
October 20, 2026 03:04
464902a to
7cd15f3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes audit finding OPS-4 (Vercel competitor audit, 2026-10-19).
What was wrong
The built node server only had
GET /health->ok, so orchestrators could not tell "process is up" from "able to serve" (e.g. during a SIGTERM drain).What changed
createDeployedServeranswersGET /ready:200 {"status":"ready"}while serving,503 {"status":"draining"}onceshutdown()has begun. No auth, no detail in the body,cache-control: no-store./healthis unchanged (liveness); the generated Dockerfile HEALTHCHECK stays on/health.AgentStorehas no cheap ping, so it is skipped. The agent is loaded before the server listens, so "starting" is never observable.lousho devuntouched (node-server/docker only; documented).Tests
src/deploy/nodeServerReady.test.ts: 200 ready and/healthstillok; no auth needed withLOUSHO_API_TOKENset (while/chatstill 401); 503 draining on a non-idle connection once shutdown starts. tsc, typecheck:tests, lint, test:coverage (6076 passed) and fallow all pass.Changelog: The built node server and Docker image add
GET /ready(200 ready, 503 draining during shutdown), separate from the/healthliveness route.🤖 Generated with Claude Code