Test fixture
Admin defaults vs per-calculator config
Subdomain hometown on Production. Set defaults for this calculator in the manager admin UI, then reload: A must show them, B merges (pinned attribute wins, admin fills the rest), C ignores them entirely (full manual mode).
A · Bare embed (admin defaults)
No attributes. Everything below should match the manager system's admin-configured defaults.
B · Attribute override (merge)
One value pinned via attribute, nothing else. The pinned field must win; every other field must still show the admin defaults.
Pinning override…
C · calculator-config (full manual)
A calculator-config attribute (theme-only here) makes the component skip
the manager fetch entirely — by design. Must show code defaults, never admin values.