[dutchakdev]

Pins paseo-plugin-account-switcher 0.9.0 (published from tag v0.9.0 by GitHub Actions with npm provenance).

• artifact.version, resolved, integrity from npm view paseo-plugin-account-switcher@0.9.0 dist; the sha512 matches the downloaded tarball.
• repository.commit is v0.9.0^{commit}.
• node scripts/validate.ts --online --changed --base upstream/main: 1 record matches its pinned artifact.
• npm test: 146 pass, 43 fail, the same counts on upstream/main in this checkout.
• npm:paseo-plugin-account-switcher@0.9.0 installed on an isolated Paseo 0.14.0 daemon reaches running, and agents are created through its hooks. That run used a stand-in codex, so no real provider session was involved.

Release notes: https://github.com/dutchakdev/paseo-plugin-account-switcher/releases/tag/v0.9.0

🤖 Generated with Claude Code

[paseo-bot]

Account Switcher 0.9.0 is approved and merged, @dutchakdev. Your description, bilingual overviews and existing media are retained. No registry edits or action from you are needed. Publication is in progress.

Review data

• Policy: main REVIEW.md blob 3c5e763c9565b93ea33fa48c9aeb83e415c72d67. Reviewed PR head 9973f261f3cb66ecc4720fe2671df7ed84675df9.
• Independently downloaded and compared the published 0.8.1 and 0.9.0 npm tarballs, checked archive paths/types before extraction, and matched both SHA-512 values against npm and the registry pins. New integrity: sha512-mHHaMTwPS3PmaDT/pDQDQ9P6Bgzaz4r7GUtNqokcphQW9voFIV6w0KncaZG/qT6F7fOWe9BzDJ8Y+G7EB/RCcw==. npm's provenance statement names the plugin repository, tag v0.9.0, owner ID 1294321 and commit 1709aa7a2c5f6fce26d682125b27c084b816b867, matching attribution and the proposed record. This is provenance inspection, not independent signature verification or a reproduced build.
• Read every changed runtime file, affected creation/session hooks, account checks, profile preparation, removal and integration paths, both overviews and metadata. Existing accepted behavior is documented in the 0.8.1 review. Compared the embedded launcher as parsed JavaScript: its changes are the optional binding timestamp and reservation recheck; other syntax and property names match after consistent identifier renaming. Read both additions directly in the formatted bundle and readable source. No plugin build was run.
• index.server.ts:137–159 and server/switching.ts:105–166: an explicit creation environment account name/ID binds only within the requested Claude/Codex provider. Ambiguous/missing accounts, disabled integration, an unfinished or unverified sign-in, and a conflicting binding default setting refuse creation. The account hint is removed from the returned session environment. The choice uses existing official CLI sign-in checks; it adds no destination or credential source.
• server/controller.ts:104–154, server/process-identity.ts:18–30 and server/launcher-main.ts:43–49: absent agents are checked individually before reservation cleanup. Unobserved creations retain their reservation for ten minutes and while a receipt's process still appears to run; ambiguous process evidence retains it. Process inspection uses signal 0 and fixed ps arguments without a shell. A managed-profile launcher re-reads the binding after profile preparation and refuses a released reservation. No new profile-deletion operation is introduced.
• Existing credential reads, Claude usage requests to api.anthropic.com, official provider subprocesses, provider-command integration, shared settings/history and user-requested managed-profile deletion remain purposeful and disclosed in both author overviews. No new remote-code download or unrelated data transmission found in the inspected changes.
• No manifest preparation or installation lifecycle command. The production shrinkwrap still fixes only @iarna/toml@2.2.5, with no transitive runtime dependencies. Independently downloaded that archive and matched its integrity; no preinstall/install/postinstall. Its development/publishing scripts are not invoked during acquisition. Host libraries remain development dependencies. Dependency bodies were not exhaustively re-audited.
• Retained the shipped English/zh-CN overviews and package description; no redundant registry fallback. Icon and all three media URLs return 200 image/png; viewed the banner and both interface images. Trusted online validation passed: 439 well-formed records, one matching pinned artifact. Exact-head Validate passed. No factory incompatibility found.
• Limits: static artifact review, with no plugin/dependency install, build, import, execution, plugin tests or live account-switch QA. Author-reported runtime checks were not rerun. No concrete harmful behavior found in the inspected update.