docs(readme): clarify Chromium preload warning is a site-level notice

[ryan-baum]

Summary

Adds one troubleshooting row clarifying that the Chromium console warning A preload for ... is found, but is not used because the request credentials mode does not match (inject-net.js:271) is a page-level Chromium notice — emitted because the passive network shim calls through to the page's original fetch() — and is not the same as an Interceptor connection failure.

Why

Users hit this on the extension error page and mistake it for an Interceptor failure. The note tells them to treat it as a site warning unless interceptor commands actually fail (and points to the existing extension: not reachable row if they do).

Verification

• Documentation-only change; no runtime behavior affected.

(Replaces #121, which inadvertently bundled a local scaffolding file.)

Summary by CodeRabbit

• Documentation
  • Updated Troubleshooting guide with information about Chrome extension preload warnings, including when they occur and how to distinguish them from actual connection issues.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 41fba9c1-8211-46ad-b29f-bfa3fd24d2be

📥 Commits

Reviewing files that changed from the base of the PR and between db35d03 and 93f5ff4.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

A single row is added to the README troubleshooting table documenting the Chrome preload credentials-mode mismatch warning (inject-net.js:271). It clarifies the warning is a page-level preload issue, not an Interceptor connectivity failure, and directs users to the existing extension-reachability row if commands fail.

Changes

README Troubleshooting Table

Layer / File(s)	Summary
New preload warning troubleshooting row README.md	Adds a row describing the Chrome preload/credentials-mode mismatch warning from inject-net.js:271, distinguishing it from Interceptor connection failures and pointing to the extension-reachability row when commands fail.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A rabbit hopped in with a one-liner fix,
A warning that Chrome likes to mix —
"It's the page, not the plug!"
The docs gave a shrug,
And the README got added to the mix. 🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding documentation to clarify that a Chromium preload warning is a site-level notice rather than an Interceptor failure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}