Core Workflow Mapping & Test Plan

[harishconti]

Acceptance Criteria:
TEST_PLAN.md is committed to the repo. It clearly lists all critical flows with module ownership, test inputs needed, and known gaps.

Tasks:

• Read the README, ROADMAP, and docs folder completely to understand the intended product behaviour
• List 5–7 core user flows (e.g., "connect a data source → run a freshness check → view result → alert fires")
• For each flow, trace which modules, services, and API endpoints are involved
• Identify what inputs each flow needs (sample data, config, credentials)
• Identify what the expected output/behaviour is for each flow
• Mark each flow as: ✅ appears to work | ⚠️ unclear | ❌ broken/missing
• Identify what is currently out-of-scope or not yet implemented
• Produce a TEST_PLAN.md file with: scope, flow list, module map, input requirements, risk areas, and known unknowns

# | Flow | Entry Point
-- | -- | --
F1 | Boot stack + API health check | docker-compose.yml → main.py
F2 | Run a data freshness check | routers/freshness.py
F3 | Run a data quality check | routers/checks.py + checks/ dir
F4 | Detect schema drift | routers/schema_diff.py
F5 | Data contract validation | routers/contracts.py
F6 | Alert suppression / noise reduction | routers/alert_noise.py + routers/suppressions.py + alerts/ dir
F7 | Webhook delivery | routers/webhooks.py