Data Quality Agent v0.2.0

Data Quality Agent v0.2.0

Data Quality Agent v0.2.0 turns the first public demo into a stronger resume-evidence release. The core product is still intentionally conservative: it demonstrates a realistic business data-quality workflow without claiming external users, customer feedback, or enterprise production adoption.

What changed

• Added a PostgreSQL-backed LLM agent route: POST /postgres/support-tickets/agent-report.
• Reused the read-only support-ticket database adapter for both deterministic reports and agent reports.
• Added safe disabled fallback when the LLM agent route is called without OPENAI_API_KEY.
• Expanded the public outcome evidence manifest with a verified postgres-agent-route claim.
• Expanded scheduled public evidence health checks from 6 to 7 checks, including source verification for the PostgreSQL agent route.
• Updated adoption metrics and history to reflect 52 passing CI tests.
• Kept feedback and user metrics at an honest zero baseline until public evidence exists.

Verified evidence

• Public demo: https://sunnnn2005.github.io/data-quality-agent/
• CI workflow: https://github.com/sunnnn2005/data-quality-agent/actions/workflows/test.yml
• Public evidence health workflow: https://github.com/sunnnn2005/data-quality-agent/actions/workflows/public-evidence-health.yml
• Outcome evidence manifest: docs/outcome-evidence.json
• Public evidence health artifact: docs/public-evidence-health.json
• Resume evidence page: docs/resume-evidence.md
• Container image: ghcr.io/sunnnn2005/data-quality-agent:latest

Verified status

• 52 automated tests pass in GitHub Actions.
• 7 public evidence health checks pass.
• Public metrics currently track 0 stars, 1 fork, 0 confirmed external users, and 0 external feedback items.
• The support-ticket case study still verifies duplicate ticket IDs, missing routing fields, negative amounts, and amount outliers.

Boundaries

• No external users are claimed yet.
• No customer feedback is claimed yet.
• No enterprise production deployment is claimed yet.
• The PostgreSQL demo uses a seeded local support-ticket table and a read-only adapter.
• External model calls remain opt-in through OPENAI_API_KEY.