fix(redirect): fail closed on non-npm: berry descriptors + yarn layering regression suite

rewrite_yarn_berry matched lock blocks by descriptor NAME only, so a
hosted redirect of a package that yarn berry builtin-patches (fsevents,
resolve, typescript) spliced an `npm:` resolution + checksum under the
`patch:`-protocol key — a corrupted key/resolution pairing in exactly
the 2026-07 strapi incident's error family, emitted with no warning.
Now non-`npm:` descriptor ranges (patch:/workspace:/portal:/link:) are
skipped byte-identically with a redirect_yarn_berry_unsupported_protocol
warning, mirroring the vendor backend's fail-closed gate
(vendor/yarn_berry_lock.rs).

New vendor::yarn_layering_tests (in-crate #[cfg(test)] module, since the
core-dedups cleanup privatized the vendor wiring internals it plumbs;
inventory_npm_lock widened to pub(crate) for the same reason) pins the
incident's flows on a strapi-shaped yarn v1 fixture (multi-version
ansi-regex + fsevents + resolve) and a yarn-4 berry fixture with real
builtin patch: entries — 9 tests, each RED-verified:
- vendored wiring is byte-surgical: untouched sibling/builtin-target
  blocks byte-identical, zero `patch:` strings introduced, file still
  parseable by the crate's own inventory
- integrity chain: #sha1 fragment, sha512 SRI, and ledger sha256/size
  all recomputed from the on-disk vendored tarball
- hosted redirect layered over vendored wiring records the vendored
  block as `original` (reversible), is byte-surgical, and re-runs are
  no-ops
- vendor revert after a hosted overlay: drift-skipped and lossy
  (deletes the blob dir, lockfile stays hosted) — pinned as current
  behavior
- berry builtin patch: entries survive vendored wiring AND hosted
  redirect byte-identically; redirecting the builtin-patched package
  itself now skips its patch: entry with the new warning

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: mikolalysenko

crates/socket-patch-core/src/patch/redirect/mod.rs

@@ -987,6 +987,26 @@ fn rewrite_yarn_berry(
             if !version_re.is_match(block) {
                 continue;
             }
+            // Descriptor ranges carry a protocol; only an `npm:` range names
+            // a registry tarball this rewriter can own. A `patch:` range
+            // (yarn's OWN builtin compat patches — the 2026-07 strapi
+            // incident family), `workspace:`, `portal:`, or `link:` block
+            // must survive byte-identically: splicing an npm resolution
+            // under such a key corrupts the key/resolution protocol pairing.
+            // Mirrors the vendor backend's fail-closed gate
+            // (vendor/yarn_berry_lock.rs).
+            if !parsed.iter().all(|p| p.unwrap().1.starts_with("npm:")) {
+                result.warnings.push(RewriteWarning {
+                    code: "redirect_yarn_berry_unsupported_protocol".into(),
+                    detail: format!(
+                        "lock entry `{raw_key}` resolves {fname}@{} through a protocol \
+                         the hosted redirect cannot own (workspace:/patch:/portal:/link:); \
+                         leaving it byte-identical",
+                        dep.version
+                    ),
+                });
+                continue;
+            }
             // Rewrite the resolution wholesale from name+version — handles a
             // pre-existing `::__archiveUrl=` (custom-registry lock) for free.
             let resolution = format!(

crates/socket-patch-core/src/patch/vendor/lock_inventory.rs

@@ -98,7 +98,9 @@ impl LockfileEntry {
 /// Inventory the project's npm-family lockfile. Routes by
 /// [`detect_npm_lock_flavor`] (PnP markers, bun.lockb, unsupported lock
 /// versions, and a missing lockfile all yield `None`).
-async fn inventory_npm_lock(project_root: &Path) -> Option<(NpmLockFlavor, Vec<LockfileEntry>)> {
+pub(crate) async fn inventory_npm_lock(
+    project_root: &Path,
+) -> Option<(NpmLockFlavor, Vec<LockfileEntry>)> {
     // Rush monorepos have no root package.json/lock pair; their single
     // pnpm source-of-truth lives under common/config/rush/. The flavor
     // probe (root-relative) can't see it, so fall back explicitly when the

crates/socket-patch-core/src/patch/vendor/mod.rs

@@ -75,6 +75,8 @@ mod toml_surgery;
 pub(crate) mod verify;
 pub(crate) mod yarn_berry_lock;
 mod yarn_classic_lock;
+#[cfg(test)]
+mod yarn_layering_tests;
 
 pub use path::{ecosystem_dir_for_purl, parse_vendor_path};
 pub use state::{load_state, lookup_entry, save_state, VendorEntry, VendorState, VENDOR_STATE_REL};