pf_app
Paul Trowbridge
ad02aba8fb
Baseline and reference loads are segment construction, not forecasting. Listing them beside the adjustments buries what the log is actually for -- on version 29 that is four load entries against however many adjustments -- and offers an undo next to them that would silently gut the version. They are managed in the Baseline view instead, which is where they can be edited in place and their date ranges seen. Filtered in the dialog rather than in the route, since Baseline.jsx and the ledger's tag lookup both read the same endpoint and do want every entry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| lib | ||
| public | ||
| routes | ||
| setup_sql | ||
| ui | ||
| .env.example | ||
| .gitignore | ||
| CLAUDE.md | ||
| install.sh | ||
| package-lock.json | ||
| package.json | ||
| PERSPECTIVE.md | ||
| pf_perspective_options.md | ||
| pf_spec.md | ||
| pf.sh | ||
| server.js | ||