pnpm run rescope-vendor:check fails on a clean checkout of master

[amittell]

pnpm run hygiene fails on a fresh clone of master because two of the EXACT_EDITS in scripts/rescope-vendor.ts anchor to text that no longer exists in the repository. Both anchors were removed by unrelated commits that did not update the edit list, and no CI mode runs this gate, so nothing caught it.

Reproduction

Fresh worktree at master (b150a551b8), fresh pnpm install --frozen-lockfile, Node 24, pnpm 11.7.0:

$ pnpm run rescope-vendor:check
rescope-vendor: exact edit knip-logger-console: knip.json is neither pending nor cleanly applied (duplicated, partial, or moved)
rescope-vendor: exact edit vendoring-cookbook-name-invariant-zh: docs/cookbook/adding-a-vendored-package.zh.md is neither pending nor cleanly applied (duplicated, partial, or moved)
rescope-vendor: 2 problem(s); nothing was written.

pnpm run hygiene fails on the same gate (FAILED vendor rescope). Nothing else in the gate is wrong — pnpm run check:ci:static is 37/37 green on the same tree, which is consistent with this gate being outside CI.

Cause

knip-logger-console anchors to an ignoreDependencies block immediately followed by the "packages/util/home" key:

      "ignoreDependencies": [
        "@cordisjs/plugin-logger-console",
        "@deepseek-ai/.+"
      ]
    },
    "packages/util/home": {

50c22ee472 ("chore(knip): drop stale and glob-duplicate workspace entries") removed the packages/util/home entry from knip.json. @cordisjs/plugin-logger-console no longer appears anywhere in knip.json either, so the edit has nothing left to do — the vendored package is already rescoped to @deepseek-ai/cordis-plugin-logger-console and is covered by the @deepseek-ai/.+ pattern beside it. That commit did not touch scripts/rescope-vendor.ts.

vendoring-cookbook-name-invariant-zh expects its replacement text to link ../rescope.md:

replace: '改写 `name` 的 scope（[映射](../rescope.md)），保留上游的 `version`/`exports`/`type`',

8d3674695b ("docs(i18n): localize Chinese internal links") changed the applied text in docs/cookbook/adding-a-vendored-package.zh.md to link ../rescope.zh.md, which is what the pairing contract's link-locale rule requires. The edit is substantively applied; only its replace string is stale. That commit also did not touch scripts/rescope-vendor.ts.

In both cases exactEditState sees neither find nor replace, so it reports invalid rather than pending or applied.

Why it went unnoticed

rescope-vendor:check is reachable only through hygieneLeafGates() in scripts/run-gates.ts, which is included by the hygiene and check-all modes. Neither is a CI mode — ci-static, ci-primary, and the rest never call it. So the gate runs only when a contributor invokes pnpm run hygiene locally, and both anchors could rot without any signal.

That orchestration gap may be the more interesting half of this report: a gate that no CI mode executes will drift silently, and this one is load-bearing for the vendoring workflow.

Fix

Retiring the obsolete knip-logger-console edit and pointing the zh cookbook edit at ../rescope.zh.md restores the gate:

rescope-vendor: check over 4671 tracked files
rescope-vendor: post-state verified — no residue, every exact edit landed, idempotent.

Happy to share the diff if it's useful, though I understand from CONTRIBUTING.md that external pull requests aren't being accepted right now — so this is a report rather than a patch offer. Either way, adding the gate to a CI mode would stop the next anchor from rotting.

Environment: macOS 15 (arm64), Node 24.18.0, pnpm 11.7.0, master at b150a551b8.

[PerryLink]

This is fixed on current master. I re-ran the gate to confirm rather than inferring it from the anchor text.

Verified at master ddefc45fbc (tag dsh-v0.1.6-alpha.2):

$ pnpm run rescope-vendor:check
$ tsx scripts/rescope-vendor.ts --check
rescope-vendor: check over 7303 tracked files
rescope-vendor: post-state verified — no residue, every exact edit landed, idempotent.
# exit 0

Both anchors you reported are gone:

• knip-logger-console: the edit no longer exists in scripts/rescope-vendor.ts (zero occurrences), and knip.json itself is no longer in the repository. The whole Knip toolchain was removed in 907c6334c1 ("Remove Knip from repository tooling").
• vendoring-cookbook-name-invariant-zh: the replace string now links ../rescope.zh.md instead of ../rescope.md — scripts/rescope-vendor.ts:297-301, with replace on line 300. That is the change your report called for, and it now matches docs/cookbook/adding-a-vendored-package.zh.md verbatim.

Version boundary. You tested b150a551b8 (the dsh-0.1.1-rc.2 release merge). The realignment landed in c365daa53c — "chore(rescope): realign two manifest anchors, allowlist the preset-id spec" — and the first tag containing it is dsh-v0.1.2-alpha.1. So the failure is real on your revision and the fix is not in it. That commit is in dsh-v0.1.2-alpha.1 and in every later tag, so that is the revision range to re-run on; re-running there should reproduce the output above.

Your second point still stands, and it is the part worth fixing separately: rescope-vendor:check comes in through hygieneLeafGates() (scripts/run-gates.ts:698, with the gate itself registered at line 701). That helper is used by case 'hygiene' (line 284) and by check-all (line 276), but by none of the twelve ci-* modes, which are enumerated at lines 136-147 and dispatched at lines 234-276. So no CI mode runs this gate, and a stale anchor cannot be caught by CI — exactly the gap that let both anchors rot after the commits that removed their target text. Adding an ci-* leg that includes hygieneLeafGates() would close it.

If this answers it, marking it as the answer would help the next person who finds the same stale-anchor output.