[gustmrg]

Firecrawl's argument tests copied the tables shared by the other web adapters, with fewer cases, because Firecrawl was not in that matrix. Adding it removes the copies and gives Firecrawl the coverage it lacked. Users see no change.

• tests/plugin-adapters.test.ts: added firecrawl to the "%s web adapter boundaries" matrix, which adds long URLs, a stray endpoint argument, sanitized HTTP 401 and 429 failures, and cancellation.
• tests/plugin-adapters.test.ts: moved the response format test to a "%s web adapter responses" matrix without Firecrawl, whose responses have another shape and their own test. The scrapeOptions case stays as its own test.
• tests/plugin-service.test.ts: removed the end of the revision test, which repeated two checks made elsewhere: a replaced key blocks a web tool, and a tool kept from a replaced session is refused. Its title is now "refreshes provider revisions and stops routing web calls to a revoked provider".

Testing

• npm run lint: clean (two pre-existing warnings in src/components/storage-*.tsx, untouched).
• npm run format:check, npm run typecheck (all four tsconfigs), and npm run build: clean.
• npm test on Node 22: 2445 passed, 6 more than main.
• Removing the session check in assertAccess still fails a kept test.
• Merges cleanly with test(plugins): drop duplicated service tests and cover the oldest settings #325, which edits the next tests in the same file.
• Built app: not checked; the change touches no production code.

Not in this PR

Splitting tests that mix independent behaviors, such as "remembers an always-allowed MCP tool through its integration and never over a Block rule", is left for later.