svc-tenders Status Code Map

Purpose

This note documents the recurring status-code families in the densest svc-tenders route modules after Cleanup Sprint 38.

Focus:

• 200 successful read/update/action responses
• 201 create-style responses
• 400 invalid input/request errors
• 403 capability or ingress denials
• 404 not-found cases
• 409 state/conflict/domain-transition errors
• stream/download paths that break the normal JSON response pattern

Labels used here:

• VERIFIED
• REAL
• TRANSITIONAL

registerTenderDeclarationRoutes.ts