[erickkkyt]

Users can now connect a brand website to Bing and Google AI reports through their signed-in BeatBrowser Chrome profile, then synchronize observations without downloading or uploading spreadsheets. The report workspace shows connection health, saved snapshots, exact platform totals, daily trends and ranked page/query rows. Failed reads preserve saved data, and concurrent sync/disconnect operations are serialized.

Browser observations are the default visibility aggregate. Plain API answers and grounded API answers remain separately selectable, so they no longer inflate consumer-platform visibility.

Validation:

• Web unit suite: 604 tests passed; AI-report library tests: 18 passed; browser reader tests: 6 passed.
• Web/library type checks and repository lint passed.
• Real UI connection and sync succeeded for both providers; saved reports and connection state survived reload. Bing returned daily/page/query tables; Google returned daily/page tables.
• PostgreSQL integration regressions passed in CI against disposable test storage. They were not run locally because their setup applies migrations. No schema migration was added, and no migration was run against the user workspace. Local services were restarted with the new skip-migrations option.

Scope and limitations: this reads official dashboard responses generated by normal browser navigation, not a public AI-report API. Chrome must remain connected and signed in; unavailable reports or changed response formats fail closed. It reads the default three-month view and records actual dates; Google page rows can be limited. Sync is explicitly triggered, with no recurring report schedule or question monitoring enabled. No credentials or raw account responses are tracked.