After the first successful sign-in, store the resolver host that found the user. Subsequent visits skip the fallback list (0.0.3) and go straight to the host that worked last time — faster, fewer wasted requests.

Storage shape

localStorage['jss-sso:resolver-history'] = JSON.stringify([
  { host: 'https://solid.social', lastSuccess: 1747000000000 }
]);

Multiple entries possible (e.g. if a user uses different keys for different pods). The flow tries the most-recently-successful host first.

Acceptance

• First successful resolution stores { host, lastSuccess }
• Subsequent loads of the page resolve via the stored host first
• If the stored host now 404s on the same pubkey (user moved pods), fall through to 0.0.3's list as if there were no stored host, and update storage on success
• Clear-storage path: a small "Forget my resolver" link in the footer

Refs

• 0.0.3 — multi-resolver fallback (the list this entry short-circuits)