You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merged corridor: one package for 0.1.3-alpha.1 → 0.1.5-rc.1. This package supersedes
the two version-locked npm names dsh-plugin-upgrade (leg A, 0.1.3-alpha.1 → 0.1.5-alpha.1, seams S1–S10 + M1) and dsh-plugin-upgrade-rc1 (leg B, 0.1.5-alpha.1 → 0.1.5-rc.1, seams C1, C2, C4, C5, H1–H4, P1). The npm name
is new, so the version line restarts at 0.1.0; the two retired names stay on the registry
and their content is now historical.
One 20-seam catalog — lib/scan.mjs carries both legs in catalog order (S3, S8, S9, M1, S4, S5, S6, S7, S2, S1, S10, C1, C2, P1, C4, C5, H1, H2, H4, H3) behind one CLI, one skill and one id-parity gate.
Seam C3 was folded into M1. Leg B's C3 was the same defect as leg A's M1 (a
local gate compiling a stale type line), so the merged catalog has one seam carrying both
causes: an unresolvable tsconfigpaths alias and dev/test types pinned at 0.1.5-alpha.*. C3 is no longer a seam id — --seams C3 matches nothing, types.d.ts
does not accept it, and the merged card records the old spelling only in its fold notes.
Merged card with two labelled legs — skills/plugin-upgrade-015/references/v0.1.3-alpha.1-to-v0.1.5-rc.1.md: a preamble (the
span, why it ends at rc.1, how to read it), §1 Leg A and §2 Leg B each carrying the
retired card's full text, evidence and path:line citations, and §3 the merged 20-seam
index.
Leg-routing skill body — the skill is now plugin-upgrade-015 (renamed directory,
frontmatter, Config default and bundle row). Its body routes the caller to the leg that
matches the peer band, and both legs' original frontmatter routing hints are preserved in
the body.
Fixtures for both legs — leg A's TypeScript/session-oriented pair is vendored as fixtures/leg-a-bad-repo / fixtures/leg-a-good-repo; the client-slot pair stays at fixtures/bad-repo / fixtures/good-repo. Each leg therefore has a bad fixture that trips
its error-severity seams and a good fixture that stays clean.
Changed
The scanner CLI is now dsh-plugin-upgrade-015-scan (scripts/scan-0.1.5.mjs, plus the
skill-local skills/plugin-upgrade-015/scripts/scan-0.1.5.mjs); the cordis row is dsh-plugin-upgrade-015.
The dev/test pin and the monthly compat probe move to the published 0.1.5-rc.2 line (the
newest published types verify the same seam catalog), while dshWorkshop.compatibility.dshVersions
lists 0.1.2-rc.1 and 0.1.5-rc.2. The peer band still keeps both segments
(>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0) — P1 forbids collapsing it.
Rename the four translated READMEs to README-<lang>.md. npm selects the package-page readme as the first markdown file matching its {README,README.*} glob (@npmcli/package-json, publish path), and that glob order puts README.<lang>.md ahead of README.md — so npm was serving the Simplified-Chinese file for this package too (measured on 15/15 sampled packages of the family). The new names sit outside the glob, so the English source is served again. No content changed apart from the language-switcher link each translation holds to its siblings, and the repo readme gate still passes. Takes effect with the next release; an already-published version cannot gain a corrected readme retroactively.