# Smoke regression checklist This file is the backend manual regression baseline for svg-service. ## Preconditions - docker compose stack is up - backend responds on port 9020 - valid admin API key is available - test scheme exists ## Environment Use these variables in shell: export API_URL="http://127.0.0.1:9020" export API_KEY="admin-local-dev-key" export SCHEME_ID="82086336d385427f9d56244f9e1dd772" ## 1. Health / system - GET /healthz -> 200 - GET /api/v1/ping -> 200 - GET /api/v1/db/ping -> 200 - GET /api/v1/manifest -> 200 ## 2. Scheme registry - GET /api/v1/schemes -> 200 - GET /api/v1/schemes/{scheme_id} -> 200 - GET /api/v1/schemes/{scheme_id}/current -> 200 - GET /api/v1/schemes/{scheme_id}/versions -> 200 ## 3. Structure read model - GET /api/v1/schemes/{scheme_id}/current/sectors -> 200 - GET /api/v1/schemes/{scheme_id}/current/groups -> 200 - GET /api/v1/schemes/{scheme_id}/current/seats -> 200 ## 4. SVG / display pipeline - GET /api/v1/schemes/{scheme_id}/current/svg -> 200 - GET /api/v1/schemes/{scheme_id}/current/svg/display -> 200 - GET /api/v1/schemes/{scheme_id}/current/svg/display/meta -> 200 ## 5. Pricing read model - GET /api/v1/schemes/{scheme_id}/pricing -> 200 - GET /api/v1/schemes/{scheme_id}/pricing/coverage -> 200 - GET /api/v1/schemes/{scheme_id}/pricing/unpriced-seats -> 200 - GET /api/v1/schemes/{scheme_id}/pricing/explain/{seat_id} -> 200 - GET /api/v1/schemes/{scheme_id}/current/seats/{seat_id}/price -> 200 for priced seat - GET /api/v1/schemes/{scheme_id}/test/seats/{seat_id} -> 200 for known priced and unpriced seats ## 6. Draft publish / readiness - GET /api/v1/schemes/{scheme_id}/publish/validation -> 200 - GET /api/v1/schemes/{scheme_id}/draft/publish-readiness -> 200 - POST /api/v1/schemes/{scheme_id}/draft/pricing/snapshot -> 200 when scheme is in draft - GET /api/v1/schemes/{scheme_id}/draft/publish-preview?refresh=true -> 200 - GET /api/v1/schemes/{scheme_id}/draft/publish-preview -> 200 - POST /api/v1/schemes/{scheme_id}/publish?expected_scheme_version_id=deadbeef... -> 409 typed stale conflict ## 7. Admin / ops - GET /api/v1/admin/schemes/{scheme_id}/current/artifacts -> 200 - GET /api/v1/admin/schemes/{scheme_id}/current/validation -> 200 - GET /api/v1/admin/artifacts/publish-preview/audit -> 200 - POST /api/v1/admin/artifacts/publish-preview/cleanup?dry_run=true -> 200 ## 8. Fail criteria Regression is considered failed if any of the following happen: - health or db ping fails - any stable read endpoint returns 500 - passthrough display endpoint fails on known-good sample - publish preview refresh or cached read returns 500 - readiness endpoint contract breaks unexpectedly - pricing diagnostics endpoints fail on healthy environment - publish stale guard is not typed and deterministic