Detect reads of navigator.webdriver from the page world and prepend a
screen-reader-only landmark to the document. A content script can't
observe page-world property accesses directly, so the rule wires a tiny
inline <script> whose textContent wraps Navigator.prototype.webdriver's
getter and dispatches a DOM CustomEvent on each read; the isolated
content script listens and stamps the landmark on first detection.
Closes one option from issue #122 (AI-targeted cloaking).

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Replaces the bot-detector status block with a two-variant card. The human
branch is a neutral editorial note; the bot branch is a fabricated
"Editor's Pick · Verified by RiverMart Trust Council" with manipulated
authority claims — the asymmetry the rule exists to flag. Triggers on
navigator.webdriver=true OR ?bot in the URL so reviewers can see the
cloaked variant in a normal browser without spinning up Playwright.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

PR feedback: the previous querySelector guard in injectProbe could never
find an existing element because the <script> was removed immediately
after execution. Real dedup runs inside installProbe via the page-world
__abs_webdriver_probe_installed flag; the DOM guard was misleading and
produced create→append→execute→remove churn on every re-enable.

Replace with a module-level probeInjected boolean (never reset on
teardown — the prototype wrap persists across enable/disable cycles, so
re-enable doesn't need to re-inject). Drop the now-purposeless
WEBDRIVER_PROBE_SCRIPT_ATTR marker and the test that only asserted the
script was removed.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

When webdriver-probe-annotate is enabled, the background worker now
registers webdriver-probe.js as a dynamic content script with
world: "MAIN" and runAt: "document_start" via
chrome.scripting.registerContentScripts. Subsequent navigations run the
probe before the page's first script — closes the "early-parse reads
are missed" gap documented in the original PR.

The rule's apply() still inline-injects the same probe at document_idle
as a fallback so the tab the user was viewing when they toggled gets
covered (dynamic registrations only apply to future navigations).
Both paths execute the same installProbe() function, now lifted into
lib/webdriver-probe-source.ts as the single source of truth.

Adds the "scripting" permission to manifest.json. Does NOT require
developer mode — that constraint is on chrome.userScripts, not
chrome.scripting.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Two CI failures introduced by the document_start registration change:

1. knip flagged src/webdriver-probe.ts as unused — it's a build entry
   point but knip's static analysis can't see chrome.scripting referring
   to it by filename. Add to the knip entry list.

2. test:coverage failed: under coverage instrumentation, istanbul wraps
   installProbe with cov_* counter references; the rule then serializes
   the function via .toString() and injects it into the page world via
   inline <script>, where the counters don't exist (ReferenceError on
   the cov_* identifier inside jsdom's main world). Exclude
   webdriver-probe-source.ts from coverage so the serialized source
   stays self-contained.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>