[tobiasehlert]

Summary

• Normalize non-breaking spaces (U+00A0) to regular spaces (U+0020) in the fansite API spouse mapping, matching existing HTML parsing.
• Cover fansite spouse normalization and explicitly compare HTML/JSON spouse values in TestCharacterTrollefar using existing fixtures.
• Document the married_to space behavior; leave other fields unchanged.

The observed live v4/v5 difference is documented in the issue. This change aligns both current parsing paths; the live v4 deployment discrepancy has not been independently established.

Validation

• go test ./src -count=1
• git diff --check

Closes #788.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.87%. Comparing base (58b61d0) to head (9d17a75).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #789   +/-   ##
=======================================
  Coverage   88.87%   88.87%           
=======================================
  Files          24       24           
  Lines        3064     3064           
=======================================
  Hits         2723     2723           
  Misses        341      341           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tobiasehlert]

Closing without merging: v5 intentionally returns plain spaces (U+0020) in character.married_to. Hosted checks for Maltusia and Trollefar confirmed consistent results from the v5 HTML and fansite parsers. The non-breaking spaces (U+00A0) in deployed v4 are an accepted version difference; v4 will receive no further updates, and v5 is the way forward. This defensive fansite normalization is therefore unnecessary.