It was the literal 'Forecast'. The moment the buckets were renamed to carry their sort prefix -- '04 - Forecast' -- nothing matched: every row counted as a comparison rather than a step, so the walk had no middle, the loads came to nothing, and the bridge showed the basis cancelling itself exactly to zero with a Forecast anchor of 0.00 over 0 rows. The version's adjustment_bucket is the right source, being the same value an unbucketed adjustment is labelled with, so the bridge and the pivot agree by construction rather than by both hardcoding the same string. If that value names no bucket in the data -- renamed since, or never configured -- it falls back to whichever bucket actually holds the adjustments. A bridge that is merely mislabelled beats one that is silently empty. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| vendor | ||
| .gitignore | ||
| eslint.config.js | ||
| index.html | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| vite.config.js | ||
React + Vite
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Currently, two official plugins are available:
- @vitejs/plugin-react uses Oxc
- @vitejs/plugin-react-swc uses SWC
React Compiler
The React Compiler is not enabled on this template because of its impact on dev & build performances. To add it, see this documentation.
Expanding the ESLint configuration
If you are developing a production application, we recommend using TypeScript with type-aware lint rules enabled. Check out the TS template for information on how to integrate TypeScript and typescript-eslint in your project.