docs: document 152.0.7977.54 release updates

Author: MSTU0

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 > **Research scope:** Entries in this changelog describe features evaluated in authorized labs and defensive benchmarking programs. Follow the [Legal Disclaimer](DISCLAIMER.md) and [Responsible Use Guidelines](RESPONSIBLE_USE.md). We work with security vendors to investigate any misuse, so report concerns to [support@botbrowser.io](mailto:support@botbrowser.io).
 
+## [2026-09-02]
+### Major
+- **Chromium Core -> 152.0.7977.54**: Started the BotBrowser 152 release line with upstream Web Platform, rendering, and security updates.
+
+### Improvements
+- **Per-Context Identity Consistency**: Improved profile-backed browser identity consistency across navigation and request workflows.
+- **Per-Context Window and Viewport Consistency**: Improved profile-backed window and viewport behavior across desktop and mobile workflows.
+- **WebKit-Family Graphics Consistency**: Improved profile-backed graphics consistency for focused Canvas workflows.
+
 ## [2026-08-30]
 ### Major
 - **Chromium Core -> 151.0.7922.174**: Updated the BotBrowser 151 release line with upstream Web Platform, rendering, and security updates.

PER_CONTEXT_FINGERPRINT.md

@@ -304,7 +304,7 @@ Most `--bot-*` flags from [CLI_FLAGS.md](CLI_FLAGS.md) work with per-context con
 | Storage and Memory | [`--bot-js-heap-size-limit`](CLI_FLAGS.md#flag-bot-js-heap-size-limit) and [`--bot-storage-quota`](CLI_FLAGS.md#flag-bot-storage-quota) for profile, real, or explicit byte-value policy |
 | Network | [`--bot-network-info-override`](CLI_FLAGS.md#flag-bot-network-info-override) for profile, native, or custom JSON network information policy, [`--bot-local-dns`](CLI_FLAGS.md#flag-bot-local-dns) for context DNS policy |
 | WebRTC | [`--bot-webrtc-ice`](ADVANCED_FEATURES.md#webrtc-leak-protection) for ICE endpoint control |
-| Window | [`--bot-always-active`](ADVANCED_FEATURES.md#active-window-emulation) to maintain active window state |
+| Screen and Window | [`--bot-config-window`](docs/guides/fingerprint/SCREEN_WINDOW.md) and [`--bot-config-screen`](docs/guides/fingerprint/SCREEN_WINDOW.md) for profile-backed desktop and mobile display settings, [`--bot-always-active`](ADVANCED_FEATURES.md#active-window-emulation) to maintain active window state |
 | Session | `--bot-inject-random-history` for session authenticity (supports precise count, e.g., `=15`), `--bot-cookies` for context-scoped cookie import at creation time |
 | Automation | [`--bot-cdp-coalesce`](CLI_FLAGS.md#flag-bot-cdp-coalesce) for context-scoped CDP hover movement, `--bot-script` for framework-less automation bootstrap at creation time |
 | Diagnostics | [`--bot-v8-log-exclude-api`](CLI_FLAGS.md#flag-bot-v8-log-exclude-api) for context-scoped V8Log API filters |
@@ -317,7 +317,7 @@ See [CLI_FLAGS.md](CLI_FLAGS.md) for the complete flag reference.
 
 ## Context Identity Lifecycle
 
-A BrowserContext accepts its full profile and identity configuration until its first renderer starts. This includes profile, browser and platform identity, locale, screen and window metrics, and other fingerprint-bearing settings.
+A BrowserContext accepts its full profile and identity configuration until its first renderer starts. This includes profile, browser and platform identity, locale, screen and window metrics, and other fingerprint-bearing settings. Profile-backed screen and window settings remain associated with that context across desktop and mobile workflows.
 
 After the first page or worker starts, the context identity is sealed. Later identity-bearing changes are rejected instead of partially updating an active context. Create a new BrowserContext when a different profile or device identity is required.
 

docs/guides/fingerprint/SCREEN_WINDOW.md

@@ -88,6 +88,12 @@ Desktop profiles default to `real` in headful mode, meaning the browser uses act
 --bot-config-screen=profile
 ```
 
+<a id="per-context-configuration"></a>
+
+### Per-Context Configuration
+
+For Per-Context Fingerprint, pass `--bot-config-window` and `--bot-config-screen` in `botbrowserFlags` before the context creates its first page or worker. The selected display policy then remains associated with that BrowserContext across desktop and mobile profile workflows. See [Per-Context Fingerprint](../../../PER_CONTEXT_FINGERPRINT.md) for the setup order.
+
 ---
 
 <a id="how-botbrowser-controls"></a>

docs/guides/platform/WEBKIT_PROFILE_CONSISTENCY.md

@@ -14,7 +14,7 @@ For the product page, see [WebKit-family Profile Consistency](../../../WEBKIT_PR
 
 ## Requirements
 
-- BotBrowser 150.0.7871.46 or newer for the current BotBrowser 150 profile line.
+- BotBrowser 150.0.7871.46 or newer with a matching WebKit-family profile package.
 - ENT Tier4 access.
 - A WebKit-family `.enc` profile issued through the enterprise channel.
 - A separate `--user-data-dir` for each browser instance.
@@ -37,7 +37,7 @@ For WebKit-family mobile profile workflows, add `--bot-mobile-keyboard` when edi
 
 - Do not use `browserBrand` or User-Agent overrides to build this profile line by hand.
 - Keep proxy settings with the browser instance or BrowserContext that uses the profile.
-- Use BotBrowser 150.0.7871.46 or newer with a matching BotBrowser 150 profile package for the current WebKit-family consistency updates.
+- Use BotBrowser 150.0.7871.46 or newer with a matching WebKit-family profile package.
 - Validate desktop and mobile profile bundles separately.
 
 **Related documentation:** [Feature Page](../../../WEBKIT_PROFILE_CONSISTENCY.md) | [Profile Management](../getting-started/PROFILE_MANAGEMENT.md) | [Per-Context Fingerprint](../../../PER_CONTEXT_FINGERPRINT.md) | [CLI Flags Reference](../../../CLI_FLAGS.md)

profiles/stable/README.md

@@ -4,12 +4,13 @@ BotBrowser 150 and newer profiles are delivered through subscription or support
 
 | Release line | Matching BotBrowser build | Profile files |
 |--------------|---------------------------|---------------|
+| v152 | 152.0.7977.54 | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
 | v151 | 151.0.7922.174 | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
 | v150 | [150.0.7871.182](https://github.com/botswin/BotBrowser/releases/tag/150.0.7871.182) | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
 | v149 | [149.0.7827.200](https://github.com/botswin/BotBrowser/releases/tag/149.0.7827.200) | Legacy public demo files: `chrome149_*.enc`, `webkit26_*.enc` |
 | v148 | [148.0.7778.97](https://github.com/botswin/BotBrowser/releases/tag/148.0.7778.97) | Legacy public demo files: `chrome148_*.enc` |
 
-Use a profile package with the matching BotBrowser major version. For example, v150 profiles require a v150 BotBrowser binary, and v151 profiles require a v151 BotBrowser binary.
+Use a profile package with the matching BotBrowser major version. For example, v151 profiles require a v151 BotBrowser binary, and v152 profiles require a v152 BotBrowser binary.
 
 > **Access:** BotBrowser 150 and newer profile packages are available through subscription or support at [support@botbrowser.io](mailto:support@botbrowser.io) or [@botbrowser_support](https://t.me/botbrowser_support). Legacy demo profiles can still be launched via [CLI](../../INSTALLATION.md#download--installation) or [Launcher](../../launcher/).