Expose browser pool Chrome policy

[IlyaasK]

Summary

• expose computed normalized chrome_policy JSON on kernel_browser_pool
• confine map[string]any to the raw SDK response boundary
• canonicalize key order and API-style numeric values without HTML escaping
• treat omission and explicit null as absent policy for managed-resource compatibility
• reject non-object response values
• update generated Registry docs

Scope

Additive v1 durable read state only. No runtime/session fields. Live acceptance remains separate.

Tests

Ran repeated focused tests, race tests, full short suite, vet, gofmt, module checks, Terraform example fmt, docs drift, and diff checks.

Coverage includes Framework state roundtrip, deterministic nested JSON, HTML-sensitive characters, numeric canonicalization, omission/null, and non-object rejection.

---

Note

Low Risk
Additive computed read on an existing datasource with no auth or write-path changes; behavior is covered by unit tests.

Overview
Adds a computed read-only chrome_policy attribute to the kernel_browser_pool data source so lookups can surface Chrome enterprise policy overrides alongside other durable pool config.

API policy JSON is unmarshaled at the SDK boundary, then re-encoded into a stable string: sorted keys, API-style numeric values, no HTML escaping in URLs/tags, and omission or explicit null surfaced as Terraform null. Non-object API values produce diagnostics instead of state.

Registry docs and datasource tests cover schema presence, read round-trip, normalization edge cases, and invalid shapes.

^{Reviewed by Cursor Bugbot for commit 95039fa. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit af40ac2. Configure here.}