Skip to content

feat: add FCAS dispatch target visibility - #9

Open
djurcola-agent wants to merge 4 commits into
djurcola:mainfrom
djurcola-agent:agent/batterywatch-fcas
Open

djurcola-agent wants to merge 4 commits into
djurcola:mainfrom
djurcola-agent:agent/batterywatch-fcas

Conversation

@djurcola-agent

Copy link
Copy Markdown
Collaborator

Summary

  • Reuse retained AEMO Next Day Dispatch UnitSolution artifacts to project all ten FCAS services alongside SOC.
  • Persist one provenance-aware grouped raw/effective record per DUID and interval with deterministic replay, conflict, and precedence handling.
  • Add a bounded GET /api/fcas endpoint and dashboard target panel with honest publication state and the explicit target-not-response disclaimer.

Verification

  • 47 focused backend tests passed.
  • 340 complete backend tests passed.
  • 29 frontend tests passed.
  • TypeScript typecheck and production build passed.
  • Pyright: 0 errors, 0 warnings, 0 informations.
  • Migration shell syntax and git diff checks passed.
  • Fresh independent final review: PASS with no material findings.

Residual risks

  • Migration 010 has static migration coverage but has not been applied to a live PostgreSQL database.
  • Production migration, backfill, deployment, and service restart remain separate explicit gates.

djurcola-agent added 4 commits September 3, 2026 09:16
Preserve owner main's endless energy paging while keeping FCAS requests
bound to the selected range with an independent abort lifecycle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant