thinkpool-pair 0.7.445 → 0.7.448

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -227,6 +227,31 @@ their own sandbox cannot bind a port or launch a browser:
227
227
  Preview roots are read-only, cannot escape the lane worktree, and accept only
228
228
  the preview server’s loopback origin for page requests.
229
229
 
230
+ The browser starts on demand and is reused while work is active. After the
231
+ last active or queued job finishes, 60 seconds of inactivity closes it; the
232
+ next job starts it again. Each job uses a fresh browser context, disposed on
233
+ success or failure. Desktop (1440×900) and mobile (390×844) run sequentially.
234
+ Mobile enables touch, mobile viewport behavior, and a mobile Chromium identity
235
+ at device scale 1. It does not claim to emulate Safari or a physical iPhone.
236
+
237
+ Managed preview jobs across all rooms share one host slot with the repository
238
+ browser checks and the Design render/freeze helpers, including the browser
239
+ tests in `test:unit`. The unit runner also uses one worker. The slot uses an exclusive loopback listener on port 47683;
240
+ it serves no application protocol and disappears if its owning process exits.
241
+ Waiting jobs time out after two minutes without stealing an active slot.
242
+ Personal Chrome tabs and independently launched browser scripts are outside
243
+ this managed limit.
244
+
245
+ From the repository, run `npm run test:browser` for sequential Chromium and
246
+ WebKit viewport, touch/click, and session-isolation checks. Use
247
+ `npm run test:browser -- --engine=chromium` on older Macs without supported
248
+ WebKit. `TP_BROWSER_PATH` also selects an installed Chrome for the app tests
249
+ and Design helpers when bundled Chromium cannot run on the host. CI installs
250
+ both pinned Playwright engines and runs the existing landing focus and Lynx
251
+ request-lifecycle app tests under WebKit (`TP_TEST_BROWSER_ENGINE=webkit`).
252
+ Safari-sensitive releases still require a real-device check of login, keyboard/focus, scrolling, and the
253
+ changed interaction; record the device/OS and result separately.
254
+
230
255
  ## Optional bridge environment variables
231
256
 
232
257
  | Variable | Purpose |