Paul Trowbridge aa03e74b5e Prefix the adjustment bucket, and list the hardcoded names ... Adjustments fell back to a bare 'Forecast' while the loads they adjust read '04 - Forecast', so the bucket column split in two and the adjustments sat apart from the rows they came from. The fallback now matches. The three fallback names are gathered into one DISPLAY DEFAULTS block at the top of sql_generator, exported, and tabulated in CLAUDE.md, so the answer to "where did that name come from" is one place rather than a grep. The incremental row stamps in the operation routes use the constant now instead of restating the literal, which is how they drifted apart in the first place. None of this belongs in the source. ADJUSTMENT_BUCKET carries a number that only suits one convention and changing it changes every version on every source; the note says what per-version would take. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-09-17 23:42:51 -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	Prefix the adjustment bucket, and list the hardcoded names	2026-09-17 23:42:51 -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