[vankudothuadhinaik]

FluxQueue closeout and free-tier demo deployment

Branch: feat/doppler-integration
Latest README update: e28b7e6cd2c74ff6edfe369caa73bf86ab949245
Latest verified full CI: run 40943705556 — all four jobs passed
Demo API: https://fluxqueue-api.onrender.com
Render API service: https://dashboard.render.com/web/srv-dbhplvei0phs73f09fcg
Render worker: https://dashboard.render.com/web/srv-dbhpm7ajnfac73ak4vqg
Neon project: fluxqueue-production (Singapore; dedicated to FluxQueue)

Verified / reported green

• Full CI: tests, PostgreSQL integration, dependency audit, security analysis, Docker build/non-root/smoke checks, config validation; all four jobs passed in run 40943705556.
• Render API and separate worker deployments are live; both bind Render's assigned port.
• Dedicated Neon PostgreSQL database uses certificate-verified TLS.
• API supports combined API+worker demo mode via RUN_WORKER=true.
• Owner reports the manual deployment smoke workflow passed, exercising API liveness/readiness and authenticated echo-job completion.
• No ESTIQ/Uptime Sentinel databases or services were reused.

Production hardening still open

• Neon automatic snapshot scheduling is not enabled for this project. One manual snapshot exists; use an external scheduled logical backup or a plan/project feature that supports scheduled backups, and test restoration.
• Confirm the previously exposed Codecov token was revoked in Codecov settings; provider-side revocation cannot be independently verified here.
• Rotate the API key exposed in chat and update the GitHub Actions secret FLUXQUEUE_API_KEY before the next smoke run.
• Test migration rollback, outage/recovery, retry exhaustion, worker termination during handlers, and controlled load/soak behavior against a production-like environment.
• Configure alert ownership/on-call, monitoring retention, least-privilege network/database access, and a key rotation/revocation process.
• Render free-tier sleep/usage limits apply; this is a demo deployment, not a production availability guarantee.

README and this PR description now reflect current status. PR remains open and unmerged.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment

Thanks for integrating Codecov - We've got you covered ☂️

[vankudothuadhinaik]

Deployment closeout update (2026-10-30): Latest branch commit aad51466e174847674bcd3cfcc861d56d4621730 has a successful CI run (40939559171). Render API deployment dep-dbhptiqfngtc73c9s600 is live; logs confirm migrations, application startup, and Uvicorn on port 10000. Render reports the separate worker web service live with WORKER_HEALTH_SERVER=true. Dedicated Neon database has jobs and alembic_version tables and the expected job indexes. The complete authenticated submit → worker execution → result retrieval flow remains unverified because the available environment cannot reach the public Render URLs; both /health/ready probes were inaccessible from the available web client. Render API healthCheckPath is still empty, and the current Render integration does not expose a service-config update action. PR intentionally remains open and unmerged.

[vankudothuadhinaik]

Added an opt-in deployment smoke workflow at .github/workflows/deployment-smoke.yml. It checks API liveness/readiness, submits an authenticated echo job, and polls until the worker completes it and the result matches. It is manual-only to avoid scheduled production writes. The workflow requires repository Actions secret FLUXQUEUE_API_KEY (the current active tenant key); the secret value is not readable through the available GitHub integration. End-to-end production verification remains pending until that secret is present and the workflow is run. PR remains open and unmerged.