critical_paths.yaml

# Unstract critical paths registry.
#
# A "critical path" is an end-to-end user or system flow whose failure would
# constitute a production incident. The rig reports:
#   ✅ covered    — at least one group in `covered_by` ran green this build
#   ⚠️ gap        — no covering group ran green this build
#   ❌ regression — a path that was ✅ on the cached main baseline is now not ✅
#
# Only one kind of gap gates --fail-on-critical-gap:
#   • in-scope gap     — a covering group ran in this tier but not green; fails.
#   • out-of-scope gap — covered only by an unrun tier, or no group declared;
#                        warn-only (a tier can't fail for coverage it can't run).
#
# Only wire `covered_by` to a group that really exercises the path — a bogus
# mapping fails the build when that group breaks, for the wrong reason.
#
# We intentionally do NOT chase 100% coverage. Focus on filling these gaps first.
version: 1

paths:
  - id: auth-login
    description: "User can log in and obtain a session cookie."
    entry: "POST /api/v1/auth/login"
    # Honest declaration: e2e-smoke only exercises the session sentinel +
    # /health/, never POST /api/v1/auth/login. Track as a gap until a real
    # login test exists (likely under tests/e2e/smoke/ or tests/e2e/auth/).
    covered_by: []

  - id: adapter-register-llm
    description: "Register and validate an LLM adapter."
    entry: "POST /api/v1/adapter/"
    # unit-sdk1 covers adapter registration + parameter validation at the SDK
    # layer (the logic the endpoint delegates to). The HTTP round-trip stays an
    # e2e concern; promote when an e2e adapter group exists.
    covered_by: [unit-sdk1]

  - id: workflow-create-execute
    description: "Create a workflow, configure source+destination, execute, poll, fetch result."
    entry: "POST /api/v1/workflow/{id}/execute/"
    covered_by: [e2e-workflow]

  - id: api-deployment-run
    description: "Deploy a workflow as an API, POST a document, receive structured JSON."
    entry: "POST /deployment/api/{org}/{name}/"
    covered_by: [e2e-api-deployment]

  - id: prompt-studio-fetch-response
    description: "Prompt Studio: create project, add prompt, run single-pass, get response."
    entry: "POST /api/v1/prompt-studio/prompt-studio-tool/{id}/fetch_response/"
    covered_by: [e2e-prompt-studio]

  - id: pipeline-etl-execute
    description: "Run an ETL pipeline from source connector to destination."
    entry: "POST /api/v1/pipeline/{id}/execute/"
    covered_by: []   # gap

  - id: usage-token-tracking
    description: "Per-execution token usage is recorded and retrievable."
    entry: "GET /api/v1/usage/get_token_usage/"
    covered_by: []   # gap

  - id: workflow-execution-fan-out
    description: "Multi-file workflow execution fans out to file-processing workers and rejoins."
    entry: "internal: backend → rabbitmq → workers/file_processing"
    covered_by: []   # gap

  - id: callback-result-delivery
    description: "Async results are posted back via the callback worker."
    entry: "internal: workers/callback → backend /internal endpoints"
    covered_by: []   # gap