Last Updated: May 17, 2026 Status: Ready for staging smoke validation
mainis merged and synced withorigin/main.- Backend Maven tests passed before the latest readiness work.
- Frontend production build and Vitest suite passed before the latest readiness work.
- Dividend dashboard overview, history, alerts, and events now persist into a durable analysis snapshot in both Mongo-backed and file-backed resource modes.
- Dividend analysis can be reconciled against live SEC sources through
POST /api/dividend/{tickerOrCik}/reconcile, and persisted snapshots can be retrieved throughGET /api/dividend/{tickerOrCik}/snapshot. - Docker Compose now exposes explicit
highandlowdeployment profiles:docker compose --profile high up --builddocker compose --profile low up --build
- Compose configuration validates for both profiles with
docker compose config. - Browser-facing frontend containers proxy
/apiand public actuator health endpoints to the backend service. - A reusable PowerShell smoke test is available at
scripts/smoke-test.ps1.
Run after containers are up:
.\scripts\smoke-test.ps1 `
-BackendBaseUrl http://localhost:8080 `
-FrontendBaseUrl http://localhost:3000For authenticated staging:
.\scripts\smoke-test.ps1 `
-BackendBaseUrl https://api.example.com `
-FrontendBaseUrl https://app.example.com `
-Username $env:EDGAR4J_SECURITY_USERNAME `
-Password $env:EDGAR4J_SECURITY_PASSWORD- Backend image definition exists.
- Frontend image definition exists.
- Compose high-resource profile includes backend, frontend, MongoDB, PostgreSQL, and Redis.
- Compose low-resource profile includes backend and frontend without external service dependencies.
- Compose high-resource profile validates.
- Compose low-resource profile validates.
- Backend liveness/readiness endpoints are public through security config.
- Frontend nginx exposes
/health. - Smoke-test script checks backend probes, frontend health, frontend shell, and dividend API reachability.
- Dividend dashboard analysis surfaces persist a latest snapshot.
- Dividend dashboard supports explicit live-source reconciliation.
- Run smoke test against the target staging infrastructure.
- Confirm production
SEC_USER_AGENTuses a monitored contact, not the default placeholder. - Confirm production secrets are supplied through the hosting platform, not committed config.
- Confirm logs and rollback procedure in the hosting platform.
The previous Docker work log described an old MongoDB container connectivity problem. The compose file has since been replaced with explicit profile-specific services and validated configuration. Final go-live approval still requires running the smoke test against the actual staging or production target because local tests cannot verify hosted secrets, DNS, TLS, ingress, or provider quotas.