dsh-scout 0.9.2 → 0.9.3

package/dist/index.js

@@ -4,6 +4,23 @@ import { addClaim, addSource, appendEvent, CLAIM_DIMENSIONS, CLAIM_IMPACTS, CLAI
 import { formatScoutString, isScoutLanguage, normalizeScoutLanguage, scoutStrings, } from './i18n.js';
 export const name = 'dsh-scout';
 export const inject = ['tools'];
+/**
+ * The version this source tree ships, stated as a literal.
+ *
+ * It is deliberately never read back from `package.json`. A release checklist
+ * anchor only works when the version is asserted in two independent places: the
+ * assertion compares this literal against the manifest, so a bump that updates
+ * one and forgets the other fails the suite instead of shipping silently.
+ * `tests/acceptance.test.mjs` pins this constant, `package.json` and the
+ * `/scout status` output to the same string.
+ *
+ * Where this reaches a user: `runScoutCommand` prints it in `/scout status`.
+ * It cannot be printed at load time — a plugin's log output is not visible in
+ * any DSH surface (cordis only buffers it in memory), and a plugin that failed
+ * to load never runs at all, so "is it loaded, and which version?" is answered
+ * by the settings plugin list instead.
+ */
+export const PLUGIN_VERSION = '0.9.3';
 export const Config = z.object({
     scoutDir: z.string().default('dsh-scout'),
     autoPersist: z.boolean().default(false),
@@ -1034,7 +1051,11 @@ export function apply(ctx, config = {}) {
                 kind: 'success',
                 text: `[${scoutCase.caseId}] ${scoutCase.decision} · identity ${scoutCase.subject.identityStatus}`
                     + ` · sources ${scoutCase.sources.length} / claims ${scoutCase.claims.length}`
-                    + ` (verified ${verified}, open ${scoutCase.claims.length - verified})`,
+                    + ` (verified ${verified}, open ${scoutCase.claims.length - verified})`
+                    // Trailing, so the case facts stay the leading, greppable part of the
+                    // line. This is the one surface that can state the version: reaching
+                    // this branch already proves the plugin loaded.
+                    + ` · dsh-scout ${PLUGIN_VERSION}`,
             };
         }
         if (action === 'questions') {

package/docs/dsh-scout-product-contract.md

@@ -16,7 +16,7 @@
 
 0.9.1 明确不做的事见 [CHANGELOG](../CHANGELOG.md)：client 面板、自造 session event、`ctx.storageDomain` 持久化重写、评分与排名（0.9.2 沿用同一非目标）。
 
-**v0.9.2（当前版本）**是收口版本：把 0.9.1 验证报告点名的最大盲区（U11）补成真实宿主门禁，并清掉三轮独立验证留下的文档税。本版本**不新增工具、不新增命令、不新增 Skill 条目**：
+**v0.9.2**是收口版本：把 0.9.1 验证报告点名的最大盲区（U11）补成真实宿主门禁，并清掉三轮独立验证留下的文档税。本版本**不新增工具、不新增命令、不新增 Skill 条目**：
 
 - **F2 · 真实宿主端到端门禁（关闭 U11）**：`scripts/profile-smoke.mjs` 扩展为六步真实宿主场景链——创建 → 导出 → 冷重启 → 惰性回填 → 跨语言导入 → 卸载，另加完成标记「缺失 / `complete:false`」两条负向对照；四版本矩阵在扩展后的门禁下 4/4 通过。**仍未覆盖**：真实 LLM / agent loop 与 approval 策略、相对路径、`autoPersist`、真实进程中断，以及其余 6 个工具（仅断言注册）。
 - **F1 · 面试问题按下标逐条对齐（关闭 D10）**：精选面试问题由「整组 all-or-nothing」改为按下标逐条——长度与出厂数组相同时逐条替换，用户改过的那条保持原样；长度不同则整组原样保留。默认行为对**未编辑**场景零变化。
@@ -24,6 +24,8 @@
 - **F4 · 依赖对齐**：`@deepseek-ai/schemastery` 由 `^3.18.2` 改为 `~3.18.4`，与宿主系列一致；`peerDependencies` 与 `engines.dsh` 范围不变。
 - **已知边界 G1（有意不修，推迟 0.10.0）**：冷启动惰性回填会把决策理由措辞由初始文案换成 `decisionReasons.identity`（并补 `decisionReasonCode`），`decision` 不变；详见 [0.9.2 门禁发现](dsh-scout-0.9.2-gate-findings.md)（仓库文档，不在 npm 包内）。
 
+**v0.9.3（当前版本）**不改运行时契约，主题是**安装体验**：此前 README 的三条「已验证路径」全是 `dsh plugin --profile <name> add …`，而桌面 App 的 `desktop` profile 被 Electron 应用独占，桌面用户第一步就撞墙——0.9.3 把「App 内安装」写成主路径，并给安装补上可执行判据。安装模型、分发源取舍与兼容性豁免见 §5.3；桌面路径的手工验收见 [安装验收 checklist](install-verification.md)（仓库文档，不在 npm 包内）；评审原件见 [安装评审](dsh-scout-install-ux-review.md)（同上）。本版本**不新增工具、命令或 Skill 条目**。
+
 ## 1. 产品承诺
 
 给定一个公司和一个岗位，`dsh-scout` 不承诺“找到所有信息”，而承诺在证据边界内回答：
@@ -123,6 +125,23 @@ scout-cases/<case-id>/
 
 > 一句话规则：**不要自造 session event。** 用户显式动作走 `command/run` + `command/done`，结构化 UI 载荷走 `output.presentationMeta` → `tool/result.meta`，持久状态走 `ctx.storageDomain`。
 
+### 5.3 安装与分发模型（0.9.3）
+
+两条入口，安装方式不同，不要混用：
+
+| 你在哪运行 | 目标 profile | 安装方式 |
+| --- | --- | --- |
+| 桌面 App（DeepSeek Harness） | `desktop` | **侧边栏 → 插件页**（唯一路径） |
+| CLI / headless / 自建 profile | 你自己的 profile 名 | `dsh plugin --profile <your-profile> add dsh-scout@<exact-version>` |
+
+- **`desktop` 由应用独占**：CLI 对它的**所有** `dsh plugin` 子命令都在参数解析层按 profile 名拒绝（`rejectElectronProfile`，`error: profile "desktop" is managed exclusively by the Electron application`），连兼容性逃生门 `allow-version` 一起拒绝。所以桌面场景既没有 CLI 判据，也没有可脚本化的自动化门禁——这正是 0.9.2 及以前的门禁盲区。
+- **spec 一律写精确版本**：pnpm ≥ 11 默认启用最小发布年龄（minimum release age）供应链保护，裸包名会把刚发布的版本静默跳过、回退到旧版；写精确版本后 pnpm 会把它记入 profile 的 `minimumReleaseAgeExclude`。
+- **分发源与代价**：npm（自带 `dist/`，不跑安装脚本，**推荐**）、本地 tarball（离线 / 自测）、git（仓库不含 `dist/`，`prepare` 会跑 `tsc` 并安装 devDependencies——**不推荐**，只在需要未发布提交时使用，ref 写真实 tag 如 `#v0.9.3`）。git 是唯一会执行代码的路径。
+- **Node 适用范围**：`engines.node >= 22.19` 只对 CLI / 门禁路径成立；桌面 App 自带运行时（实测 node 24.21.0 + pnpm 11.7.0），无需安装 Node。
+- **成功判据与排障面（两个 GUI 面，别混）**：**侧边栏 → 插件页**是**管理面**，回答「装的是哪版」——`dsh-scout` 在「已安装」里，**详情页**标题旁带 `v{version}`（`BundleInfo.version`），安装 / 启用 / 停用 / 移除都在这里；**设置 → 内置插件 → 插件列表**是**只读检查面**，回答「装没装 / 为什么没生效」——该行**已启用 + 运行中**（不是**已停用** / **启动失败** / **条件启用**），按「会话插件 / 全局插件」分组，**不显示版本号**（wire 行只有 `{ entryId, moduleName, meta?, enabled, fiberPhase }`）。再加上新开一轮对话是否出现 12 个 `scout_*` 工具、`/scout status <caseId>` 是否命中且输出末尾带 `· dsh-scout <version>`。CLI 的 `--dump-config` 只证明「组合进去了」，**不等于**运行时挂上了——不匹配时插件行被置为 disabled，且**这一行只对 CLI 用户可见**（stderr 打 `dsh: disabling profile plugin <row>: <reason>`）。桌面 App 没有可见 stderr、没有运行日志（实测 Electron 主进程的 fd0/fd1/fd2 指向 `/dev/null`，日志目录为空），插件被 disabled 时它自己不可能输出任何东西——但**答案就在 GUI 里**：启动时被禁用的行会被投影成插件列表里的「已停用」（宿主侧 `enabled: !entry.disabled`，`dsh-host-plugin-inventory/lib/index.js:131`），所以插件列表是桌面唯一的排障入口。
+- **版本豁免（桌面手动路径）**：桌面用户用不了 `allow-version`，需要在 `~/.dsh/profiles/desktop/compatibility.json` 手写豁免——平铺 JSON：精确 `package@version` → 允许的精确 DSH 版本数组，例如 `{ "dsh-scout@0.9.3": ["0.2.0-rc.2"] }`。与工具 / CLI 写入的是同一组边界：只接受精确版本、只授权「这一个包版本 + 这一个 DSH 版本」这一对、不随升级继承、不授权依赖安装脚本、下一次组合生效；手写绕过 `acceptRisk` 风险确认，写法不合规的记录会被忽略并告警（不会让 profile 不可用）。
+- **验收**：桌面路径由发版前手工 checklist 覆盖（`docs/install-verification.md`：Lane D 桌面 App / Lane C CLI，含两条 lane 的差异与触发时机，仓库文档、不在 npm 包内）；CLI 自动化仍是 `npm run test:profile` 的六步链与 `npm run check:release` 的四版本矩阵。
+
 ## 6. 明确非目标
 
 - 不重做通用搜索、浏览器或 MCP provider。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-scout",
-  "version": "0.9.2",
+  "version": "0.9.3",
   "description": "Evidence-driven company and job intelligence plugin for DeepSeek Harness.",
   "icon": "./assets/icon.svg",
   "license": "MIT",

package/scripts/check-release.mjs

@@ -24,6 +24,13 @@
  *                           `DSH_VERSIONS=0.2.0-rc.2 node scripts/check-release.mjs`)
  *   DSH_ALLOW_OUT_OF_RANGE  `1` downgrades out-of-range failures to warnings
  *
+ * README preflight (P2-4): the READMEs pin the released version in their install
+ * commands and artifact names, and nothing used to check them. The primary guard
+ * lives in `tests/package.test.mjs` (it runs on every `npm test` and in CI, in
+ * milliseconds); this gate repeats the check as an independent second
+ * implementation so a stale README fails in milliseconds instead of after the
+ * whole unit suite and the ~2 minute four-version profile matrix below.
+ *
  * SemVer semantics (do NOT "fix" this matcher): this script has no runtime
  * dependency, so it carries a small comparator-set matcher that mirrors
  * node-semver's `{ includePrerelease: true }` mode — the exact mode DSH uses to
@@ -196,6 +203,227 @@ console.log('  range semantics: node-semver includePrerelease:true (mirrors dsh-
 console.log(`  profile matrix: ${versions.join(', ')} (${source})`)
 console.log(`  out-of-range failures: ${ALLOW_OUT_OF_RANGE ? 'warn only (DSH_ALLOW_OUT_OF_RANGE=1)' : 'fatal, reported as OUT OF DECLARED RANGE'}`)
 
+// --- README release-reference preflight (see the module doc) ------------------
+//
+// Deliberately a second, simpler implementation of the guard in
+// tests/package.test.mjs rather than a shared import: tests are not a library, and
+// this one has to fail before the expensive work below. Same rule as that guard -
+// only install/artifact references are checked: `dsh-scout-<v>.tgz`, the
+// `dsh-scout@<v>` pin in its three live forms (install operand, alone on its
+// line, or a quoted version key), the ` · dsh-scout <v>` status banner, a
+// `#v<v>` git ref, and the phrase-anchored `本次发布创建 \`v<v>\`` /
+// `this release creates \`v<v>\`` tag claim. Historical mentions in the
+// verified-version matrix, the roadmap, and release prose are left alone.
+// 0.9.3 freezes this rule set: a new version-reference style is evaluated in the
+// change that introduces it, not by widening this list indefinitely.
+const README_FILES = ['README.md', 'README.en.md']
+const README_SEMVER = String.raw`\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?`
+/** An exact specifier: `1.2.3` or `v1.2.3`. */
+const README_EXACT_SPECIFIER = new RegExp(`^v?(${README_SEMVER})$`)
+/**
+ * A specifier naming a version *or a range* (`0.9`, `0.9.x`, `^0.9.2`, `>=0.9.2`,
+ * `=0.9.2`, `*`). Ranges are live references node-semver satisfies, but this
+ * preflight carries no range semantics, so it fails closed rather than waving
+ * them through (F-1). Dist-tags and placeholders name no version and stay valid.
+ */
+const README_VERSION_OR_RANGE = /^[\^~<>=|\s]*(?:v?\d|\*|x)/i
+/** Exact version, unsupported specifier, or not a version claim at all. */
+const classifySpecifier = token => {
+  const exact = README_EXACT_SPECIFIER.exec(token)
+  if (exact !== null) return { version: exact[1] }
+  if (README_VERSION_OR_RANGE.test(token)) {
+    return {
+      problem:
+        `uses the unsupported specifier "${token}"; a range or comparison cannot be compared to ` +
+        'the released version - write the exact version, or extend README_REFERENCE_PATTERNS ' +
+        'with the semantics of this form',
+    }
+  }
+  return null
+}
+const README_REFERENCE_PATTERNS = [
+  {
+    kind: 'tarball name',
+    pattern: new RegExp(`dsh-scout-(${README_SEMVER})\\.tgz`, 'g'),
+    classify: match => ({ version: match[1] }),
+  },
+  {
+    kind: 'npm install pin',
+    // Token charset excludes sentence punctuation, so `dsh-scout@0.9.3。` still
+    // reads as an exact pin while `dsh-scout@^0.9.2` is captured whole.
+    pattern: new RegExp('dsh-scout@([0-9A-Za-z.*^~<>=|+-]+)', 'g'),
+    classify: (match, line) => {
+      const before = line.slice(0, match.index)
+      const after = line.slice(match.index + match[0].length)
+      // the operand of an install verb ...
+      const livePosition =
+        /(?:^|[\s`'"(])(?:add|install|dlx|i)\s+(?:--?[\w-]+(?:=\S+)?\s+)*(?:file:)?$/.test(before.replace(/[`"')\]]+$/, '')) ||
+        // ... a specifier alone on its line (the desktop app's plugin field) ...
+        (before.replace(/^[\s>]*(?:[-*+]\s+)?/, '') === '' && after.replace(/[`"')\]]+$/, '').trim() === '') ||
+        // ... or a quoted `"package@version"` key (compatibility.json).
+        (/["']$/.test(before) && /^["']\s*:/.test(after))
+      return livePosition ? classifySpecifier(match[1]) : null
+    },
+  },
+  {
+    kind: 'git install ref',
+    pattern: new RegExp(`dsh-scout(?:\\.git)?#v?(${README_SEMVER})`, 'g'),
+    classify: match => ({ version: match[1] }),
+  },
+  {
+    // ` · dsh-scout <v>` - the /scout status banner (src/index.ts appends
+    // ` · dsh-scout ${PLUGIN_VERSION}`); the separator is required so that prose
+    // and report titles naming the package next to a version are not pins.
+    kind: 'status banner',
+    pattern: new RegExp(`·\\s*dsh-scout (${README_SEMVER})`, 'g'),
+    classify: match => ({ version: match[1] }),
+  },
+  {
+    // `本次发布创建 \`v<v>\`` / `this release creates \`v<v>\`` - the tag this
+    // release creates. The phrase is what makes a bare `v<semver>` safe to guard
+    // here: the same line also lists historical tags (`v0.3.0` ... `v0.9.2`).
+    kind: 'release tag claim',
+    pattern: new RegExp(`(?:本次发布创建|this release creates)\\s*\`?v?(${README_SEMVER})\`?`, 'g'),
+    classify: match => ({ version: match[1] }),
+  },
+]
+const expectedVersion = packageJson.version
+const staleReferences = []
+const reportedLines = new Set()
+const anchorFailures = []
+const releaseTagClaimFiles = new Set()
+let readmeReferenceCount = 0
+for (const file of README_FILES) {
+  const text = readFileSync(new URL(`../${file}`, import.meta.url), 'utf8')
+  text.split('\n').forEach((line, lineIndex) => {
+    for (const { kind, pattern, classify } of README_REFERENCE_PATTERNS) {
+      pattern.lastIndex = 0
+      let match
+      while ((match = pattern.exec(line)) !== null) {
+        const verdict = classify(match, line)
+        if (verdict === null) continue
+        if (kind === 'release tag claim') releaseTagClaimFiles.add(file)
+        readmeReferenceCount += 1
+        if (verdict.problem !== undefined) {
+          staleReferences.push(`${file}:${lineIndex + 1} ${match[0]} ${verdict.problem} (${kind})`)
+          // Only *offending* lines are deduped, so the section scan below still
+          // sees a stale bare token on a line that also carries a correct pin
+          // (F-3): this matches guardFailures() in tests/package.test.mjs.
+          reportedLines.add(`${file}:${lineIndex + 1}`)
+        } else if (verdict.version !== expectedVersion) {
+          staleReferences.push(
+            `${file}:${lineIndex + 1} pins ${match[0]} but package.json is ${expectedVersion} (${kind})`,
+          )
+          reportedLines.add(`${file}:${lineIndex + 1}`)
+        }
+      }
+    }
+  })
+}
+
+// The release-tag claim is phrase-anchored, so rewording the sentence would stop
+// guarding it silently. Asserted per file: a rule that can no longer match
+// anything is the false green this preflight exists to prevent.
+for (const file of README_FILES) {
+  if (!releaseTagClaimFiles.has(file)) {
+    anchorFailures.push(
+      `${file}: no "release tag claim" reference matched - either the sentence that creates the ` +
+        'release tag was reworded (update the phrase in README_REFERENCE_PATTERNS here and in ' +
+        'tests/package.test.mjs) or it was removed (retire this rule deliberately with the docs owner)',
+    )
+  }
+}
+
+// --- success-criteria section scan (T-G) --------------------------------------
+//
+// The success-criteria section says how to confirm that *this* release is the one
+// that loaded, so every version token inside it must be the released version -
+// including the bare forms the pattern scan above cannot claim safely (the card's
+// `v0.9.3` tag, `and version `0.9.3``), because a bare `v<semver>` elsewhere is
+// legitimate history (the release-history line lists `v0.3.0` ... `v0.9.2`).
+//
+// The anchors are explicit and a miss is a FAILURE, never a skip: a silently
+// skipped section would let a reworded heading disarm the guard, which is exactly
+// the false green this preflight exists to prevent.
+const SECTION_ANCHORS = [
+  { file: 'README.md', heading: /^(#{2,4})\s*装上了吗（成功判据）$/, label: '装上了吗（成功判据）' },
+  { file: 'README.en.md', heading: /^(#{2,4})\s*Did it install\? \(success criteria\)$/, label: 'Did it install? (success criteria)' },
+]
+// `@` is deliberately not excluded: a prose reference inside the section such as
+// `` 安装 `dsh-scout@0.9.2` 后 `` names a version the pattern scan does not claim
+// (it is not in an install position) and the section contract still covers it
+// (F-2). `-` stays excluded so a tarball name is left to the pattern scan.
+const SECTION_VERSION_TOKEN = /(?<![\w./-])v?(\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?)(?![\w.-])/g
+const SECTION_ANCHOR_REMEDY =
+  'the success-criteria heading was reworded or moved: update SECTION_ANCHORS here and ' +
+  'SUCCESS_CRITERIA_SECTIONS in tests/package.test.mjs. This preflight must never skip it silently.'
+let sectionTokenCount = 0
+/** Section body bounds for one heading anchor; null when the anchor no longer matches. */
+const sectionBounds = (lines, heading) => {
+  let fenced = false
+  let start = -1
+  let level = 0
+  for (let index = 0; index < lines.length; index += 1) {
+    const trimmed = lines[index].trim()
+    // A `# ...` shell comment inside the section's fenced CLI example is body
+    // text, not a heading, so fences are tracked while looking for the end.
+    if (/^(?:```|~~~)/.test(trimmed)) {
+      fenced = !fenced
+      continue
+    }
+    if (fenced) continue
+    const marker = /^(#{1,6})\s/.exec(trimmed)
+    if (start === -1) {
+      if (heading.test(trimmed)) {
+        start = index
+        level = /^#+/.exec(trimmed)[0].length
+      }
+      continue
+    }
+    if (marker !== null && marker[1].length <= level) return { start, end: index }
+  }
+  return start === -1 ? null : { start, end: lines.length }
+}
+for (const { file, heading, label } of SECTION_ANCHORS) {
+  const lines = readFileSync(new URL(`../${file}`, import.meta.url), 'utf8').split('\n')
+  const section = sectionBounds(lines, heading)
+  if (section === null) {
+    anchorFailures.push(`${file}: no heading matches "${label}" - ${SECTION_ANCHOR_REMEDY}`)
+    continue
+  }
+  for (let index = section.start + 1; index < section.end; index += 1) {
+    const line = lines[index]
+    if (reportedLines.has(`${file}:${index + 1}`)) continue
+    SECTION_VERSION_TOKEN.lastIndex = 0
+    let match
+    while ((match = SECTION_VERSION_TOKEN.exec(line)) !== null) {
+      sectionTokenCount += 1
+      readmeReferenceCount += 1
+      if (match[1] !== expectedVersion) {
+        staleReferences.push(
+          `${file}:${index + 1} pins ${match[0]} in the success-criteria section but package.json is ${expectedVersion}`,
+        )
+      }
+    }
+  }
+}
+
+if (staleReferences.length > 0 || anchorFailures.length > 0) {
+  console.error('')
+  if (staleReferences.length > 0) {
+    console.error(`README release references are stale (package.json is ${expectedVersion}):`)
+    for (const reference of staleReferences) console.error(`  ${reference}`)
+  }
+  if (anchorFailures.length > 0) {
+    console.error('README guard anchors/phrases no longer resolve:')
+    for (const failure of anchorFailures) console.error(`  ${failure}`)
+  }
+  console.error(`dsh-scout release gate: FAIL - bump the install/artifact references before releasing`)
+  console.error('(the same rule is asserted on every `npm test` in tests/package.test.mjs)')
+  process.exit(1)
+}
+console.log(`  readme release references: ${readmeReferenceCount} checked (${sectionTokenCount} inside the success-criteria section), all pinned to ${expectedVersion}`)
+
 run('npm', ['test'])
 
 const regressions = []

package/tests/acceptance.test.mjs

@@ -23,7 +23,11 @@
  *   7. lazy rehydration from `<scoutDir>/<caseId>/`, including the case-id guard
  *      that stops an export of another case being adopted;
  *   8. `language: 'en'` end to end (including the persisted `report.md`) and the
- *      unchanged `zh-CN` byte shape.
+ *      unchanged `zh-CN` byte shape;
+ *   9. the release literal, pinned in three independent places at once: the
+ *      exported `PLUGIN_VERSION` constant, `package.json`, and the `/scout status`
+ *      line — the one surface that can name the version, because reaching it
+ *      already proves the plugin loaded.
  *
  * Round 1 of this suite pinned six defects as *characterization* tests; round 2
  * pinned a seventh as a *documented boundary* (`D10`). All seven were fixed and
@@ -45,8 +49,9 @@
  */
 import test from 'node:test'
 import assert from 'node:assert/strict'
+import { readFileSync } from 'node:fs'
 import { assertSupportedJsonSchema, validateJsonSchemaValue } from '@deepseek-ai/dsh-tools'
-import { Config, apply } from '../dist/index.js'
+import { Config, PLUGIN_VERSION, apply } from '../dist/index.js'
 import { CLAIM_DIMENSIONS, EXPORT_FILE_NAMES, scoutStrings } from '../dist/model.js'
 
 /* ------------------------------------------------------------------ *
@@ -1682,3 +1687,58 @@ test('the /scout command exposes four working sub-actions and the scout Skill ca
   assert.equal((await invoke('status missing')).kind, 'error')
   assert.match((await invoke('status missing')).text, /Unknown case: missing/)
 })
+
+/* ------------------------------------------------------------------ *
+ * 11b. T-C · the loaded version, stated where a user can actually read it
+ *
+ * A load-time version banner was implemented, measured against a real
+ * `dsh --profile` boot, and rejected: cordis' only built-in exporter writes to
+ * an in-memory ring buffer, so `ctx.logger(name).info(...)` reaches no DSH
+ * surface at all (stdout and stderr both stayed byte-empty while direct writes
+ * from the same plugin appeared on both), nothing in DSH reads that buffer, and
+ * in the desktop App the host's stdout is piped to `/dev/null` while its stderr
+ * is kept only as a 64 KiB tail used when the host dies. A plugin that a peer
+ * conflict disabled never runs at all, so it can log nothing either way.
+ *
+ * `/scout status` is therefore the one honest place: reaching that branch
+ * already proves this exact version is the one that loaded.
+ * ------------------------------------------------------------------ */
+
+test('T-C · one release literal across the exported constant, package.json and /scout status', async () => {
+  // Hardcoded on purpose, mirroring `RELEASE_VERSION` in tests/package.test.mjs:
+  // reading the version back out of package.json and comparing it to itself
+  // would assert nothing. This literal is the third, independent statement, so a
+  // bump that updates the manifest but forgets the constant (or vice versa)
+  // fails here instead of shipping a mislabelled build.
+  const RELEASE_VERSION = '0.9.3'
+
+  assert.equal(PLUGIN_VERSION, RELEASE_VERSION, 'the exported constant must be the release literal')
+  const manifest = JSON.parse(readFileSync(new URL('../package.json', import.meta.url), 'utf8'))
+  assert.equal(manifest.version, RELEASE_VERSION, 'package.json must carry the same release literal')
+
+  const commands = []
+  const harness = createHarness()
+  harness.ctx.mount('commands', { register: definition => { commands.push(definition); return () => {} } })
+  await call(
+    harness,
+    'scout_start',
+    { caseId: 'ver', companyName: 'Version Co', roleTitle: 'HR Head', location: '' },
+    execFor('version-session'),
+  )
+
+  const invoke = rawInput => commands[0].handler({ rawInput, agent: { id: 'version-session' } })
+  const status = await invoke('status ver')
+  assert.equal(status.kind, 'success')
+  assert.ok(
+    status.text.endsWith(` · dsh-scout ${RELEASE_VERSION}`),
+    `status must end with the loaded version, got: ${status.text}`,
+  )
+  // Trailing, so the case facts remain the leading, greppable part of the line.
+  assert.match(
+    status.text,
+    /^\[ver\] VERIFY · identity needs_verification · sources 0 \/ claims 0 \(verified 0, open 0\) /,
+  )
+  // The version belongs to the plugin, not to the case: no other sub-action
+  // states it, and the usage line stays byte-identical.
+  assert.equal((await invoke('')).text, 'usage: /scout status <caseId> | /scout questions <caseId> | /scout report <caseId> | /scout export <caseId> [targetDir]')
+})