Avoid blocking account config on status reads

[Pigbibi]

Summary

• make /api/config return account options even when current GitHub variable status reads are slow
• cap current strategy status reads with a fallback instead of blocking switching
• show a loading state while account config is being read

Validation

• jq empty web/strategy-switch-console/strategy-profiles.example.json
• node --experimental-default-type=module tests/strategy_switch_worker_validation.mjs
• sed -n '/<script>/,/</script>/p' web/strategy-switch-console/index.html | sed '1d;' | node --check --input-type=commonjs
• node --check --input-type=module < web/strategy-switch-console/page_asset.js
• node --check --input-type=module < web/strategy-switch-console/worker.js
• python3 scripts/runtime_settings.py validate
• python3 -m unittest discover -s tests -v

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 01ef7340ff

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore render after config load failures

When /api/config fails, returns non-OK, or the session expires and returns no accountOptions, this new loading state is rendered before the request but the failure/no-config paths only set state.configSource = "default" without calling render(). The UI therefore stays stuck on “Loading config” with switching disabled until the page is reloaded; re-render after the fallback state is applied.

Useful? React with 👍 / 👎.