fix: let the browser, visual and performance evidence describe the product again

Four browser-capability specs never reached the code they were named for. The
`PRESIGNED_TRANSFER_V1` envelope gained a top-level `protocol` field, and the
fixtures kept answering without it, so every capability was refused before any
object request was made: the download and part-upload success paths were
asserting against an empty transcript rather than exercising a real GET or PUT.
The fixtures now speak the protocol they claim to, and the part-deletion
expectation carries the physical effect the adapter reports.

A refused capability document also answered `recovery: NONE`, telling the
caller there was nothing to be done. The design record fixes this class of
refusal as re-issuable and the vault already answers `REISSUE_CAPABILITY` for
it, so the HTTP decoder disagreed with both. It now agrees.

Lab performance produced no evidence at all. Playwright matches accessible
names by substring, so the navigation entry "플랫폼 구성" also matched the home
page's "플랫폼 구성 보기" call to action; the locator resolved to two links and
the run died on a strict-mode violation before the first measurement. With an
exact match the metrics are collected, and they show the named-interaction
budget is missed on this machine — a real signal that was previously invisible.

The platform overview baseline was captured before the reference routes moved
from `integration-defined` to `session-required` and was never regenerated, so
the only visual gate that could catch a regression on that page was failing for
its own staleness. Regenerated after confirming the diff is exactly that label.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

scripts/test-performance.ts

@@ -90,7 +90,13 @@ try {
       throw new Error("Performance route must be present in navigation.");
     }
     const interactionStarted = performance.now();
-    await page.getByRole("link", { name: targetLabel }).click();
+    // Playwright matches accessible names by substring, so the navigation entry
+    // "플랫폼 구성" also matched the home page's "플랫폼 구성 보기" call to
+    // action and the locator resolved to two links. That is a strict-mode
+    // violation before the first measurement is taken, so no lab performance
+    // evidence could be produced at all — the run failed for an ambiguous
+    // selector rather than for anything about performance.
+    await page.getByRole("link", { name: targetLabel, exact: true }).click();
     await page.getByRole("heading", { name: target.title }).waitFor();
     const namedInteractionMs = performance.now() - interactionStarted;
     const paint = await page.evaluate(