docs: changelog 2026-05-15, sync to 148.0.7778.168 with per-context proxy stability and canvas fingerprint replay

Author: MSTU0

CHANGELOG.md

@@ -3,6 +3,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-05-15]
+### Major
+- **Chromium Core → 148.0.7778.168**: Updated to Chrome 148 stable (148.0.7778.168). Web Platform consistency, rendering accuracy, and security patches stay aligned with upstream Chrome.
+
+### Improvements
+- **Per-Context Proxy Stability**: `setBrowserContextFlags` now preserves the context proxy route when a later call only supplies `--proxy-ip`. Existing proxies configured via `Target.createBrowserContext` stay active, and explicit `--proxy-server` overrides still replace the route for new targets.
+- **Canvas Fingerprint Replay**: Full WebGPU canvas recording and kernel-side replay are now production-ready. Canvas operations across 2D, WebGL, and WebGPU are recorded, matched by operation hash at runtime, and returned from profile data rather than live GPU execution.
+
+
 ## [2026-05-09]
 ### Major
 - **Chromium Core → 148.0.7778.120**: Updated to Chrome 148 stable (148.0.7778.120). Web Platform consistency, rendering accuracy, and security patches stay aligned with upstream Chrome.

CLI_FLAGS.md

@@ -106,7 +106,7 @@ This skips per-page IP lookups and speeds up navigation.
 
 ⚠️ Important:
 - Browser-level proxy: use `--proxy-server` for protected geo-detection across contexts
-- [Per-context proxy](PER_CONTEXT_FINGERPRINT.md) (ENT Tier1): set different proxies via `createBrowserContext({ proxy })`; BotBrowser auto-derives geo info in both cases. Guide: [Per-Context Proxy](https://botbrowser.io/docs/network/per-context-proxy/)
+- [Per-context proxy](PER_CONTEXT_FINGERPRINT.md) (ENT Tier1): set different proxies via `createBrowserContext({ proxyServer })` or `BotBrowser.setBrowserContextFlags` with `--proxy-server`; BotBrowser auto-derives geo info in both cases. Guide: [Per-Context Proxy](https://botbrowser.io/docs/network/per-context-proxy/)
 - Avoid: framework-specific options like `page.authenticate()` that disable BotBrowser's geo-detection, which may leak location information
 
 <a id="--proxy-bypass-rgx"></a>
@@ -228,14 +228,14 @@ Guide: [Bookmark Seeding](https://botbrowser.io/docs/identity/bookmark-seeding/)
 ### `--bot-canvas-record-file`
 Canvas forensics and tracking analysis.
 
-Records all Canvas 2D, WebGL, and WebGL2 API calls to a JSONL file for forensic analysis and replay.
+Records all Canvas 2D, WebGL, WebGL2, and WebGPU API calls to a JSONL file for forensic analysis and replay.
 
 ```bash
 --bot-canvas-record-file="/tmp/canvaslab.jsonl"
 ```
 
 **Key Features:**
-- Complete Canvas 2D, WebGL, and WebGL2 API call recording with full parameter serialization
+- Complete Canvas 2D, WebGL, WebGL2, and WebGPU API call recording with full parameter serialization
 - Deterministic capture (noise variance disabled during recording)
 - JSONL format for easy parsing and analysis
 - HTML replay viewer with WebGL enum reverse-lookup and source location mapping

PER_CONTEXT_FINGERPRINT.md

@@ -204,7 +204,7 @@ await Promise.all([
 
 Pass the proxy via context creation options, and set `--proxy-ip` via CDP to skip IP lookups.
 
-> **Note**: Puppeteer uses `proxyServer`, Playwright uses `proxy: { server }`. See [examples/](examples/) for framework-specific syntax.
+> **Note**: Puppeteer uses `proxyServer`, Playwright uses `proxy: { server }`. See [examples/](examples/) for framework-specific syntax. `--proxy-ip` only updates the exit IP for geo-detection. When calling `setBrowserContextFlags` with only `--proxy-ip` (no `--proxy-server`), the proxy routing set via `createBrowserContext({ proxyServer })` is preserved.
 
 ```javascript
 // Puppeteer example
@@ -339,6 +339,8 @@ See [CLI_FLAGS.md](CLI_FLAGS.md) for the complete flag reference.
 
 ⚠️ 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.
 
+⚠️ 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.
+
 ## High-Concurrency Tuning
 
 When running many per-context fingerprints under one browser instance (for example, 20+ concurrent BrowserContexts), launch with [`--bot-gpu-emulation=priority`](CLI_FLAGS.md#--bot-gpu-emulation) to prioritize GPU and WebGPU command-buffer scheduling across sibling contexts. Default behavior is unchanged; this is an opt-in mode for high-concurrency workloads. See [`--bot-gpu-emulation` modes](docs/guides/deployment/LINUX_GPU_BACKEND.md#gpu-emulation-modes).

VALIDATION.md

@@ -299,7 +299,6 @@ For detailed, measured performance data, see [BENCHMARK.md](BENCHMARK.md). Key f
 ### Ongoing Studies
 
 **Advanced Tracking Techniques:**
-- WebGPU tracking research
 - Machine learning-based tracking
 - Behavioral biometric analysis
 - Network-level tracking

docs/guides/getting-started/CANVASLAB.md

@@ -1,6 +1,6 @@
 # CanvasLab: Canvas Forensics and Tracking Analysis
 
-> Record Canvas 2D, WebGL, and WebGL2 API calls to study tracking techniques and verify fingerprint protection.
+> Record Canvas 2D, WebGL, WebGL2, and WebGPU API calls to study tracking techniques and verify fingerprint protection.
 
 ---
 
@@ -27,15 +27,15 @@ chromium-browser \
     "https://example.com"
 ```
 
-After the session, `/tmp/canvaslab.jsonl` contains every Canvas 2D, WebGL, and WebGL2 API call the page made. Open it in the [Replay Viewer](https://botswin.github.io/BotBrowser/tools/canvaslab/canvas_replay_viewer.html) to inspect calls interactively.
+After the session, `/tmp/canvaslab.jsonl` contains every Canvas 2D, WebGL, WebGL2, and WebGPU API call the page made. Open it in the [Replay Viewer](https://botswin.github.io/BotBrowser/tools/canvaslab/canvas_replay_viewer.html) to inspect calls interactively.
 
 ---
 
 <a id="how-it-works"></a>
 
 ## How It Works
 
-When `--bot-canvas-record-file` is set, BotBrowser intercepts every Canvas API call at the browser engine level and writes it to a JSONL file. Each line is a JSON object representing one API call, including:
+When `--bot-canvas-record-file` is set, BotBrowser intercepts every Canvas API call at the browser engine level and writes it to a JSONL file. This covers Canvas 2D, WebGL, WebGL2, and WebGPU. Each line is a JSON object representing one API call, including:
 
 - **Event type**: `canvas_init`, `context_create`, `state`, `draw`, `read`, `resize`
 - **Full parameters**: all arguments serialized (ImageData as base64, Path2D as command arrays, gradients as color stops)
@@ -136,7 +136,7 @@ diff /tmp/canvaslab-linux.jsonl /tmp/canvaslab-macos.jsonl
 
 ## Next Steps
 
-- [CanvasLab Documentation](../../../tools/canvaslab/). Complete reference including recording format, event types, and replay viewer usage.
+- [CanvasLab Documentation](../../../tools/canvaslab/). Complete reference including recording format, event types, replay viewer usage, and canvas fingerprint replay.
 - [Canvas Fingerprinting](../fingerprint/CANVAS.md). Configure Canvas noise and rendering consistency.
 - [WebGL Fingerprinting](../fingerprint/WEBGL.md). Manage WebGL parameter control.
 - [CLI Flags Reference](../../../CLI_FLAGS.md#--bot-canvas-record-file). Flag documentation.

docs/guides/network/PER_CONTEXT_PROXY.md

@@ -120,19 +120,23 @@ const ctxB = await browser.createBrowserContext({
 
 ### 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:
+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:
 
 ```javascript
+const ctx = await browser.createBrowserContext({
+  proxyServer: "socks5://user:pass@proxy.example.com:1080",
+});
 await client.send("BotBrowser.setBrowserContextFlags", {
   browserContextId: ctx._contextId,
   botbrowserFlags: [
     "--bot-profile=/path/to/profile.enc",
-    "--proxy-server=socks5://user:pass@proxy.example.com:1080",
     "--proxy-ip=203.0.113.1",
   ],
 });
 ```
 
+> **Note**: `--proxy-ip` only updates the exit IP used for geo-detection. Omitting `--proxy-server` in `setBrowserContextFlags` does not clear proxy routing already set via `createBrowserContext({ proxyServer })`. If the context was created without `proxyServer`, pass `--proxy-server` in `botbrowserFlags` to set the per-context proxy route.
+
 ---
 
 <a id="common-scenarios"></a>
@@ -222,6 +226,7 @@ await client.send("BotBrowser.setBrowserContextFlags", {
 | Geo signals identical across contexts | Each context needs a different proxy. Verify proxies resolve to different IPs. |
 | `setBrowserContextFlags` not found | Send CDP commands to the browser-level session, not a page-level session. |
 | Flags not taking effect | Call `setBrowserContextFlags` before creating any page in the context. |
+| Proxy seems lost after calling `setBrowserContextFlags` with `--proxy-ip` | Passing only `--proxy-ip` does not clear the proxy set via `createBrowserContext`. If no proxy was set during context creation, pass `--proxy-server` in `botbrowserFlags`; if the proxy still disappears, ensure you are on a current binary. |
 | Need to change proxy after context creation | Use `BotBrowser.setBrowserContextProxy` (ENT Tier3) for runtime switching. See [Dynamic Proxy Switching](DYNAMIC_PROXY_SWITCHING.md). |
 
 ---

tools/canvaslab/README.md

@@ -36,9 +36,8 @@ CanvasLab records every Canvas 2D, WebGL, and WebGL2 API call so you can see exa
 |-----------|--------|
 | **Canvas 2D Recording** | **Shipped** - full API coverage with call stack tracking |
 | **WebGL / WebGL2 Recording** | **Shipped** - full API coverage including shaders, textures, buffers, uniforms |
+| **WebGPU Recording** | **Shipped** - full API coverage including adapters, devices, pipelines, render/compute passes, and readback |
 | **Replay Viewer** | **Shipped** - HTML-based event viewer with Canvas 2D and WebGL support |
-| **Canvas 2D Browser Replay** | **In Development** - reconstruct canvas operations from JSONL |
-| **WebGL Browser Replay** | **Planned** |
 
 ---
 
@@ -53,10 +52,10 @@ chromium \
 ```
 
 **Step 2: Visit a site and let tracking happen**
-Go to the website you want to study. Let it load normally. CanvasLab will record every Canvas 2D, WebGL, and WebGL2 API call the tracking code makes.
+Go to the website you want to study. Let it load normally. CanvasLab will record every Canvas 2D, WebGL, WebGL2, and WebGPU API call the tracking code makes.
 
 **Step 3: Look at what was recorded**
-Close BotBrowser. Your recording is saved to `/tmp/canvaslab.jsonl`. You can now see exactly what Canvas and WebGL calls the tracking code tried to make.
+Close BotBrowser. Your recording is saved to `/tmp/canvaslab.jsonl`. You can now see exactly what Canvas, WebGL, and WebGPU calls the tracking code tried to make.
 
 ---
 
@@ -131,14 +130,11 @@ Close BotBrowser. Your recording is saved to `/tmp/canvaslab.jsonl`. You can now
 
 ---
 
-## What's Next
+## Canvas Fingerprint Replay
 
-### Canvas 2D Browser Replay (In Development)
-Load your JSONL recordings back into BotBrowser to test privacy protections:
-- **Verify privacy protection** - replay tracking code's Canvas calls and check if BotBrowser handles them correctly
-- **Cross-platform testing** - check that privacy works the same on Windows, macOS, and Linux
-- **Ongoing validation** - make sure each BotBrowser update keeps privacy protections working
+BotBrowser supports exact canvas fingerprint replay: when a profile contains canvas data for a specific site, BotBrowser returns those recorded values at runtime instead of performing live GPU/CPU rendering. This makes canvas fingerprints deterministic and site-specific.
 
+Canvas data is embedded in the profile, not controlled by a CLI flag. To get a profile with replay support for a specific site or antibot system, contact us at [support@botbrowser.io](mailto:support@botbrowser.io). We analyze the target's canvas fingerprinting approach and provide a profile with the corresponding canvas data.
 
 ---