Paul Trowbridge 98322a6080 Close the write-only surface left behind by the ordinals ... bucket_order and log.seq were still settable -- PUT /versions/:id took the first, PATCH /log/:logid the second -- with nothing left to read either. A field that only ever gets written is worse than a missing one: the call succeeds, so the caller has no way to find out it did nothing. The columns themselves stay, marked vestigial where they are declared. Dropping a column is not worth a migration to reclaim two that cost nothing. pf.log.bucket is untouched and stays exactly as it was -- what a row counts toward, read first by BUCKET_EXPR. It is the bucket *order* that no longer needs storing, the text having become the order. Also removes a comment head in Forecast.jsx that survived its function and had glued itself onto fitColumns. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-09-17 22:51:34 -04:00
..
auth.js	Put the app behind a login	2026-09-14 22:20:25 -04:00
log.js	Close the write-only surface left behind by the ordinals	2026-09-17 22:51:34 -04:00
operations.js	Put the ordering prefix in the stored label, not in an expression	2026-09-17 22:42:57 -04:00
sources.js	Keep master data for a dim_group instead of re-deriving it from the source	2026-09-17 00:19:39 -04:00
tables.js	Expose pf_note/pf_op in forecast data; fix tables list duplicates	2026-04-28 19:51:45 -04:00
versions.js	Close the write-only surface left behind by the ordinals	2026-09-17 22:51:34 -04:00