v1.1.2 Persistent browser session profiles

1.1.2 (2026-05-19)

Features

• Added opt-in persistent per-origin Chromium profiles via session.enabled, allowing sites to reuse cookies, localStorage, IndexedDB, and anti-bot challenge credentials across webfetch calls.
• Added session.cacheDir config option. When unset, profiles are stored under the global OpenCode config directory in cloakfetch-sessions.
• Skips automatic per-origin profiles when cloakbrowser.launchOptions.userDataDir is explicitly configured.
• Added profile locking with heartbeat and stale-lock cleanup so concurrent fetches do not corrupt the same persistent profile.

Maintenance

• Updated packageManager, CI, and release workflows to pnpm@11.1.3.
• Added tests for session defaults, origin-stable profile paths, privacy-safe profile names, manual userDataDir precedence, config merging, profile creation, and lock release.
• Added repository agent instructions for future maintenance.

Documentation

• Documented the new session configuration block in README and configSchema.json.
• Clarified that persistent sessions are opt-in because they store site session data on disk.

Full Changelog: v1.1.1...v1.1.2