[codex] Integrate household costs into cliff reporting#4
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR finishes the household-cost integration that started with CHIP premiums.
It updates both the browser-side PolicyEngine path and the Python calculator path so household costs are treated consistently in net resource calculations, cliff drivers, and the chart UI.
What changed
chip_premiumfromnet_resourcesin the browser-side PolicyEngine transformer for both household and series resultschip_premiumfrom the browser-side PolicyEngine situation payload and carry it through the returned result shapemetadata.household_costs, including CHIP premium as a visible negative series and as a tooltip row in net-income modeWhy
Max's package refactor correctly introduced household costs on the Python side, but the app still had three integration gaps:
net_resourcesThat meant the app could miss real CHIP-premium cliffs in normal usage and under-explain them even when they were present.
Impact
Users now see household costs reflected consistently in:
This keeps the browser path, fallback API path, and visual explanations aligned.
Validation
uv run pytestnpm testnpm run build