docs: prepare 150.0.7871.127 release documentation

Author: MSTU0

CHANGELOG.md

@@ -3,6 +3,18 @@
 > **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-07-24]
+### Major
+- **Chromium Core -> 150.0.7871.127**: Updated the BotBrowser 150 release line to 150.0.7871.127. Web Platform consistency, rendering accuracy, and security patches stay aligned with upstream Chrome.
+
+### Improvements
+- **Runtime Math Consistency**: Improved profile-backed runtime math behavior across supported host platforms and browser families.
+- **Proxy Regional Consistency**: Improved automatic language, locale, and timezone alignment for proxy-backed main and per-context sessions.
+- **Per-Context Automation Isolation**: Kept process-level automation bootstrap separate from context-scoped automation across multi-context workflows.
+- **Android Target Isolation**: Improved per-context platform behavior for external protocol handling in Android-target sessions.
+- **Navigation Stability**: Improved resilience for controlled response and extension-related navigation workflows.
+
+
 ## [2026-07-11]
 ### Major
 - **Chromium Core -> 150.0.7871.46**: Updated the BotBrowser 150 release line to 150.0.7871.46. Web Platform consistency, rendering accuracy, and security patches stay aligned with upstream Chrome.

CLI_FLAGS.md

@@ -520,6 +520,8 @@ Execute a JavaScript file right after BotBrowser starts in a privileged, non-ext
 --bot-script="/path/to/script.js"
 ```
 
+At process launch, the script runs once for that browser process. Creating a BrowserContext does not replay it. Pass `--bot-script` explicitly in the context's `botbrowserFlags` when that context needs its own bootstrap.
+
 **Key Features:**
 - No framework dependencies: pure Chrome DevTools Protocol access
 - Earlier intervention: runs before navigation

PER_CONTEXT_FINGERPRINT.md

@@ -351,6 +351,8 @@ Supported live session controls remain available after identity sealing when the
 
 ⚠️ Each context can load a completely different profile (`--bot-profile`), or use `--bot-config-*` flags to override specific settings from the browser's base profile.
 
+⚠️ A process-level `--bot-script` runs once at browser startup and is not replayed when new BrowserContexts are created. Pass `--bot-script` explicitly in a context's `botbrowserFlags` when that context needs its own automation bootstrap.
+
 ⚠️ Proxy merge semantics are explicit: `--proxy-server` in `botbrowserFlags` sets or replaces the context proxy route, while `--proxy-ip` only supplies the exit IP for geo-detection. If a context was created with `createBrowserContext({ proxyServer })`, a later `setBrowserContextFlags` call with only `--proxy-ip` preserves that proxy route.
 
 ⚠️ After identity sealing, dedicated proxy commands may update the route server or bypass rules while preserving the existing proxy IP identity. Changing or clearing `proxyIp` is rejected because it would change geo-derived identity. Create a new BrowserContext when the exit identity must change.

docs/guides/getting-started/BOT_SCRIPT.md

@@ -63,6 +63,8 @@ That is it. BotBrowser loads the profile, opens a browser window, and executes y
 
 For multi-identity workflows, `--bot-script` can also be passed through Per-Context Fingerprint when creating a BrowserContext. Use this when each context needs its own framework-less automation bootstrap.
 
+The process-level script runs once when BotBrowser starts. Creating additional BrowserContexts does not repeat it. Pass `--bot-script` explicitly when creating a context to run a separate context-scoped bootstrap.
+
 ---
 
 <a id="how-it-works"></a>
@@ -140,6 +142,8 @@ const { browserContextId } = await client.send("Target.createBrowserContext", {
 
 Create pages after the context is created so the script and profile are available from the start of the workflow.
 
+Process-level and context-scoped scripts are independent. A process-level script is not inherited by new BrowserContexts.
+
 ### Interacting with iframe content
 
 Bot scripts can monitor for embedded iframes and interact with them using CDP input events:

docs/guides/identity/TIMEZONE_LOCALE_LANGUAGE.md

@@ -115,6 +115,8 @@ Settings are resolved in this order (highest priority first):
 2. **Profile `configs`** (`timezone`, `locale`, `languages` fields in the profile JSON)
 3. **Auto-detected** from proxy IP (default behavior)
 
+An `auto` value selects automatic alignment rather than acting as a manual override. Explicit values apply per setting, so the remaining settings can continue to follow the proxy.
+
 ---
 
 <a id="common-scenarios"></a>

docs/guides/network/PER_CONTEXT_PROXY.md

@@ -118,6 +118,8 @@ const ctxB = await browser.createBrowserContext({
 // -> timezone = "Asia/Tokyo"
 ```
 
+Explicit geographic settings are resolved independently for each context and each setting. Settings left on `auto` continue to derive from that context's proxy.
+
 ### Using --proxy-ip to Skip Detection
 
 When you know the exit IP for each proxy, pass it via `--proxy-ip` to skip the auto-detection step. This eliminates the one-time IP lookup overhead per context. The proxy routing set via `createBrowserContext({ proxyServer })` is preserved:

docs/guides/network/PROXY_GEOLOCATION_ALIGNMENT.md

@@ -44,7 +44,9 @@ This guide focuses on **configuration strategy**:
 
 1. Launch with proxy (`--proxy-server`).
 2. BotBrowser derives geographic signals from the proxy exit IP.
-3. Optional overrides (`--bot-config-timezone`, `--bot-config-locale`, `--bot-config-languages`) take priority.
+3. Explicit CLI or profile `configs` values take priority for the settings they define.
+
+Values set to `auto` keep proxy-based alignment enabled. For example, an explicit locale can remain fixed while timezone and languages continue to follow the proxy.
 
 For internals (lookup pipeline, data source behavior, accuracy boundaries), see [GeoIP Database](GEOIP_DATABASE.md).
 

docs/guides/platform/ANDROID_EMULATION.md

@@ -97,6 +97,10 @@ BotBrowser configures all platform-related surfaces to report Android identity:
 
 BotBrowser normalizes the DevTools inspector page zoom and font scaling when debugging Android profiles, keeping the interface readable on desktop.
 
+### External Protocol Isolation
+
+Android-target contexts prevent unsupported external URL schemes from opening applications on the desktop host. Standard web navigation continues normally.
+
 ---
 
 <a id="phone-vs-tablet"></a>

profiles/stable/README.md

@@ -4,7 +4,7 @@ BotBrowser 150 profiles are delivered through subscription or support at [suppor
 
 | Release line | Matching BotBrowser build | Profile files |
 |--------------|---------------------------|---------------|
-| v150 | [150.0.7871.46](https://github.com/botswin/BotBrowser/releases/tag/150.0.7871.46) | Subscription profiles: [support@botbrowser.io](mailto:support@botbrowser.io), [@botbrowser_support](https://t.me/botbrowser_support) |
+| v150 | [150.0.7871.127](https://github.com/botswin/BotBrowser/releases/tag/150.0.7871.127) | 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` |