refactor(deadcode): localize browser plugin declarations#101898
Conversation
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: refactor(deadcode): localize browser plugin declarations This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
|
Land-ready verification:
Known proof gap: the full browser shard has 13 failures in 5 files on both this PR head and a clean detached checkout of the exact current-main base. The same stale SSRF expectations and missing |
|
Merged via squash.
|
What Problem This Solves
The private browser plugin implementation still exported 15 declarations that have no consumers outside their defining modules. Those exports expanded the apparent internal API without providing a supported package surface.
Why This Change Was Made
Localize the unused declarations at their ownership sites across eight browser implementation modules. The browser plugin's package barrels and runtime API continue to expose the same supported surface.
This is an export-only cleanup: 15 declarations changed from exported to module-local, with 15 insertions and 15 deletions.
User Impact
None expected. Runtime behavior, public browser plugin APIs, and package exports are unchanged.
Evidence
9dbb1ed3d24655a144be1fe58a652f13ebe9f311e260600c10667a9c302dd959b0db0ba69813a4b7OPENCLAW_TESTBOX=1 pnpm check:changed: passed forextensionsandextensionTests, including extension typechecks, changed-file lint, guards, and import-cycle checks.Response.arrayBuffermock gaps. These failures are current-main drift and unrelated to this export-only diff.git diff --check: passed.AI Assistance
AI-assisted code search, editing, review, and validation were used. No agent transcript is attached.