dsh-plugin-upgrade 0.1.3 → 2.0.0

package/AGENTS.md

@@ -1,37 +1,95 @@
 # AGENTS.md
 
-Standalone DeepSeek Harness plugin repository (`dsh-plugin-upgrade`). Development follows
-the dsh-plugin-guide skill and the official plugin contract; this file records repo-local
-decisions. Read `README.md` (external contract) and the packaged version card
-(`skills/plugin-upgrade-015/references/v0.1.3-alpha.1-to-v0.1.5-alpha.1.md`) before
-changing behavior.
+Standalone DeepSeek Harness plugin repository (`dsh-plugin-upgrade`). Development
+follows the dsh-plugin-guide skill and the official plugin contract; this file records
+repo-local decisions. Read `README.md` (external contract) and the packaged merged corridor
+card (`skills/plugin-upgrade/references/v0.1.3-alpha.1-to-v0.1.5-rc.1.md`) before changing
+behavior.
+
+## A corridor never widens (and one package may carry several closed corridors)
+
+- **A corridor never widens.** This package upgrades plugins across `0.1.3-alpha.1 →
+  0.1.5-rc.1` and nothing else. Do not widen the peer band or the card to "all versions":
+  a drifting card is worse than no card. A hop that adds a seam is a new package.
+- **One package may carry several *closed* corridors.** That is what this repository is: one
+  npm package holding leg A (`0.1.3-alpha.1 → 0.1.5-alpha.1`) and leg B (`0.1.5-alpha.1 →
+  0.1.5-rc.1`) as **two closed corridors of one span**, each keeping its own evidence, card
+  section, fixtures and rollback path. Neither leg may absorb a third hop.
+- **This supersedes the family's earlier rule.** The retired `dsh-plugin-upgrade` and
+  `dsh-plugin-upgrade-rc1` each carried a "**The corridor is locked** … a new corridor is a
+  new package" section plus "**zero code dependency on the sibling corridor**: no `import`,
+  no vendoring, no shared `SEAMS`". The owner deliberately superseded the second half of that
+  pair: the merged package **does** share one `SEAMS` (one scanner, one catalog, one
+  id-parity gate) because the two legs are contiguous hops of one span. What survives
+  unchanged is the numbering discipline — a corridor is *closed*, not open-ended — and the
+  per-leg ownership below.
+
+Consequences accepted by this repository:
+
+- The merged catalog (20 seams: `S3`, `S8`, `S9`, `M1`, `S4`, `S5`, `S6`, `S7`, `S2`, `S1`,
+  `S10`, `C1`, `C2`, `P1`, `C4`, `C5`, `H1`, `H2`, `H4`, `H3`) is evidence-bound to the two
+  tag ranges it was measured on — leg A `dsh-v0.1.5-alpha.1` (2026-09-09 wave over 40 plugin
+  repos) and leg B `dsh-v0.1.5-alpha.1..dsh-v0.1.5-rc.1` (2026-09-10). A hop after
+  `0.1.5-rc.1` (rc.2, the final release, anything later) is a **new package**, not a wider
+  card. The harness hop `0.1.5-rc.1 → 0.1.5-rc.2` added no plugin-facing seam, which is why
+  the span ends at rc.1 while the dev/test pin and the CI probe run on `0.1.5-rc.2`.
+- **Leg A owns the session-format seams** (`assistant/message.stream`, `S3`;
+  `SessionHandleReadResult`, `S8`; `EpochHeader.system`, `S2`; `ctx.agent`, `S5`; `Inbox`,
+  `S6`; `SystemPrompt.persona`, `S9`; the V3 log generation, `S1`) and **leg B does not
+  restate them** — measured: the whole `packages/core/session/src` diff inside leg B's range
+  is two added event-type literals and one comment line. Each leg's card section keeps its own
+  scope statement; restating across legs is drift.
+- **`C3` is retired.** Leg B's card spelled the stale-type-line false green `C3`; it is the
+  same defect as leg A's `M1` and is folded into it, so `M1` carries both causes (an
+  unresolvable `tsconfig` `paths` alias and dev/test types pinned at `0.1.5-alpha.*`). The
+  card records the old spelling in the fold notes, but `C3` is not a seam id: `--seams C3`
+  matches nothing and `types.d.ts` does not accept it.
+- The peer band is **unchanged** by both legs. `>=0.1.2-rc.1 <0.2.0` alone rejects
+  `0.1.5-rc.1` under npm semver's prerelease-tuple rule (measured `false` on semver 7.8.5);
+  the `|| >=0.1.5-alpha.1 <0.2.0` segment is what admits it. `P1` forbids dropping it, and
+  this package's own `peerDependencies` keeps both segments.
+- The `C1` ruling (the bare `conversation` slot removal is a **public extension-point
+  break**, kept at `error`, with a rewrite recipe and a real-browser exit criterion) is
+  recorded in card §2 §3.3. Do not downgrade it to an advisory without new upstream
+  evidence (an alias, a shim, or an official migration note).
 
 ## Layout (JS form, pure host, no browser half)
 
 ```
 index.mjs             single host face: Config schema + skill bundle reader + apply()
-types.d.ts            Config, SeamHit, ScanReport and the public function surface
-lib/scan.mjs          zero-dependency seam catalog + scanner + CLI main()
+types.d.ts            Config, SeamId, SeamHit, ScanReport and the public function surface
+lib/scan.mjs          zero-dependency merged seam catalog (both legs) + scanner + CLI main()
 scripts/scan-0.1.5.mjs   thin bin wrapper (npx dsh-plugin-upgrade-scan)
-skills/plugin-upgrade-015/scripts/scan-0.1.5.mjs  the same wrapper inside the skill directory,
-                      so the skill body's `./scripts/...` resolves against its resourceBase
+skills/plugin-upgrade/scripts/scan-0.1.5.mjs  the same wrapper inside the skill
+                      directory, so the skill body's `./scripts/...` resolves against its
+                      resourceBase
 scripts/sweep-all.mjs    maintainer tool: sweep a workspace of plugin repos into a table
 scripts/changelog-section.mjs  print one CHANGELOG section for GitHub Release notes
 scripts/verify-self-contained.mjs  every import resolves inside the package
-scripts/verify-artifacts.mjs       pack + inspect the published tarball
+scripts/verify-artifacts.mjs       pack + inspect the published tarball (also asserts that
+                                   test/, fixtures/ and .github/ do NOT ship, and that a
+                                   leg-A seam fails the packaged CLI)
 scripts/check-readme-sync.mjs      five-language README consistency
-skills/plugin-upgrade-015/SKILL.md  the bundled skill body (frontmatter name is the skill id)
-skills/plugin-upgrade-015/references/…  the version card
-test/scan.test.mjs    synthetic bad/good fixtures + a live negative on an adapted repo
-test/plugin.test.mjs  real Cordis Context + real SkillRegistry: register, dispose, negative
-fixtures/             scanner fixtures (bad-repo, good-repo)
-cordis.patch.yml      bundle declaration (insert dsh-plugin-upgrade); every Config key inline
+skills/plugin-upgrade/SKILL.md  the bundled skill body (frontmatter name is the skill id;
+                                    it routes the caller to the leg matching its peer band)
+skills/plugin-upgrade/references/v0.1.3-alpha.1-to-v0.1.5-rc.1.md  the merged card:
+                                    §1 Leg A, §2 Leg B, §3 the 20-seam index
+test/scan.test.mjs    synthetic bad/good fixtures for BOTH legs + --seams + a live negative
+test/plugin.test.mjs  real Cordis Context + real SkillRegistry: register, dispose, negatives
+test/card.test.mjs    the card↔catalog id/severity parity gate
+fixtures/             scanner fixtures — never published:
+                        bad-repo / good-repo            leg B (client-slot oriented)
+                        leg-a-bad-repo / leg-a-good-repo  leg A (TypeScript/session oriented)
+docs/EVIDENCE.md      the command→output record every card claim traces to
+                      (§A = leg A's provenance, §1–§10 = leg B's records)
+cordis.patch.yml      bundle declaration (insert dsh-plugin-upgrade); every
+                      Config key inline
 pnpm-workspace.yaml   nearest-workspace root (isolates this repo from a surrounding harness checkout)
 package.json          npm metadata; files whitelist = published content
-.github/workflows/    CI (3 OS × 2 Node), monthly compat probe, v* npm release,
-                      plugin-doctor static R/K gate, OpenSSF Scorecard
+.github/workflows/    CI (3 OS × 2 Node), monthly compat probe, v* npm release + GitHub
+                      Release, plugin-doctor static R/K gate, OpenSSF Scorecard
 README.md             English primary (GitHub default page; source of truth)
-README.{zh,es,pt,hi}.md  translations, top switcher, updated in the same commit
+README-{zh,es,pt,hi}.md  translations, top switcher, updated in the same commit
 CHANGELOG.md          Keep a Changelog, [Unreleased] at the top
 SECURITY.md           private vulnerability reporting + scope
 THIRD_PARTY_NOTICES.md  install-time dependencies (none bundled)
@@ -40,38 +98,52 @@ LICENSE               Apache-2.0
 
 ## Hard rules applied here
 
-- **The corridor is locked.** This package upgrades plugins across `0.1.3-alpha.1 →
-  0.1.5-alpha.1` and nothing else. Do not widen the peer band or the card to "all versions":
-  a drifting card is worse than no card. A new corridor is a new package.
-- **M1 is an error, never a warning.** If a `tsconfig` `paths` alias does not resolve, every
-  other local signal is fake. The scanner must keep failing the run for it.
+- **`C1` is an error, never a warning.** The deletion has no alias and the injection callback
+  never runs, so the only honest level is error. Only promote `C4`/`C5`/`H1`/`H2`/`H4` from
+  advisory to error with evidence and a fixture that proves the false positive is gone.
+- **`M1` and `P1` are blockers, never warnings.** If the local type line is stale (either
+  cause), or the peer band lost its second segment, every other local signal is fake. `M1`
+  and `P1` are **structured** checks, so their catalog `test` is `null` without being
+  card-only.
+- **The leg-A error seams stay errors.** `S3`, `S8`, `S9`, `S4`, `S5` and `S6` each make a
+  repo that looks green fail on the target host; only demote one with new upstream evidence.
+- **Advisory seams stay advisory.** `S7`/`S2`/`S1`/`S10` and `C4`/`C5`/`H1`/`H2`/`H4` have
+  legitimate matches; they are leads for manual review. Only promote one to `error` with
+  evidence and a fixture that proves the false positive is gone.
+- **`H3` is card-only.** It is documented, id-parity checked, and deliberately has no
+  detector; `CARD_ONLY` is exactly `['H3']` and the test suite asserts it stays that way.
 - **The scanner is read-only and dependency-free.** No network, no child process, no write
   inside `--repo`; `lib/scan.mjs` imports only `node:fs` and `node:path`. Keep it that way.
-- **Advisory seams stay advisory.** `S7`/`S1`/`S2`/`S10` have legitimate matches; they are
-  leads for manual review. Only promote one to `error` with evidence and a fixture that
-  proves the false positive is gone.
 - **A clean scan is necessary, not sufficient.** Never describe a scan as proof of
-  adaptation; the card's exit criterion is a real-host smoke on a temp `DSH_HOME`.
+  adaptation: this span's breakage is silent from both ends, so a session-log writer needs a
+  resume round-trip (`S3`), a client half needs a real browser assertion, and the card's exit
+  criterion is a real-host smoke on a temp `DSH_HOME`.
+- **The card and the catalog are one catalog.** `test/card.test.mjs` fails when their ids or
+  severities disagree, and when the card mints an id outside the merged 20. Change the card
+  first, then the catalog, in the same commit.
 - **Mount loud.** A missing `SKILL.md`, an empty body, or a frontmatter without `name` must
   abort the mount. Never register a placeholder skill.
 - **The skill id is the frontmatter name.** `skillName` selects the directory; the registered
-  name comes from the file. Keep the two in sync (`plugin-upgrade-015`).
+  name comes from the file. Keep the four in sync (`plugin-upgrade`: directory,
+  frontmatter `name`, `package.json` Config default, `cordis.patch.yml`).
 - **Registration is an effect.** `ctx.skills.register()` runs inside `ctx.effect()` so the
   disposer removes the contribution on unload; the test asserts that.
 - **No build step.** Pure ESM: `index.mjs` + `lib/` are the shipped artifacts. There is no
   `build`/`prepare` script — keep it that way.
 - **Optional seams fail closed.** `skills` is a hard `inject`; if the service is absent the
   plugin waits rather than registering into a void.
+- **License headers.** `// SPDX-License-Identifier: Apache-2.0` is the first line of every
+  source file; `# SPDX-License-Identifier: Apache-2.0` heads `cordis.patch.yml`.
 
 ## Checks
 
 ```sh
-pnpm install
-pnpm test                          # node --test (11 tests: scanner + real-registry mount)
-pnpm run verify:self-contained     # dependency specs resolve from the registry
-pnpm run verify:artifacts          # shipped files present + entry importable from the tarball
-pnpm run check:readmes             # five-language README consistency
-pnpm pack                          # the published tarball
+npm install                        # or: pnpm install (pnpm-lock.yaml is committed)
+npm test                           # node --test: scanner (both legs) + card parity + real-registry mount
+npm run verify:self-contained      # every import resolves inside the package
+npm run verify:artifacts           # tarball contents + entry import + dev-only content excluded
+npm run check:readmes              # five-language README consistency
+npm pack                           # the published tarball
 ```
 
 `pnpm-workspace.yaml` keeps `minimumReleaseAge: 0`: pnpm 11 enables a 1440-minute age gate by
@@ -81,23 +153,50 @@ after every harness release.
 
 ## Release
 
-Version is currently `0.1.2`. For a new version: bump `package.json#version`, stamp the
-CHANGELOG `[Unreleased]` section into `## [<x.y.z>] - <UTC date>`, re-run the full gate,
-commit `chore(release): <x.y.z>`, and `git tag -a v<x.y.z>`. `git push origin main
---follow-tags` triggers `.github/workflows/release.yml`, which re-runs the gate, publishes to
-npm with provenance (skipped without the `NPM_TOKEN` secret), and creates the GitHub Release
-from the stamped CHANGELOG section. Never push a tag for a version already on the registry.
+Version is currently `0.1.0`. The npm name `dsh-plugin-upgrade` is brand new, so
+this package starts its own version line at `0.1.0`; the two retired packages' histories live
+in `CHANGELOG.md` under `[Unreleased]` and below. For a new version: bump
+`package.json#version`, stamp the CHANGELOG `[Unreleased]` section into `## [<x.y.z>] - <UTC
+date>`, re-run the full gate, commit `chore(release): <x.y.z>`, and `git tag -a v<x.y.z>`.
+`git push origin main --follow-tags` triggers `.github/workflows/release.yml`, which re-runs
+the gate, publishes to npm with provenance (skipped without the `NPM_TOKEN` secret) and
+creates the GitHub Release from the stamped CHANGELOG section behind an idempotent
+`gh release view` guard. Never push a tag for a version already on the registry.
+**Publish incident (2026-09-10, the first tag of the retired `dsh-plugin-upgrade-rc1`).**
+`v0.1.0`'s first run failed in `Publish to npm` with `*** is not a legal HTTP header value`,
+after the provenance statement had already been signed and published to the transparency log.
+The step read the token through setup-node's `${NODE_AUTH_TOKEN}` expansion at the time; it
+now normalises line breaks and writes `//registry.npmjs.org/:_authToken=…` into
+`NPM_CONFIG_USERCONFIG` itself. The rewritten step reports whether the secret carried line
+breaks, and it reported **no** — so the trailing-newline hypothesis is disproven and the
+mechanism of the env-expanded failure is NOT established. What is established: that path
+failed, the directly written userconfig publishes. `v0.1.0` was re-tagged onto the fix
+(allowed: the version was not on the registry yet). The rewritten step is inherited by this
+package unchanged; do not reintroduce `${NODE_AUTH_TOKEN}` without re-testing it.
 
 The scanner catalog is evidence-bound: a version bump that changes a seam must update the
-card, the fixtures and `CHANGELOG.md` in the same commit.
+card, `docs/EVIDENCE.md`, the fixtures **of the leg it belongs to** and `CHANGELOG.md` in the
+same commit.
+
+**Post-publish integration (not done in this repository's history yet).** The README badge
+row expects `PerryLink/dsh-plugin-doctor` to carry a
+`PerryLink__dsh-plugin-upgrade.svg` badge, and the family also enrols each package
+in the Gitee mirror, the `dsh-catalog` directory and the omdsh workshop list. Those are
+release-side steps performed from the family workspace after the first tag. The two retired
+package names stay on the registry (unpublished content is not removed by publishing a new
+name); their README/card wording is now historical.
 
 ## Docs
 
-- Five-language READMEs (`README.md` is the source; `README.zh.md`, `README.es.md`,
-  `README.pt.md`, `README.hi.md` follow). Every behavior change updates all five in the same
-  commit; `check:readmes` enforces the shared surface in CI.
+- Five-language READMEs (`README.md` is the source; `README-zh.md`, `README-es.md`,
+  `README-pt.md`, `README-hi.md` follow). Every behavior change updates all five in the same
+  commit; `check:readmes` enforces the shared section count and the install line in CI.
 - GitHub topics `dsh`, `dsh-plugin`, `deepseek-harness`, `deepseek`, `cordis`,
-  `plugin-upgrade`, `migration`, `skill`, `version-card`, `scanner` (mirror `package.json`
-  keywords; the ecosystem's visibility channel is the `dsh-plugin` topic).
+  `plugin-upgrade`, `migration`, `skill`, `version-card`, `scanner`, `client-slots` (mirror
+  `package.json` keywords; the ecosystem's visibility channel is the `dsh-plugin` topic).
 - License is Apache-2.0 (`LICENSE` + the package.json `license` field).
   `THIRD_PARTY_NOTICES.md` documents install-time dependencies; nothing is bundled.
+- Every factual claim in the card or the scanner traces to a command recorded in
+  `docs/EVIDENCE.md` — §A for leg A's provenance (via the retired `dsh-plugin-upgrade` card,
+  now merged in as Leg A) and §1–§10 for leg B's records. Where a claim could not be verified
+  it is marked **unverified** and kept out of the card.

package/CHANGELOG.md

@@ -5,52 +5,112 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
-
-## [0.1.3] - 2026-09-10
+## [2.0.0] - 2026-09-19
 
 ### Changed
 
-- Pin the `@deepseek-ai/dsh-*` dev/test dependencies to the published `0.1.5-rc.1` line and record `0.1.5-rc.1` in `dshWorkshop.compatibility.dshVersions`; the monthly Compat workflow now runs against `0.1.5-rc.1`. The peer range `>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0` is unchanged, so no supported host line is dropped.
+- The retired name returns as the new-generation single package: one package, one corridor index. It absorbs the merged corridor 0.1.3-alpha.1 -> 0.1.5-rc.1 that lived in dsh-plugin-upgrade-015 (legs A+B, 20 seams) and it is the package the later corridor 0.1.5-rc.2 -> 0.1.6-alpha.2 (E1-E5, from dsh-plugin-upgrade-016) is folded into.
+- The skill and the CLI are one entry point: the scanner detects the caller peer band and routes to the matching corridor; the corridor index is the growth point (a new corridor adds a card and an index row, not a new package).
+- Names: the skill id is plugin-upgrade and the CLI is dsh-plugin-upgrade-scan.
 
-### Docs
+### Supersedes
 
-- Refresh the five-language README compatibility baseline to `dsh-v0.1.5-rc.1` (verified 2026-09-10).
+- dsh-plugin-upgrade-015 (npm 0.1.1) - its corridors are carried here.
+- dsh-plugin-upgrade-rc1 and the old 0.1.x line of this name.
 
+## [0.1.1] - 2026-09-12
 
-## [0.1.2] - 2026-09-09
+## [0.1.0] - 2026-09-11
 
-### Fixed
+### Added
 
-- **The shipped version card no longer describes itself as unpublished.** Its status line
-  now names the three published channels and points at the packaged CLI
-  (`dsh-plugin-upgrade-scan`) for reproduction instead of a workspace-private evidence
-  path that no reader of the tarball can follow.
+- **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 `tsconfig` `paths` 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/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` (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
 
-- Family-standard CI: the `plugin-doctor` static R/K gate and OpenSSF Scorecard now run in
-  this repository, and `dsh-plugin-upgrade` is enrolled in the
-  `dsh-plugin-doctor` verified registry (badge: passing).
-
-## [0.1.1] - 2026-09-09
-
-### Fixed
+- The scanner CLI is now `dsh-plugin-upgrade-scan` (`scripts/scan-0.1.5.mjs`, plus the
+  skill-local `skills/plugin-upgrade/scripts/scan-0.1.5.mjs`); the cordis row is
+  `dsh-plugin-upgrade`.
+- 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.
 
-- **SKILL.md frontmatter on a CRLF checkout.** The parser required the `---\n`
-  delimiter, so a Windows checkout (`core.autocrlf=true`) mounted the skill with the
-  frontmatter leaked into the body and no description/`whenToUse`. Line endings are now
-  normalized before parsing, `.gitattributes` pins every text file to LF, and the suite
-  covers both a CRLF string and a CRLF-converted bundle on disk. Caught by the Windows
-  CI leg of v0.1.0.
+## [0.1.0] - 2026-09-10 · retired package `dsh-plugin-upgrade-rc1` (leg B)
 
-## [0.1.0] - 2026-09-09
+> *Historical entry, kept as published: every package name, CLI name and skill id below is as
+> it was in the retired leg-B package (`dsh-plugin-upgrade-rc1`, skill
+> `plugin-upgraderc1`, CLI `dsh-plugin-upgrade-rc1-scan`). Their merged equivalents are in
+> `[Unreleased]`. Leg B's seam `C3` below is the merged `M1`, and this entry is retained
+> verbatim apart from that fold.*
 
 ### Added
 
-- **Bundled agent skill `plugin-upgrade-015`** — the version-locked `0.1.3-alpha.1 → 0.1.5-alpha.1` upgrade corridor: a 6-step fix-and-verify loop plus the version card with host path, commit, minimal fix and regression for every seam.
-- **Zero-dependency seam scanner** (`dsh-plugin-upgrade-scan`, also `dsh-plugin-upgrade/scan`) — reports `file:line` facts for ten seams measured against 40 real plugin repositories during the 2026-09-09 adaptation wave; exit `1` on any error-severity hit.
-- **Ten-seam catalog** — `S1` V3 session format / generation-scoped log name, `S2` `EpochHeader.system` removal, `S3` `assistant/message.stream` required, `S4` `tool/code-dispatch` → `tool/ptc-dispatch`, `S5` `ctx.agent` removal, `S6` `Inbox` typed interface, `S7` `SubprocessHandle.pid` removal, `S8` `SessionHandleReadResult`, `S9` `SystemPrompt.persona` → `personaPrefix`/`personaSuffix`, `M1` stale `tsconfig` `paths` producing a silently fake-green typecheck.
-- **M1 as a first-class defect** — the scanner resolves every checkout-style `tsconfig` alias and fails the scan when a target directory does not exist, instead of letting the repo compile against published types.
-- **Plugin surface** — `enabled`, `skillName`, `skillsRoot`, `userInvocable` config keys; the skill registers through the injected `skills` service and unregisters with its effect disposer. A missing bundle, an empty body or a nameless frontmatter fails the mount loud.
-- **Gates** — `node --test` against a real Cordis `Context` and the real `SkillRegistry`, five-language README consistency, self-contained import resolution, and a packed-tarball artifact check that imports the entry under plain Node.
+- **Bundled agent skill `plugin-upgraderc1`** — the version-locked `0.1.5-alpha.1 →
+  0.1.5-rc.1` corridor: a 6-step fix-and-verify loop plus the corridor card with the
+  from→to mapping, the seam catalog and the rewrite recipes.
+- **Zero-dependency seam scanner** (`dsh-plugin-upgrade-rc1-scan`, also
+  `dsh-plugin-upgrade-rc1/scan`) — reports `file:line` facts for ten seams re-read from the
+  harness tag range on 2026-09-10; exit `1` on any error-severity hit.
+- **Ten-seam catalog** — `C1` the bare client slot `conversation` deleted with no alias
+  (silent unmount), `C2` the `dsh-client-ui-sidebar-textpreview` →
+  `…-sidebar-documentpreview` package rename, `M1` the client-side false green from a stale
+  type line or an unresolvable `tsconfig` `paths` alias (leg B's card spelled this seam `C3`;
+  it is now one seam with leg A's `M1`), `C4` the new global main-panel model
+  and the `usePanelInfo` standard prop, `C5` the `sidebar.right.tab.document` document
+  preview slot and the `rightbar` → `rightbar.session` parent change, `H1` the two new
+  fail-closed session event types, `H2` the `present` tool taking the `'present'` tool-view
+  key, `H3` the additive capabilities (card-only, no detector), `H4` the DeepSeek adapter's
+  default advisory catalog now led by `deepseek-flash`, and `P1` the peer-range trap where
+  `>=0.1.2-rc.1 <0.2.0` alone rejects `0.1.5-rc.1`.
+- **`C1` ruling and rewrite recipe** — the removal is documented as a **public
+  extension-point break** (no alias, no shim, no upstream deprecation note, and
+  `ctx.slots.inject()` never fires without the declaration), with the
+  `conversation` → `main.conversation` / `main` recipe and a real-browser exit criterion.
+- **Honest blast-radius record** — the card states that the family's own client halves use
+  eight slot keys, all of which survive in rc.1, so this hop is latent breakage for them and
+  actual breakage only for third-party halves that targeted the bare key.
+- **`M1` (leg B's `C3`) and `P1` as structured checks** — they resolve `tsconfig` `paths` and
+  the declared peer band instead of matching text, mirroring leg A's `M1` treatment.
+- **Card↔catalog parity gate** — `test/card.test.mjs` asserts that the card and
+  `lib/scan.mjs` name exactly the same seam ids with the same severities, turning the
+  evidence-binding rule into a machine gate.
+- **Plugin surface** — `enabled`, `skillName`, `skillsRoot`, `userInvocable` config keys; the
+  skill registers through the injected `skills` service and unregisters with its effect
+  disposer. A missing bundle, an empty body or a nameless frontmatter fails the mount loud.
+- **Evidence seal** — `docs/EVIDENCE.md` records the command and the observed output behind
+  every card claim, and marks what could not be verified.
+- **Gates** — `node --test` against a real Cordis `Context` and the real `SkillRegistry`,
+  five-language README consistency, self-contained import resolution, and a packed-tarball
+  artifact check that also proves `test/`, `fixtures/` and `.github/` never ship.
+- **Family-standard CI** — 3 OS × 2 Node `ci.yml`, a monthly `compat.yml` probe against the
+  published `0.1.5-rc.1` line, OpenSSF `scorecard.yml`, the `plugin-doctor.yml` static R/K
+  gate, and a tag-triggered `release.yml` that gates, publishes to npm with provenance and
+  creates the GitHub Release behind an idempotent guard.