[dutchakdev]

Bumps the pin to 0.10.0 (npm provenance from the v0.10.0 tag, integrity checked against the tarball). node scripts/validate.ts --online --changed passes. Installed from npm on an isolated Paseo 0.15.0-beta.1 daemon: running, and a mock agent passed through its hooks.

Accepts Paseo 0.15, which refused the previous range, and follows the host's Check usage setting.

🤖 Generated with Claude Code

[paseo-bot]

Account Switcher 0.10.0 is approved, @dutchakdev. It accepts Paseo 0.15, respects the host’s Check usage setting, and uses the host reload API when available. Your description, English/Chinese overviews and media are retained; no registry edits or further action from you are needed.

Review data

• Policy: main REVIEW.md blob 3c5e763c9565b93ea33fa48c9aeb83e415c72d67. Reviewed registry head 61c42d8d2e5d5683037c26e02e8bbb8beb1575d0. Read current PR, accepted #1647, original import #120 and linked #91, including discussion. Existing attribution and submitter retained.
• Independently downloaded and compared published paseo-plugin-account-switcher 0.9.0 and 0.10.0. URLs, versions and SHA-512 match fresh npm metadata and both registry records. New integrity: sha512-U2UB3CExMVUwvUwElHzN6DBraLAF7jEfxQx70dCpOi2RxYJyWWo3JMrg1mXr3dFjV2YVFgJjhpZUTaB6eNNFFQ==. All archive paths/types checked before confined extraction.
• Read every changed runtime file, affected controller reload/account-check flow, usage service and source, turn-end failover hook, RPC contracts, client controls, manifest/package/shrinkwrap and both overviews. Explicit daemon.usage.enabled: false in the existing host config prevents new scheduled/manual usage rounds and queued requests from dispatching, and prevents turn-end switch offers. Missing/unreadable config retains enabled behavior. Accounts receives checksOff, shows a notice and disables limit refresh controls. Requests already underway are not cancelled when the setting changes; an in-progress turn-end check is not atomically locked against that change. No new credential destination or runtime installer is introduced.
• During a switch, the controller calls the selected agent’s existing reload() when supplied by the host; older hosts keep the CLI reload path with fixed execFile arguments. Failure is reported without retrying a reload that already ran. The existing command-list call and launch-receipt confirmation remain. This changes how the same selected agent is reloaded, without adding a different command or remote endpoint.
• Decoded both embedded launcher strings as data and parsed them with a JavaScript parser, without executing or rebuilding them. The syntax trees differ only in two added optional checksOff response-schema fields; all other syntax/property values match with consistent bijective identifier renaming. Read the added schemas and unchanged readable launcher entry. Existing credential/profile handling, official CLI subprocesses, api.anthropic.com usage calls, provider account-server calls, integration and user-requested profile removal remain as disclosed and previously reviewed. Unchanged third-party/credential internals were not exhaustively re-audited.
• No manifest preparation or installation lifecycle command. The production shrinkwrap remains unchanged except root version, fixing only @iarna/toml@2.2.5 with public npm resolution and SHA-512, no transitive runtime dependencies. Independently downloaded and checksum-verified it and read its scripts; development/pack-time fixture preparation is suppressed during acquisition. No plugin/dependency installation, build, import or execution performed.
• Retained English and zh-CN overviews, package description, icon and three media entries. Both languages describe the new host setting consistently. All four public image URLs return HTTP 200/image/png; viewed banner and interface images. No registry fallback or editorial change needed.
• Trusted current-main scripts match this branch; online changed-record validation passes for one artifact, zero skipped. All 189 registry tests passed earlier this execution on the same scripts. Exact-head Validate passes. Author exact-commit CI reports 528 tests across 39 files passing on macOS/Linux with Node 22.12/24, supporting evidence not rerun here. No live sign-in, Keychain, provider quota, account-switch or UI QA was performed in this review. No factory-policy incompatibility found.