chore: mark v0.0.82 (#1764)

## ✨ Highlights

- **🧰 WebMCP tools become real MCP tools** — the tools a page registers
through the [WebMCP](https://webmachinelearning.github.io/webmcp/) API
now show up right in the tool list as `webmcp_<tool>`, with the page's
own input schema and annotations, so an agent can call them directly and
let the page do the work instead of driving its UI. The list follows the
current tab, and clients get a `tools/list_changed` notification when it
changes. This replaces `browser_webmcp_list` / `browser_webmcp_call`
from v0.0.81, which are no longer exposed over MCP. Tool names,
descriptions, schemas and results come from the page, so treat them as
untrusted input. Pass `--no-webmcp` (config `webmcp: false`, env
`PLAYWRIGHT_MCP_WEBMCP=false`) to opt out. WebMCP is experimental, see
[WebMCP in Chrome](https://developer.chrome.com/docs/ai/webmcp) for how
to enable it.
([microsoft/playwright#42671](microsoft/playwright#42671))
- **🌗 Switch between light and dark color scheme**
([microsoft/playwright#42243](microsoft/playwright#42243))
— an agent working on a dark theme had no way to see it mid-session. The
new **`browser_emulate_media`** tool emulates media features on the fly:
`colorScheme`, `reducedMotion`, `forcedColors`, `contrast` and the
`media` type (screen / print). Omitted parameters are left unchanged,
`null` clears an override.
([microsoft/playwright#42668](microsoft/playwright#42668))
- **📁 Absolute paths in results**
([microsoft/playwright#42497](microsoft/playwright#42497))
— links to snapshots, screenshots, console logs and downloads are
relative to the workspace root, which a client without one cannot
resolve. Pass `--file-paths=absolute` (config `filePaths: "absolute"`,
env `PLAYWRIGHT_MCP_FILE_PATHS=absolute`) to get absolute paths instead.
([microsoft/playwright#42673](microsoft/playwright#42673))

## 🐛 Fixes

- `fix(mcp): keep upload modal and reject bad headers` — a failed
`browser_file_upload` (e.g. a missing file) reports the error and keeps
the file chooser open so it can be retried, and `browser_route` (opt-in
via `--caps=network`) returns an error for a header that is not in the
`Name: Value` form instead of setting a header named `""`.
([microsoft/playwright#42713](microsoft/playwright#42713))
- `fix(chromium): bypass service workers on the storage state page` —
`browser_storage_state` (opt-in via `--caps=storage`) no longer runs the
site's own scripts, or fails when they redirect, for origins with an
active service worker
([microsoft/playwright#42656](microsoft/playwright#42656)).
([microsoft/playwright#42664](microsoft/playwright#42664),
[microsoft/playwright#42741](microsoft/playwright#42741))

## 📦 Upgrading

Configs that use `@playwright/mcp@latest` pick this release up on the
next client restart. To pin it:

```bash
npx @playwright/mcp@0.0.82
```

Author: pavelfeldman

.claude/skills/release.md

@@ -57,11 +57,35 @@ Filter for `feat(mcp)`, `fix(mcp)`, `feat(extension)`, `fix(extension)`, `feat(a
 
 ## 5. Write `release-notes.md`
 
-Follow the format from the prior release (`gh pr view <prev-PR> --repo microsoft/playwright-mcp --json body -q .body`). **No top-level `#` header** — the PR title is the heading. Sections: `## What's New` (with `### New Tools`, `### Tool Improvements`, optional `### Browser Extension`, `### Dashboard`, `### Other Changes`) then `## Bug Fixes`. Link each entry to its PR (`[#NNNNN](https://github.com/microsoft/playwright/pull/NNNNN)` or the playwright-mcp equivalent). Fold follow-up PRs into the feature they extend (e.g. a `browser_find` enhancement joins the `browser_find` bullet).
+Follow the format from the prior release (`gh pr view <prev-PR> --repo microsoft/playwright-mcp --json body -q .body`; v0.0.82, [#1764](https://github.com/microsoft/playwright-mcp/pull/1764), is the reference). **No top-level `#` header** — the PR title is the heading. Three sections:
+
+````markdown
+## ✨ Highlights
+
+- **<emoji> Short headline** ([microsoft/playwright#<issue>](https://github.com/microsoft/playwright/issues/<issue>)) — <what the user could not do before>. <What is new: the tool with its parameters, or `--option` (config `key`, env `PLAYWRIGHT_MCP_KEY`)>. ([microsoft/playwright#<pr>](https://github.com/microsoft/playwright/pull/<pr>))
+
+## 🐛 Fixes
+
+- `<commit subject>` — <user-visible effect, naming the tool> ([microsoft/playwright#<issue>](https://github.com/microsoft/playwright/issues/<issue>)). ([microsoft/playwright#<pr>](https://github.com/microsoft/playwright/pull/<pr>))
+
+## 📦 Upgrading
+
+Configs that use `@playwright/mcp@latest` pick this release up on the next client restart. To pin it:
+
+```bash
+npx @playwright/mcp@0.0.<next>
+```
+````
+
+- **Highlights** — one bullet per feature, most exciting first, each with its own emoji. Lead with the motivation (the linked issue, when there is one; omit the issue link otherwise), then what is new. New tools, tool improvements, options, extension and dashboard changes all go here. Fold follow-up PRs into the feature they extend (e.g. a `browser_find` enhancement joins the `browser_find` bullet).
+- **Fixes** — start with the commit subject in backticks, then say what changes for the user. Reword the subject when it does not match what landed.
+- Link PRs as `[microsoft/playwright#NNNNN](https://github.com/microsoft/playwright/pull/NNNNN)`, or `[#NNNN](https://github.com/microsoft/playwright-mcp/pull/NNNN)` for this repo.
 
 Wording rules:
 - Only list things that change user-visible behavior.
-- **Do not mention features that are not enabled by default** — confirm with the user before listing experimental flags.
+- **Describe what landed, not what the PR description says** — read the diff (`git show <sha>`). Descriptions go stale during review: parts get dropped, behavior changes (e.g. "ignores" became "returns an error").
+- **Do not mention features that are not enabled by default** — confirm with the user before listing experimental flags. A fix to an opt-in tool can be listed when annotated, e.g. `browser_route` (opt-in via `--caps=network`).
+- When a release removes or replaces something announced earlier, say so in the bullet of the feature that replaces it.
 
 ## 6. Commit, push, open the PR with the notes as its body
 

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@playwright/mcp",
-  "version": "0.0.81",
+  "version": "0.0.82",
   "description": "Playwright Tools for MCP",
   "repository": {
     "type": "git",

package.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/microsoft/playwright-mcp",
     "source": "github"
   },
-  "version": "0.0.81",
+  "version": "0.0.82",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "@playwright/mcp",
-      "version": "0.0.81",
+      "version": "0.0.82",
       "transport": {
         "type": "stdio"
       }