Documentation cleanup pass #6
Labels
No labels
bug
decision
docs
enhancement
integration
ops
security
tech-debt
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/BatteryStorageCalculator#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Docs have drifted from reality:
docs/roadmap.mdis 727 lines with every one of its ~400 checkboxes marked complete. It reads as a finished historical artifact but is still presented as a live roadmap. Remaining work actually lives in the audit doc, not here.docs/implementation-audit.mdis dated 2026-05-13 but describes work committed well after that (server-side calculation API, caching, whole-home exclusion).Missingsection contains anInverter Modelingsubsection whose remaining gaps readNone- it belongs under implemented, not missing.docs/calculation-logic-audit.md(849 lines) needs a freshness check.Goal: roadmap retired or clearly marked historical, audit re-dated and corrected, remaining work pointed at the issue tracker rather than restated in prose.
Cleanup pass done across four documents.
docs/roadmap.md— reframed as a historical record. Added a header stating it is complete, that work is tracked in issues, and that a checked box means scope delivered rather than capability live (Milestones 7 and 8 delivered a framework and a manual/CSV path, not live integrations). The Open Questions section now links to #15-#18 instead of restating them.docs/implementation-audit.md— re-dated to 2026-07-16 with the 2026-05-13 revision noted. Fixes:Missing > Inverter Modelinglisted ~11 implemented features under a heading that said its remaining gaps wereNone. Moved to a newImplementedsection.Missingrenamed toKnown Gaps, with every gap now linking to its issue.Partial Or Needs Reworkrenamed toImplemented With Caveats— it contained no outstanding work.src/App.jsx:47has 11 (missing Billing, Reports, Admin).docs/calculation-logic-audit.md— verified against code before editing. Its formulas and every rate constant are still accurate (onlysimulation.jsandoutage.jschanged since it was written, and that was a behavior-neutral perf refactor), so those were left untouched. What was wrong was structural — it claimedsrc/App.jsxis the calculation coordinator, which stopped being true when calculation moved to the shared runtime. Rewrote Data Flow, added aWhere Calculations Runsection (worker/backend parity, routes, fallback, cache revisions,warningscodes), repointed three location claims tocalculationEngine.js/projections.js, documented per-circuit whole-home exclusion under outage — explicitly noting it does not affect bill savings — and extended the test list.README.md— migration table listed 3 of 7 migrations and wrongly attributed calculation results to001(it's004). Rebuilt from the actual DDL. Added a Contributing section covering changelog, versioning, CI, and Renovate. Added the missing Reports tab.Also noted: two migrations share the
003_prefix. Verified this is not a bug —backend/src/migrate.jskeys each by full filename and sorts lexicographically, so ordering is deterministic. Documented as a naming smell with a note to use007_next.Staged in the working tree; not yet committed.
Done in #20 (
a0d604b) and corrected in #21 (5411033).The #21 follow-up was necessary because the #20 branch was cut from a stale
main: the calculation audit merged in still described payback as plain division and asserted battery degradation was unmodeled, both untrue afterb31aa8c. Now reconciled againsta0d604b.