Upgrade CloakBrowser to 0.5.1 and release 0.13.1

[brandonkramer]

Summary

• upgrade CloakBrowser from the 0.3.x line to 0.5.1
• bump pi-scraper to 0.13.1
• expand the opt-in browser smoke to prove a persistent profile can be closed and reopened on Windows
• close browser sessions before temporary storage cleanup

Why

The 0.3.x dependency range could not select current CloakBrowser releases. During live verification, a direct Bun runtime probe produced a misleading persistent-launch timeout. Pi-scraper targets Node; the actual tool path succeeds. This adds end-to-end coverage so future upgrades validate the supported runtime and disk-backed profile reuse.

Impact radius

Affected:

• CloakBrowser browser backend dependency
• opt-in live browser smoke and cleanup
• package version

Unaffected:

• fast/readable/fingerprint HTTP modes
• public tool contracts
• stored data schema

Validation

• bun run check — 105 test files, 916 passed, 5 skipped
• PI_SCRAPER_BROWSER=1 CLOAKBROWSER_AUTO_UPDATE=false bun run smoke:browser — live Cloak render plus fresh/reopened persistent profile
• bun run audit:strict — no vulnerabilities
• bun run package:check — 0.13.1 package dry-run passed

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.