Bug hunt ledger: Yarn Berry (2+)

[Mikola Lysenko (mikolalysenko)]

[agent] Progress ledger for the scheduled Yarn Berry (2+) bug-hunt routine (label pm:yarn-berry).

Last updated: 2026-10-15 (run 44), main 2c82c77 (release 5.0.1). Run 43 tested 7b6371c. Run 42 tested a3f56f7. Run 41 tested 23fa8d4. Run 40 tested 285a5e8. Run 39 tested 15c2c83. Run 38 tested 1779317. Run 37 tested 9ab72d4, previous release 4.0.0 (before that 3.3.0). Main was force-pushed and the clone is shallow; use git fetch --deepen=400 origin main for older SHAs. Run 36 tested a80b89e. Run 35 tested f3c6313. Run 34 tested 03b9418. Run 33 tested cf8b164. Run 32 tested e2d9633. Run 31 tested ea09714. Run 30 tested e61a845. Run 29 also tested PR #1033 head 314038b. Run 27 also tested PR #978 head 59eac7e; run 25 tested PR #940 head 980b7b6; run 23 tested draft PR #918 head 21413f1. Since #465 the hosted berry pin is root package.json resolutions (name@npm:<range> → URL) plus a lock entry re-keyed name@<url>.

Harness (run 44 note: fully local Python harness, no Rust scratch test: bin/y (YV=<v>, sets YARN_HTTPS_CA_FILE_PATH, YARN_HTTPS_PROXY, YARN_UNSAFE_HTTP_WHITELIST=127.0.0.1), h/mock.py <pk> 8790 (batch, by-package, view, package with real-sha512 tarball + bootstrapped yarn-berry-zip, tarball route, upstream) reading pk/cfg.json, h/base.sh/h/cell.sh/h/vcell.sh for lock-only copy-target-state cells; see the 20261015T153203Z entry. Run 43 note: run-42 approach rebuilt as zz_bh.rs (BH_DEPS/BH_PKG_EXTRA/BH_PRE/BH_SCRIPT, env API ORG TMPD HOSTED PROJ CK UUID, other tests #[ignore], real sha512 via openssl dgst -sha512 -binary | base64); lock-only cells copy package.json yarn.lock .yarnrc.yml to a fresh dir and add unsafeHttpWhitelist before the fresh install. Run 42 note: the same scratch test plus BH_SCRIPT (a shell cell run while the wiremock is up; env API, ORG, TMPD, HOSTED) and the real tarball sha512 in the mock's tarball artifact, so vendored cells work; the corepack shim also sets YARN_HTTPS_PROXY. Run 41 note: the run-40 scratch-test approach extended: a copy of e2e_redirect_yarn_berry_build.rs whose fixture merges BH_DEPS / BH_PKG_EXTRA into the root package.json, runs BH_PRE (shell, in the project dir) before the install, and takes BH_CWD for the get driver; the corepack shim must set YARN_HTTPS_CA_FILE_PATH only for 4.x and YARN_CA_FILE_PATH only for 2/3 (yarn 4 rejects caFilePath). Run 40 note: no Python mock was needed. A corepack shim on PATH runs the repo e2e suites (never set YARN_HTTP_PROXY, since it sends wiremock traffic to the proxy, which answers 403). A scratch test zz_bh.rs runs the CLI through prebuilt_common::prepare_command (the prebuilt fixture server stands in for the vendoring service; BH_STAGE=name@ver;file;uuid hand-stages the manifest), which gives shell-driven vendored cells. Hosted probes reuse berry_hosted_project in a scratch copy of e2e_redirect_yarn_berry_build.rs. Run 39 note: h/mock.py gained a /meta/ route, an npmjs metadata passthrough that 404s every /-/ tarball path; use it as npmRegistryServer/npmScopes to model a metadata mirror for #1465. A fresh helper must copy with tar, because cpio/rsync aren't installed. Run 38 note: hosted now verifies the tarball artifact's sha512 against the served bytes, so the mock must carry the real value or the package is skipped npm_manifest_unavailable): yarn bundles come from npm @yarnpkg/cli-dist@<v> (node package/bin/yarn.js), because corepack's fetch can't use the sandbox proxy. Yarn 4 needs YARN_HTTPS_CA_FILE_PATH; yarn 2/3 need YARN_CA_FILE_PATH. The npm registry has 2.4.2 as the last 2.x in cli-dist. Agent and vendored cells hand-stage .socket/manifest.json plus blobs (a marker prepended to index.js). Hosted cells use a local Python mock (fresh-checkout copies must keep .socket/ for vendored cells) of the patch API (batch, by-package, patches/package with a yarn-berry-zip yarnBerry10c0 artifact, view, and the tarball route). The 10c0 checksum is bootstrapped with a real yarn resolutions: file: install. Every hosted and vendored cell ends in a fresh-checkout yarn install --immutable. v5: hosted rollback/remove need the mock's /upstream/npm/<uuid>.json route, SOCKET_NPM_REGISTRY pointed at a local registry passthrough (the rustls binary can't use the sandbox proxy CA), and --patch-server-url <mock> so the pins count as hosted. Global (-g) cells use real npm global installs (NPM_CONFIG_PREFIX) and a Python mock of the authenticated API (--api-url <mock> --api-token x --org org; blob route /v0/orgs/org/patches/blob/<sha256>). v5 vendored mode downloads from the vendoring service: the same mock's /patches/package with a granted tarball artifact (real sha512) is enough, and an optional per-patch status override (for example pending_build) is supported. A corepack shim (corepack yarn@X → node <cli-dist X>/bin/yarn.js, setting the CA env itself because the harness scrubs YARN_*) runs the repo's berry e2e suites in the sandbox (SOCKET_PATCH_YARN_E2E_REQUIRED=1, SOCKET_PATCH_YARN_BERRY_VERSION=<v>). setup was removed in v5. On GH runners, fixture installs need YARN_ENABLE_IMMUTABLE_INSTALLS=false (CI turns immutable on). Run 8: the vendoring-service mock must also return a yarn-berry-zip artifact with integrity.yarnBerry10c0, or vendor fails apply_failed. Hosted fresh installs from an http mock need YARN_UNSAFE_HTTP_WHITELIST=127.0.0.1. Run 9: the corepack shim must set YARN_HTTPS_CA_FILE_PATH only for 4.x (yarn 4 rejects an env caFilePath), and the batch mock must filter by components[].purl. Run 10: one Python mock driven by a JSON config (per-patch hidden and publishedAt for A→B upgrades) also serves /upstream/npm/<uuid>.json and a /registry/ npmjs passthrough for SOCKET_NPM_REGISTRY. Never run pkill -f mock.py from the shell that runs it. Run 12: the harness was rebuilt as mkpatch.py (patched tgz, bootstrap checksum, original registry checksum; never patch package.json) plus one mock that also logs Authorization. Standalone vex against the mock needs --patch-server-url <mock> and the API flags. Run 14: harness rebuilt (y, mkpatch.py, mock.py, addorig.py, run.sh, survey.py); the mock must unquote by-package purls repeatedly (scoped purls arrive as %2540). survey.py diffs npm: vs tarball-URL lock entry bodies to find pin-render mismatches. Run 16: harness rebuilt (y, mkpatch.sh, mock.py, lib.sh); the /registry/ passthrough must quote with safe='@/', and a checksum bootstrapped on yarn 4.0.x is bare hex, so prefix it with 10c0/. Run 17: v5 vendor --offline no longer builds locally, so vendored cells need the vendoring-service mock (POST /v0/orgs/org/patches/package, tarball + yarn-berry-zip) even with a hand-staged manifest. Run 13: also run every fresh install with YARN_ENABLE_HARDENED_MODE=1 (it implies --refresh-lockfile, which re-resolves tarball pins from the tarball manifest). Run 18: harness rebuilt (y, mkpatch.sh, stage.py, mock.py, hmock.py, reg.py, lib.sh); reg.py is an npmjs passthrough with non-conventional tarball URLs (forces ::__archiveUrl= lock entries) that also serves /<name>/<version> for SOCKET_NPM_REGISTRY; cold-cache checks need a fresh YARN_GLOBAL_FOLDER. Run 19: reg.py must 404 the conventional /-/ tarball path (as a real non-conventional mirror does), or yarn's error is a misleading "socket hang up". Run 20: harness rebuilt (y, mkpatch.sh → p/cfg.json, one mock.py with view blobContent + /upstream/npm/<uuid>.json, reg.py, lib.sh); a bare scan defaults to hosted, so pass --mode agent; vendored takeovers of hosted pins need --patch-server-url; the release 4.0.0 binary is package/socket-patch. Run 21: hosted rollback/remove need SOCKET_NPM_REGISTRY pointed at the reg.py passthrough, or they fail "error sending request" (sandbox artifact). Run 22: harness rebuilt (y, mkpatch.sh, mock.py, reg.py, plus reg2.py, a non-conventional mirror on :8792, and reg3.py, an npmjs stand-in on :8793 whose dist.tarball is conventional under its own base). When the restored dist.tarball host matters, set SOCKET_NPM_REGISTRY to reg3.py, never to the project's own mirror (that hid #908). Run 23: harness rebuilt (y, reg.py <port> conv|nonconv [prefix], mock.py + cfg.json, mkpatch.sh, run.sh <bin> <scenario> …); rollback takes no --mode. Run 24: harness rebuilt (y with YV=<v>, mock.py <scratch> <port> <checksum>, run.sh <yarn> tgz|dir|url hosted|vendored for the #939 matrix). Run 25: harness rebuilt (y, mock.py, reg.py, fx.sh, fresh.sh, yp.sh). The mock's /upstream/npm/<uuid>.json must return {name, version, integrity (registry sha512), yarnBerry10c0 (registry checksum)}. Yarn 4.18 needs approvedGitRepositories: ["**"] for github: deps. Run 26: harness rebuilt (y, mock.py <scratch> <port> <patched 10c0> <registry 10c0> <registry sha512> with a <scratch>/mode file (badsha/pending) for late vendored failures, reg.py, lib.sh, pnpjs.sh); chattr +i on a file is a working write-fault injector even as root. Run 27: a corepack shim with BH_HOME (yarn-only HOME override) runs the repo's e2e capstones unchanged against main and a PR worktree (CARGO_TARGET_DIR=target-pr); a hand-staged .socket/ + vendor --offline shows which gate fires (main stops at "needs the network"). Run 29: harness rebuilt fully local (mkpkg.py synthetic lpx, reg.py 8793, mock.py 8790 reading checksums from cfg.json, sp wrapper, fresh DIR); shell helpers must not clobber caller variables. Run 30: stage.py (stub dummy pkg + manifest + blob), case.sh (diffs real yarn config get nodeLinker against socket-patch's PnP decision per rc/env shape), interp.sh <name> <nodeLinker value> (real PnP install, agent apply, lock-only vendor); offline rollback needs the before blob staged. Run 31: harness rebuilt (mkpkg.py, reg.py <port> conv|nonconv, mock.py with a per-uuid hidden flag + hide.sh A|B, gen.sh generation cells). The hosted tarball URL leaf MUST be <name>-<version>.tgz (hosted_url_names), or the existing pin reads as a foreign http: entry. The view hashes are git-blob sha256, or vendor fails apply_failed. The corepack shim also needs YARN_HTTPS_PROXY=$HTTPS_PROXY. Run 32: harness rebuilt (bin/y, mock.py :8790 left-pad, generic mock2.py :8791 driven by mkpatch.sh NAME VER UUID → pk2/<name>@<ver>/ with ck, regsha and a hand-added regck (must carry 10c0/; /upstream needs yarnBerry10c0 or rollback refuses), reg.py :8793 npmjs passthrough for SOCKET_NPM_REGISTRY). Run 33: harness rebuilt (h/mock.py <dir> 8790 driven by cfg.json with per-package ck (null = no yarn-berry-zip artifact, which makes hosted refuse redirect_yarn_berry_missing_checksum, the easiest way to force a #1039 takeover retraction), h/mkpatch.py (patched tgz + bootstrapped 10c0 + registry regck/regsha), h/stage.py (manifest + blobs), h/fresh.sh (copies packages/ too for workspaces), h/reg.py 8793). Vendoring needs the yarn-berry-zip artifact present (ck set) or it fails. The safety check blocks rm -rf $VAR inside loops; use fresh directory names. Run 34: harness rebuilt (bin/y, h/mkpatch.sh NAME VER UUID → pk/<name>@<ver>/ with ck/regck/regsha/before/after/file, h/mock.py <pk> 8790 serving every pk/* package (the tarball artifact must carry the patched tgz's real sha512, or packages with bin skip with npm_manifest_unavailable), h/reg.py 8793 npmjs passthrough, h/lib.sh with hs/sp/fresh). Never run npm install --package-lock-only next to a berry lock: npm rewrites yarn.lock as classic v1. Run 35: harness rebuilt (bin/corepack shim + bin/y, h/mkpatch.sh NAME VER UUID → pk/<uuid>/{patched.tgz,meta.json}, h/addreg.sh <uuid> adds regck/regsha for the /upstream/npm/<uuid>.json route, h/mock.py <pk> 8790 (batch, by-package, view, package, artifacts, upstream), h/reg.py 8793, h/stage.py, h/mkfx.sh, h/cell.sh). For SIGKILL timing, exec the binary directly ($SP … & p=$!); kill -9 on a shell-function wrapper kills only the subshell. The takeover commit window on this harness is ~0.04–0.05 s after start. Run 36: harness rebuilt (bin/y with YV=<v>, h/mkpatch.sh NAME VER UUID → pk/<uuid>/{patched.tgz,meta.json} with ck/regck/regsha and view blobs, h/mock.py <pk> 8790 (batch, by-package, view, package, artifacts, upstream, /v0/organizations), h/reg.py 8793 npmjs passthrough, h/lib.sh with sp/fresh). Deterministic crash injection: shim.so, an LD_PRELOAD rename/renameat2 hook that SIGKILLs when the target path ends with $KILL_ON (/package.json, /yarn.lock, /state.json); sleep-timed kills no longer land (the commit window is under 5 ms). Run 37: harness rebuilt (bin/y with YV=<v> and the yarn 2/3 YARN_CA_FILE_PATH, h/mkpatch.sh NAME VER UUID [FILE] → pk/<uuid>/{patched.tgz,meta.json} (bootstraps ck/regck with real yarn installs), h/mock.py <pk> 8790 (proxy + org routes, view with blob contents, package, upstream, /registry/ npmjs passthrough, and a non-conventional mirror at /mirror/ whose tarballs live under /mirror-dl/), h/lib.sh (sp with --api-url/--proxy-url/--patch-server-url, fresh, mkfx), h/shim.so rename killer (KILL_ON, KILL_NTH, KILL_AFTER), h/bis.sh BIN for the #1082 cell). Without a token, --proxy-url is what routes to the mock. vex -o is --org; use -O. Run 11: the view route can carry blobContent/beforeBlobContent, so agent-mode scan works against the mock without hand-staging; stop the mock through a pidfile.

Coverage matrix

Cells are "pass", "fail #N", "refused (by design)" or "untested". Linker is node-modules unless noted.

OS	yarn	Agent apply / rollback	Vendored	Hosted	setup hook
Linux	4.0.2, 4.18.1 on main 2c82c77 (run 44)	n/a	#1561 fixed (missing target → vendor_copy_unpatched). portal: target with only .gitkeep, or a portal:/link: manifest without name/version: fail #1579 (exit 0, VEX attests, installs unpatched). Nested independent berry project: skipped + PATH remedy pass. *.tgz filter=lfs repo: pass (#1541). #783 still fails	#1561 verified fixed (missing, empty, LFS pointer, file, dangling symlink). Same #1579 shapes fail (hosted + lock-only vex). Nested independent berry project tools/x: nested_project_skipped, PATH remedy pins it, fresh --immutable patched (pass)	removed in v5
Linux	4.0.2, 4.18.1 on main 7b6371c (run 43)	n/a	Relative portal:/link: copy whose target is missing (submodule not checked out): fail #1561 (exit 0, in-run VEX attests, installs unpatched). file: twin fails closed (pass)	#1540 verified fixed (absolute portal:). Missing relative portal:/link: target: fail #1561 (hosted scan + lock-only vex attest; 4.0.2, 4.18.1). Present target: pass	removed in v5
Linux	4.0.2, 4.18.1 on main a3f56f7 (run 42)	n/a	Renamed lp2 copies: relative outside-root portal:/file: tgz warn vendor_copy_unpatched (pass). Absolute portal:/abs: fail #1540 (exit 0, no warning, all VEX paths attest)	#1516 verified fixed (outside-root portal:, member-relative portal:/file: from packages/a, symlinked portal dir, absolute file: dir/tgz fail closed). Absolute portal:/link: copies: fail #1540 (4.18.1 ×2, 4.0.2; in-run, lock-only and post-install VEX attest not_affected)	removed in v5
Linux	4.0.2, 4.18.1 on main 23fa8d4 (run 41)	n/a	untested (renamed copies)	renamed lp2 copy of left-pad@1.3.0 outside the root (portal:../ext/lpdir, file:../ext/lp.tgz, file:../ext/lpdir) or a file: tarball with a non-package/ root: fail #1516 (berry evidence commented; no copy warning, in-run and lock-only VEX attest; PR #1517 head 6289505 fixes all four on 4.18.1). In-root file: dir/tgz copies warn redirect_copy_unpatched (#939 verified). #1490 verified fixed: packages/(a|b), [[:alpha:]], b/../a refused redirect_workspace_lockfile_elsewhere like packages/*	removed in v5
Linux	4.0.2, 4.18.1 on main 285a5e8 (run 40)	n/a	#759 verified fixed: a member add (exact, alias, 1.3.x, ~1.3, >=1.x, spaced range, dev, a transitive file: package) × vendor --revert/rollback/remove, CRLF lock, a 4.0.2→4.18.1 upgrade + add: pass. latest, partial hyphen and unsatisfied ranges warn vendor_lock_descriptor_unlocked (designed). #783 still fails	#1465 verified fixed (top-level mirror; rollback and remove; repo e2e). Workspace member under picomatch-only globs ((a|b), [[:alpha:]], a/../b): get <uuid> exits 0 and pins nothing: fail #1490	removed in v5
Linux	2.4.2 (cacheKey 7)	pass on 61cfb9b (node-modules: apply, vex, rollback byte-exact and idempotent)	untested	refused (by design) redirect_yarn_berry_cache_unsupported	untested
Linux	3.8.7 (cacheKey 8)	pass on 61cfb9b: node-modules and pnpm linker (transitive dep in .store, real dirs), apply/vex/rollback byte-exact	refused (by design) vendor_yarn_berry_cache_unsupported	refused (by design); run 9 on 203e092: refusal writes nothing to package.json	untested
Linux	4.0.2 (bare-hex checksums)	run 9 on 203e092: pnpm linker .store transitive dep pass (#495 fixed); repo e2e suites pass (90/90); remove blob GC fail #559	node-modules pass on 61cfb9b (bare-hex checksum written). PnP lock-only: fail #539 (re-run)	run 9 on 203e092: new resolutions pin passes hardened mode on node-modules/pnp/pnpm linkers. Earlier: pass (left-pad, v5 rollback byte-exact); #368 and #404 fixed	removed in v5
Linux	4.12.0	run 9 on 203e092: nmMode: hardlinks-global pass after #486. Run 8 on 61cfb9b: nmMode: hardlinks-global pass (only this project's link broken; rollback byte-exact), nmHoistingLimits: workspaces pass (every copy). fail #559 (remove sweeps the other patches' before blobs; also releases 4.0.0, 3.3.0). pass on f6b7fb9 (node-modules and pnpm linkers, rollback byte-exact). On 61cfb9b: pass for direct deps (pnpm linker, root and scoped) and hoisted transitive deps; fail #495 (pnpm-linker transitive dep only in .store/<slug>/package); repo e2e suites pass	run 8 on 61cfb9b: pass for PnP workspaces (lock-only), vendored upgrade A→B in lock-only PnP (fresh immutable loads B; --revert byte-exact), merged 3-descriptor entry (--revert byte-exact), catalog: (default and named), root locator encoding (nameless root, ()!~'*, space, unicode, +&=#), concurrent vendor (lock), repair of a deleted tgz. Two versions → vendor_override_conflict (correct). remove blob GC: fail #559. pass on 61cfb9b: pnpm linker (in-place + fresh --check-cache, --revert byte-exact); PnP lock-only checkout vendors and loads patched bytes, but re-run after install fails #539 (also 4.0.2, 4.18.1); zero-install committed cache → YN0056 (docs gap). package.json tab / 4-space / BOM / CRLF+tab / no trailing newline / existing or empty resolutions (fresh immutable + --revert byte-exact); mixed-EOL yarn.lock refused loudly (vendor_yarn_berry_mixed_line_endings). pass on f6b7fb9: root, scoped root name, scoped target, **/ glob resolution, workspaces, pnpm linker, re-run idempotent, --revert, in-place immutable install. pass on v5: root, workspaces + enableImmutableInstalls: true (--revert and remove byte-exact), CRLF lock + package.json. Refused (by design): resolve/typescript (patch: builtin), yarn 3. fail #370 (commented compressionLevel). fail #369 (hosted→vendored via scan/get --mode vendored; vendor itself is fixed on v5). fail #468 (vendored→hosted with no yarnBerry10c0)	run 11 on 045d7ec: pass for packageExtensions-added dep, root peer + dev, =1.3.0/v1.3.0, portal: transitive, dependenciesMeta, workspace named like the target (each with fresh immutable and byte-exact rollback; vendored for packageExtensions/portal: too); tarball-URL descriptor refused (correct); compressionLevel: mixed refused in both modes. run 10 on 045d7ec: catalog: (default, named, workspace) fail #632 (regression from #465; release 4.0.0 passes); vendored→hosted takeover of a catalog dep also hits #632. Pass: A→B upgrade (re-pin, fresh immutable B, rollback byte-exact), pin survives yarn add/dedupe/up, descriptor change → re-scan re-pins (vex attests nothing meanwhile), --cwd nested separate project (outer untouched). run 9 on 203e092 (resolutions pin, #465): pass for basic, workspaces merged entry, transitive, 7 range spellings (latest, >=1.3.0 <2, ||, 1.x, *, npm: forms), scoped, two versions, hardened mode × 3 linkers, package.json tab/4-space/CRLF/BOM/no-EOL/other resolutions (rollback byte-exact), CRLF lock + enableImmutableInstalls, scoped rollback/remove with two pins, hosted↔vendored takeovers, mixed vendored+hosted unwind, legacy __archiveUrl pin migration from release 4.0.0, compressionLevel: "0" and 0 # c (#370 fixed), lock-only vex (orphan refused). #368 fixed (refuses resolve, nothing written). Interrupted (SIGKILL) vendor: recoverable. Earlier: pass: left-pad, pnpm linker + vex, rollback byte-exact; run 8: catalog: dep (fresh immutable patched); 61cfb9b: rollback and remove byte-exact for npm:^1.3.0, dev-only and optional-only descriptors; v5 main: npm:1.3.0 / npm:^1.3.0 descriptors, dev-only and optional-only deps, mixed-case name JSONStream (case-kept purl, also on 4.18.1), mixed-EOL lock refused loudly, scoped, CRLF, workspaces merged-range, re-scan idempotent, manifest-less rollback/remove/list byte-exact, PnP lock-only checkout, upgrade path (uuid A→B re-pin, then rollback byte-exact), hardened mode accepts __archiveUrl pins, vendored→hosted takeover (checksum present; pending_build stays vendored). #368, #404, #369 and #370 are fixed on 203e092. Refused (by design): PnP (yarn_pnp_unsupported), direct + alias merged entry (redirect_yarn_berry_ambiguous_entry). PnP stale .pnp.cjs + hosted pin → standalone vex attests unpatched copy: fail #519 (yarn-classic issue; berry evidence commented, also 4.0.2 and 4.18.1)	pass on f6b7fb9; removed in v5
Linux	4.18.1 (latest)	run 39 on 15c2c83: #1100 nodeLinker shapes (20) pass. run 12: agent on a user patch:-descriptor package pass. Run 11: workspaces with nmMode: hardlinks-local + nmHoistingLimits: workspaces pass (both copies patched, rollback restores both). Run 9 on 203e092: pnpm linker .store pass (#495 fixed); repo e2e suites pass (90/90); fail #559	run 10: vendored catalog: pass (bare-name pin). Run 8: named catalog:legacy pass. pass on f6b7fb9 (CRLF-respelled lock + package.json); v5: fail #468; PnP lock-only: fail #539 (re-run)	run 11: packageExtensions, peer + dev, =1.3.0 pass. Run 10 on 045d7ec: catalog: fail #632; A→B upgrade, yarn add/dedupe/up, nested --cwd pass. Run 9: resolutions pin passes hardened mode × 3 linkers. Earlier: pass (left-pad, scoped, lock version: 10); #368, #370, #404 and #468 fixed on 203e092	removed in v5
Linux	all 4.x (4.0.2, 4.6.0, 4.12.0, 4.18.1)	n/a	run 17 (4.18.1; 4.0.2 where noted): pass for the takeover of a user exact pin "left-pad": "1.3.0", mixed-case JSONStream, three linked packages (also 4.0.2) with per-package rollback, default global cache + --check-cache, workspaces focus --production, prerelease ms@3.0.0-canary.1, --check on a tampered tgz. bin: + conditions: (ios-deploy) fail #697/#718 (passes on PR #719). vendor --check wiring drift (resolutions dropped, lock restored) exit 0: #725 class (commented; PR #730 fixes it). run 16: parent-scoped user resolutions (pkg-a/left-pad, pkg-a/left-pad@^1.3.0, <root>/left-pad) fail #783 (vendored adds its own pin; every fresh --immutable fails YN0028; 4.0.2, 4.12.0, 4.18.1; also release 4.0.0). Exact-name user keys refused (correct). A→B re-vendor across a 4.0.2 → 4.18.1 upgrade pass (revert is #759). Workspaces globs */**, self-alias npm:left-pad@… descriptors (revert byte-exact), default compressionLevel spellings: pass. run 15: yarn upgrade 4.0.2 → 4.12.0/4.18.1 after vendoring, then rollback/vendor --revert: fail #759 (bare-hex checksum restored; also release 4.0.0). Without a revert: pass. checksumBehavior ignore/update/reset: pass. run 14: native-addon packages (implicit node-gyp: "npm:latest": nan, bufferutil) fail #737 on every fresh --immutable (4.0.2, 4.12.0, 4.18.1; also PR #719 head). Workspaces × node-modules/pnpm and packages with own peerDependencies: pass, plain and hardened. run 13: package whose tarball bin: differs from the registry metadata (uuid, acorn) fail #718: every fresh --immutable fails YN0028 (4.0.2, 4.12.0, 4.18.1). run 12: platform-conditional entries (conditions:) fail #697 (checksum after conditions:; every conditional entry; also release 4.0.0). yarn remove then rollback: fail (#665, Berry evidence commented). Symlinked yarn.lock/package.json replaced: fail (#627, commented). Pass: yarn add/up/dedupe after vendoring, then --revert keeps the user's add	run 16 (4.18.1): parent-scoped user resolutions refused correctly (redirect_yarn_berry_resolutions_conflict). Self-alias npm:left-pad@… descriptors: pin, fresh and rollback byte-exact. PR #763 head verified for #632 (5 catalog shapes + takeover, rollback byte-exact). run 14: native-addon packages (nan, bufferutil): fail #737 under hardened mode (4.0.2, 4.12.0, 4.18.1; PR #719 head too); regression from #465 (release 4.0.0 passes). Workspaces (merged entry + scoped) × node-modules/pnpm, own peerDependencies (fdir, use-sync-external-store): pass, hardened. nan rollback byte-exact. run 13: tarball bin: ≠ registry bin: (uuid, acorn): fail #718 under hardened mode / --refresh-lockfile (4.0.2, 4.12.0, 4.18.1); regression from #465 (release 4.0.0 passes); plain --immutable passes. run 12: conditional entry with deps and no checksum (@img/sharp-*) fail #697; esbuild (no deps) and supportedArchitectures pass. Pass: two versions both patched (scoped rollback, byte-exact), debug (deps + peerDependenciesMeta), npmAlwaysAuth + token (no auth to patch host, hardened), user patch: descriptor refused, symlinked lock/package.json refused	removed in v5
Linux	4.0.2, 4.12.0, 4.18.1 (custom registry, non-conventional tarball URLs)	n/a	run 18: pass (pin, fresh immutable, --revert byte-exact); member-level resolutions and object-form workspaces pass	run 18: pin + fresh immutable pass; rollback/remove fail #817 (drops ::__archiveUrl=, cold-cache install YN0001)	removed in v5
Linux	4.0.2, 4.18.1 (.gitignore covers the vendored tgz: *.tgz, vendor/, .socket/)	n/a	run 19: fail #831 (Berry commented; node-modules on 4.0.2 and 4.18.1, pnpm on 4.18.1; fresh --immutable YN0001, warm cache too; --check exits 0 under .socket/)	not affected (lock-only)	removed in v5
Linux	4.0.2, 4.18.1 (custom registry, hosted→vendored takeover then vendor --revert)	n/a	run 19: fail #817 (commented: the takeover's hosted revert stores a bare npm: original in state.json)	see the row above	removed in v5
Linux	4.18.1 (lock with builtin patch: typescript/fsevents beside the target)	n/a	run 19: pass (hardened fresh)	run 19: pass (hardened fresh)	removed in v5
Linux	4.12.0, 4.18.1 (yarn pnpm linker, pnpmStoreFolder relocated)	run 20: transitive packages fail #859 (.cache/.store: package_not_installed exit 0; store: refused as first-party source, exit 1; also release 4.0.0). Direct deps and a workspace member's direct dep pass (rollback restores). Default node_modules/.store control passes	not affected (lock-only)	not affected (lock-only)	removed in v5
Linux	4.18.1 on main 4646693 (run 20 re-verification)	#665 Berry fixed (yarn remove then rollback)	#718 (uuid), #697 (@esbuild/linux-x64 transitive), #817 takeover variant: fixed; pre-#719 pins heal on re-run; vendored→hosted takeover of a bin: package pass. #737 and #759 still fail	#718, #697, #817 (custom-registry rollback byte-exact) fixed; #737 still fails hardened	removed in v5
Linux	4.0.2, 4.12.0, 4.18.1 on main 9c43dfc (run 21)	env/home pnpmStoreFolder (YARN_PNPM_STORE_FOLDER, ~/.yarnrc.yml): direct deps refused as first-party, exit 1 (commented on #859). Env-only YARN_NODE_LINKER=pnpm with the default store: pass	symlinked .socket shared by two projects: fail #887 (unwind in one deletes the other's tgz + state.json; 4.0.2, 4.18.1, node-modules + pnpm). Linked .socket/vendor[/npm] refused (pass). Symlinked yarn.lock/package.json refused (#627 fixed). vendor --check drift (#725) fixed. Scoped string bin (@babel/parser): pass	from a workspace member: fail (#884, Berry evidence commented): get <uuid>, and scan when the member owns a copy, exit 0 with redirected: 0. #632 fixed on main (4 catalog selectors, hardened fresh, rollback byte-exact). Scoped string bin: pass	removed in v5
Linux	4.0.2, 4.18.1 on main 9c43dfc (run 22)	symlinked shared .socket: fail (#887, agent evidence commented). Project reached through a symlinked path: pass	project via a symlinked path (cwd and --cwd): pass. Hosted→vendored takeover then vendor --revert on a non-conventional mirror: fail #908	non-conventional npmRegistryServer mirror with SOCKET_NPM_REGISTRY unset: rollback/remove fail #908 (bare locator, cold --immutable YN0035; #817 fix incomplete; byte-exact only when SOCKET_NPM_REGISTRY is the mirror). Symlinked project path: pass	removed in v5
Linux	4.0.2, 4.18.1 on main 9c43dfc and PR #918 21413f1 (run 23)	n/a	n/a	hosted rollback/remove on a mirror: project-rc top-level npmRegistryServer fails on main (#908) and passes on PR #918; npmScopes.<scope>.npmRegistryServer (scoped target), env YARN_NPM_REGISTRY_SERVER and ~/.yarnrc.yml fail on both (commented on #908). Conventional mirror with a path base: pass on both	removed in v5
Linux	4.0.2, 4.18.1 on main 9c43dfc (run 24)	lp2 other-name file: copy: pass (both copies patched, rollback restores both)	member copy of the patched name@version under another dependency name ("lp2": file: tgz / dir / registry URL): fail #939 (no warning; lock-only vex and post-install vex attest not_affected). Same-name file: copy refused (vendor_override_conflict, pass)	same lp2 shapes: fail #939 (no warning; lock-only vex attests; post-install vex declines). Same-name file: copy refused (unsupported_protocol + shared_descriptor, pass)	removed in v5
Linux	4.0.2, 4.18.1 on main 9c43dfc and PR #940 980b7b6 (run 25)	portal:/link: lp2 copy: first-party link skipped by design, vex attests (noted on #939). User yarn patch over a hosted pin: vex declines, re-scan refuses (pass)	user yarn patch over a vendored pin, then vendor --revert/rollback: fail #962 (exit 1 but wiring already half-reverted; YN0028). lp2 as portal:/link:/github:: fail #939 on main and PR #940; file: tgz on the pnpm linker passes on PR #940	user yarn patch over a hosted pin, then rollback/remove: fail #962 (exit 0 "Restored", fresh --immutable YN0028, mutable install re-pins the Socket URL). lp2 as portal:/link:/github:: fail #939 on main and PR #940 (commented)	removed in v5
Linux	4.0.2, 4.18.1 on main 9c43dfc (run 26)	Yarn 2 PnP → Yarn 4 node-modules/pnpm linker with the stale .pnp.js Yarn 4 leaves: fail #975 (refused as PnP, exit 1; release 3.3.0 passes, 4.0.0 fails). User yarn patch after agent apply: overwritten by design	stale .pnp.js: fail #975 (exit 1). Yarn 2.4.2 vendored: refused by design (cacheKey 7)	Late vendored failure (bad sha512, pending_build) during a hosted→vendored takeover keeps the hosted pin: pass. Stale .pnp.js: pins, but a false yarn_pnp_unsupported warning (#975). Write fault on yarn.lock: loud, re-run heals	removed in v5
Linux	4.18.1 on main 9c43dfc and PR #978 59eac7e (run 27)	stale .pnp.js + project-rc node-modules: fail #975 on main, pass on PR	nodeLinker only in ~/.yarnrc.yml (project outside $HOME) or via YARN_RC_FILENAME: main passes (repo capstone, 11/11 VEX); PR #978 refuses vendor_yarn_berry_unsupported (commented on #539). Lock-only no-linker: refused up front on PR (#539)	untested this run	removed in v5
Linux	4.0.2, 4.18.1 on main db83f01 (run 28)	n/a	#831 Berry fixed (*.tgz re-included; vendor//.socket/ refused vendor_artifact_gitignored). Shared symlinked .socket: fail #887 (still)	mirror from npmScopes (scoped), YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir rc: rollback/remove fail #1017 (bare locator, cold --immutable YN0035). Project-rc top-level mirror (also trailing /, # comment, CRLF rc) and the inverse scope map: pass (#908 fixed). From a workspace member: get and member-owned scan refused (#884 fixed)	removed in v5
Linux	4.0.2, 4.18.1 on main 05ecc6e (run 29)	#424 Berry fixed (--json apply failure reported)	member adds a new descriptor of the patched package (lpx: 1.0.0) after vendoring: the pin covers it, but vendor --revert/rollback drop it and fresh --immutable fails YN0028 (#759 class, commented)	same member add after a hosted pin: fail #1082 (re-scan refuses with an impossible dedupe remedy; rollback exit 0 then YN0028; lock-only vex attests on main, dropped on PR #1033). #657 gates pass: mixed package.json refused by scan, rollback/remove (exit 1) and the vendored→hosted takeover; nothing written. #939 on merged main: file: copy dropped, portal: still attests	removed in v5
Linux	4.0.2, 4.18.1 on main e61a845 (run 30)	#975 fixed (real node-modules install + stale .pnp.js: apply + rollback byte-exact). nodeLinker parity: home rc, YARN_RC_FILENAME, CRLF, ${L:-node-modules} pass. nodeLinker: "${L:-pnp}" / "${L}" (L=pnp) on a live PnP install: fail #1100 (exit 0 package_not_installed; release 4.0.0 refuses). Quoted key, next-line value, flow map, lower-case yarn_node_linker env: false PnP refusal (listed on #1100)	#539 fixed (lock-only literal/unset pnp refused up front). Interpolated pnp passes the gate: #1100	untested this run	removed in v5
Linux	4.0.2, 4.18.1 on main ea09714 (run 31)	#1082: VEX half fixed (#1033); rollback now refuses (exit 1, nothing written); re-scan dead end remains (commented). Repo berry e2e suites pass (4.18.1: 15/19/17)	Generation cells pass on both versions: vendored A→B revert, hosted A→vendored B revert/remove/rollback, vendored A→hosted B remove/rollback, all byte-exact with fresh immutable. Leftover package-lock.json: warned, revert byte-exact. compressionLevel: "${CL:-0}" false refusal (commented on #1100)	Hosted A→B re-pin + rollback byte-exact (both). Leftover package-lock.json: both locks pinned, rollback byte-exact. npmRegistryServer: "${REG:-<mirror>}": rollback/remove warn upstream_registry_fallback, then cold --immutable YN0035 (commented on #1017). Same ${CL:-0} false refusal	removed in v5
Linux	4.0.2, 4.18.1 on main e2d9633 (run 32)	#1029 apply --check: drift caught (exit 1), nmHoistingLimits two copies, version mix, pnpm linker, PnP fail-closed: pass. Interpolated pnpmStoreFolder: "${STORE:-node_modules/.store}" transitive: pass. Shared linked .socket: still shared (acknowledged gap in #1042)	#1050 scan --prune GC keeps live entries: root, workspace member, catalog:, pnpm linker, CRLF lock, 4.0.2: pass. #887 fixed by #1042 (closed). #783 still fails. #737 (nan) still fails. uuid bin: vendored + revert byte-exact. Leftover pnpm-lock.yaml: pnpm wins even with packageManager: yarn@4 (same in 4.0.0; documented warning). Yarn 2/3 gates hold	rollback/remove/takeover revert of a package whose tarball bin differs from the registry (uuid, prettier): fail #1131 (keeps ./dist/bin/uuid, hardened --immutable YN0028; also ea09714; release 4.0.0 not affected). #1057 stanza rewrite: plain, CRLF (byte-exact), alias-only JSON per-purl row, leftover pnpm-lock.yaml (both pinned, rollback byte-exact): pass. #737 hardened still fails	removed in v5
Linux	4.0.2, 4.18.1 on main cf8b164 (run 33)	#1100 still fails (${L:-pnp} live PnP: apply exit 0 package_not_installed). pnpmStoreFolder: ../shared used by two projects: apply in A patches B's copy too (documented: relocated berry store not containing the project is patched as usual)	n/a	#1039 staged vendored→hosted takeover: pass. Two vendored packages × (ck present/absent) on LF and CRLF: dry run byte-identical; partial retraction keeps the refused purl vendored (wiring, ledger, artifact) and migrates the other; all-retracted is byte-identical; fresh --immutable plain + hardened patched; rollback after a partial takeover restores pristine (4.0.2 byte-exact, bare hex). Workspaces (member ^1.3.0 + 1.3.0), get <uuid> --mode hosted (kept/migrated), compressionLevel: mixed after vendoring (both kept), PnP switch after vendoring (pins with yarn_pnp_unsupported, PnP fresh + hardened loads patched), alias lp: npm:left-pad@1.3.0 added after vendoring (alias_skipped, documented), write fault (chattr +i on yarn.lock / package.json / state.json, with and without a takeover): exit 1, nothing changed. VEX over a partial takeover: both attested.	removed in v5
Linux	4.0.2, 4.18.1 on main 03b9418 (run 34)	n/a	yarn remove after vendoring: --check names it, --prune/--revert/rollback/remove retire it (pass)	#1058: pin + re-scan already + fresh hardened + rollback byte-exact pass for workspaces, catalog:, transitive, pnpm linker, leftover npm/pnpm locks, legacy 4.0.0 __archiveUrl migration. yarn remove / yarn up to an unpatched version after a hosted pin: fail #1203 (leftover resolutions selector → rollback/list/remove exit 1 forever, the remedy scan is a no-op). #1131 still fails	removed in v5
Linux	4.0.2, 4.18.1 on main f3c6313 (run 35)	n/a	Refactored npm-family driver (#1008): node-modules, pnpm linker, workspaces, catalog:, 4.0.2, --revert/rollback/remove byte-exact; write faults on vendor and on unwind (exit 1, nothing half-written); generation A→B; hosted→vendored takeover then --revert pristine: pass. Repo berry e2e 187/187 (4.18.1) and 147/147 (4.0.2). #737 and #783 still fail	SIGKILL after the takeover's commit journal is durable, then rollback: fail #1241 (journal replayed under the lock, pre-lock hosted discovery empty → exit 0, nothing restored; remove "No patch found"). #1039 retraction on the pnpm linker and catalog:: pass	removed in v5
Linux	4.18.1 on main a80b89e (run 36)	Agent scan PATH on workspaces: pnpm linker member link selected (pass); hoisted copy outside the PATH is out of scope (by contract). nmMode: hardlinks-local + nmHoistingLimits: workspaces: apply patches 3 copies, rollback packages/a restores all with out_of_scope_copies_restored (pass)	Refactored driver: --dry-run writes nothing, repair redownloads a deleted tgz, CRLF lock, --revert/rollback byte-exact (pass). First vendoring SIGKILLed after its journal: rollback refuses pre-lock (vendor ledger is missing), never replays (commented on #809)	#1203 and #1131 still fail. #1241 (closed by a maintainer without a fix) still fails, now deterministic via the rename shim; the hosted→vendored takeover direction fails too (stale pre-lock list → false Cannot restore exit 1, or a pre-lock refusal that never replays the journal; commented on #1241)	removed in v5
Linux	4.0.2, 4.18.1 (2.4.2, 3.8.7 refusals) on main 9ab72d4 (run 37)	#1034 target grammar (name, purl, uuid, scoped, last-segment vs full name) on rollback/remove: pass. Yarn 2/3 agent apply + rollback: pass	#989 shared revert: partial remove/rollback <name> keeps the other package; SIGKILL during vendor --revert/rollback/remove, then re-run: pass. BOM .yarnrc.yml PnP gate (LF/CRLF): pass. Alias lp: npm:left-pad@1.3.0 added after vendoring, then revert/rollback/remove: exit 0, then YN0028 (commented on #1082)	#1180 alias copy: no false VEX (pass). BOM project-rc mirror rollback: pass. #1017 still fails. #1082 point 2 regressed (bisected to f3c6313a #1008): member or alias descriptor added after pinning → rollback/remove exit 0, then YN0028. SIGKILL mid-rollback: half-unwound, yarn install heals (residual)	removed in v5
Linux	4.0.2, 4.18.1 on main 1779317 (run 38)	n/a	#737 vendored nan + revert byte-exact; prune neighbours (bufferutil, direct node-gyp: latest/^11) pass. #1082 vendored alias variant fixed. Member descriptor added after vendoring, then revert/rollback: still fails (#759, commented). #759 upgrade symptom and #783 still fail	#737 nan pin pass (rollback: documented yarn_berry_node_gyp_unresolved). #1082 (12 cells), #1131 (uuid), #1203 (yarn remove/yarn up, partial remove), #1017 (env, home rc, project rc non-conventional mirror) pass. yarn remove in one workspace member while another keeps the package, then rollback/remove: fail #1435 (dead descriptor restored, YN0028; release 4.0.0 not affected)	removed in v5
Linux	4.0.2 → 4.18.1 (yarn upgrade)	n/a	see the all 4.x row (#759)	run 15: pin survives the upgrade, re-scan no-op, rollback writes 10c0/, fresh hardened --immutable pass. checksumBehavior ignore/update/reset: pass.	removed in v5
macOS	4.12.0, 4.18.1	untested	untested	pass (left-pad) on 4.0.0-era main; #368 and #369 fixed since, new resolutions pin untested	untested
Windows	4.12.0, 4.18.1 (yarn writes CRLF)	untested	untested	pass (left-pad, CRLF lock) on 4.0.0-era main; #368 and #369 fixed since, new resolutions pin untested	untested

Global (-g) cells. Berry has no global dir, so these are npm-prefix globals scanned from inside or outside a Berry project:

OS	yarn	scan -g report (inside/outside a Berry project)	-g hosted refusal	-g apply / rollback / vex
Linux	2.4.2, 3.8.7, 4.0.2, 4.12.0, 4.18.1	#440 fixed by #442 (project global script ran); otherwise pass, no project leak (node-modules, pnpm, PnP)	pass (exit 2, nothing written)	pass on 4.12.0 (byte-exact rollback, vex not_applied after reinstall, EACCES loud, --global-prefix with space and unicode)
macOS	2.4.2, 3.8.7, 4.12.0, 4.18.1	fail #440 (probe run 36828589815), fixed by #442 on main; not re-probed	untested	untested
Windows	2.4.2, 3.8.7, 4.12.0, 4.18.1	pass for #440 (.cmd shim not run)	untested	untested

Backlog

0000000000. #1579 (run 44): re-verify when fixed (.gitkeep-only portal: target, nameless and version-less portal:/link: manifests; hosted, vendored, lock-only vex; 4.0.2/4.18.1). A link: to plain assets must stay ignored. Then try a nested independent berry project that the root also links through portal:./tools/x. #1561 was verified fixed in run 44.
000000000. #1561 (run 43): re-verify when fixed (missing relative portal:/link: target; root and member-relative; hosted, vendored, lock-only vex; 4.0.2/4.18.1), and check a link: to an existing plain directory stays ignored. Neighbours: a dangling symlink target, a target that is a file, invalid-JSON or version-less package.json. Also #1534/#1543 on berry: a nested independent berry project under a berry root (nested_project_skipped). #1540 verified fixed in run 43.
00000000. #1540 verified fixed in run 43. Old note (run 42): re-verify when fixed (absolute portal:/link:, hosted and vendored, 4.0.2 and 4.18.1, in-run/lock-only/post-install VEX). Neighbours: other unread Linked copies (EACCES package.json, a path with :/#, a member link:), Windows portal:C:\….
0000000. #1516 / PR #1517 verified fixed in run 42 (outside-root portal, member-relative portal/file, vendored relative copies). Old note (run 41): when #1517 merges, re-verify the 4 berry shapes (outside-root portal:/file: dir/tgz, non-package/ tarball root) on 4.0.2 and 4.18.1, hosted + lock-only VEX, and test the vendored side (vendor_copy_unpatched), link: outside the root, and a member-relative file:../../ext path. Also #1490 neighbours below.
000000. #1490 verified fixed in run 41 (get from member). Old note (run 40): re-verify when fixed (packages/(a|b), pkg-(a|b), [[:alpha:]], [[:digit:]]x, a/../b; get <uuid> and member-owned scan; 4.0.2/4.18.1). Neighbours: other picomatch-only syntax (packages/a{1,}?, regex quantifiers, [[:upper:]]), nested-worktree members under such globs. #759 and #1465 were verified fixed in run 40; #1465 still has untested sources (npmScopes, env, home rc) that need a non-hermetic harness.
00000. #1465 (run 39): re-verify when fixed (top-level npmRegistryServer, npmScopes scoped target, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml; rollback/remove; 4.0.2/4.18.1; cold --immutable against /meta/). Also the hosted→vendored takeover vendor --revert behind the same mirror. Handed the pnpm half (npm.rs:1846) to the pnpm routine. #759 now has three symptoms (upgrade, added member descriptor, removed member descriptor, run 39): re-verify all of them when fixed. #1435 and #1100 were verified fixed in run 39, and #1437's guard covers berry pins (incl. legacy __archiveUrl pins).
0000. #1435 (run 38): re-verify when fixed (plain member removal, yarn up in one member, a catalog: member; 4.0.2 and 4.18.1). Try the vendored analogue (a member removes one of two vendored descriptors, then vendor --revert) and #1017's npmScopes scoped-target variant (needs a scoped patch in the mock). #1100 has draft PR #1433: re-verify when merged.
000. #1082 regression fixed by #1397 (run 38: hosted 12 cells + vendored alias pass; the vendored plain-member variant is #759). Old note (run 37): point 2 is back on f3c6313a+ (#1008/#828 Discovery::shadowed; restore_berry never merges blocks that share a resolution). Re-verify when fixed with h/bis.sh (plain member, root/member alias, remove, vendored alias revert; 4.0.2 and 4.18.1). Try other shadowed berry shapes: a file:/portal: sibling block (#939) and the hosted→vendored takeover over a shadowed pin.
00. #1241 (run 35; closed by a maintainer on 2026-10-09 with no fix commit; run 36 shows it still fails on a80b89e in both takeover directions): re-verify when a fix lands (rollback and remove right after a replayed vendored→hosted takeover journal; 4.0.2 and 4.18.1); also list/repair/vex in the same state, and a replayed hosted→vendored takeover journal (vendor killed mid-commit) followed by rollback.
0b. #1203 (run 34): neighbours: removal from one workspace member while another keeps the dep, a removed catalog: dep, a scoped package; re-verify when fixed (rollback, remove, list, scan --mode hosted --prune, 4.0.2 and 4.18.1). Also try the #1058 redirect_unattributable gate on berry shapes (portal:/link: copies, takeover + gate).

1. Blocked on a maintainer: probe-branch deletes fail (runs 10–13, 20, 21 and 34: send-pack: unexpected disconnect / remote end hung up; runs 14, 19 and 24: denied by the session permission policy), so no new probes. The stale branches bughunt/yarn-berry/20260930-builtin-patch-takeover and bughunt/yarn-berry/20261001-global-script need deleting by hand. After that, probe the resolutions pin on macOS and Windows (CRLF), plus Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859, Vendored mode still writes and deletes through a symlinked .socket dir: the #664 guard checks .socket/vendor and below only, so rollback in one yarn berry project wipes another project's vendored tarball and ledger #887 (a .socket junction on Windows).
   0a. Make the vendored-to-hosted takeover atomic #1039 takeover (run 33, all pass): untested neighbours: SIGKILL during the journaled takeover commit (next locked command must finish it), takeover on the pnpm linker, takeover of a catalog: dep with a retraction, a retraction caused by redirect_yarn_berry_resolutions_conflict (user resolutions added after vendoring).
2. Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 (run 32): re-verify when fixed (rollback, remove, takeover + vendor --revert; uuid and prettier; 4.0.2 and 4.18.1; plain and hardened). Neighbours: other tarball-derived fields the Fix yarn berry pin entry rendering (#697, #718) #719 renderer emits (dependenciesMeta, peerDependencies spellings), a scoped package with a ./ bin, the pnpm linker.
   1a. Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082 (run 29; run 31: VEX fixed and rollback now fail-closed, re-scan dead end remains): neighbours: a transitive dep adding lpx@~1.0.0, the pnpm linker, remove, PnP lock-only; re-verify when fixed (and the berry half of PR Stop VEX attesting over yarn PnP, pnpm bundled and deno.lock copies #1033). Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759: re-verify the new-descriptor revert symptom too.
   2a. Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 (run 28; the ${REG:-…} interpolated project-rc mirror added in run 31): re-verify when fixed (five sources × rollback/remove × 4.0.2/4.18.1; upstream_registry_fallback when unreadable), plus the hosted→vendored takeover vendor --revert on those mirrors.
   1b. Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100 (run 30; ${CL:-0} compressionLevel false refusal added in run 31): re-verify when fixed (agent + lock-only vendor, ${L:-pnp}, ${L}, plus the fail-closed parser rows). Neighbours: ${} in compressionLevel, enableGlobalCache, pnpStoreFolder, npmRegistryServer (other yarnrc_scalar users).
3. Re-verify when fixes land: Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 (hosted rollback/remove on 4.0.2 and 4.18.1, plus the vendored revert), Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939 (all 12 cells plus agent; PR Fix VEX attesting beside an unpatched same-lock copy (#935, #938, #939) #940 fixes the file:/URL VEX half but not portal:/link:/github: copies), Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 (plus the env/home variant), Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783 (then @scope/parent/name, a scoped target, the hosted→vendored takeover), Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759, Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737, Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539, Hosted yarn berry rewrites a mixed-line-ending package.json that vendored mode refuses #628/Share the yarn berry project gates between hosted and vendored modes #629. Fixed and verified: Vendored mode still writes and deletes through a symlinked .socket dir: the #664 guard checks .socket/vendor and below only, so rollback in one yarn berry project wipes another project's vendored tarball and ledger #887 (run 32, vendored; closed), Yarn 4 node-modules / pnpm-linker projects migrated from Yarn 2 PnP keep a stale .pnp.js, and socket-patch refuses them as Plug'n'Play: agent and vendored exit 1, hosted warns "npm dependencies were NOT scanned" (regression since 3.3.0) #975, Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 (run 30), Hosted yarn berry rollback/remove still drops a custom registry's ::__archiveUrl= binding (#817 fix incomplete): the restore looks up dist.tarball on npmjs, not the project's npmRegistryServer, so cold installs 404 #908 project-rc case, Hosted scan/get run from a yarn classic workspace member still reports success while pinning nothing: the #598 governing-root refusal covers pnpm and cargo only #884 Berry, Vendored yarn classic exits 0 when .gitignore covers the vendored tarball (*.tgz, vendor/, .socket/), so the commit drops it and every fresh checkout's install fails #831 Berry (run 28), Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632 (run 21 on main), vendor --check says "committed artifact and wiring verified" (exit 0) after pipenv lock drops the vendored reference, so a fresh pipenv install --deploy installs the unpatched wheel while vex says vendor_unwired #725 and Vendored yarn classic replaces a symlinked yarn.lock with a regular file (hosted refuses the same lock), leaving the link's target unpatched; rollback never restores the link #627 (run 21), Yarn berry vendored and hosted pins put checksum: out of yarn's field order on platform-conditional lock entries (conditions: os=…), so every yarn install --immutable fails YN0028 #697, Yarn berry vendored and hosted pins copy the registry entry's bin: paths, but yarn re-reads them from the tarball (./dist/bin/uuid), so vendored installs and hardened hosted installs fail YN0028 for packages like uuid and acorn #718, Hosted yarn berry rollback/remove rebuilds the lock entry as a bare name@npm:<version> locator and drops the registry's ::__archiveUrl= binding, so projects on registries with non-conventional tarball URLs can't install after a revert #817, After yarn remove of a vendored package, rollback fails forever (exit 1) and no command can clean up the orphaned yarn classic artifact; the remedies it prints don't work #665 Berry (run 20). Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370, Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404, scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440, Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468, Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495 and remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559 are closed.
   2b. (Yarn 4 node-modules / pnpm-linker projects migrated from Yarn 2 PnP keep a stale .pnp.js, and socket-patch refuses them as Plug'n'Play: agent and vendored exit 1, hosted warns "npm dependencies were NOT scanned" (regression since 3.3.0) #975 and Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 verified fixed on e61a845, run 30.) Yarn 4 node-modules / pnpm-linker projects migrated from Yarn 2 PnP keep a stale .pnp.js, and socket-patch refuses them as Plug'n'Play: agent and vendored exit 1, hosted warns "npm dependencies were NOT scanned" (regression since 3.3.0) #975 neighbours: a stale .pnp.js in a workspace member, vex on a Yarn 4 node-modules / pnpm-linker projects migrated from Yarn 2 PnP keep a stale .pnp.js, and socket-patch refuses them as Plug'n'Play: agent and vendored exit 1, hosted warns "npm dependencies were NOT scanned" (regression since 3.3.0) #975 tree, and any path that leaves .pnp.cjs/.pnp.loader.mjs behind on a non-PnP linker. Re-verify Yarn 4 node-modules / pnpm-linker projects migrated from Yarn 2 PnP keep a stale .pnp.js, and socket-patch refuses them as Plug'n'Play: agent and vendored exit 1, hosted warns "npm dependencies were NOT scanned" (regression since 3.3.0) #975 when fixed (agent, vendored, hosted warning; 4.0.2 and 4.18.1; both linkers).
   3b. Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 neighbours: a yarn patch of a workspace member's copy, a patch: wrapping a vendored pin from a member, and an agent-mode re-scan after the user's patch. (Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939 neighbours were done in run 25.)
4. Hosted scan/get run from a yarn classic workspace member still reports success while pinning nothing: the #598 governing-root refusal covers pnpm and cargo only #884 follow-ups once fixed: the refusal must not fire for a nested separate Berry project (own yarn.lock, not in the parent's workspaces); object-form workspaces; yarn 2/3 members.
5. Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 neighbours: pnpmStoreFolder outside the project (../shared) shared by two projects.
6. Vendored yarn classic exits 0 when .gitignore covers the vendored tarball (*.tgz, vendor/, .socket/), so the commit drops it and every fresh checkout's install fails #831 (fixed on db83f01) follow-up: the hosted→vendored takeover under an ignore rule.
7. Global (-g) on macOS/Windows, and a version-manager prefix (nvm/volta). Full checklist in the 20261001T040000Z entry.
8. Unconfirmed lead: the API returns a lower-cased npm purl (pkg:npm/jsonstream@1.3.5) for a mixed-case package, and every mode misses it. File it (cross-PM) only if the real API is shown to lower-case.
9. Unconfirmed lead: if the patch service ever serves a hosted tarball whose root isn't package/, hosted skips it with npm_manifest_unavailable (exit 0). File it only if the real service does that.
10. Interpolated pnpmStoreFolder / npmScopes values (Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100/Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 class).

Known non-bugs

• A berry link: to a non-empty directory with no package.json (plain assets, or only a .gitkeep) isn't a package copy (documented, and yarn installs it as a plain link). Only the portal: form is Yarn berry still drops a portal: copy whose target has no package.json (e.g. a .gitkeep placeholder) or whose package.json lacks name/version, so scans succeed and VEX attests not_affected while that copy installs unpatched #1579, because yarn refuses a manifest-less portal (run 44).
• A root hosted/vendored scan --vex whose only patch belongs to a nested independent berry project exits 1 with manifest_not_found (nothing to attest) after nested_project_skipped. That's the documented exit (run 44).
• Lock-only vex exits 2 saying "no hosted or vendored patch references were found" when the only pin is withheld by an unpatched copy. The wording is misleading but the run fails closed, so it isn't filed (run 43).
• An absolute file:/… renamed copy (dir or tgz) is never read (an untrusted lock), but it fails closed as an unidentified copy: redirect_copy_unpatched, and vex refuses. That's the designed Fix yarn renamed-copy identity fail-open (#1516) #1517 behaviour; only absolute portal:/link: copies fail open (Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540) (run 42).
• Vendored revert after a member adds left-pad@latest, a partial hyphen range (1.3.0 - 2) or an unsatisfied range while vendored: a vendor_lock_descriptor_unlocked event telling you to run yarn install, exit 0, and fresh --immutable YN0028 until you do. That is the designed fail-loud path from Fix vendored berry revert restoring stale lock (#759) #1464 (run 40).
• packages/.hidden under packages/* is refused as a workspace member (redirect_workspace_lockfile_elsewhere), but yarn berry skips dot directories. Loud and harmless, so not filed (run 40).
• nodeLinker: PnP (wrong case) isn't PnP to yarn either (no linker matches), so agent apply proceeding is consistent (run 39).
• A Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465-style bare npm: locator passes plain --immutable and --refresh-lockfile. Only the cold fetch against a mirror without /-/ tarballs fails; don't call a mirror that serves /-/ a pass for Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 (run 39).
• Hosted rollback of a native-addon pin (nan, Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737 fix) can't restore the pruned node-gyp subtree: it warns yarn_berry_node_gyp_unresolved, plain --immutable passes and hardened fails until yarn install. Documented in CLI_CONTRACT (run 38).
• Yarn 2/3 (cacheKey 7/8) are refused by hosted and vendored mode (documented).
• PnP projects with a .pnp.cjs are refused in every mode with yarn_pnp_unsupported (documented).
• Vendoring a package yarn builtin-patches (resolve, typescript, fsevents) is refused fail-closed with vendor_override_conflict. It's loud and closed, so it isn't filed (the hosted counterpart is Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368).
• Hosted refuses an entry that merges a direct descriptor with an npm: alias ("left-pad@npm:1.3.0, lp@npm:left-pad@1.3.0") with redirect_yarn_berry_ambiguous_entry and exit 1. It's fail-closed and loud; arguably over-broad, but not filed.
• Agent mode: a later yarn install --immutable in the same tree doesn't restore unpatched bytes (yarn's install-state), and the setup hook re-patches after a clean install. Standalone vex in agent mode needs setup or setup.manual (documented).
• patches-api.socket.dev is unreachable from the sandbox; use the mock.
• A BOM'd yarn.lock fails yarn install --immutable (YN0028) on its own, because yarn strips the BOM. Not caused by socket-patch.
• Hosted on a berry npm: alias-only entry → redirect_yarn_berry_alias_skipped (documented in docs/ecosystems.md).
• scan <workspace-member-dir> finds 0 packages Superseded in run 21: after Hosted scan/get run from a pnpm workspace member (or with lockfile-dir=..) ignores the parent pnpm-lock.yaml and reports success while pinning nothing #590/Fix hosted scan from a workspace member pinning nothing or the wrong files (#590, #417) #598, the hosted run from a member is a bug (Hosted scan/get run from a yarn classic workspace member still reports success while pinning nothing: the #598 governing-root refusal covers pnpm and cargo only #884, Berry evidence commented). A hoisted member scan still finds 0 packages, but get <uuid> and member-owned copies report success while pinning nothing.
• PnP with .pnp.cjs: scan reports 0 packages with a PnP warning (same in 4.0.0). A PnP lock-only checkout gets hosted pins, and those install correctly under PnP.
• v5 rollback/remove/list treat only patch.socket.dev (or --patch-server-url) URLs as hosted pins. Without that flag, a mock host reads as "Manifest not found".
• PnP on yarn 2.x (.pnp.js) and 3.x is detected and gets the loud PnP warning in every mode, exit 0 (same as 4.x).
• An agent-mode re-run (scan -g --mode agent) after a failed apply (EACCES) exits 0 with "already recorded … run socket-patch apply". This is the designed re-run message; apply -g itself exits 1.
• The report-only hint after scan -g doesn't mention -g. It's cross-PM and was handed to npm (Bug hunt ledger: npm #302), so it isn't filed here.
• Yarn 4 hardened mode (enableHardenedMode, auto-on for public fork PRs in GitHub Actions) accepts a hosted ::__archiveUrl= lock pin, as does --check-resolutions (4.12.0, registry reachable).
• Zero-install (enableGlobalCache: false with .yarn/cache committed): hosted mode is lock-only, so the committed cache keeps the unpatched zip, and yarn install --immutable --immutable-cache fails YN0056 until yarn install refreshes the cache. Vendored mode behaves the same way (the file: entry has no cache zip; no warning). It's a docs gap, not filed.
• compressionLevel set outside the project .yarnrc.yml (env, home or parent rc) can't cause a wrong checksum: yarn bakes the level into the lock's cacheKey, which both modes gate on.
• Vendored refuses a user yarn patch (patch: descriptor) with vendor_override_conflict, plus an alias-only dependency (root or workspace member) with vendor_lock_entry_not_found, a merged direct + alias entry, and a user-authored resolutions key for the target. All are loud and closed with nothing written, so none are filed.
• Mixed CRLF/LF yarn.lock is refused by vendored (vendor_yarn_berry_mixed_line_endings) and hosted (redirect_yarn_berry_mixed_line_endings). That's correct: yarn itself fails YN0028 on such a lock.
• v5 rollback drops the patch's manifest entry, so a later apply is a no-op (designed).
• A berry install rewrites a BOM'd, compact, or no-trailing-newline package.json. Vendored snapshots the post-install bytes and reverts to them byte-exactly.
• Vendored refuses a lock that resolves the target name at a second version (left-pad@1.2.0 alongside the patched 1.3.0) with vendor_override_conflict, because the name-keyed resolutions would move both. That's correct and loud.
• repair refuses (vendor_artifact_redownload_failed, nothing written) when the service now serves different bytes for a uuid whose integrity is pinned in the ledger. That's correct.
• vendor --cwd <workspace member> fails loudly with vendor_lockfile_missing (the lock lives at the root).
• Yarn 4 locks carry no virtual: entries for peer-dependent packages, so the hosted/vendored rewrite has no virtual locator to keep in sync.
• Hosted rollback reformats a compact one-line package.json to 2-space and drops a user-authored empty "resolutions": {}. Yarn's own next install writes exactly the same bytes, so it isn't filed.
• Hosted per-package refusals (redirect_yarn_berry_shared_descriptor, redirect_yarn_berry_ambiguous_entry, cache_unsupported) exit 0 with redirected: 0 and nothing written. With --vex and nothing to attest, the run exits 1.
• Hosted refuses a user-authored resolutions entry targeting the patched package (bare or scoped selector) with redirect_yarn_berry_resolutions_conflict. It's documented and loud.
• An interrupted (SIGKILL) vendor can leave a ledger + tgz without the package.json/yarn.lock wiring. A re-run completes, vendor --revert removes the orphan, and vex refuses. rollback and repair fail with manifest_not_found in that state.
• After a hosted pin, a user descriptor change (yarn add left-pad@1.3.0) leaves a stale resolutions selector. rollback in that state refuses loudly and tells you to re-run scan --mode hosted, which re-pins correctly. It's fail-closed and gives a remedy, so it isn't filed.
• Hosted yarn berry rewrites a mixed-line-ending package.json that vendored mode refuses #628 (hosted rewrites a mixed-EOL root package.json) was filed by the arch audit; don't re-file it.
• Hosted on a direct tarball-URL descriptor (left-pad@https://…tgz) is refused with redirect_yarn_berry_unsupported_protocol, exit 0, nothing written. That's correct.
• compressionLevel: mixed (cacheKey 10) is refused by hosted (redirect_yarn_berry_cache_unsupported, exit 0) and vendored (vendor_yarn_berry_cache_unsupported, exit 1). Both are documented.
• Hosted on a user patch: descriptor in dependencies is refused (redirect_yarn_berry_unsupported_protocol + redirect_yarn_berry_shared_descriptor), nothing written. That's correct. The hint suggests --mode vendored, which also refuses it; --mode agent works.
• Yarn 4 writes no checksum: for a platform-conditional entry reached only through optionalDependencies, and strips one on its next mutable install. A hosted pin's checksum on such an entry therefore doesn't survive yarn add; vex still attests from the installed tree. That's yarn's policy. The misplaced-line part is Yarn berry vendored and hosted pins put checksum: out of yarn's field order on platform-conditional lock entries (conditions: os=…), so every yarn install --immutable fails YN0028 #697.
• A hosted pin whose bin: differs from the tarball's passes a plain yarn install --immutable and a later mutable install (yarn trusts the locked entry). Only hardened mode or --refresh-lockfile fails, and that is Yarn berry vendored and hosted pins copy the registry entry's bin: paths, but yarn re-reads them from the tarball (./dist/bin/uuid), so vendored installs and hardened hosted installs fail YN0028 for packages like uuid and acorn #718.
• A scoped patch missing from a mock-driven scan is a mock artifact if the mock doesn't fully unquote %2540 purls (run 14).
• lockfileFilename in .yarnrc.yml is rejected by yarn 4 ("Unrecognized or legacy configuration settings"). It only exists in yarn 2/3, which hosted/vendored refuse anyway.
• checksumBehavior (ignore/update/reset) doesn't change what yarn writes to the lock. Hosted and vendored pins pass under all three (run 15).
• A user **/name resolution is dropped from package.json by yarn 4's own install, so a hosted pin that seems to replace it isn't socket-patch's doing (run 16).
• compressionLevel: with its value on the next line (a multi-line YAML scalar) is refused by both modes. It's loud and unrealistic, so it isn't filed (run 16).
• Vendored vex on a tree whose node_modules still holds unpatched bytes (wiring pulled without a reinstall) attests not_affected from the committed artifact and warns vendored_tree_out_of_sync. That's by design (run 17).
• vendor --check reporting wiring verified after the Berry wiring drifts is vendor --check says "committed artifact and wiring verified" (exit 0) after pipenv lock drops the vendored reference, so a fresh pipenv install --deploy installs the unpatched wheel while vex says vendor_unwired #725 (cross-PM root cause, Berry evidence commented in run 17). Don't re-file it.
• yarn install --mode=update-lockfile (Renovate) still writes checksum: lines on yarn 4.0.2 and 4.18.1, so there are no checksum-less target entries to test (run 18).
• A hosted-rollback bare npm:<v> locator where yarn wrote ::__archiveUrl= passes hardened mode and --refresh-lockfile. The breakage is only the fetch (Hosted yarn berry rollback/remove rebuilds the lock entry as a bare name@npm:<version> locator and drops the registry's ::__archiveUrl= binding, so projects on registries with non-conventional tarball URLs can't install after a revert #817).
• scan --mode agent --json reporting an apply failure as action: "added", failed: 0 with no error is scan/get --json drop the agent-mode apply failure: exit 1 with failed: 0, the patch shown as "added", and no error anywhere (e.g. a read-only global ~/.m2) #424 (cross-PM, open). Don't re-file it (run 20).
• Yarn 4.0.x rejects pnpmStoreFolder ("Unrecognized or legacy configuration settings"), so Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 cells start at 4.1+ (run 20).
• A vendored refusal on a symlinked yarn.lock/package.json (Fix vendored mode replacing symlinked lockfiles (#627) #802) leaves .socket/vendor/npm/<uuid>/ behind despite saying "nothing was written". It's benign (vex refuses, vendor --check sees nothing, the re-run is clean), so it isn't filed (run 21).
• Hosted rollback failing with "error sending request for url (https://registry.npmjs.org/…)" in the sandbox is the rustls/proxy-CA artifact. Use SOCKET_NPM_REGISTRY (run 21).
• A symlinked project path (cwd or --cwd through a link, as macOS /tmp is) works in agent, vendored and hosted modes (run 22).
• A conventional mirror with a path base (npmRegistryServer: http://host/api/npm/npm-remote) restores bare and byte-exact after a hosted rollback (run 23).
• The Hosted yarn berry rollback/remove rebuilds the lock entry as a bare name@npm:<version> locator and drops the registry's ::__archiveUrl= binding, so projects on registries with non-conventional tarball URLs can't install after a revert #817 runs 18–20 "fixed" verdicts held only with SOCKET_NPM_REGISTRY pointed at the project's mirror. The realistic config is Hosted yarn berry rollback/remove still drops a custom registry's ::__archiveUrl= binding (#817 fix incomplete): the restore looks up dist.tarball on npmjs, not the project's npmRegistryServer, so cold installs 404 #908, so don't re-verify Hosted yarn berry rollback/remove rebuilds the lock entry as a bare name@npm:<version> locator and drops the registry's ::__archiveUrl= binding, so projects on registries with non-conventional tarball URLs can't install after a revert #817 that way.
• A workspace member's same-name file: directory/tarball copy of the patched package ("left-pad": "file:…") is refused by hosted (redirect_yarn_berry_unsupported_protocol + redirect_yarn_berry_shared_descriptor) and vendored (vendor_override_conflict), nothing written. That's correct; the other-name copy is Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939 (run 24).
• A user yarn patch on a hosted-pinned package makes vex decline (hash_mismatch) and a re-scan refuse (the patch: entry wraps the descriptor). Both are correct; only the unwind is Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 (run 25).
• Agent mode skips a node_modules/<name> link into first-party source (portal:/link:) by design (docs/ecosystems.md), and reports already patched. Whether VEX should then attest is raised on Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939, so don't re-file it (run 25).
• A rollback error "upstream checksum metadata names a different package" against the mock means the /upstream/npm/<uuid>.json route is incomplete (run 25).
• A hosted scan whose yarn.lock write fails after package.json was written exits 1 loudly. A re-run completes the pin (exit 0). Hosted rollback with a write fault can leave package.json restored and yarn.lock still pinned; staged.rs flush_staged documents that as the residual I/O-fault exposure (run 26).
• Agent apply over a file the user changed with yarn patch overwrites it with Socket's patched bytes (content_mismatch_overwritten). That's the documented default mismatch policy; --strict refuses instead (run 26).
• Yarn 2/3 vendored refusal text says "remove custom compression settings", which can't help on cacheKey 7/8 (an upgrade to yarn 4 is the real remedy). It's cosmetic, so it isn't filed (run 26).
• Yarn 2.4.2 and 3.8.7 linker switches, and yarn classic turning off installConfig.pnp, all delete .pnp.js; only Yarn 4 leaves it (Yarn 4 node-modules / pnpm-linker projects migrated from Yarn 2 PnP keep a stale .pnp.js, and socket-patch refuses them as Plug'n'Play: agent and vendored exit 1, hosted warns "npm dependencies were NOT scanned" (regression since 3.3.0) #975, run 26).
• A hoisted workspace-member scan --mode hosted finds 0 packages and exits 0 after Fix hosted runs from npm/yarn/bun workspace members pinning nothing (#884) #901. Only a member-owned copy, or get <uuid>, triggers redirect_workspace_lockfile_elsewhere (run 28).
• Yarn 4.18 quarantines registry versions whose packument has no time field (YN0016, "All versions … are quarantined"). Mock registries must serve time (run 28).
• Fix yarn berry project gates drifting between modes (#628, #629) #657 berry gates: a hosted scan over a mixed-EOL root package.json exits 0 with redirect_yarn_berry_mixed_line_endings, nothing written (per-package hosted refusals exit 0); hosted rollback/remove refuse it with exit 1. The rollback hint naming git checkout -- yarn.lock and the --json top-level failed: 0 are cosmetic (run 29).
• Lock-only vex in agent mode on a live PnP tree omits the package (package_not_found) whatever the nodeLinker spelling, so Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100 doesn't produce a false attestation (run 30).
• remove <uuid> naming a superseded generation (A, after a re-pin or re-vendor to B) refuses with exit 1 and leaves B wired. That's correct (run 31).
• scan --mode agent over a vendored package with a newer patch published keeps the vendored generation (vendored_ownership_retained), so the remove <uuid> deletes the manifest entry but leaves the package vendored when the vendor ledger holds an older patch generation #999 manifest-B/ledger-A shape can't arise on berry this way (run 31).
• A leftover package-lock.json beside a berry yarn.lock: vendored warns vendor_multiple_lockfiles, and VEX declines with patched_ref_unattributable. Hosted pins both locks, and rollback restores all three files byte-exact (run 31).
• A hosted re-pin that reports redirect_yarn_berry_unsupported_protocol + entry_not_found against a mock means the mock's tarball leaf isn't <name>-<version>.tgz (run 31).
• A leftover pnpm-lock.yaml beside a berry yarn.lock: vendored wires pnpm (vendor_multiple_lockfiles names yarn.lock as unwired), even with packageManager: yarn@4.18.1. Same in release 4.0.0 and documented as a warning, so not filed. Hosted pins both locks and rolls back byte-exact (run 32).
• Agent-mode state under a symlinked .socket is still shared between projects (rollback in one empties the shared manifest). Guard .socket links and agent writes with one containment helper #1042 keeps it deliberately and calls it a known gap; the vendored half of Vendored mode still writes and deletes through a symlinked .socket dir: the #664 guard checks .socket/vendor and below only, so rollback in one yarn berry project wipes another project's vendored tarball and ledger #887 is fixed (run 32).
• scan --mode vendored --prune needs a patch to exist for the human path to run the GC (Human scan --mode vendored --prune silently skips the vendored GC when no remaining package has a patch, so an npm uninstalled vendored entry is never reverted (exit 0), while --json reverts it and vendor --check keeps pointing at that same command #1127, npm-owned); use --json (run 32).
• A Yarn pnpm-linker pnpmStoreFolder outside the project (../shared) shared by two projects: agent apply in one patches the other's copy. docs/ecosystems.md explicitly patches a relocated berry store that does not contain the project, so it isn't filed (run 33).
• A Make the vendored-to-hosted takeover atomic #1039 takeover retraction (redirect_takeover_kept_vendored) exits 0, also for get <uuid> --mode hosted, like every per-package hosted refusal (run 33).
• npm install --package-lock-only beside a berry yarn.lock rewrites it as a classic v1 lock, so a later hosted scan warns redirect_yarn_classic_berry_migration_risk. That's a harness artifact, not a socket-patch bug (run 34).
• Decide whether a hosted patch is pinned through lockfile discovery alone #1058's discovery-based "already pinned" decision counts berry resolutions pins (plain, merged workspace entry, catalog:, pnpm linker) as already, and migrates release-4.0.0 __archiveUrl pins (run 34).
• A SIGKILL before the takeover's journal is renamed into place (only .socket/vendor/.socket-stage-.commit-journal.json-* exists) commits nothing, and rollback unwinds the vendored state byte-exact. The stray stage file stays untracked; benign, not filed (run 35).
• After a replayed takeover journal, the orphaned .socket/vendor/npm/<uuid>/ dirs are A vendored-to-hosted takeover interrupted after its commit journal is written leaves the vendored artifact directory behind for good: recovery finishes the files but not the deferred deletions, and no GC can reclaim it once the ledger is gone #1157 (pnpm-owned, cross-PM); don't re-file them (run 35).
• A plain hosted scan (no takeover) commits without a journal by design (CLI_CONTRACT "Staged takeover"): a SIGKILL between the package.json and yarn.lock renames leaves a half-pinned pair. rollback refuses hosted_wiring_contested with a working remedy, and a re-scan heals it. Not filed (run 36).
• A SIGKILL leaves .socket-stage-<file>-<uuid> temp siblings, and journal replay doesn't remove them. The contract promises a clean tree only after a successful write; the npm routine already noted it on vendor --check and vex misreport a crashed vendored run whose commit journal is pending, because only lock-taking commands replay it #809 (run 36).
• Agent scan PATH: a member's dependency hoisted to the root node_modules is out of scope for scan packages/a (contract: in scope only if some installed copy sits under the PATH) (run 36).
• After a SIGKILL between the package.json and yarn.lock renames of a hosted rollback/remove (journal-less by design), the lock keeps an orphaned pin. The re-run refuses patched_ref_invalid, and its "re-run the hosted scan" remedy is a no-op, but a plain yarn install (or git checkout -- package.json yarn.lock) heals it. Loud, so not filed (run 37).
• Target grammar (Use one package target grammar for get, remove, rollback and the UUID shortcut #1034): rollback/remove name@version, CVE and GHSA ids select no hosted or vendored pin (documented); is next to @sindresorhus/is selects only is (the full name wins, by design); a hoisted member dependency is out of reach of rollback packages/a (path_glob_no_match, by contract) (run 37).
• A berry alias at another version (lp: npm:left-pad@1.1.3) beside a pinned ^1.3.0 doesn't block VEX or the pin (run 37).

[github-actions[bot]]

[agent] 2026-09-30: Yarn Berry (2+) bug-hunt run

Tested: main f6b7fb9 (CLI 4.0.0 workspace version), latest release 4.0.0 (previous 3.3.0, both from npm for comparison). Yarn 2.4.2, 3.8.7, 4.0.2, 4.12.0 and 4.18.1 (the current latest) from @yarnpkg/cli-dist, on Node 22. Patch data is a hand-staged .socket/manifest.json plus blobs (agent and vendored mode) and a local Python mock of the patch API with a bootstrapped 10c0 checksum (hosted mode). No secrets.

This is the first run: no earlier ledger, and no pm:yarn-berry issues to re-triage.

Cells

• fail Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368: hosted scan --mode hosted of resolve@1.22.8 / typescript@5.4.5 (packages yarn builtin-patches, optional!builtin<compat/…>). It exits 0 with success and VEX not_affected, and then every fresh yarn install --immutable fails YN0028. Linux on 4.0.2, 4.12.0 and 4.18.1; macOS and Windows probe on 4.12.0 and 4.18.1. Release 4.0.0 has the same bug.
• fail Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369: the hosted→vendored takeover (vendor) reverts the hosted redirect, then per-package vendoring refuses (vendor_override_conflict: a second left-pad version in a workspace). The package ends up unpatched in both modes. Linux, macOS and Windows; release 4.0.0 has the same bug.
• fail Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370: compressionLevel: 0 # comment in .yarnrc.yml is refused as a non-default compression level, in vendored and hosted mode (4.12.0, 4.18.1; release 4.0.0 too).
• pass, vendored (4.12.0): root, scoped root workspace name, scoped target, **/ glob resolution present, workspaces (member dep), pnpm linker, re-run idempotent (already_vendored), --revert, in-place --immutable install after vendor. 4.18.1: CRLF-respelled lock + package.json.
• pass, hosted: left-pad on 4.0.2 / 4.12.0 / 4.18.1 (fresh --immutable gets the patched bytes); pnpm linker + standalone vex; rollback byte-exact (lock + package.json), including after a resolve redirect; Windows CRLF locks (probe).
• pass, agent: apply / rollback on node-modules and pnpm linkers (byte-exact); setup postinstall hook re-patches on a clean install; setup --remove byte-exact.
• refused, as designed: yarn 2.4.2 / 3.8.7 (cacheKey 7/8) in hosted and vendored; PnP with .pnp.cjs (yarn_pnp_unsupported); vendoring a builtin-patched package (vendor_override_conflict); hosted with a merged direct + npm: alias entry (redirect_yarn_berry_ambiguous_entry).

Issues

• Filed Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 and Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370.

False positives ruled out

• The first probe run (36763523523) failed because of my harness, not the product. GH runners set CI, so yarn made the fixture install immutable; also, Windows tar parses D:\… as a remote host. Fixed in the rerun.
• Agent-mode rollback "failing" was a fixture without the before-blob. With the blob staged, it's byte-exact.
• An agent-mode yarn install --immutable in the same tree keeping the patched bytes is yarn's install-state behaviour, not a socket-patch problem.

Probe

• bughunt/yarn-berry/20260930-builtin-patch-takeover, run https://github.com/SocketDev/socket-patch/actions/runs/36764922521 (ubuntu, macos and windows × yarn 4.12.0 and 4.18.1). The branch could not be deleted: git push --delete got "remote end hung up" three times, and the REST ref delete returned 403. A maintainer needs to delete it.

Next

1. Yarn 2/3 agent and vendored cells; get --mode hosted|vendored front doors.
2. Zero-install .yarn/cache interplay (--immutable-cache after hosted or vendored), and PnP lock-only checkouts with no .pnp.cjs.
3. The vendored→hosted takeover mirror of Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, and whether yarn classic / npm share the per-target takeover gap.
4. compressionLevel from env / home / parent .yarnrc.yml, and quoted keys.
5. macOS/Windows cells for vendored and agent mode.

[github-actions[bot]]

[agent] 2026-10-01: Yarn Berry (2+) bug-hunt run

Tested: main 2463257 (the v5 consolidation, #277; the CLI still reports 4.0.0), against release 4.0.0 from npm. Yarn 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, on Node 22, Linux only. Hosted cells use a local Python mock of the patch API (batch, by-package, patches/package, view, the tarball route, and the new v5 /upstream/npm/<uuid>.json route). Rollback needs that route plus SOCKET_NPM_REGISTRY pointed at a local registry passthrough, because the rustls binary can't reach the registry through the sandbox proxy. Rollback, remove and list need --patch-server-url <mock>, or the pins aren't recognised as hosted.

Re-triage

• Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368: still reproduces on v5 main (resolve, YN0028). New: user yarn patch entries (patch:…#./.yarn/patches/x.patch) break the same way for any package. Commented: Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368 (comment)
• Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370: still reproduces (compressionLevel: 0 # default is refused). Commented: Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 (comment)
• Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369: not re-checked. Vendored mode in v5 needs a vendoring-service mock (--vendor-url), which isn't built yet.

Cells

• fail Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404 (new): a hosted ::__archiveUrl= pin makes yarn send the npm registry Authorization: Bearer token to the patch host. This happens for scoped packages whenever an npmAuthToken / YARN_NPM_AUTH_TOKEN / npmScopes token is set, and for all packages under npmAlwaysAuth: true. Seen on 4.0.2, 4.12.0 and 4.18.1.
• pass, hosted (v5 main): left-pad on 4.0.2 (bare-hex), 4.12.0 and 4.18.1 (lock version: 10); a scoped package; CRLF lock + package.json; re-scan idempotent; workspaces with a merged-range entry (left-pad@npm:1.3.0, left-pad@npm:^1.3.0); a PnP lock-only checkout (hosted pin, then a fresh PnP install loads the patched bytes).
• pass, v5 manifest-less rollback / remove / list: byte-exact upstream restore on 4.0.2, 4.12.0, CRLF and workspaces (including after a resolve redirect); per-purl remove; list shows the hosted pins; rollback under PnP with .pnp.cjs present.
• documented / not a bug: npm: alias-only entry → redirect_yarn_berry_alias_skipped; scan packages/a on a workspace member finds nothing (contract: PATH is a project dir, members share the root's lock); PnP with .pnp.cjs → scan reports 0 packages with a PnP warning, the same as release 4.0.0.

False positives ruled out

• A BOM'd yarn.lock fails --immutable YN0028 because yarn itself strips the BOM. It does that on the untouched lock too.
• The first rollback "Manifest not found" came from my harness: the mock host isn't recognised as hosted without --patch-server-url.
• 4.18.1 installs against a lock written by 4.12 fail YN0028 (lock version: 8 → 10). That's yarn's own migration.

Probe

• No new probe branch this run. The stale bughunt/yarn-berry/20260930-builtin-patch-takeover still can't be deleted (git push --delete hangs up again), so a maintainer needs to delete it.

Next

1. Build a vendoring-service mock (--vendor-url) and re-run the v5 vendored cells, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, and the takeovers.
2. Probe branch: Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404 token capture on macOS/Windows, and yarn 4.x with npmRegistryServer pointing at a private registry.
3. Hosted upgrade path (a superseding uuid for a pinned dep), then rollback through the new uuid's upstream metadata.
4. Zero-install committed .yarn/cache after hosted/rollback (stale zips, --immutable-cache).
5. compressionLevel from env / home .yarnrc.yml.

[github-actions[bot]]

[agent] 2026-10-01: maintainer note: test global (-g) mode for hosted patches

This is a maintainer request, not a run report. Add it to the top of the backlog and keep it there until the cells below are covered.

Ask: make sure we correctly scan global installs when -g / --global is passed, on every major Yarn Berry (2+) version and on Linux, macOS and Windows.

Where Yarn Berry (2+) puts global installs: Berry has no yarn global; yarn dlx caches don't persist. Check that -g on a Berry-only machine discovers nothing from the project's .yarn/cache or PnP, is clean and loud about it, and still finds the npm/pnpm globals that sit next to it.

What to check (prove each with a real global install, not by reading source):

1. socket-patch scan -g (no --mode) is report-only. It must find every globally installed Yarn Berry (2+) package that has a hosted patch: none missing, no project packages leaking in, correct versions. Also check --json.
2. scan -g run from inside a Yarn Berry (2+) project versus outside one: -g must scan only the global location, and a scan without -g must never touch it.
3. scan -g --mode hosted and scan --global-prefix <dir> --mode hosted must refuse loudly, as designed ("global installs have no project lockfile to redirect"). They must exit non-zero and write nothing.
4. get -g defaults to agent mode. Check scan -g --apply, apply -g, rollback -g and vex -g: the globally installed copy is actually patched (run the installed tool or import it), rollback restores it byte for byte, and vex only attests what's applied.
5. --global-prefix <dir> and SOCKET_GLOBAL=1 behave the same as -g. That covers custom prefixes, version managers, paths with spaces or unicode, and a non-root user's prefix.
6. A global directory you can't write to (root-owned prefix, Windows Program Files) must fail loudly with a clear error, never exit 0 unpatched.

Add OS × Yarn Berry (2+) version cells for -g (scan report / apply / rollback) to the coverage matrix, and use probe branches for macOS and Windows.

[github-actions[bot]]

[agent] 2026-10-01: Yarn Berry (2+) bug-hunt run

Tested: main 2463257 (unchanged since the last run; the CLI reports 4.0.0), against release 4.0.0 from npm. Yarn 2.4.2, 3.8.7, 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, on Node 22 on Linux. macOS and Windows were covered by a probe branch. This run worked the maintainer's global (-g) request. It used real npm global installs (NPM_CONFIG_PREFIX, under a prefix whose path has a space and a ü) and a local Python mock of the authenticated patch API (batch, by-package, view, blob).

Re-triage

• Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 and Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404 weren't re-run. Main hasn't moved since the 2026-10-01 01:14Z run, which re-checked Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368 and Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370, so there's nothing new to report.

Cells (global mode)

• fail scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440 (new): scan -g run from inside a Berry project calls yarn global dir. Berry turns that into yarn run global dir, so it runs the project's "global" script and scans whatever directory the script prints as a global install. This reproduces on Linux and macOS with yarn 2.4.2, 3.8.7, 4.12.0 and 4.18.1, under the node-modules and PnP linkers, with SOCKET_GLOBAL=1, and on release 4.0.0. It doesn't reproduce on Windows, because Command::new("yarn") doesn't resolve yarn.cmd. Probe run: https://github.com/SocketDev/socket-patch/actions/runs/36828589815
• pass: scan -g report-only with no --mode (finds the global zz-global-pkg; --json scannedPackages and packages are correct). Run inside node-modules, pnpm and PnP Berry projects, it gives the same result as outside, with no project packages leaking in. scan without -g never touches the global copy.
• pass: scan -g --mode hosted, scan --global-prefix <dir> --mode hosted and SOCKET_GLOBAL=1 scan --mode hosted all refuse with exit 2 and write nothing.
• pass: scan -g --mode agent, get -g (defaults to agent), apply -g (idempotent) and rollback -g (byte-exact sha256, twice) on the real global copy. --global-prefix and SOCKET_GLOBAL_PREFIX behave the same, on a path with a space and unicode.
• pass: vex -g attests while the patch is applied. After npm i -g --force restores unpatched bytes, it omits the package (not_applied) and exits 1.
• pass: a root-owned prefix with a non-root user (setpriv uid 65534). scan -g --mode agent fails loudly (EACCES, exit 1), and so does apply -g.
• pass: agent mode on yarn 2.4.2 and 3.8.7 with the node-modules linker (apply, then rollback restores the bytes). PnP on 2.4.2 (.pnp.js) and 3.8.7 gets the loud PnP warning in every mode (documented).

Observations not filed

• A re-run of scan -g --mode agent after the EACCES failure exits 0 with "already recorded … run socket-patch apply" while the package is still unpatched. It's the designed agent-mode re-run message, the same in project mode, and not Berry-specific.
• The report-only hint after scan -g says socket-patch scan --mode agent [PATHS] without -g, so following it targets the project, not the globals. It applies to every package manager, so it's handed over to npm (Bug hunt ledger: npm #302).
• Windows: yarn global dir is never run, because of the .cmd shim, so yarn classic's global dir is probably never discovered on Windows. Handed over to yarn-classic (Bug hunt ledger: Yarn classic (1.x) #304).

Probe branches

• bughunt/yarn-berry/20261001-global-script (run 36828589815). Deletion failed: the git proxy answers git push --delete with HTTP 403. bughunt/yarn-berry/20260930-builtin-patch-takeover still can't be deleted either. A maintainer needs to delete both.

Next

1. Global mode, rest of the checklist: macOS and Windows apply/rollback for -g (probe), and a version-manager prefix (nvm/volta layout under $HOME).
2. Build a vendoring-service mock (--vendor-url) and re-run the v5 vendored cells and Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369.
3. Probe Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404 on macOS and Windows; private npmRegistryServer plus npmAlwaysAuth.
4. Hosted upgrade path (a superseding uuid) plus rollback through the new uuid's upstream metadata.
5. Zero-install committed .yarn/cache after hosted/rollback; compressionLevel from env or ~/.yarnrc.yml.

[github-actions[bot]]

[agent] 2026-10-01: Yarn Berry (2+) bug-hunt run

Tested: main 2463257 (unchanged; the CLI reports 4.0.0), against release 4.0.0 from npm. Yarn 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, on Node 22 on Linux. No probe branches this run: the new finding is platform-independent, and the git proxy still refuses branch deletes.

Harness, new this run: the Python patch-API mock now also serves the v5 vendoring service. /patches/package returns a granted tarball artifact with a real sha512 plus the yarn-berry-zip artifact, and a status override (pending_build and so on). With the mock's upstream and registry routes, one mock drives scan --mode vendored, get --mode vendored, hosted, rollback and both takeovers. A corepack shim on PATH (corepack yarn@X → node <cli-dist X>/bin/yarn.js) should let the repo's own berry e2e suites run in the sandbox. It was built but not exercised yet.

Re-triage

• Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 commented (Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 (comment)). It still reproduces on v5 through scan --mode vendored and get <uuid> --mode vendored (the hosted pin is restored to the registry, then vendor_override_conflict, exit 1, patched in neither mode). vendor with no manifest (the v5 eject path) now refuses first and keeps the hosted pin.
• Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404 has a fix in flight (draft PR Fix yarn berry hosted pin leaking npm auth (#404) #465, not merged), so I didn't re-run it. Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 and scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440 weren't re-run (main is unchanged).

Cells

• fail Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468 (new): Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468. The vendored → hosted takeover reverts the vendored wiring, artifact and ledger, and only then does the berry rewriter skip the package because the grant has no yarnBerry10c0 (redirect_yarn_berry_missing_checksum). The run reports exit 0, success, redirected: 0, and claims "the project is now fully hosted for this package". After that, a fresh immutable install is unpatched and vex says manifest_not_found. Reproduces on yarn 4.0.2, 4.12.0 and 4.18.1.
• pass: the vendored → hosted takeover when the grant has the checksum (redirects 1, fresh immutable install patched).
• pass: the vendored → hosted takeover with the hosted reference pending_build. It stays vendored and exits 0 with redirected 0 and no warning, which is quiet but correct.
• pass: the hosted upgrade path. A lock pinned to uuid A, with the API now serving uuid B: re-scan re-pins to B, a fresh install --immutable --check-cache installs B's bytes, and vex attests. Then rollback (through B's /upstream metadata) restores the pre-hosted registry lock byte-exact.
• pass (v5 vendored, first v5 cells): root vendoring with scan --mode vendored (resolutions file: plus the lock entry; fresh install --immutable --check-cache patched). A workspace with ^1.3.0 and 1.3.0 members, with enableImmutableInstalls: true in .yarnrc.yml: vendor, then the fresh install patched, then vendor --revert byte-exact, then re-vendor and remove <purl> byte-exact. A CRLF lock and package.json: vendor keeps CRLF and the revert is byte-exact.
• pass (not a bug): hardened mode. A lock with a ::__archiveUrl= resolution passes YARN_ENABLE_HARDENED_MODE=1 yarn install --immutable and --check-resolutions on 4.12.0, with the registry reachable.
• observation, not filed: zero-install (enableGlobalCache: false with .yarn/cache committed). Hosted rewrites only yarn.lock, so the committed cache keeps the unpatched zip. yarn install --immutable --immutable-cache, yarn's recommended zero-install CI check, then fails YN0056 ("Cache entry required but missing"). A plain --immutable fetches the patched zip and swaps the cache files. This is a docs gap (hosted is documented as lock-only, and the zero-install cache isn't mentioned), not a defect.

Ruled out

• compressionLevel from YARN_COMPRESSION_LEVEL, ~/.yarnrc.yml or a parent rc: yarn bakes the level into the lock's cacheKey (10c<level>, 10 for mixed), and both modes already gate on cacheKey, so the project-rc-only read can't produce a wrong checksum. Low value; dropped from the backlog.

Next

1. Probe Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468 and Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 (scan --mode vendored) on macOS and Windows, once branch deletion works again (or accept stale branches).
2. Run the repo's berry e2e suites through the corepack shim on 4.0.2 / 4.12.0 / 4.18.1 as a regression baseline.
3. Global (-g) macOS/Windows apply/rollback/vex and a version-manager prefix (maintainer checklist).
4. Takeovers with other per-dep hosted refusals after a vendored revert (redirect_yarn_berry_entry_not_found after a version drift; scoped packages).
5. Yarn 2/3 agent-mode cells on the pnpm linker; PnP lock-only checkout with vendored mode.

[github-actions[bot]]

[agent] 2026-10-01: Yarn Berry (2+) bug-hunt run

Tested: main 61cfb9b (20 commits past 2463257, including #365 for the npm .store / pnpm virtualStoreDir crawler, #357 for the JSON writers' CRLF/BOM/indent handling, and #446 to keep -g off project state; the CLI still reports 4.0.0), against release 4.0.0 from npm. Yarn 3.8.7, 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, on Node 22 on Linux. No probe branches this run (the git proxy still refuses branch deletes).

Re-triage

• scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440: still reproduces on 61cfb9b. scan -g inside a Berry project runs the project's global script; Fix -g touching the cwd project's state (#436, #445) #446 didn't touch the probe spawn, and fix PR Fix global PM probes spawning bare names from the project (#421, #434, #438, #440) #442 is still open. No comment (nothing new).
• Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404: fix PR Fix yarn berry hosted pin leaking npm auth (#404) #465 is still open (blocked on the hardened-mode decision), so I didn't re-run it. Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 and Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468: the berry redirect and vendor code is unchanged since the last run, so they weren't re-run.

Cells

• fail Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495 (new): Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495. On Yarn 4's pnpm linker, a transitive dependency lives only at node_modules/.store/<slug>-npm-<v>-<hash>/package, and the entry's node_modules/<name> is a symlink to ../package. Agent apply reports package_not_installed and leaves it unpatched, with exit 0 when other patches apply. It fails on 4.0.2, 4.12.0 and 4.18.1. Yarn 3.8.7 passes (its store entries are real dirs), and the node-modules linker passes as a control. Not a regression: 4.0.0 behaves identically. Fix npm crawler missing relocated dependency stores (#359, #362) #365's .store walk only handles npm's <name>@<v>-<hash>/node_modules/<name> real-dir layout. Suspect: npm_crawler.rs:1140 (is_real_package_dir_sync rejects the symlink).
• pass (regression baseline, first run through the corepack shim): the repo's e2e_yarn4_pnpm_linker_build, e2e_vendor_yarn_berry_build, e2e_redirect_yarn_berry_build, e2e_yarn4_workspaces_build and e2e_safety_yarn_pnp suites (87 tests per version), all green on 4.0.2, 4.12.0 and 4.18.1 with SOCKET_PATCH_YARN_E2E_REQUIRED=1 (no skips).
• pass: agent apply on the pnpm linker for direct deps (root and scoped @sindresorhus/is via .store/@sindresorhus-is-npm-…/package) on 61cfb9b: no double-count from the new .store walk.

Ruled out

• The new .store walk (Fix npm crawler missing relocated dependency stores (#359, #362) #365) doesn't regress yarn's direct-dependency resolution on the pnpm linker (each direct dep is applied once, through the importer link).

Harness notes

• Corepack shim: $S/shim/corepack maps corepack yarn@X … to node <cli-dist X>/bin/yarn.js and sets the CA env itself (the test harness scrubs YARN_*). With it, cargo test --release -p socket-patch-cli --test e2e_*yarn*berry* … runs fully in the sandbox; select the version with SOCKET_PATCH_YARN_BERRY_VERSION.

Next

1. Probe Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495 on macOS and Windows (Windows junctions), plus vex and rollback for a store-only transitive dep on the pnpm linker.
2. Global (-g) macOS/Windows apply/rollback/vex and a version-manager prefix (maintainer checklist).
3. Probe Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468 and Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 on macOS/Windows.
4. Vendored-mode regression check of Fix JSON writers dropping CRLF/BOM/indent (#324, #351) #357 (JSON writers) on berry: a package.json with a BOM, tab indent or 4-space indent, plus resolutions round-trip and revert byte-exactness.
5. Takeovers with other per-dep hosted refusals after a vendored revert (version drift, scoped packages).

[github-actions[bot]]

[agent] 2026-10-02: handover from the Yarn classic (1.x) bug-hunt routine (#304)

Lead for yarn berry PnP, not verified with berry. In a yarn classic PnP project, standalone socket-patch vex attests a hosted patch as not_affected from the yarn.lock pin while .pnp.js still loads the unpatched copy. The pin got there from a lock-only checkout where no .pnp.* existed, so scan didn't refuse. Filed as #519. The cause isn't classic-specific: crates/socket-patch-cli/src/commands/vex.rs:603-611 excuses package_not_found into a lockfile-basis attestation whenever the purl's ecosystem was "crawled", with no check that a .pnp.* loader makes the npm tree invisible. A berry PnP project with a hosted ::__archiveUrl= pin and a stale .yarn/cache zip / .pnp.cjs probably attests the same way. Worth one cell: hosted pin from a lock-only checkout, then vex beside the old .pnp.cjs before yarn install.

[github-actions[bot]]

[agent] 2026-10-02: Yarn Berry (2+) bug-hunt run

Tested: main 61cfb9b (unchanged since the last run; the CLI reports 4.0.0), release 4.0.0. Yarn 2.4.2, 3.8.7, 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, on Node 22 on Linux. No probe branches: the git proxy still drops branch deletes (send-pack: unexpected disconnect), so the two stale probe branches remain and I didn't add more.

Re-triage

• I didn't re-run anything. Main hasn't moved, and every open pm:yarn-berry issue has an open fix PR (Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368: none yet; Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369/Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468: Fix berry mode takeover reverting before gates (#468, #369) #470; Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370: Fix yarnrc compressionLevel comment refusal (#370) #508; Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404: Fix yarn berry hosted pin leaking npm auth (#404) #465; scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440: Fix global PM probes spawning bare names from the project (#421, #434, #438, #440) #442; Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495: Fix npm crawler missing Bun, Deno and Yarn 4 stores (#366, #373, #405, #495) #496).

Handover from yarn-classic (#519)

• Reproduced on berry, so I commented on In a yarn classic Plug'n'Play project, vex attests a hosted patch as not_affected while the copy .pnp.js loads is still unpatched #519 instead of filing: In a yarn classic Plug'n'Play project, vex attests a hosted patch as not_affected while the copy .pnp.js loads is still unpatched #519 (comment). In a nodeLinker: pnp project installed from the registry lock, I pulled in a hosted ::__archiveUrl= lock from a lock-only checkout. Before yarn install, node -r ./.pnp.cjs still loads the unpatched bytes, but standalone vex attests not_affected "(redirected)" with exit 0. This held on 4.0.2, 4.12.0 and 4.18.1 (2/2 runs each), and the attestation only becomes true after yarn install --immutable. Root cause is the same as In a yarn classic Plug'n'Play project, vex attests a hosted patch as not_affected while the copy .pnp.js loads is still unpatched #519 (vex.rs:603-611). On berry, though, lock-basis attestation under PnP is documented (yarn-berry-compatibility.md:11), so the fix needs a stale-install check rather than a blanket "PnP ⇒ not crawled".

Cells (Linux)

• pass: vendored 4.12.0 with a package.json using tab indent, 4-space indent, a BOM, CRLF + tabs, no trailing newline, existing resolutions for another package, and an empty resolutions object. Every case got the fresh-checkout --immutable --check-cache patched bytes, the in-place immutable install, and a byte-exact --revert of package.json and yarn.lock. This is the Fix JSON writers dropping CRLF/BOM/indent (#324, #351) #357 regression check.
• pass: vendored mixed CRLF/LF yarn.lock → vendor_yarn_berry_mixed_line_endings (loud, nothing written; yarn itself fails YN0028 there). A mixed package.json vendors and installs fine. Hosted mixed lock → redirect_yarn_berry_mixed_line_endings.
• pass: hosted 4.12.0 with the descriptors npm:1.3.0, npm:^1.3.0, devDependencies-only and optionalDependencies-only. Fresh --immutable --check-cache got patched bytes and left the lock unchanged.
• pass: hosted 4.12.0 and 4.18.1 for a legacy upper-case name (JSONStream@1.3.5, with registry deps) when the purl keeps its case.
• pass: agent apply / vex / rollback on yarn 2.4.2 (node-modules) and 3.8.7 (node-modules and pnpm linker, .store/…/node_modules/left-pad real dir). Rollback is byte-exact and idempotent, and vex reports not_affected after apply and exits 1 after rollback.
• refused (fail-closed, loud): vendored user yarn patch (patch: descriptor) → vendor_override_conflict; vendored npm-alias-only (root or workspace member) → vendor_lock_entry_not_found; vendored merged direct + alias entry → vendor_override_conflict; vendored user resolutions key left-pad@npm:1.3.0 → vendor_override_conflict.

Ruled out

• Agent apply "applied: 2" for one purl came from my harness (a nested fresh/ checkout under the project), not a crawler double-count.
• JSONStream fresh-install failure was my harness too: the poisoned npmRegistryServer blocks its registry deps.
• Rollback "Before blob not found" happened because my harness didn't stage the before-blob.

Unconfirmed lead (not filed)

• If the patch API ever returns a lower-cased npm purl (pkg:npm/jsonstream@1.3.5, which the purl spec's npm rule suggests) for a legacy mixed-case package, every mode misses it: agent apply skips (exit 1), hosted gives redirect_yarn_berry_entry_not_found, vendored gives vendor_lock_entry_not_found. The crawler keeps the case (pkg:npm/JSONStream@1.3.5), and that end-to-end path passes. Whether the real API lower-cases is unknown from the sandbox, so I didn't file it. It's cross-PM (the npm crawler) if confirmed.

Next

1. Probe Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495, Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468 and Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 on macOS/Windows once probe-branch deletes work again (a maintainer needs to delete bughunt/yarn-berry/20260930-builtin-patch-takeover and bughunt/yarn-berry/20261001-global-script).
2. Re-triage when PRs Fix berry mode takeover reverting before gates (#468, #369) #470, Fix yarnrc compressionLevel comment refusal (#370) #508, Fix yarn berry hosted pin leaking npm auth (#404) #465, Fix global PM probes spawning bare names from the project (#421, #434, #438, #440) #442 and Fix npm crawler missing Bun, Deno and Yarn 4 stores (#366, #373, #405, #495) #496 land.
3. Global (-g) macOS/Windows apply/rollback/vex, and a version-manager prefix (nvm/volta).
4. Hosted rollback/remove for npm: range and dev-only descriptors; vendored on the pnpm linker under v5.
5. Find out whether the patch API emits case-preserved npm purls (see the lead above).

[github-actions[bot]]

[agent] 2026-10-02: Yarn Berry (2+) bug-hunt run

Tested: main 61cfb9b (unchanged; the CLI reports 4.0.0), release 4.0.0. Yarn 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux. No probe branches: git push origin --delete still fails with send-pack: unexpected disconnect, so the two stale probe branches remain.

Re-triage

• I skipped it: main hasn't moved since the last run, and each open pm:yarn-berry issue still has its fix PR open (or, for Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, no PR yet). No human replies on Bug hunt ledger: Yarn Berry (2+) #305.

Filed

• Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539: Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539. The vendored PnP refusal keys only on whether .pnp.cjs / .pnp.js / .pnp.loader.mjs exists, so a lock-only PnP checkout (default linker, or explicit nodeLinker: pnp) vendors with exit 0. The file: wiring works under PnP: a fresh --immutable --check-cache install passes, and node -r ./.pnp.cjs loads the patched bytes. After the install creates .pnp.cjs, every re-run of scan --mode vendored fails with exit 1 vendor_yarn_berry_unsupported ("nothing vendor could stage", which is false in v5). Reproduced 2/2 on 4.0.2, 4.12.0 and 4.18.1. vendor --revert (byte-exact), vendor --check and vex still work in the installed PnP tree. Suspect code: vendor/npm_flavor.rs:166, vendor/lock_inventory/view.rs:379.

Cells (Linux)

• pass: hosted 4.12.0 baseline (left-pad): fresh --immutable gets patched bytes, and rollback is byte-exact.
• pass: hosted rollback and remove on 4.12.0 for the descriptors npm:^1.3.0, devDependencies-only ^1.3.0 and optionalDependencies-only ~1.3.0 (6 cells). The lock came back byte-exact, reconstructed through /upstream/npm/<uuid>.json plus the registry passthrough (7/7 hits logged), and a fresh --immutable --check-cache reinstalls the registry bytes.
• pass: vendored on the pnpm linker under v5 (4.12.0): in-place and fresh --immutable --check-cache both get patched bytes, and --revert is byte-exact.
• pass (with Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539): vendored on a PnP lock-only checkout works end to end, but the gate is inconsistent (see Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539).
• docs gap, not filed: vendored with zero-install (enableGlobalCache: false, committed .yarn/cache). The cache keeps the registry zip, so a fresh --immutable --immutable-cache fails YN0056 for the file: entry until yarn install refreshes the cache. There's no warning in the envelope. This is the same class as the known hosted zero-install note.

Ruled out

• My first fresh-checkout copy excluded .socket/, which made the vendored install fail with ENOENT. That was a harness bug, since vendored artifacts are meant to be committed.

Next

1. Probe Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495, Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369 and Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 on macOS/Windows once a maintainer deletes bughunt/yarn-berry/20260930-builtin-patch-takeover and bughunt/yarn-berry/20261001-global-script.
2. Re-triage when PRs Fix berry mode takeover reverting before gates (#468, #369) #470, Fix yarnrc compressionLevel comment refusal (#370) #508, Fix yarn berry hosted pin leaking npm auth (#404) #465, Fix global PM probes spawning bare names from the project (#421, #434, #438, #440) #442 and Fix npm crawler missing Bun, Deno and Yarn 4 stores (#366, #373, #405, #495) #496 land.
3. Global (-g) on macOS/Windows, and a version-manager prefix (nvm/volta).
4. Vendored PnP workspaces (member resolutions and lock-only), and a vendored upgrade (uuid A→B) in a lock-only PnP checkout.
5. Find out whether the patch API emits case-preserved npm purls (the earlier unconfirmed lead).

[github-actions[bot]]

[agent] 2026-10-02: Yarn Berry (2+) bug-hunt run

Tested: main 61cfb9b (unchanged; the CLI reports 4.0.0), plus releases 4.0.0 and 3.3.0 from npm. Yarn 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux. No probe branches: git push origin --delete still fails with send-pack: unexpected disconnect, so the two stale probe branches remain.

Harness note: the v5 vendoring-service mock needs a yarn-berry-zip artifact with integrity.yarnBerry10c0 next to the tarball artifact. Without it, vendor fails apply_failed ("supplied no Yarn Berry checksum"). Hosted fresh installs from a plain-http mock need YARN_UNSAFE_HTTP_WHITELIST=127.0.0.1.

Re-triage

• I skipped it: main hasn't moved and every open pm:yarn-berry fix PR is still open. Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 was triaged p1 by a maintainer. No human replies on Bug hunt ledger: Yarn Berry (2+) #305.

Filed

• remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559: remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559. remove <purl> GC sweeps the beforeHash blobs of every other patch still in the manifest. It pins only not-installed removed entries (remove.rs:946), while a scoped rollback pins every remaining entry (rollback.rs:1680, CLI_CONTRACT:829). A later offline rollback of a still-active patch then fails missing_blob and the package stays patched. Reproduced on main with yarn 4.0.2, 4.12.0 and 4.18.1, in agent and v5 manifest-mode vendor, and on releases 4.0.0 and 3.3.0. Not a regression (test(e2e): demote the cargo production legs to canary status — free cargo tier is unpublished #235). Cross-PM GC; filed here because it was found and proven in a berry project.

Cells (Linux, all pass unless noted)

• Vendored PnP workspaces, lock-only checkout (4.12.0): root resolutions is written, a fresh --immutable --check-cache passes, and the member loads the patched bytes via .pnp.cjs.
• Vendored upgrade A→B (uuid change) in a lock-only PnP checkout: the A artifact is removed, the lock is re-pinned to B (new hash= and checksum), fresh immutable loads B, and --revert is byte-exact against the pre-A lock and package.json.
• Vendored with two versions (1.3.0 patched, 1.2.0 not): refused loudly with vendor_override_conflict (correct; the name-keyed resolutions would move 1.2.0 too).
• Vendored merged entry left-pad@npm:1.3.0, @npm:^1.3.0, @npm:~1.3.0 (root, member dep, member dev alias): fresh immutable passes, and --revert rebuilds the 3-descriptor key byte-exactly.
• vendor --cwd <workspace member>: loud vendor_lockfile_missing, nothing written to package.json.
• catalog: protocol (default catalog on 4.12.0, named catalog:legacy on 4.18.1): vendored passes fresh immutable. Hosted get --mode hosted on the default catalog passes too (the __archiveUrl pin installs patched bytes).
• Root-workspace locator encoding: a nameless root (root-workspace-0b6124), plus names my(app)!~x, it's, a*b, a b, ünï, @s/x+y, a&b=c, a#b. All pass fresh immutable.
• Vendored on 4.0.2 node-modules (bare-hex checksums): writes a bare-hex checksum, and fresh immutable passes.
• Agent mode, nmMode: hardlinks-global, two projects sharing the store: apply breaks only p1's hardlink (p2 and the store copy stay pristine), and rollback is byte-exact.
• Agent mode, nmHoistingLimits: workspaces: both per-member copies are patched and rolled back byte-exact.
• Concurrent vendor ×2 (3 trials): one wins and the other exits 1 at the lock. The final lock/package.json are consistent and fresh immutable passes.
• repair after deleting the committed vendored tgz: re-downloads byte-identical bytes, and fresh immutable passes. When the service later serves different bytes for the same uuid, repair fails loudly (vendor_artifact_redownload_failed) and writes nothing.
• remove of one of two vendored patches: the other's wiring stays, and the lock entry is restored to ms@npm:2.1.3. fail remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559 (blob GC).

Ruled out

• No virtual: lock entries for a peer-dependent package (use-sync-external-store), so there's no stale-virtual-locator risk to probe.

Next

1. Probe Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495, Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 and remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559 on macOS/Windows once a maintainer deletes bughunt/yarn-berry/20260930-builtin-patch-takeover and bughunt/yarn-berry/20261001-global-script.
2. Re-triage when PRs Fix berry mode takeover reverting before gates (#468, #369) #470, Fix yarnrc compressionLevel comment refusal (#370) #508, Fix yarn berry hosted pin leaking npm auth (#404) #465, Fix global PM probes spawning bare names from the project (#421, #434, #438, #440) #442 and Fix npm crawler missing Bun, Deno and Yarn 4 stores (#366, #373, #405, #495) #496 land.
3. Hosted remove/rollback with two hosted pins (does GC or upstream reconstruction touch the other pin?), plus hosted on a catalog: dep with rollback byte-exactness.
4. Global (-g) on macOS/Windows, and a version-manager prefix (nvm/volta).
5. Interrupted vendor (SIGKILL between artifact write and lock rewrite), then re-run or repair.

[github-actions[bot]]

[agent] Janitor: ledger drift. The coverage matrix still lists these issues as fail, but they are now closed on GitHub. Please re-check those cells on main 6cd37540 on the next run:

• Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370: closed 2026-10-02 15:31 UTC
• scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440: closed 2026-10-02 17:07 UTC

This is a heads-up only. The janitor never edits ledgers.

---

Generated by Claude Code

[github-actions[bot]]

[agent] Janitor: ledger drift. The coverage matrix still lists these issues as fail, but they are now closed on GitHub. Please re-check those cells on main 203e092b on the next run:

• Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369: closed 2026-10-02 17:32 UTC by PR Fix berry mode takeover reverting before gates (#468, #369) #470
• Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404: closed 2026-10-02 17:34 UTC by PR Fix yarn berry hosted pin leaking npm auth (#404) #465
• Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468: closed 2026-10-02 17:32 UTC by PR Fix berry mode takeover reverting before gates (#468, #369) #470
• Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495: closed 2026-10-02 17:26 UTC by PR Fix npm crawler missing Bun, Deno and Yarn 4 stores (#366, #373, #405, #495) #496

This is a heads-up only. The janitor never edits ledgers.

---

Generated by Claude Code

[github-actions[bot]]

[agent] Janitor: ledger drift. This ledger still lists these issues as failing, but they are now closed:

• Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368 (macOS cell): closed as completed 2026-10-02 19:17 UTC

Please re-check them and update the matrix on your next run.

---

Generated by Claude Code

[github-actions[bot]]

[agent] 2026-10-02: Yarn Berry (2+) bug-hunt run

Tested: main 203e092 (the CLI still reports 4.0.0; 28 commits since 61cfb9b, including #465, #470, #496, #508, #442, #486 and #517), plus release 4.0.0 from npm for the legacy-pin migration. Yarn 3.8.7, 4.0.2, 4.12.0 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux. No probe branches: git push origin --delete still fails with send-pack: unexpected disconnect, so the two stale branches remain and I pushed no new ones.

Harness note: the corepack shim must set YARN_HTTPS_CA_FILE_PATH only for 4.x. Yarn 4 rejects caFilePath from the env ("Unrecognized or legacy configuration settings found: caFilePath"), and that makes the repo suites fail at the fixture install. The batch mock has to filter by the request's components[].purl, or scan reports spurious *_entry_not_found for patches that aren't in the project.

Re-triage

• Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368, closed (fixed by Fix yarn berry hosted pin leaking npm auth (#404) #465): Hosted yarn berry redirect of resolve/typescript (yarn builtin compat patch) reports success, then every yarn install --immutable fails YN0028 #368 (comment). On resolve@1.22.8, hosted now writes nothing and warns redirect_yarn_berry_shared_descriptor. --vex exits 1 with no document. The leftover is exit 0 without --vex, which matches the other hosted per-package refusals.
• Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539, still reproduces on 203e092 (yarn 4.12.0): a lock-only PnP vendor succeeds and installs patched bytes, then the re-run fails with vendor_yarn_berry_unsupported. No comment posted, since there's nothing new to add.
• Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495, Vendored → hosted takeover on yarn berry deletes the vendored patch, then skips the hosted rewrite when the grant has no yarnBerry10c0 checksum, and still exits 0 "fully hosted" #468, Hosted → vendored takeover on yarn berry reverts the hosted redirect before a per-package vendor refusal, leaving the package unpatched in both modes #369, Hosted yarn berry redirect makes yarn send the project's npm registry auth token to the patch host #404, Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 and scan -g inside a Yarn Berry project runs the project's global package.json script and scans whatever directory it prints as a global install #440 were closed by their PRs before this run. I spot-checked Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495 and Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 here (see the cells below).

Cells (Linux, all pass unless noted)

• Repo berry e2e suites (redirect, vendor, pnpm linker, workspaces, PnP safety) on 4.18.1 and 4.0.2: all 90 tests pass each.
• New hosted pin form (Fix yarn berry hosted pin leaking npm auth (#404) #465: root resolutions name@npm:<range> → URL, plus the lock re-keyed name@<url>):
  • Basic, workspaces with a merged ^1.3.0 + 1.3.0 entry, and a transitive dep (ms via debug): the fresh --immutable --check-cache gets patched bytes, the re-scan is idempotent, and rollback is byte-exact.
  • Range spellings: latest, >=1.3.0 <2, ^1.0.0 || ^1.3.0, 1.x, *, npm:left-pad@^1.3.0, npm:^1.3.0. Each passes fresh immutable, and rollback is byte-exact.
  • Scoped (@isaacs/string-locale-compare), with an @ inside the URL key: pass.
  • Two versions (root ^1.3.0 patched, member 1.2.0 not): only 1.3.0 is moved.
  • Hardened mode (YARN_ENABLE_HARDENED_MODE=1) × node-modules / pnp / pnpm linkers × 4.0.2 / 4.12.0 / 4.18.1, lock-only workspace checkout with a direct and a transitive pin: all 9 cells install patched bytes.
  • package.json tab, 4-space, CRLF, BOM, no trailing newline, and an existing resolutions for another package: rollback is byte-exact. Compact one-line JSON and an empty "resolutions": {} aren't restored byte-exactly, but yarn's own next install writes exactly what rollback produces, so I didn't file them (see Known non-bugs).
  • CRLF lock + CRLF package.json + enableImmutableInstalls: true: pass.
  • Scoped rollback <purl> and remove <purl> with two hosted pins: the other pin stays wired, and its fresh install is still patched. (Backlog 2b, hosted GC: pass.)
  • Takeovers: hosted → vendored (scan --mode vendored) and vendored → hosted both rewrite resolutions correctly, the fresh install is patched, and rollback is byte-exact.
  • Mixed project (ms vendored + left-pad hosted, both in resolutions): rollback of the hosted pin keeps the vendored wiring, and vendor --revert keeps the hosted pin.
  • Legacy ::__archiveUrl= pin written by release 4.0.0: main's re-scan migrates it to the new form (fresh immutable patched), and main's rollback of the legacy pin is byte-exact.
  • Refusals write nothing: yarn 3.8.7 (cacheKey 8), compressionLevel: 9 and mixed all give redirect_yarn_berry_cache_unsupported with package.json untouched. compressionLevel: "0" and 0 # default proceed and install patched (Yarn berry vendored and hosted modes refuse compressionLevel: 0 # comment in .yarnrc.yml as a non-default compression level #370 fix holds).
  • Standalone vex: a lock-only complete pin gives not_affected (redirected). A pin with its resolutions removed is refused as orphaned (exit 2). Unpatched node_modules beside the pin is omitted as not_applied (exit 1). No false attestations.
• Agent mode, pnpm linker, transitive ms only in .store (4.0.2 and 4.18.1): apply patches it, vex gives not_affected, and rollback is byte-exact (Yarn 4 pnpm linker: transitive packages that live only in node_modules/.store are "not installed" in agent mode and stay unpatched #495 fixed).
• Agent nmMode: hardlinks-global after Fix agent apply writing into shared package stores (#332, #361) #486: only this project's hardlink is broken, and the other project and store stay pristine.
• Interrupted vendor (SIGKILL at 1–19 ms, 10 trials): package.json and yarn.lock are never half-written. A re-run always completes, and the fresh immutable install is patched. In the kill-after-download state (ledger + tgz, no wiring), vex refuses (nothing to attest) and vendor --revert removes the orphan (vendor_orphan_removed). rollback and repair exit 1 with manifest_not_found there. That's loud, and the recovery is a re-run, so I didn't file it.

Filed

• None. The new hosted pin held up in every cell above.

Ruled out

• Compact package.json and an empty resolutions table aren't byte-exact after a hosted rollback: yarn normalizes both the same way on install.
• redirect_yarn_berry_ambiguous_entry now exits 0 (the earlier ledger said exit 1). It's consistent with every other hosted per-package refusal, and still loud and closed.

Next

1. Probes for macOS/Windows (the new resolutions pin on Windows CRLF, Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539, remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559) once a maintainer deletes the two stale bughunt/yarn-berry/* branches.
2. Re-triage Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 and remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559 when fix PRs appear.
3. Hosted upgrade A→B (uuid change) under the new pin with real yarn, plus a hosted pin followed by yarn up / yarn dedupe / yarn add of another package.
4. Hosted catalog: rollback byte-exactness under the new form, and --cwd into a nested project.
5. Global (-g) on macOS/Windows, and a version-manager prefix (nvm/volta).

[github-actions[bot]]

[agent] 2026-10-03: Yarn Berry (2+) bug-hunt run

Tested: main 045d7ec (the CLI still reports 4.0.0). It has 7 commits since 203e092, and none touch the Berry redirect or vendor code; #587 changes the zip verifier used for jar/nupkg. I also tested release 4.0.0 from npm for the regression check. Yarn 4.12.0 and 4.18.1 come from @yarnpkg/cli-dist, on Node 22 and Linux. No probe branches: git push origin --delete still fails with send-pack: unexpected disconnect, and the two stale bughunt/yarn-berry/* branches remain.

Harness: this run rebuilt the hosted mock as a single Python server driven by a JSON config. It serves batch (filtered by components[].purl), by-package, patches/package (it returns the uuids that appear in the body), both view routes, /upstream/npm/<uuid>.json, the tarball route, and a /registry/ passthrough to npmjs for SOCKET_NPM_REGISTRY. A hidden / publishedAt flag per patch makes A→B upgrades possible. Run pkill -f mock.py only from a separate shell, because it kills the calling shell.

Re-triage

• Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 and remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559 are still open with no merged fix. Share rollback artifact retention across remove and rollback #600 (the fix for remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559) is open and unmerged. I didn't re-run them: main has no relevant change since run 9, where both reproduced.
• New pm:yarn-berry issues not filed by this routine: Hosted yarn berry rewrites a mixed-line-ending package.json that vendored mode refuses #628 (hosted rewrites a mixed-EOL package.json) and Share the yarn berry project gates between hosted and vendored modes #629 (refactor), both from the arch audit. I didn't touch them. Hosted yarn berry rewrites a mixed-line-ending package.json that vendored mode refuses #628 is now known, so don't re-file it.

Cells (Linux)

• Hosted upgrade A→B (uuid change, resolutions pin, 4.18.1): the re-scan re-pins both resolutions and the lock to B. In-place and fresh --immutable --check-cache both install B, and rollback is byte-exact to the pre-hosted files. pass
• Hosted pin, then yarn add is-number, yarn dedupe, yarn up left-pad: the pin survives every one and the bytes stay patched. pass
• Hosted pin, then a descriptor change (yarn add left-pad@1.3.0): yarn drops the pin and installs unpatched. vex attests nothing (manifest_not_found), and the re-scan replaces the stale left-pad@npm:^1.3.0 selector with left-pad@npm:1.3.0, after which the install is patched. pass. rollback in the stale state (before any re-scan) refuses loudly ("cannot be attributed to one package version … re-run scan --mode hosted"), which is fail-closed and gives a remedy, so I didn't file it.
• Hosted catalog: (4.12.0, 4.18.1; root, workspace members, named catalog:legacy): fail, filed Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632. The resolutions selector left-pad@npm:^1.3.0 doesn't match a catalog: descriptor, so every --immutable install fails YN0028 and a mutable install is silently unpatched. Release 4.0.0 passes the same cell. First bad commit: 203e092 (Fix yarn berry hosted pin leaking npm auth (#404) #465). Rollback is byte-exact, including .yarnrc.yml.
• Vendored catalog: (4.18.1): pass, because vendored pins by bare name. The vendored→hosted takeover of that project reverts the working vendored pin, then hits Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632 (commented there).
• Hosted --cwd into a nested, separate berry project: only the inner files change, the inner fresh install is patched, and rollback is byte-exact with the outer project untouched. pass

Filed / commented

• Filed Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632: Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632
• Commented Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632 (vendored→hosted takeover amplifier): Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632 (comment)

Ruled out

• The stale-selector rollback refusal after a user changes the descriptor is loud, fail-closed and comes with a remedy.

Next

1. Once Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632 is fixed: re-verify catalog:, named catalogs, workspace-member-only catalog deps, and the vendored→hosted takeover.
2. Other manifest-vs-lock descriptor mismatches the resolutions matcher could miss: peerDependencies with a dev copy, packageExtensions-added deps, dependenciesMeta, and a descriptor written v1.3.0 / =1.3.0.
3. Probes (macOS/Windows, CRLF resolutions pin, Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539, remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559, Hosted yarn berry pin of a catalog: dependency keys resolutions by the resolved npm: range, so every yarn install --immutable fails YN0028 (regression from #465) #632) once a maintainer deletes the two stale branches.
4. Re-triage Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 and remove <purl> garbage-collects the beforeHash blobs of every other patch still in the manifest, so a later offline rollback of those patches fails missing_blob #559 when Share rollback artifact retention across remove and rollback #600 or a Vendored yarn berry PnP refusal keys only on .pnp.cjs: a lock-only PnP checkout vendors successfully, then every re-run in an installed checkout fails exit 1 with vendor_yarn_berry_unsupported #539 fix lands.
5. Private npmRegistryServer + npmAlwaysAuth under the new pin, and global (-g) on macOS/Windows.

[github-actions[bot]]

[agent] 2026-10-08: Yarn Berry (2+) bug-hunt run

Tested: main cf8b164 (CLI 4.0.0; latest release 4.0.0, previous 3.3.0). Since run 32 (e2d9633) main adds #1039 (staged, atomic vendored→hosted takeover; the berry takeover pre-gates are deleted), #1117 (BOM strips via formats::text) and non-npm changes. Yarn 4.18.1 (still latest) and 4.0.2 from @yarnpkg/cli-dist, Node 22, Linux.

Probes: none. Deleting the stale branches bughunt/yarn-berry/20260930-builtin-patch-takeover and bughunt/yarn-berry/20261001-global-script was again denied by the session permission policy; they still need deleting by hand.

Re-triage

• Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100: still fails on cf8b164 (nodeLinker: "${L:-pnp}", live PnP install, apply exit 0 package_not_installed). Nothing new, no comment.
• Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 and the other open berry issues: no commit since run 32 touches their code paths; not re-run.

Cells (Linux, cf8b164), focus #1039

Cell	Result
Takeover dry run, one purl retracted (no yarnBerry10c0)	pass (tree byte-identical, would_revert + kept_vendored)
Takeover wet, partial retraction (either package), LF and CRLF	pass (refused purl stays vendored byte for byte; other pinned; CRLF kept; fresh --immutable plain + hardened patched)
Takeover, all retracted	pass (byte-identical)
Workspaces (member ^1.3.0 + 1.3.0), partial retraction	pass (both selectors pinned, fresh immutable)
get <uuid> --mode hosted over a vendored package (kept / migrated)	pass
compressionLevel: mixed after vendoring	pass (both kept vendored, nothing written)
PnP switch after vendoring	pass (pins + yarn_pnp_unsupported; PnP fresh + hardened loads patched)
Alias lp: npm:left-pad@1.3.0 added after vendoring	documented redirect_yarn_berry_alias_skipped
Write fault (chattr +i yarn.lock / package.json / .socket/vendor/state.json), with and without a takeover	pass (exit 1, "nothing was changed", tree identical)
Rollback after a partial takeover (hosted + vendored mix), 4.18.1 CRLF and 4.0.2	pass (4.0.2 byte-exact with bare hex; .socket/vendor removed)
vex / scan --vex over a partial takeover	pass
pnpmStoreFolder: ../shared shared by two projects, agent apply	patches the other project's copy too; documented (relocated berry store not containing the project is patched as usual), not filed

Filed / commented / closed

None. No new bug met the filing bar.

Ruled out

• A workspace takeover "YN0028" was the harness: the fresh-checkout copy lacked packages/.
• A CRLF "left-pad not vendored" was the mock serving no yarn-berry-zip artifact at vendor time (vendored needs it).
• The repo's mode_migration_npm berry takeover test can't run in the sandbox (its in-process reqwest to registry.npmjs.org fails TLS through the proxy).

Next

1. Make the vendored-to-hosted takeover atomic #1039 neighbours: SIGKILL during the journaled takeover commit, pnpm linker, catalog: dep retraction, a retraction caused by a user resolutions entry added after vendoring.
2. Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 neighbours (scoped ./ bin, pnpm linker), then re-verify when fixed.
3. Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100 / Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 interpolation neighbours (npmScopes with ${}).
4. Re-verify Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859, Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759, Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737, Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082 when fixes land.
5. Probes on macOS/Windows once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-09: Yarn Berry (2+) bug-hunt run

Tested: main 03b9418 (CLI 4.0.0; latest release 4.0.0, previous 3.3.0). Since run 33 (cf8b164), main adds #1058 (hosted "already pinned" now decided by lockfile discovery only, plus the new redirect_unattributable attribution gate), #1147 (vendored revert of a removed dependency), #1085, #1030, #1031 (removes scan --apply/--vendor and get --no-apply), #1027 (--json errors are {code, message}) and the rollback/hosted_unwind refactor. Yarn 4.18.1 (still the latest) and 4.0.2 from @yarnpkg/cli-dist, Node 22, Linux.

Probes: none. Deleting the stale branches bughunt/yarn-berry/20260930-builtin-patch-takeover and bughunt/yarn-berry/20261001-global-script failed again (send-pack: unexpected disconnect). They still need deleting by hand.

Re-triage

• Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131: still fails on 03b9418 (uuid@9.0.1: rollback restores uuid: ./dist/bin/uuid, and a hardened fresh --immutable hits YN0028). No comment.
• Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082: unchanged (re-scan prints the redirect_yarn_berry_ambiguous_entry "dedupe" remedy, nothing written). No comment.
• Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100: no berry gate change since run 33 (only the BOM helper). Not re-run.

Cells (Linux, 03b9418, 4.18.1 unless noted)

Cell	Result
#1058 hosted pin + re-scan (already counted, nothing rewritten) + fresh plain/hardened --immutable + rollback byte-exact: workspaces (merged ^1.3.0/1.3.0 + scoped member dep), catalog: default + named, transitive + npm: alias of another version, pnpm linker	pass
Leftover package-lock.json / pnpm-lock.yaml beside the berry lock: pin, re-scan already, rollback byte-exact (.npmrc removed)	pass
Legacy release-4.0.0 __archiveUrl pins (root, workspaces, transitive) re-scanned by main: migrated to the resolutions pin, fresh hardened patched; rollback byte-exact both before and after the migration	pass
Vendored, then yarn remove one package: vendor --check names it (exit 1), scan --vendored --prune, vendor --revert, rollback, remove <uuid> retire it, --immutable passes	pass
Hosted, then yarn remove (4.0.2, 4.18.1) or yarn up to an unpatched version	fail #1203 (leftover resolutions selector → rollback/list/remove exit 1 forever with hosted_wiring_contested; the remedy scan is a no-op; release 4.0.0 not affected)

Filed / commented / closed

• Filed After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203 (After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203) and commented with the yarn up variant.

Ruled out

• A lo-npm "classic migration risk" warning plus a non-byte-exact rollback came from the harness: npm install --package-lock-only rewrites an existing yarn.lock as classic v1. With the berry lock restored, the cell passes.
• npm_manifest_unavailable ("hosted tarball does not match its published sha512") for uuid came from the mock: packages with bin need the real sha512 of the patched tgz in the tarball artifact.

Next

1. After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203 neighbours: removal from a workspace member while another member keeps the dep, a catalog: dep removed, yarn remove of a scoped package; re-verify when fixed (rollback, remove, list, --prune).
2. Decide whether a hosted patch is pinned through lockfile discovery alone #1058 gate (redirect_unattributable) on berry shapes: portal:/link: lp2 copies (Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939), member-level registry copies, takeover + gate.
3. Make the vendored-to-hosted takeover atomic #1039 neighbours (SIGKILL during the takeover commit, pnpm linker, catalog: retraction).
4. Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 neighbours (scoped ./ bin, pnpm linker); Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100/Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 interpolation neighbours.
5. Probes on macOS/Windows once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-09: Yarn Berry (2+) bug-hunt run

Tested: main f3c6313 (CLI 4.0.0; latest release 4.0.0, previous 3.3.0). Since run 34 (03b9418), main adds #1008 (the npm open-issue batch, including the npm-family vendor backends refactored onto one generic driver (#920/#922; yarn_berry_lock.rs now runs through vendor_npm_family), "keep an older vendored patch only while its wiring is still live", and the #898/#1005 failed-commit reporting) plus #1191 BOM helpers. Yarn 4.18.1 (still the latest) and 4.0.2 from @yarnpkg/cli-dist, Node 22, Linux.

Probes: none (the stale probe branches still need deleting by hand; see the backlog).

Re-triage

• Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737 (nan, implicit node-gyp: "npm:latest"): still fails on f3c6313. Vendored fresh --immutable hits YN0028. No comment.
• Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783 (parent-scoped pkg-a/left-pad resolution): still fails. Vendored adds a bare left-pad pin, and fresh --immutable hits YN0028. No comment.

Cells (Linux, f3c6313)

Cell	Result
Repo berry e2e suites (vendor, redirect, workspaces, pnpm linker, PnP safety) on 4.18.1 (187/187) and 4.0.2 (147/147)	pass
Refactored vendored driver, two packages: node-modules (--revert), pnpm linker (rollback), 4.0.2 (remove <uuid> ×2), workspaces, catalog: default + named. Fresh cold --immutable is patched, vendor --check passes, and the unwind is byte-exact	pass
Write fault (chattr +i) on yarn.lock / package.json during vendor: exit 1, both failed vendor_commit_failed, nothing written, no artifacts or ledger left (#898/#1005)	pass
Write fault on yarn.lock during vendor --revert / rollback / remove: exit 1, wiring intact, --check passes, retry is byte-exact	pass
Vendored generation A→B (manifest swap, vendor): vendor_stale_artifact_removed, fresh install loads B, --revert byte-exact (4.18.1, 4.0.2)	pass
Hosted→vendored takeover via vendor, then vendor --revert lands on the pristine registry lock (4.18.1, 4.0.2 bare hex)	pass
#1039 neighbours: vendored→hosted takeover with one purl retracted (redirect_yarn_berry_missing_checksum → redirect_takeover_kept_vendored) on the pnpm linker and on catalog: deps. Fresh install patched, rollback pristine	pass
SIGKILL during the vendored→hosted takeover commit, then rollback	fail #1241: killed after the journal is durable but before any file is replaced, the next rollback replays the journal and exits 0 having restored nothing (hosted pins left). remove says "No patch found". 4.18.1 and 4.0.2. Kills elsewhere in the window recover correctly; a second rollback restores the project

Filed / commented / closed

• Filed After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 (After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241). It's cross-PM CLI ordering: rollback.rs/remove.rs discover hosted pins before acquire_or_emit replays the journal.

Ruled out

• An early SIGKILL loop "showed" rollback misbehaving, but kill -9 $! on a shell function only kills the wrapper subshell; the binary kept running. Exec the binary directly.
• A kill before the journal is renamed into place (only .socket-stage-.commit-journal.json-* exists) isn't a bug: nothing was committed, and rollback unwinds the vendored state byte-exact. The stray stage file stays untracked under .socket/vendor/. It's benign, so not filed.
• Orphaned .socket/vendor/npm/<uuid>/ dirs after a journal replay are A vendored-to-hosted takeover interrupted after its commit journal is written leaves the vendored artifact directory behind for good: recovery finishes the files but not the deferred deletions, and no GC can reclaim it once the ledger is gone #1157 (pnpm), not re-filed.

Next

1. Re-verify After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 when fixed (rollback and remove after a replayed takeover journal; 4.0.2 and 4.18.1), and check list/repair in the same state.
2. After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203 neighbours (member-level removal, catalog:, scoped); Decide whether a hosted patch is pinned through lockfile discovery alone #1058 redirect_unattributable gate on portal:/link: copies.
3. Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 neighbours (scoped ./ bin, pnpm linker); Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100/Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 interpolation neighbours.
4. Vendored-driver refactor follow-ups: repair of a deleted tgz, vendor --dry-run parity, CRLF lock + package.json through the new driver.
5. Probes on macOS/Windows once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-09: Yarn Berry (2+) bug-hunt run

Tested: main a80b89e (CLI 4.0.0; latest release 4.0.0, previous 3.3.0). Since run 35 (f3c6313), main adds #1007 (15 pnpm fixes, including the shared npm-family upstream restore and the agent scan PATH copy scoping, #778), #1041 (org resolved once per run), #1227 (line_endings::terminator in vendored writers; berry's block_eol fallback now uses the majority rule), plus non-npm fixes. I used yarn 4.18.1 from @yarnpkg/cli-dist, Node 22, on Linux.

Probes: none. Deleting the stale probe branches was denied again by the session permission policy, so they still need deleting by hand.

Re-triage

• After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203: still fails (after yarn remove, rollback exits 1 with hosted_wiring_contested and the hosted re-scan is a no-op). list now exits 0 with "No patches". No comment.
• Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131: still fails (uuid bin: ./dist/bin/uuid is kept, so hardened --immutable hits YN0028). No comment.
• After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241: closed by a maintainer at 07:50 with no fix commit (the only reference is the run-35 ledger commit). It still fails on a80b89e and is now deterministic. Commented: After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 (comment)

Cells (Linux, a80b89e, 4.18.1)

Cell	Result
Agent scan --mode agent packages/a in a berry workspace: pnpm linker (member link) / node-modules (hoisted to the root)	pass / out of scope by contract
nmMode: hardlinks-local + nmHoistingLimits: workspaces: apply patches all 3 copies; rollback packages/a restores all 3 with out_of_scope_copies_restored; unscoped rollback	pass
Vendored driver: scan --mode vendored --dry-run writes nothing; repair redownloads a deleted tgz (--check 1 → 0); CRLF yarn.lock; fresh cold --immutable (plain and hardened) is patched; --revert / rollback byte-exact	pass
Vendored→hosted takeover SIGKILLed at the package.json / yarn.lock rename (LD_PRELOAD shim), then rollback	fail #1241: exit 0 with nothing restored, or exit 1 hosted_wiring_contested; hosted-pinned either way. remove <uuid> reports "No patch found"
Hosted→vendored takeover SIGKILLed at the package.json / yarn.lock / state.json rename, then rollback	fail (#1241 root cause, commented): either a false Cannot restore … no hosted wiring exit 1 after the replay, or a pre-lock refusal (orphaned resolutions; "vendor ledger is missing, restore state.json from version control", a file that was never committed) that never replays the journal
First vendoring SIGKILLed at the yarn.lock / state.json rename, then rollback	fail: pre-lock "ledger missing" refusal, and the journal stays pending (commented on #809: #809 (comment))
Plain hosted scan SIGKILLed between the package.json and yarn.lock renames	half-pinned. No journal by design; rollback refuses with a working remedy and a re-scan heals it (not filed)

Filed / commented / closed

• No new issues. Commented on After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 (still open in substance, both takeover directions) and on vendor --check and vex misreport a crashed vendored run whose commit journal is pending, because only lock-taking commands replay it #809 (rollback doesn't replay either).

Ruled out

• Hoisted member deps under agent scan PATH: out of scope by contract.
• A crash in a non-takeover hosted commit: journal-less by design.
• .socket-stage-* litter after a SIGKILL: already noted on vendor --check and vex misreport a crashed vendored run whose commit journal is pending, because only lock-taking commands replay it #809.

Next

1. Re-verify After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 (both takeover directions, plus the first-vendoring rollback) when a fix lands, using the rename shim. Also try vendor --revert and repair from each kill point.
2. Shim-driven kills during unwinds: vendor --revert, rollback and remove killed mid-commit on berry, then re-run.
3. After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203 neighbours (member-level removal, catalog:, scoped); Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 neighbours (scoped ./ bin, pnpm linker).
4. Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100/Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 interpolation neighbours; 4.0.2 legs of this run's cells.
5. macOS/Windows probes once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-09: Yarn Berry (2+) bug-hunt run

Tested: main 9ab72d4 (CLI 5.0.0; chore(release): 5.0.0 has merged, but npm still has 4.0.0 as the latest published release). Since run 36 (a80b89e), main adds #1180 (yarn npm: alias copies no longer count as pinned; #1081/#1158), #1034 (one target grammar for get/remove/rollback), #989 (vendored reverts finish through one shared step), #1277 (BOM handling), #1262 (VEX writes through the stage + rename writer) and the 5.0.0 release. I used yarn 2.4.2, 3.8.7, 4.0.2 and 4.18.1 from @yarnpkg/cli-dist, Node 22, on Linux. Note: main was force-pushed, so the clone is shallow; run git fetch --deepen=400 to reach older SHAs.

Probes: none (the stale probe branches still need deleting by hand).

Re-triage

• Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783 (vendored with a parent-scoped pkg-a/left-pad resolution): still fails YN0028 on 4.18.1. No comment.
• Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737 (vendored nan, implicit node-gyp: npm:latest): still fails YN0028. No comment.
• Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 (YARN_NPM_REGISTRY_SERVER mirror, then rollback): still drops ::__archiveUrl=. No comment.
• Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082 point 2 has regressed: rollback/remove exit 0 again and fresh --immutable fails YN0028, on 4.0.2 and 4.18.1. Bisected to f3c6313a (Fix open npm issues #1008; parent b17a114a is good, and run 31's ea09714 refused). The npm: alias variant and the vendored alias variant fail the same way. Commented: Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082 (comment)

Cells (Linux, 9ab72d4)

Cell	Result
Hosted + vendored basic (left-pad + ms), 4.0.2 and 4.18.1: pin, fresh --immutable patched, rollback byte-exact	pass
#1180 on berry: hosted pin, then yarn add lp@npm:left-pad@1.3.0; scan --mode hosted --vex, standalone vex	pass (alias copy warned, nothing attested)
#1180: alias at another version (lp/@x/lp → npm:left-pad@1.1.3) beside a pinned ^1.3.0	pass (in-run VEX attests; fresh patched)
Vendored → hosted takeover with an alias added after vendoring	pass (alias warned, no retraction needed: the alias block was never vendored)
#1034 target grammar, hosted and vendored rollback/remove: name, upper-case name, versionless purl, versioned purl, uuid (also upper-case), @scope/name, is beside @sindresorhus/is (full name wins, by design)	pass. name@version, CVE and GHSA select nothing (documented)
get <name> / get <uuid> / get pkg:npm/x@v → hosted pin	pass. A versionless purl is sent to the API verbatim; the mock has no versionless route, so this is unverified
#989 vendored unwinds: vendor --revert, rollback, remove <name>, rollback <name>, remove <uuid> with two vendored packages	pass (the others are kept; fresh --immutable correct)
SIGKILL (rename shim) during vendored vendor --revert/rollback/remove at the package.json / 2nd yarn.lock / state.json renames, then re-run	pass (re-run completes; pristine and byte-exact). Stage-file litter only (#809)
SIGKILL during hosted rollback/remove between the package.json and yarn.lock renames	half-unwound: the re-run refuses patched_ref_invalid (orphaned lock pin), and the printed "re-run the hosted scan" remedy is a no-op. yarn install heals it. Known journal-less residual (not filed)
BOM'd .yarnrc.yml (nodeLinker: pnp, LF/CRLF) lock-only vendored	pass (refused as PnP)
BOM'd .yarnrc.yml with nodeLinker: node-modules, lock-only vendored + revert	pass
BOM'd project-rc npmRegistryServer (non-conventional mirror), hosted rollback	pass (byte-exact ::__archiveUrl=)
Path-scoped rollback packages/a (hosted and vendored) on workspaces: pnpm linker / node-modules (hoisted)	pass / path_glob_no_match exit 1 (contract: hoisted copy is not under the path)
Yarn 3.8.7 and 2.4.2: hosted/vendored refusal (nothing written), agent apply + rollback	pass
Hosted pin, then a member left-pad@1.3.0 or an alias lp: npm:left-pad@1.3.0, then rollback / remove left-pad	fail (#1082 regression, commented)
Vendored, then lp: npm:left-pad@1.3.0, then vendor --revert / rollback / remove left-pad	fail (same unmerged-block cause; on #1082, #759 class)

Filed / commented / closed

• No new issues. Commented on Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082 (regression bisected to f3c6313a).

Ruled out

• The rollback hint "use ./left-pad@1.3.0" for name@version: the grammar has no name@version (documented).
• rollback is choosing is over @sindresorhus/is: the full name beats a last-segment match by design (utils/target.rs).
• Hoisted member deps under rollback packages/a: out of scope by contract (the wording "patches for uninstalled packages" is a bit misleading).
• An upper-case UUID passed to get reaches the API unchanged; my mock is case-sensitive, so this isn't confirmed against the real API (cross-PM if real).

Next

1. Re-verify Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082 when a fix lands: plain member, root/member alias, remove, vendored alias revert; 4.0.2 and 4.18.1. Other npm hosted pin next to a bundled copy can't be unwound: rollback/remove refuse it, and the vendored takeover skips the restore, so vendor --revert lands back on hosted and allow-remote=all stays #828 shadowed shapes on berry: a file:/portal: sibling block (Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939), plus the hosted→vendored takeover over a shadowed berry pin.
2. Kill hosted rollback mid-commit with three or more pins (the lock written first?), and a hosted→vendored takeover killed mid-unwind.
3. After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203 neighbours (member-level removal, catalog:, scoped); Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131 neighbours.
4. Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100/Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 interpolation neighbours.
5. macOS/Windows probes once the stale branches are deleted.

[github-actions[bot]]

[agent] Janitor: ledger drift. These issues are now closed but this ledger still lists them as fail or open: #737 (completed 2026-10-09), #1131 (completed 2026-10-09), #1203 (completed 2026-10-10). Please re-verify them on current main and update the matrix.

---

Generated by Claude Code

[github-actions[bot]]

[agent] Janitor: ledger drift. These issues are now closed but this ledger still lists them as fail or open: #1082 (completed 2026-10-11 by #1397 1fb8901a). Please re-verify them on current main and update the matrix.

---

Generated by Claude Code

[github-actions[bot]]

[agent] 2026-10-12: Yarn Berry (2+) bug-hunt run

Tested: main 1779317 (CLI 5.0.0; npm still has 4.0.0 as the latest published release, which I also used for comparison). Since run 37 (9ab72d4), main adds the berry fixes #1319 (#737), #1321 (#1203), #1322 (#1131), #1323 (#1017) and #1397 (#1082). Yarn 4.0.2 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux, node-modules linker. The harness was rebuilt from scratch: a Python mock of the org patch API that now also needs the real tarball sha512 on the tarball artifact (hosted verifies it), /upstream/npm/<uuid>.json, a /registry/ passthrough and a non-conventional /mirror/ route.

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759: both symptoms still fail (4.0.2 → 4.18.1 upgrade restores bare hex; a member descriptor added after vendoring is dropped by revert). Commented: Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 (comment)
• Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783 (parent-scoped pkg-a/left-pad resolution, vendored): still fails YN0028 on 4.18.1. No new information, so no comment.

Cells (Linux, 1779317)

Cell	Result
#737 hosted nan@2.22.0 pin (22 → 2 lock entries), fresh plain + hardened, 4.0.2 and 4.18.1	pass
#737 hosted rollback of nan	documented degradation: yarn_berry_node_gyp_unresolved; the node-gyp subtree isn't restored; plain --immutable passes, hardened YN0028 until yarn install
#737 vendored nan + vendor --revert (byte-exact), 4.0.2 and 4.18.1	pass
#737 prune neighbours: nan + bufferutil, nan + direct node-gyp: latest (hosted + vendored, byte-exact)	pass
nan + direct node-gyp: ^11 (two node-gyp versions), hosted rollback	the documented yarn_berry_node_gyp_unresolved again; vendored byte-exact
#1082 hosted: member left-pad@1.3.0, root alias, member alias added after pinning × rollback / remove left-pad × 4.0.2 / 4.18.1 (12 cells)	pass
#1082 vendored alias added after vendoring × vendor --revert / rollback	pass
Vendored member descriptor added after vendoring × vendor --revert / rollback	fail (#759, commented)
#1131 uuid@8.3.2 hosted pin + rollback byte-exact, hardened fresh, 4.0.2 / 4.18.1	pass
#1203 yarn remove left-pad / yarn up left-pad@1.2.0 after a hosted pin; list / rollback / partial remove left-pad keeps ms	pass (hosted_resolution_orphaned)
#1203 neighbour: yarn remove in one workspace member while another keeps the package, then rollback / remove / scan --prune + remove	fail #1435 (new): exit 0, the restored key brings back the dead left-pad@npm:1.3.0 descriptor, YN0028; 4.0.2 and 4.18.1; release 4.0.0 not affected
#1017 non-conventional mirror from YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml, project rc; rollback byte-exact (::__archiveUrl= kept), cold fresh install	pass (the npmScopes variant is untested this run)

Filed / commented / closed

• Filed Hosted yarn berry rollback/remove put back a descriptor that yarn remove deleted from one workspace member, so every yarn install --immutable fails YN0028 #1435: Hosted yarn berry rollback/remove put back a descriptor that yarn remove deleted from one workspace member, so every yarn install --immutable fails YN0028 #1435
• Commented on Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759.
• Nothing closed: Yarn berry vendored and hosted pins of native-addon packages (nan, bufferutil, utf-8-validate, node-addon-api) keep the registry entry's implicit node-gyp: "npm:latest" dependency, so vendored installs and hardened hosted installs fail YN0028 #737, Yarn berry hosted pin can't cover a descriptor added after pinning: re-scan refuses with an impossible "dedupe" remedy, and rollback reports success but leaves a lock every yarn install --immutable rejects (YN0028) #1082, Hosted yarn berry rollback/remove keep the pin's tarball-form bin: paths (./dist/bin/uuid) on the restored npm: entry, so hardened yarn install --immutable fails YN0028 for packages like uuid and prettier #1131, After yarn remove of a hosted-pinned yarn berry package, its leftover resolutions pin makes rollback, remove and list fail forever with hosted_wiring_contested, and the remedy they print (re-run the hosted scan) changes nothing #1203 and Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 were already closed by their fixes, and the cells above confirm them.

Ruled out

• Hosted nan rollback leaving the node-gyp subtree out of the lock: documented in CLI_CONTRACT (yarn_berry_node_gyp_unresolved).
• A hosted scan skipping nan with npm_manifest_unavailable ("hosted tarball does not match its published sha512"): a harness artifact (the mock served a placeholder sha512).

Next

1. Re-verify Hosted yarn berry rollback/remove put back a descriptor that yarn remove deleted from one workspace member, so every yarn install --immutable fails YN0028 #1435 when fixed: plain member removal, yarn up in one member, catalog: member; 4.0.2 and 4.18.1; also the vendored analogue (a member removes one of two vendored descriptors, then vendor --revert).
2. Hosted yarn berry rollback/remove still drops a mirror's ::__archiveUrl= binding when the registry comes from npmScopes, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml or a parent-dir .yarnrc.yml (#908 fix covers only the project rc's top-level key) #1017 npmScopes scoped-target variant (needs a scoped patch in the mock) and the hosted→vendored takeover revert on a mirror.
3. Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 / Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783 re-verify when fixed. Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100 has a draft PR (Fix yarnrc ${VAR} and YAML setting reads (#1100) #1433): re-verify the ${L:-pnp} / ${CL:-0} rows once merged.
4. After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 takeover journal replay; Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 re-verify.
5. macOS/Windows probes once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-13: Yarn Berry (2+) bug-hunt run

Tested: main 15c2c83 (CLI 5.0.0; npm still has 4.0.0 as the latest published release, used for the legacy-pin cell). Since run 38 (1779317), main adds #1436 (#1435), #1433 (#1100), #1440 (#1437) and #1444 (#1220). Yarn 4.0.2 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux, node-modules linker. The harness was rebuilt (bin/y, h/mkpatch.sh NAME VER UUID → pk/<uuid>/{patched.tgz,meta.json}, h/mock.py <pk> 8790 with a new /meta/ route: an npmjs metadata passthrough that 404s every /-/ tarball path, h/lib.sh, h/case.sh).

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Hosted yarn berry rollback/remove put back a descriptor that yarn remove deleted from one workspace member, so every yarn install --immutable fails YN0028 #1435 (closed by Fix berry restore keeping removed descriptors (#1435) #1436): verified fixed. A member yarn remove then hosted rollback / remove left-pad gives a fresh --immutable pass on 4.0.2 and 4.18.1.
• Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100 (closed by Fix yarnrc ${VAR} and YAML setting reads (#1100) #1433): verified fixed. 20 rc/env shapes (${L:-pnp}, ${L-pnp}, ${L} with L=pnp, quoted key, next-line value, flow mapping, !!str, anchor, block scalar, duplicate key, %YAML directive, CRLF, YARN_NODE_LINKER / lower-case env) all match yarn config get nodeLinker in the PnP decision.

Cells (Linux, 15c2c83)

Cell	Result
#1437: vendored ms + hosted left-pad pin, bare scan / bare get <uuid>	pass (exit 2 mode_ambiguous, nothing written)
#1437: vendored (v5) + release-4.0.0 legacy __archiveUrl hosted pin, bare scan	pass (mode_ambiguous)
#1220: 9 hosted pins (incl. scoped) hosted scan, fresh plain + hardened, rollback byte-exact, also under ulimit -n 20	pass
#1435 vendored analogue: member yarn remove after vendoring, then vendor --revert / rollback / remove left-pad, 4.0.2 and 4.18.1	fail: the removed descriptor is restored, YN0028 (#759 root cause; commented)
#1017 npmScopes scoped target (@sindresorhus/is), with a mirror whose packument keeps npmjs tarball URLs	fail #1465 (new)
Top-level npmRegistryServer mirror serving npmjs tarball URLs × rollback/remove × 4.0.2/4.18.1	fail #1465: ::__archiveUrl= dropped, cold --immutable YN0035 404 (8/8 cells)
nodeLinker: PnP (wrong case)	not PnP to yarn either; applies, consistent

Filed / commented / closed

• Filed Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465: Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465
• Commented on Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 (third symptom, removal): Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 (comment)
• Nothing closed: Hosted yarn berry rollback/remove put back a descriptor that yarn remove deleted from one workspace member, so every yarn install --immutable fails YN0028 #1435 and Yarn berry PnP refusal misses a live Plug'n'Play project whose .yarnrc.yml sets nodeLinker through ${VAR} interpolation: agent apply exits 0 "not installed" and lock-only vendor passes the PnP gate (regression from #978) #1100 were already closed by their fixes.

Ruled out

• The bare npm: locator after a Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 rollback passes plain --immutable and --refresh-lockfile when the mirror also serves /-/ tarballs. Only a mirror without /-/ tarballs breaks (the cold fetch).
• The compressionLevel gate expands ${…} against no environment by design (berry_gates.rs). The lock cacheKey gate covers env-set levels.

Next

1. Re-verify Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 when fixed (top-level, npmScopes, env, home rc; rollback/remove; 4.0.2/4.18.1). Also the vendored hosted→vendored takeover vendor --revert behind the same mirror.
2. Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 re-verify (three symptoms: 4.0→4.1 upgrade, added member descriptor, removed member descriptor).
3. Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 re-verify.
4. After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 takeover journal replay re-check.
5. macOS/Windows probes once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-13: Yarn Berry (2+) bug-hunt run

Tested: main 285a5e8 (CLI 5.0.0; npm still has 4.0.0). Since run 39 (15c2c83), main adds the berry fixes #1464 (#759) and #1466 (#1465), plus #1480 (#1097, the per-manager workspaces glob dialects) and #1470 (#1266). Yarn 4.0.2, 4.1.0 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux, node-modules linker.

Harness (new this run): no Python mock. A corepack shim (corepack yarn@X runs node <cli-dist X>/bin/yarn.js and sets YARN_HTTPS_CA_FILE_PATH + YARN_HTTPS_PROXY; never set YARN_HTTP_PROXY, because it sends the e2e wiremock's http://127.0.0.1 traffic through the proxy, which answers 403). Vendored cells go through a scratch test zz_bh.rs, a bridge that runs the CLI through prebuilt_common::prepare_command, so the prebuilt fixture server stands in for the vendoring service. BH_STAGE hand-stages the manifest and blob from the installed copy. Hosted cells use a scratch copy of e2e_redirect_yarn_berry_build.rs with an extra test that reuses berry_hosted_project's wiremock. Both scratch files were deleted afterwards.

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783 (vendored, parent-scoped pkg-a/left-pad user resolution): still fails on 285a5e8 (4.18.1; vendored adds left-pad: file:… beside it, and fresh --immutable gives YN0028). Nothing new, so no comment.
• Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 (closed by Fix mirror archiveUrl dropped on berry restore (#1465) #1466): verified fixed. The repo e2e berry_hosted_rollback_keeps_archive_url_behind_passthrough_mirror passes on 4.0.2 and 4.18.1, for both rollback and remove left-pad (a local variant).
• Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 (closed by Fix vendored berry revert restoring stale lock (#759) #1464): verified fixed. The repo e2e issue_759_* (3 tests) pass on 4.0.2 and 4.18.1, as do the neighbour cells below.

Cells (Linux, 285a5e8)

Cell	Result
#759 neighbours: a member adds 1.3.0, alias lp: npm:left-pad@^1.3.0, 1.3.x, ~1.3, >=1.x, >= 1.0.0 < 2, devDependencies ^1.0.0, or a transitive file: package depending on left-pad@^1.0.0, all while vendored; then vendor --revert, fresh --immutable (4.18.1; 4.0.2 for add/alias/x/dev/transitive)	pass
Same with rollback and remove left-pad (4.0.2, 4.18.1)	pass
CRLF yarn.lock + member add + revert (4.0.2, 4.18.1)	pass (CRLF kept)
4.0.2 → 4.18.1 upgrade + member add, then vendor --revert / rollback	pass
Member adds latest, 1.3.0 - 2 (partial hyphen) or 1.1.3 (unsatisfied) while vendored	loud vendor_lock_descriptor_unlocked event, exit 0; fresh --immutable YN0028 until yarn install (designed)
#1097 berry dialect: 23 workspaces shapes, yarn workspaces list vs get <uuid> --mode hosted from the member (4.0.2, 4.18.1)	fail #1490 (new): packages/(a|b), packages/pkg-(a|b), [[:alpha:]], [[:digit:]]x and packages/a/../b are listed by yarn but not refused (exit 0, nothing pinned). Pass: *, **, ./, trailing /, @(a|b), !(z), ?(x), [a-c], [!b], [^b], **/b, ! negation. !packages/(b|c) gives a false refusal (loud, noted on #1490). packages/.hidden is refused although yarn skips dot dirs (loud, not filed)

Filed / commented / closed

• Filed Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490: Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490
• No comments; nothing closed (Vendored yarn berry revert restores the pre-vendor lock entry verbatim, so after upgrading from yarn 4.0.x it writes back a bare-hex checksum and every yarn install --immutable fails YN0028 #759 and Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 were already closed by their fixes).

Ruled out

• vendor_lock_descriptor_unlocked for latest and for a partial hyphen range (1.3.0 - 2) is the documented fail-loud path ("or its range could not be read"). Not filed.
• A CRLF package.json coming back as LF after vendoring: yarn's own install rewrites it to LF (known non-bug); the revert is byte-exact to the post-install bytes.
• The Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 e2e failing with "403 /meta/left-pad" was my shim's YARN_HTTP_PROXY, a sandbox artifact.

Next

1. Re-verify Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490 when fixed (the 5 failing shapes on 4.0.2 and 4.18.1, plus the scan path with a member-owned copy).
2. Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 neighbours not covered by the repo e2e: npmScopes scoped target, YARN_NPM_REGISTRY_SERVER, ~/.yarnrc.yml (they need a non-hermetic harness), and the hosted→vendored takeover vendor --revert behind a mirror.
3. Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 re-verify.
4. After a vendored-to-hosted takeover is interrupted once its commit journal is written, the next rollback replays the journal, then exits 0 having restored nothing, and the project stays hosted-patched (remove says "No patch found") #1241 takeover journal replay re-check.
5. macOS/Windows probes once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-14: handover from the Yarn classic (1.x) bug-hunt (ledger #304)

While testing #1489 for yarn classic I filed #1516: renamed-copy detection fails open when it can't read the copy's identity. That happens for a file: path outside the project root, a file: tarball whose top directory isn't package/, or a non-registry URL. Scans then report success and VEX attests not_affected while the copy installs unpatched.

The berry side shares the reader in crates/socket-patch-core/src/formats/yarn/copy.rs and is untested here:

• berry_copy_path → normalize_rel(&workspace, path) returns None for a file: / portal: / link: path that leaves the root (e.g. "lp2": "portal:../shared/left-pad"), so berry_copy_ref gives up.
• A berry file: tarball is read through the same tarball_manifest_name (lenient decoder, only a literal package/ root).
• A non-registry URL (CopyRef::Url) returns None identity.

Suggested cells: berry 3 / 4, "lp2": "portal:../ext/lpdir", "lp2": "file:../ext/lp.tgz", and "lp2": "file:./lp.tgz" with a left-pad-1.3.0/ root. Check H/V scan warnings, in-run and lock-only VEX, and the installed copy.

[github-actions[bot]]

[agent] 2026-10-14: Yarn Berry (2+) bug-hunt run

Tested: main 23fa8d4 (release 5.0.1), plus PR #1517 head 6289505. Since run 40 (285a5e8), main adds #1493 (fixes #1490) and #1489 (fixes #939 / #1236 renamed yarn copies). Yarn 4.0.2 and 4.18.1 from @yarnpkg/cli-dist, Node 22, Linux, node-modules linker.

Harness: a scratch copy of e2e_redirect_yarn_berry_build.rs with env hooks (BH_DEPS, BH_PKG_EXTRA, BH_PRE, BH_CWD) on berry_hosted_project. The scratch file was deleted afterwards.

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859, Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783: no commit since run 40 touches them, so I didn't re-run them.
• Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490 (closed by Fix berry workspace globs with regex groups (#1490) #1493): verified fixed. Details are in the cells below.
• Yarn berry hosted and vendored scans miss a file:/URL copy of the patched package locked under another dependency name, so lockfile VEX (and vendored VEX after install) attests not_affected while that copy installs unpatched #939 (closed by Fix scans missing renamed yarn copies (#939, #1236) #1489): the in-root controls pass (see the cells below).

Cells (Linux)

Cell	main 23fa8d4	PR #1517 6289505
Handover from yarn-classic: renamed lp2 (left-pad@1.3.0) as portal:../ext/lpdir (outside the root); 4.0.2, 4.18.1 ×2	fail #1516: hosted scan exit 0, no copy warning; in-run and lock-only VEX attest not_affected; node_modules/lp2 unpatched	pass (redirect_copy_unpatched, vex_omitted, scan exit 1, vex exit 2)
file:../ext/lp.tgz (4.0.2, 4.18.1)	fail #1516	pass
file:../ext/lpdir (4.18.1)	fail #1516	pass
file:./lp.tgz with a left-pad-1.3.0/ root (4.0.2, 4.18.1 ×2)	fail #1516	pass
Controls: in-root file:./lpdir, and file:./lp.tgz with a package/ root (#939)	pass (warns)	pass
#1490: get <uuid> --mode hosted from member packages/a under packages/(a|b), packages/[[:alpha:]], packages/b/../a, packages/* (4.0.2, 4.18.1)	pass: every shape is refused redirect_workspace_lockfile_elsewhere (exit 1, nothing pinned), the same as the * control	n/a

Filed / commented / closed

• Commented on Yarn classic renamed-copy detection (#1489) misses a file: copy outside the project root and a tarball whose root isn't package/, so scans succeed and VEX attests while that copy installs unpatched #1516 with the Berry evidence and the PR Fix yarn renamed-copy identity fail-open (#1516) #1517 results: Yarn classic renamed-copy detection (#1489) misses a file: copy outside the project root and a tarball whose root isn't package/, so scans succeed and VEX attests while that copy installs unpatched #1516 (comment). I didn't file a new issue, because the root cause is the same shared reader (formats/yarn/copy.rs berry_copy_path / tarball_manifest_name) and an open fix PR covers it.
• Nothing closed.

Ruled out

• Yarn 4 rejects YARN_CA_FILE_PATH (caFilePath is legacy), which is a shim artifact.

Next

1. When Fix yarn renamed-copy identity fail-open (#1516) #1517 merges, re-verify the 4 Berry shapes on 4.0.2 and 4.18.1. Add vendored (vendor_copy_unpatched), link: outside the root, and a member-relative outside path.
2. Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490 neighbours: [[:upper:]], {1,} quantifiers, a nested worktree member.
3. Hosted yarn berry rollback/remove drop the ::__archiveUrl= binding when the project's mirror serves npmjs tarball URLs, so cold installs fetch a mirror path that 404s #1465 neighbour sources (npmScopes, env, home rc), which need a non-hermetic harness.
4. Re-verify Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 and Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 when fixes land.
5. macOS/Windows probes once the stale branches are deleted.

[github-actions[bot]]

[agent] 2026-10-14: Yarn Berry (2+) bug-hunt run

Tested: main a3f56f7 (release 5.0.1 is still the latest tag). Since run 41 (23fa8d4), main adds #1517 (313d532, fixes #1516) and a set of CI and non-npm fixes. I tested yarn 4.0.2 and 4.18.1 from @yarnpkg/cli-dist, on Node 22, Linux, with the node-modules linker.

Harness: a corepack shim (corepack yarn@X runs node <cli-dist X>/bin/yarn.js, setting YARN_HTTPS_CA_FILE_PATH and YARN_HTTPS_PROXY). The run-41 scratch copy of e2e_redirect_yarn_berry_build.rs came back with BH_DEPS, BH_PKG_EXTRA and BH_PRE, plus BH_SCRIPT: after the mocks are mounted, it runs a shell cell (MODE=hosted|vendored) instead of the built-in scan. I changed the mock's tarball artifact sha512 to the real value (computed with openssl), so vendored cells work too. Each cell runs scan with --vex, then lock-only vex in a fresh checkout, then yarn install --immutable, then checks the marker in node_modules/{left-pad,lp2}, then post-install vex. I deleted the scratch file afterwards.

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Yarn classic renamed-copy detection (#1489) misses a file: copy outside the project root and a tarball whose root isn't package/, so scans succeed and VEX attests while that copy installs unpatched #1516 (closed by Fix yarn renamed-copy identity fail-open (#1516) #1517): Berry shapes verified fixed (cells below).
• Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859, Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783: no commit since run 41 touches them, so I didn't re-run them.

Cells (Linux, main a3f56f7)

Cell	Result
lp2: portal:../ext/lpdir (outside root), hosted, 4.18.1	pass: redirect_copy_unpatched, vex_omitted, scan exit 1; lock-only and post-install vex exit 2 (#1516 fixed)
Member packages/a portal:../../../ext/lpdir and file:../../../ext/lp.tgz, hosted, 4.18.1	pass (same codes)
Vendored portal:../ext/lpdir and file:../ext/lp.tgz, 4.18.1	pass: vendor_copy_unpatched, vex_omitted; lock-only vex exit 1
Absolute file:/abs/ext/lpdir and file:/abs/ext/lp.tgz, hosted, 4.18.1	pass: fail-closed unidentified copy, redirect_copy_unpatched, vex exit 2
Relative portal through a symlinked dir (portal:../ext/lnk), hosted, 4.18.1	pass
Absolute portal:/abs/ext/lpdir: hosted 4.18.1 ×2, hosted 4.0.2, vendored 4.18.1	fail #1540: scan exit 0, no copy warning; in-run, lock-only and post-install VEX attest not_affected; node_modules/lp2 unpatched
Absolute link:/abs/ext/lpdir, hosted 4.18.1	fail #1540 (same)

Filed / commented / closed

• Filed Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540: Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540. An unread Linked copy is dropped (vendor/yarn_copies.rs:111, vex/discover/yarn.rs:878), and read_path never reads anchored paths (copy.rs:46).
• Nothing closed. Yarn classic renamed-copy detection (#1489) misses a file: copy outside the project root and a tarball whose root isn't package/, so scans succeed and VEX attests while that copy installs unpatched #1516 was already closed by its maintainer.

Ruled out

• The member-relative portal:../../ext "Manifest not found" was my path error: from packages/a, the shared directory is three levels up.

Next

1. Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540: when it's fixed, re-verify absolute portal: / link: (hosted and vendored, 4.0.2 and 4.18.1, all three VEX paths), plus link: from a workspace member, and a ~/env-interpolated path, if yarn expands one.
2. Other unread Linked copies: a portal directory whose package.json is unreadable (EACCES) or a symlink to outside the tree; a portal: path containing : or # (berry_copy_ref splits on both).
3. Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490 neighbours: [[:upper:]], {1,} quantifiers, a nested worktree member.
4. Re-verify Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 and Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 when fixes land.
5. macOS/Windows probes once the stale branches are deleted (Windows portal:C:\… belongs to the Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540 class).

[github-actions[bot]]

[agent] 2026-10-15: Yarn Berry (2+) bug-hunt run

Tested: main 7b6371c (release 5.0.1 is still the latest tag). Since run 42 (a3f56f7), main adds #1551 (75e49ae, fixes #1540), #1543 (nested npm projects, #1534), #1555 (vlt extglob members, which leaves the berry glob dialect unchanged), and CI-only test rewrites (#1089). I tested yarn 4.0.2 and 4.18.1 from @yarnpkg/cli-dist, on Node 22, Linux, with the node-modules linker.

Harness: a corepack shim (corepack yarn@X runs node <cli-dist X>/bin/yarn.js, setting YARN_HTTPS_CA_FILE_PATH and YARN_HTTPS_PROXY). I rebuilt the scratch copy of e2e_redirect_yarn_berry_build.rs (zz_bh.rs) with BH_DEPS, BH_PKG_EXTRA, BH_PRE and BH_SCRIPT (env API, ORG, TMPD, HOSTED, PROJ, CK, UUID), and the mock's tarball artifact carries the real sha512 (openssl dgst -sha512 -binary | base64). Mark every other test in the copy #[ignore]. I deleted the scratch file afterwards. Cells: cell.sh runs a hosted scan with --vex, then lock-only vex with the copy target absent and then present. cell2.sh runs a lock-only scan --mode hosted|vendored --vex with the target absent, then restores the target, runs a fresh yarn install --immutable, and checks for the marker in node_modules/{left-pad,lp2}.

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540 (closed by Fix yarn berry absolute portal:/link: copies (#1540) #1551): verified fixed. With absolute portal: on 4.0.2 and 4.18.1, the hosted scan warns redirect_copy_unpatched and exits 1, and lock-only vex exits 2 with the target absent and present.
• Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962, Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859: no commit since run 42 touches the berry vendored or redirect code, so I didn't re-run them.

Cells (Linux, main 7b6371c)

Cell	Result
#1540 absolute portal: (4.0.2, 4.18.1)	pass (fixed)
Relative portal:./vend/lp / link:./vend/lp, target present, hosted scan + lock-only vex (4.0.2, 4.18.1)	pass: redirect_copy_unpatched, vex exit 2
Relative portal:/link:, target ABSENT (submodule not checked out), lock-only vex (4.18.1 ×2, 4.0.2; link 4.18.1)	fail #1561: exit 0, attests not_affected
Same, lock-only scan --mode hosted --vex (portal 4.0.2 and 4.18.1, link 4.18.1)	fail #1561: exit 0 success, no copy warning, in-run VEX attests; after restoring the target, yarn install --immutable leaves node_modules/lp2 unpatched
Same, scan --mode vendored --vex (portal 4.18.1, link 4.0.2)	fail #1561 (same)
Control: file:./vend/lp with the target absent, hosted / vendored / vex (4.0.2, 4.18.1)	pass: fails closed (#1516 design)

Filed / commented / closed

• Filed Yarn berry drops a relative portal: / link: copy whose target directory is missing (e.g. an uninitialized git submodule), so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1561: Yarn berry drops a relative portal: / link: copy whose target directory is missing (e.g. an uninitialized git submodule), so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1561. The relative linked copy whose read fails hits the old continue (vex/discover/yarn.rs:894, vendor/yarn_copies.rs:113). Fix yarn berry absolute portal:/link: copies (#1540) #1551 widened fail-closed only to anchored paths.
• Nothing closed. Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540 was already closed by Fix yarn berry absolute portal:/link: copies (#1540) #1551.

Ruled out

• vex exit 2 with "Manifest not found … no hosted or vendored patch references were found" when the only pin is withheld by a copy is misleading wording (the lock does carry the pin, and the copy warning prints first). It's cosmetic, so I didn't file it.
• Fix vlt extglob workspace members (#1542) #1555 changes only the vlt dialects plus a dot field, and the npm/yarn dialects keep dot: true, so there's no berry glob regression to chase.

Next

1. Yarn berry drops a relative portal: / link: copy whose target directory is missing (e.g. an uninitialized git submodule), so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1561: when it's fixed, re-verify the missing relative portal:/link: (root and member-relative, hosted/vendored/vex, 4.0.2/4.18.1). Also check that a link: to an existing plain directory with no package.json is still ignored, and add neighbours: a dangling symlink target, a target that is a file and not a directory, and a package.json that is invalid JSON or has no version.
2. Root scan --mode vendored exits 1 forever and drops its in-run VEX when a nested independent npm project installs a patched package the root lock doesn't have (hosted mode only warns) #1534 / Fix vendored scans failing on nested npm projects (#1534) #1543 on berry: a nested independent berry project (own yarn.lock, not in workspaces) under a berry root, hosted and vendored (nested_project_skipped), plus a nested project that the root also links through portal:.
3. Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490 neighbours: [[:upper:]], {1,} quantifiers, a nested worktree member.
4. Re-verify Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 and Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 when fixes land.
5. macOS/Windows probes once the stale branches are deleted (Windows portal:C:\… belongs to the Yarn berry renamed-copy detection ignores a portal: / link: copy with an absolute path, so hosted and vendored scans succeed and every VEX path attests not_affected while that copy installs unpatched #1540 class).

[github-actions[bot]]

[agent] 2026-10-15: Yarn Berry (2+) bug-hunt run

Tested: main 2c82c77 (release 5.0.1 is still the latest tag). Since run 43 (7b6371c), main adds #1571 (2e71d5f, fixes #1561), #1559 (e76cb9b, vendored tarballs vs Git LFS, #1541), and non-berry fixes and CI test rewrites. I tested yarn 4.0.2 and 4.18.1 from @yarnpkg/cli-dist on Node 22, Linux, with the node-modules linker.

Harness (run 44, fully local, no Rust scratch test): bin/y (YV=<v> → node yd/<v>/package/bin/yarn.js, setting YARN_HTTPS_CA_FILE_PATH, YARN_HTTPS_PROXY and YARN_UNSAFE_HTTP_WHITELIST=127.0.0.1). h/mock.py <pk> 8790 is a Python patch API: batch, by-package, view, patches/package with a tarball artifact (real sha512) and a yarn-berry-zip artifact (10c0 bootstrapped with a real resolutions: file: install), the tarball route, and /upstream. pk/cfg.json holds uuid, purl, git-blob sha256 before/after, sha512 and ck. h/base.sh DIR portal|link|file YV does a real install of left-pad@1.3.0 plus lp2: <proto>:./vend/lp. h/cell.sh BASE OUT STATE makes a lock-only copy with the target in STATE (missing, empty, lfs, plain, gitkeep, nover, noname, file, dangling, present), then runs a hosted scan --vex and a lock-only vex. h/vcell.sh does the same in vendored mode. Build this in about 10 minutes; it's quicker than the Rust scratch test.

Probes: none. The stale probe branches still need deleting by hand.

Re-triage

• Yarn berry drops a relative portal: / link: copy whose target directory is missing (e.g. an uninitialized git submodule), so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1561 (closed by Fix yarn berry missing portal:/link: copies (#1561) #1571): verified fixed. On 4.18.1, a missing, empty, or LFS-pointer portal: target, a target that is a file, and a dangling symlink target each make the hosted scan warn redirect_copy_unpatched (exit 1), and lock-only vex exits 2. Missing still passes on 4.0.2. Vendored with a missing target warns vendor_copy_unpatched.
• Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783: still fails on 2c82c77 (vendored adds a bare left-pad pin beside pkg-a/left-pad, then fresh --immutable fails YN0028). No new information, so no comment.

Cells (Linux, main 2c82c77)

Cell	Result
#1561 shapes (missing, empty, LFS pointer, file, dangling symlink), portal: hosted + vex (4.18.1; missing also 4.0.2)	pass (fixed)
portal: target is a non-empty dir with no package.json (.gitkeep placeholder), hosted + vendored + vex (4.0.2, 4.18.1 ×2)	fail #1579: exit 0 success, VEX attests. yarn itself refuses a manifest-less portal (YN0001 "Manifest not found"), so a fetch step must fill it; after that, node_modules/lp2 is unpatched
portal:/link: target package.json without name or without version, hosted + vex (4.0.2, 4.18.1), vendored (4.18.1)	fail #1579: yarn installs it, and lp2 is unpatched left-pad code
Control: file:./vend/lp with a nameless or version-less package.json	pass (fails closed)
link: to a dir holding only .gitkeep or logo.svg	dropped, documented ("A link: to a non-empty directory with no package.json is not a package copy")
#1534/#1543: nested independent berry project tools/x (own yarn.lock, not in workspaces) under a berry root, hosted and vendored	pass: nested_project_skipped warning, root files byte-identical; the PATH remedy scan --mode <m> tools/x pins tools/x only, fresh --immutable installs patched bytes, vex --cwd tools/x attests, and root vex exits 2
#1541/#1559: vendored berry in a repo with *.tgz filter=lfs (git-lfs 3.4.1)	pass: the <uuid>/.gitattributes unsets filter, the committed blob is the real gzip, and a GIT_LFS_SKIP_SMUDGE=1 clone --immutable installs patched bytes
#783 parent-scoped pkg-a/left-pad (4.18.1)	fail #783 (still)

Filed / commented / closed

• Filed Yarn berry still drops a portal: copy whose target has no package.json (e.g. a .gitkeep placeholder) or whose package.json lacks name/version, so scans succeed and VEX attests not_affected while that copy installs unpatched #1579: Yarn berry still drops a portal: copy whose target has no package.json (e.g. a .gitkeep placeholder) or whose package.json lacks name/version, so scans succeed and VEX attests not_affected while that copy installs unpatched #1579. The cause is linked_copy_unknown (vendor/yarn_copies.rs:143-163): its plain-dir exemption also applies to portal:, and manifest_parsed short-circuits. CopyRef::identity (formats/yarn/copy.rs:73) needs both name and version.
• Nothing closed (Yarn berry drops a relative portal: / link: copy whose target directory is missing (e.g. an uninitialized git submodule), so hosted and vendored scans succeed and VEX attests not_affected while that copy installs unpatched #1561 was already closed by Fix yarn berry missing portal:/link: copies (#1561) #1571).

Ruled out

• link: to plain assets (non-empty dir, no manifest) is documented and yarn installs it as a plain link, so it isn't filed.
• A root-scan exit 1 with manifest_not_found when --vex has nothing to attest (everything skipped to a nested project) is the documented "nothing to attest" exit.

Next

1. Yarn berry still drops a portal: copy whose target has no package.json (e.g. a .gitkeep placeholder) or whose package.json lacks name/version, so scans succeed and VEX attests not_affected while that copy installs unpatched #1579: re-verify when fixed (.gitkeep portal, nameless and version-less manifests; portal:/link:; hosted, vendored, vex; 4.0.2/4.18.1). Check that a link: to plain assets stays ignored.
2. A nested independent berry project that the root also reaches through portal:./tools/x (root lock lists the dep, tools/x has its own install): which copy node resolves, and whether VEX should hold back.
3. Hosted get/scan from a yarn berry workspace member still pins nothing and exits 0 when the root's workspaces glob uses a regex group (packages/(a|b)), a POSIX class ([[:alpha:]]) or a .. segment #1490 neighbours: [[:upper:]], {1,} quantifiers, a nested worktree member.
4. Re-verify Vendored yarn berry misses a parent-scoped user resolutions entry (pkg-a/left-pad), reports success, and every yarn install --immutable fails YN0028 #783, Yarn berry hosted rollback/remove report success after a user yarn patch of the pinned package, but leave a lock that every yarn install --immutable rejects (YN0028); the next install re-pins the Socket tarball #962 and Agent mode misses transitive packages in Yarn's pnpm-linker store when pnpmStoreFolder moves it out of node_modules: skipped as package_not_installed, or refused as "first-party source" #859 when fixes land.
5. macOS/Windows probes once the stale branches are deleted.