First week fixes - stability, monitoring, and content corrections

The first week after launch was all about listening to feedback and tightening things up. Here is what changed.

Scenarios stay put

Your active scenario now persists across page refreshes and browser restarts. Previously, navigating away could lose your selected scenario. Fixed.

Bridge fund accuracy

The bridge fund label and calculation now use consistent nominal amounts, so the ratio displayed matches the underlying numbers exactly.

Error monitoring

We wired Sentry into both the Go API and the browser. Every 500 error and unhandled exception is now captured automatically, so we can spot and fix issues before you notice them.

New health monitoring performs deep checks on the database and encryption layer, giving us early warning if anything degrades.

Education content corrections

Several of you flagged inaccuracies in the education articles - thank you. We have corrected the errors and tightened the content.

Database stability

A handful of edge cases in the encryption and scenario storage layers were causing silent failures for some users. All resolved:

• Legacy scenario data now migrates cleanly to the encrypted format
• Double-encoding bug in the encryption migration is fixed
• The feedback button text renders correctly on all screen sizes