Christian Byrne 2d0980cb1c fix: use authenticated API for remote config polling (#8266) ...

## Summary
- Fixes remote config polling to use authenticated API
- Consolidates `loadRemoteConfig` into `refreshRemoteConfig` with auth
control
- Adds unit tests for both auth modes

## Problem
The cloud extension's polling interval was using unauthenticated
`fetch`, causing it to receive only default feature flags instead of
user-specific configurations.

**Root cause:**
1. Bootstrap called `loadRemoteConfig()` (raw `fetch`, no auth) -
correct, auth not initialized yet
2. Extension watch called `refreshRemoteConfig()` (`api.fetchApi`, with
auth) - correct
3. Extension interval called `loadRemoteConfig()` (raw `fetch`, no auth)
- **bug**

## Solution
- Consolidate into single `refreshRemoteConfig()` with optional
`useAuth` parameter (defaults to `true`)
- Bootstrap: `refreshRemoteConfig({ useAuth: false })`
- Polling: `refreshRemoteConfig()` (authenticated by default)

## Test Plan
- Unit tests verify both auth modes
- `pnpm typecheck`, `pnpm lint`, `pnpm test:unit` all pass

┆Issue is synchronized with this [Notion
page](https://www.notion.so/PR-8266-fix-use-authenticated-API-for-remote-config-polling-2f16d73d3650817ea7b0e3a7e3ccf12a)
by [Unito](https://www.unito.io)

2026-01-23 15:41:21 -08:00

..

refreshRemoteConfig.test.ts

fix: use authenticated API for remote config polling (#8266)

2026-01-23 15:41:21 -08:00

refreshRemoteConfig.ts

fix: use authenticated API for remote config polling (#8266)

2026-01-23 15:41:21 -08:00

remoteConfig.ts

fix: use authenticated API for remote config polling (#8266)

2026-01-23 15:41:21 -08:00

types.ts

feat: add per-tab workspace authentication infrastructure (#8073)

2026-01-15 17:24:48 -08:00