QUALITY 1: Quality vectors

[ktursunov]

Tech story (internal engineering program) — in progress; the foundation the other QUALITY features build on.

The engineering side of quality: the CI gates that enforce the product Quality Framework — named metrics, each guarded by a check that blocks changes lowering the floor.

Problem

No enforced definition of "good": untested code merges and unvalidated metrics ship.

Outcome

Every merged change meets the floor; quality numbers move only up.

Scope — test/coverage gates (required CI checks on every PR)

• Live today: E2E metric reconciliation, bronze→API (e2e-bronze-to-api.yml, declarative metrics/*.test.yaml) + metric-catalog coverage gate; unit/component coverage 80% + 80% new-code (ci.yml); API-contract OpenAPI-drift (openapi-specs.yml).
• Promote to a gate: deployment smoke (functional-k3s.yml) — exists but is manual (workflow_dispatch), not required.
• The real gap: bronze→silver / silver→gold transformation gates — exist only as open PRs feat(ingestion): cross-connector silver-contract parity gate (git commits) #1344 / test(data): ClickHouse data-presence / dedup / freshness audit #1335; land and gate them.

The substantive work is closing those last two — the E2E, unit, and API-contract gates already run.

---

Planning:
Scope: Deployment testing; CI: E2E and unit tests; API contract tests; bronze-to-silver transformation tests; silver-to-gold tests.
Assignee: Konstantin Tursunov
Estimation (days): 15