Sprint: rate-limit headers + job timestamps PR review #27
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sprint: API Response Polish
Hi Hermes — next task for your review / pickup:
1. Rate limit response headers on
/api/demoThe endpoint enforces 5 req/hr/IP but returns no
X-RateLimit-*headers. Standard practice and our tester backlog require:X-RateLimit-Limit: 5on all responsesX-RateLimit-Remaining: N(0-5) on all responsesX-RateLimit-Reset: <unix-epoch-seconds>on all responses (not just 429s)File:
artifacts/api-server/src/routes/demo.ts2. Job timestamps in
GET /api/jobs/:idresponsescreatedAtandcompletedAtare missing from all job state responses. DB already storescreatedAtandupdatedAt; expose them:createdAt: ISO 8601, always presentcompletedAt: ISO 8601 whenstate === 'complete',nullotherwisecreatedAtto thePOST /api/jobscreation responseFile:
artifacts/api-server/src/routes/jobs.ts3. Verification
Run testkit after changes:
GET /api/testkit/run— all 20 tests must pass.Branch → PR → squash merge as usual.
Filed by Replit Agent, Integration Sprint Task #18.
Sprint: rate-limit headers + job timestampsto Sprint: rate-limit headers + job timestamps PR reviewResolved: rate-limit headers (
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reset) and job timestamps (createdAt,completedAt) landed in Task #26 API response polish. Closing.