docs(smoke): drop the #2132 references now that the issue is closed

#2132 was closed without the investigation going anywhere, so every
'pending #2132' pointer in the tree was about to send a reader to a
closed issue whose own diagnosis had already been retracted.

The docs now say what is actually known, and nothing more: the two App
smokes fail under Playwright's WebKit for unidentified reasons; it does
not reproduce in real Safari; an isolated repro of the suspected
mechanism did not reproduce it under Playwright's WebKit either; and
chasing it further was judged not worth the effort. A reader hitting it
locally is told to treat it as unexplained rather than as a defect.

The matrix decision is unchanged and never depended on the cause — the
engine fails, so it is not gated.

No behavior change.

Signed-off-by: cliffhall <cliff@futurescale.com>

scripts/lib/headless-browser.mjs

@@ -27,11 +27,12 @@
  * catch engine-level CSP and iframe divergence, and not close enough to certify
  * Safari specifically — a green run here is not a Safari guarantee.
  *
- * **And that cuts both ways: a RED run here is not a Safari indictment.** #2132
- * was written up as a Safari bug on the strength of a failure in this build
- * alone; a manual check in Safari did not reproduce it. The divergence is widest
- * in the networking layer, which is exactly where that failure lives. Reproduce
- * in the real browser before describing a finding as one users hit.
+ * **And that cuts both ways: a RED run here is not a Safari indictment.** The
+ * WebKit App-smoke failure was once written up as a Safari bug on the strength
+ * of a failure in this build alone; a manual check in Safari did not reproduce
+ * it, an isolated repro of the claimed mechanism did not reproduce it here
+ * either, and the whole line of investigation was dropped. Reproduce in the real
+ * browser before describing a finding as one users hit.
  *
  * Playwright is resolved with a `createRequire` based at
  * clients/web/package.json rather than a bare `import("playwright")`: a bare ESM

scripts/smoke-web-app.mjs

@@ -46,11 +46,12 @@
  * `SMOKE_BROWSER` picks the engine (`chromium` — the default — `firefox`, or
  * `webkit`). CI gates **Chromium** (in the `build` job's `npm run smoke`) and
  * **Firefox** (in the `Sandbox smokes` matrix job); WebKit runs here but is not
- * gated yet — it fails on #2132 under Playwright's WebKit, by a mechanism that
- * is NOT yet identified (the first diagnosis was retracted when an isolated
- * repro did not reproduce it, and the failure stage varies between runs). It has
- * NOT been reproduced in real Safari, so treat it as a property of that build
- * rather than a browser bug until someone shows otherwise (#2086).
+ * gated: this smoke fails under Playwright's WebKit for reasons nobody has
+ * identified, and nobody is currently investigating. It does NOT reproduce in
+ * real Safari, and an isolated SSE repro did not reproduce it in Playwright's
+ * WebKit either — so it is a property of that build, not a browser bug, and it
+ * was judged not worth chasing. Run WebKit locally if you want the signal; do
+ * not read a failure here as a defect until someone has looked (#2086).
  *
  * This smoke is one of the two places the
  * MCP Apps sandbox is genuinely exercised, and the sandbox is built out of the

scripts/smoke-web-browser.mjs

@@ -48,8 +48,8 @@
  * which is also where `SMOKE_BROWSER` picks the engine: `chromium` (the
  * default), `firefox`, or `webkit` (#2086). CI gates Chromium (in the `build`
  * job's `npm run smoke`) and Firefox (in the `Sandbox smokes` matrix job);
- * WebKit runs but is not gated yet, pending #2132 — note this smoke PASSES in
- * WebKit, it is the two App smokes that do not.
+ * WebKit runs but is not gated — note this smoke PASSES in WebKit, it is the two
+ * App smokes that do not (see their headers).
  *
  * The engine question here is narrower than in the App smokes — this asserts a clean
  * first paint, i.e. that the shipped bundle's syntax and API level are

scripts/smoke-web-elicitation.mjs

@@ -27,11 +27,12 @@
  * `SMOKE_BROWSER` picks the engine (`chromium` — the default — `firefox`, or
  * `webkit`). CI gates **Chromium** (in the `build` job's `npm run smoke`) and
  * **Firefox** (in the `Sandbox smokes` matrix job); WebKit runs here but is not
- * gated yet — it fails on #2132 under Playwright's WebKit, by a mechanism that
- * is NOT yet identified (the first diagnosis was retracted when an isolated
- * repro did not reproduce it, and the failure stage varies between runs). It has
- * NOT been reproduced in real Safari, so treat it as a property of that build
- * rather than a browser bug until someone shows otherwise (#2086).
+ * gated: this smoke fails under Playwright's WebKit for reasons nobody has
+ * identified, and nobody is currently investigating. It does NOT reproduce in
+ * real Safari, and an isolated SSE repro did not reproduce it in Playwright's
+ * WebKit either — so it is a property of that build, not a browser bug, and it
+ * was judged not worth chasing. Run WebKit locally if you want the signal; do
+ * not read a failure here as a defect until someone has looked (#2086).
  *
  * Along with `smoke:web:app` this is one
  * of the two places the MCP Apps sandbox is actually loaded, and the two nested