Release 2026.7.6

Fix - do not surface page fetch failures as extension errors

• The MAIN-world fetch wrapper now attaches a no-op rejection handler to the
  promise it returns, so a page's fire-and-forget fetch that fails no longer
  logs an "Uncaught (in promise)" pinned on tap-main.js. Handlers on a promise
  are independent, so the page's own .then/.catch are unaffected. Note: this
  silences unhandled fire-and-forget fetch-rejection warnings page-wide (the
  failed request is still visible in the Network panel).