2.0.1

Changelog

All notable user-facing changes to What-If Weaver are documented here.

This is the user-facing log. For development history with implementation detail, see CLAUDE.md ## Status & Roadmap and the git tag history.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

No user-visible changes pending.

[2.0.0] — 2026-05-23

A major release. What-If Weaver now ships with a new projection engine — built over the past several months and verified against the previous engine for parity on every scenario type the app supports. Your existing files load and project the same way, but the engine that produces those projections is fundamentally more capable.

Changed

• New projection engine. The Mycroft engine that produces your projections is a from-scratch rebuild. The previous engine remains available as a fallback for the 2.0.x patch window (advanced setting) but is no longer the default.

Added — capabilities the new engine brings

• Per-account fidelity. Projections now track each account's balance individually instead of rolling all investments / all cash into single buckets. Charts and tables that previously summarized across accounts still do, but the underlying math is per-account — so an investment in a 401(k) and an investment in a brokerage compound on their own paths, the way they would in real life.
• Weekly resolution. The engine runs on a weekly calendar (52 ticks per year) instead of monthly. Paydays, expenses, and interest accrual now fall on more realistic schedules.
• More drawdown options. Beyond the "4% rule" fixed-real-dollar drawdown introduced in 1.86.0, the engine now also supports a "liquidity target" drawdown that pulls a configurable weekly amount.
• Richer Monte Carlo. The Monte Carlo simulation now treats different asset classes as independent random walks (stocks, real estate, vehicles each draw their own shocks) instead of one shared coin flip for the whole portfolio.
• Better failure diagnostics. When a projection halts because a household runs out of money, the projection summary now tells you why and which account triggered it (e.g., "Credit wall — Visa Card · 2042"), not just the year. More halt categories will surface in future releases as the engine learns to detect them.

Fixed

• Credit-card charges no longer double-count. The previous engine reduced your projected cash flow and grew your credit-card balance for the same monthly charge — net-worth changed by twice the charge amount. The new engine grows the balance only, matching how a credit card actually works. Your retirement projections that lean on a credit card may look meaningfully different (typically healthier) as a result.

Removed

• Nothing. Existing scenario files (.whatifweaver) load identically.

Notes

• The new engine has been audited against the previous one on every event type and every scenario shape the app supports. The largest residual difference is ~2% at long horizons — a timing artifact of weekly vs monthly compounding, not a math error.
• If you see a projection that doesn't look right, you can fall back to the previous engine via the rollback build flag. The previous engine code is retained in this release for that purpose; it will be removed in a future cleanup release.

[1.86.5] — 2026-05-22

Improved

• Accessibility and visual-consistency polish across the app.

[1.86.1] — 2026-05-21

Improved

• Exported files now lead with your household name, so every file for a household sorts and groups together.

[1.86.0] — 2026-05-21

Changed

• Retirement withdrawals now follow the classic fixed, inflation-adjusted approach (the "4% rule" style): your first-year withdrawal is set as your chosen percentage of your portfolio at retirement, then held steady in real terms each year after. Previously the withdrawal was recalculated every year as a percentage of your then-current balance. Your retirement projections may look different as a result — this is the intended, more standard model.

[1.85.0] — 2026-05-21

Added

• A "Sell asset" plot twist. Pick an asset, enter what you sell it for, optionally pay off an attached loan from the proceeds, and send the rest to cash or investments.

Fixed

• A sold asset no longer keeps appreciating in the projection after its sale date.

[1.84.0] — 2026-05-21

Added

• A "Pay off loan" plot twist. Pick a loan and where the money comes from (cash, investments, or both), and the projection pays off the full remaining balance at that point — no more building it by hand.

[1.83.12] — 2026-05-21

Improved

• Exported files (report, CSV, and saved scenarios) now include your household name in the filename, so they're easy to tell apart and find later.

[1.83.11] — 2026-05-21

Improved

• Refined the wording of the cash-flow guidance so it reads as neutral, factual reference points rather than judgments about your finances.

[1.83.2] — 2026-05-19

Changed

• Renamed the "Cyberpunk 2077" palette to "Cyber Punk" in the palette picker. Same colors, same theme — just a different label.

[1.83.0] — 2026-05-18

Fixed

• Liability values on the breakdown chart and in summary surfaces now display in today's dollars when "Show Real $" is enabled, matching the rest of the breakdown's deflation behavior. Previously, asset categories (cash, investments, real estate, vehicles) were deflated under Show Real $ but liabilities were shown in nominal future dollars — a per-period mismatch that caused net-worth totals on the breakdown chart to disagree with the headline net-worth number on the same page.
• This fix completes the resolution of the net-worth display inconsistency originally diagnosed in v1.79.3. The structural double-counting that originally drove the issue was resolved in v1.81.0; this release closes the remaining display-side deflation drift.

[1.82.1] — 2026-05-18

Changed

• Settings → About panel and the Mycroft glossary entry now describe the engine more precisely: "Mycroft is a deterministic, discrete-time vector-state simulation engine that routes chronological cash flows through prioritized liquidity waterfalls and chain-route switched deficit trees to chart a household's multi-decade trajectory toward either compound accumulation or cascading financial ruin."
• Documentation for the whatifweaver file format now specifies the two precise primitives for converting investments to cash: a one_time plot twist with negative amount (cash → inv → emergency-cash absorption), or a chained pair of asset_event plot twists in the same year (one to remove investments, one to add cash). Replaces an earlier imprecise recommendation.

Internal

• Verified that the net-worth display inconsistency originally reported in v1.79.3 has been resolved by the architectural unification in v1.81.0 and v1.82.0. The original two-engine-paths-producing-different-totals mechanism is structurally closed. A separate residual under the showReal=true display mode (where liabilities aren't deflated like assets) remains as a smaller follow-up; flagged for a future fix.

[1.82.0] — 2026-05-18

Added

• New "Excess Retirement Withdrawals" bucket on the breakdown chart. When your retirement drawdown income exceeds expenses, the surplus accumulates here instead of recycling back into investments. The bucket is functionally cash for net-worth purposes — it shows up in your NW totals and summary bars — but is visually distinct so you can see how much of your portfolio you've withdrawn but haven't spent.
• Bucket protects against credit-card debt growth in retirement: when expenses spike and the bucket has a balance, it absorbs the deficit before any new credit-card debt accrues. Credit-card minimum payments still apply normally, so balances can amortize or stay flat (at the min-payment-equals-interest edge case), but cannot grow while the bucket is available.

Changed

• Documentation now reflects the post-v1.81.0 engine architecture for pre-retirement deficit handling: deficits do not auto-liquidate investments. To convert investments to cash at any life stage, use asset_event or one_time plot twists. The retirement event activates the drawdown mechanism; before that point, investments are a reservoir that grows via ROI and contributions only.
• Test suite audited and rearchitected to verify the post-Spec-157 engine model rather than the pre-Spec-157 paternalistic auto-drain assumption.

[1.81.0] — 2026-05-18

Changed

• Post-retirement withdrawals now model as income. The retirement withdrawal-rate slider sets the percentage of your investment balance withdrawn each year (computed at the start of each year, distributed monthly). The withdrawal adds to your monthly income; investments deplete as withdrawal accumulates. If your total income (withdrawals + Social Security + other) covers your expenses, surplus flows to cash and investments per your allocation. If it doesn't, the shortfall accrues as credit-card debt — visible via the existing banner from the previous release.
• Pre-retirement deficits behave unchanged: investments are a reservoir that grows untouched, and any income shortfall flows through cash reserves and credit-card absorption as before.
• The withdrawal slider's semantic shifted from "draw at least this much, more if needed" to "draw exactly this percentage per year." The slider is now the final arbiter — set it to match your intended annual withdrawal rate. The 0-100% range will be narrowed to a more conventional retirement-planning band in a future release once the new semantic settles.

Fixed

• Resolved the structural double-counting between the previous retirement drawdown mechanism and credit-card def...

1.83.10

Revise README for What-If Weaver releases

Updated README to provide detailed information about What-If Weaver, including features, download instructions, and support contact.