Tracking issue for the v0.2.0 milestone.
Goal: Schema completeness, API parity, CLI consistency, deployability.
Builds on v0.1.0 by closing gaps between the documented schema/API surface and what's actually implemented, aligning CLI flags with the docs, and making the system straightforward to deploy.
Ordered in rough working sequence. Issues within a phase can be done in parallel.
Phase 1 — Lock down the ingest boundary first
Do these before mutating the schema — they reduce the risk of subsequent migrations silently drifting from the incoming data.
Phase 2 — Schema & ETL additions
Schema changes that downstream API work depends on.
Phase 3 — API endpoints
Depends on Phase 2 — the load_zone filter needs #16, and the direct-lookup endpoint benefits from stable schema.
Phase 4 — Downloader resilience
Independent track — can run in parallel with Phases 1–3.
Phase 5 — CLI & deployability
Align the surface and ship a deployable image. Do last so the Docker image and docs capture the final CLI shape.
Auto-closes when every linked issue is closed. Progress is tracked by GitHub via the task list above.
Tracking issue for the v0.2.0 milestone.
Goal: Schema completeness, API parity, CLI consistency, deployability.
Builds on v0.1.0 by closing gaps between the documented schema/API surface and what's actually implemented, aligning CLI flags with the docs, and making the system straightforward to deploy.
Ordered in rough working sequence. Issues within a phase can be done in parallel.
Phase 1 — Lock down the ingest boundary first
Do these before mutating the schema — they reduce the risk of subsequent migrations silently drifting from the incoming data.
Phase 2 — Schema & ETL additions
Schema changes that downstream API work depends on.
esiid_documentstable design with CLAUDE.mdpublish_datefrom ERCOT filenamessettlement_load_zoneto theesiidsschema and ETLPhase 3 — API endpoints
Depends on Phase 2 — the
load_zonefilter needs #16, and the direct-lookup endpoint benefits from stable schema.load_zonesearch filterGET /esiid/{esiid}direct lookup endpointPhase 4 — Downloader resilience
Independent track — can run in parallel with Phases 1–3.
Phase 5 — CLI & deployability
Align the surface and ship a deployable image. Do last so the Docker image and docs capture the final CLI shape.
block_in_placeandblock_onpattern in ETL loaderDockerfileanddocker-composefor local development and deploymentAuto-closes when every linked issue is closed. Progress is tracked by GitHub via the task list above.