dsh-plugin-cicd 0.5.0 → 0.5.1

package/index.js

@@ -667,6 +667,58 @@ function firstLine(value) {
 /** How many changed file names the overview carries; the count is carried in full. */
 const LOCAL_FILE_LIMIT = 20
 
+/**
+ * Ask repeatedly whether a comment can be read back, and answer honestly either way.
+ *
+ * The reader is injected because the interesting part is the RETRY, and the route that
+ * uses it cannot be driven in a test — reaching a real post needs a readable release
+ * list, and the suite deliberately hands the Host a `gh` that cannot exist.
+ *
+ * @param {object} params - `{read, aid, rpid, attempts, delayMs, wait}`.
+ * @returns {Promise<{visible: boolean, attempts: number, code: number|null, message: string}>}
+ */
+export async function confirmVisible({
+  read,
+  aid,
+  rpid,
+  attempts = 3,
+  delayMs = 3000,
+  wait = (ms) => new Promise((settle) => setTimeout(settle, ms)),
+}) {
+  let last = { code: null, message: '' }
+  for (let attempt = 1; attempt <= attempts; attempt += 1) {
+    const found = await read(aid, rpid)
+    if (found !== null && found !== undefined && found.ok === true && found.visible === true) {
+      return { visible: true, attempts: attempt, code: 0, message: '' }
+    }
+    last = { code: found?.code ?? null, message: String(found?.message ?? '') }
+    if (attempt < attempts) await wait(delayMs)
+  }
+  return { visible: false, attempts, code: last.code, message: last.message }
+}
+
+/** A clone moves a repository, not a request: give it minutes, not seconds. */
+const CLONE_TIMEOUT_MS = 180_000
+
+/**
+ * The address `git clone` would use for a repository, when nothing better was given.
+ *
+ * Derived rather than demanded — the panel exists to remove steps, and "paste the clone
+ * URL of the repository you already registered" is one of them. A bare name needs
+ * `owner` from the config; a name written `owner/repo` does not.
+ *
+ * @param {string} owner - the configured owner, possibly ''.
+ * @param {string} repo - the repository id as configured.
+ * @returns {string} an https URL, or '' when there is nothing to derive it from.
+ */
+export function defaultCloneUrl(owner, repo) {
+  const name = text(repo).trim()
+  if (name === '') return ''
+  if (name.includes('/')) return `https://github.com/${name.replace(/^\/+|\/+$/g, '')}.git`
+  const login = text(owner).trim()
+  return login === '' ? '' : `https://github.com/${login}/${name}.git`
+}
+
 /**
  * The path out of one `git status --porcelain` line.
  *
@@ -1834,6 +1886,13 @@ export async function collectRepo({ config, ghPath, entry }) {
     slug,
     label: entry.label !== '' ? entry.label : entry.repo,
     localPath: entry.localPath,
+    /*
+     * What a 克隆 would use, and where it would land. Sent with the overview so the
+     * panel can offer the address pre-filled instead of asking someone to type a URL
+     * the Host can already derive from the repository name.
+     */
+    cloneUrl: defaultCloneUrl(config.owner, entry.repo),
+    checkoutRoot: config.projectsRoot,
     problems: [],
   }
   if (slug === null) {
@@ -3700,8 +3759,15 @@ export function apply(ctx, rawConfig) {
       return
     }
     const outcome = mutateConfig(current, (draft) => {
-      const entry = { repo, ...(localPath !== '' ? { localPath } : {}), label: '' }
       const index = draft.repos.findIndex((candidate) => candidate.repo === repo)
+      /* Merged into whatever is already there, not written over it: this route is also
+         how a path gets set, and rebuilding the entry from scratch would drop the
+         Bilibili binding — a video unbound as a side effect of editing a directory. */
+      const entry = {
+        ...(index === -1 ? {} : draft.repos[index]),
+        repo,
+        ...(localPath !== '' ? { localPath } : {}),
+      }
       if (index === -1) draft.repos.push(entry)
       else draft.repos[index] = entry
       return { ok: true, owner: draft.owner, repos: draft.repos }
@@ -3713,6 +3779,132 @@ export function apply(ctx, rawConfig) {
     writeJson(res, 200, { ok: true, value: { repo, localPath, registered: outcome.count, file: current.configFile } })
   }
 
+  /**
+   * Clone a registered repository into the checkout root, and record where it landed.
+   *
+   * The missing step for a repository that is registered but has no working tree:
+   * everything the console does with one — the dirty chip, 提交, 构建, 发布 — needs it,
+   * and until now the answer was "go and clone it yourself".
+   *
+   * The address is derived from the repository name unless one is given, and the panel
+   * shows that same derivation pre-filled (`cloneUrl` in the overview), because being
+   * asked to paste the clone URL of a repository the Host can already name is exactly
+   * the kind of step this console exists to remove. The destination is
+   * `projectsRoot/<name>`, which is where `findLocalCheckout` would look for it next.
+   */
+  const cloneHandler = async (req, res) => {
+    if (!guard(req, res)) return
+    const body = await readJsonBody(req)
+    const current = live()
+    const target = findEntry(current, body)
+    if (!target.ok) {
+      writeJson(res, 400, { ok: false, code: 'bad-request', message: target.message })
+      return
+    }
+    const entry = target.entry
+
+    /* Already there: say so rather than making a second copy beside the first. */
+    if (entry.localPath !== '') {
+      const existing = await readLocalState(entry.localPath, current.requestTimeoutMs)
+      if (existing.available === true) {
+        writeJson(res, 409, {
+          ok: false,
+          code: 'already-cloned',
+          message: `这个仓库已经有本地检出了：${entry.localPath}`,
+          value: { repo: entry.repo, path: entry.localPath },
+        })
+        return
+      }
+    }
+
+    const requestedUrl = text(body?.url).trim()
+    const url = requestedUrl !== '' ? requestedUrl : defaultCloneUrl(current.owner, entry.repo)
+    if (url === '') {
+      writeJson(res, 400, {
+        ok: false,
+        code: 'no-url',
+        message: '没有可用的仓库地址：填一个，或者把行配置写成 "owner/repo"',
+        value: { repo: entry.repo },
+      })
+      return
+    }
+    /* A shell is never involved, so this is not about injection: it is about not asking
+       git to fetch something that is not a repository address at all. */
+    if (!/^(https?:\/\/|git@|ssh:\/\/|file:\/\/|\/|[A-Za-z]:[\\/])/.test(url)) {
+      writeJson(res, 400, { ok: false, code: 'bad-url', message: `不像是 git 地址：${JSON.stringify(url)}`, value: { repo: entry.repo } })
+      return
+    }
+
+    const requestedDirectory = text(body?.directory).trim()
+    if (requestedDirectory !== '' && !isAbsolute(requestedDirectory)) {
+      writeJson(res, 400, { ok: false, code: 'bad-request', message: 'directory must be absolute', value: { repo: entry.repo } })
+      return
+    }
+    const directory = requestedDirectory !== ''
+      ? requestedDirectory
+      : (current.projectsRoot === '' ? '' : join(current.projectsRoot, bareRepoName(entry.repo)))
+    if (directory === '') {
+      writeJson(res, 409, {
+        ok: false,
+        code: 'no-projects-root',
+        message: '`projectsRoot` 还没设置，所以不知道该克隆到哪里：在 profile 的 cordis.patch.yml 里给它一个绝对路径，或者指定一个目录。',
+        value: { repo: entry.repo },
+      })
+      return
+    }
+    if (existsSync(directory)) {
+      let occupied = true
+      try {
+        occupied = readdirSync(directory).length > 0
+      } catch {
+        /* Unreadable counts as occupied: cloning into it could destroy something. */
+        occupied = true
+      }
+      if (occupied === true) {
+        writeJson(res, 409, {
+          ok: false,
+          code: 'target-exists',
+          message: `${directory} 已经存在且不是空的；换一个目录，或者先把它移走。`,
+          value: { repo: entry.repo, path: directory },
+        })
+        return
+      }
+    }
+
+    const cloned = await runTool('git', ['clone', '--', url, directory], CLONE_TIMEOUT_MS)
+    if (cloned.ok !== true) {
+      writeJson(res, 502, {
+        ok: false,
+        code: 'clone-failed',
+        message: commandFailureLine(cloned, 'git clone failed'),
+        value: { repo: entry.repo, url, path: directory },
+      })
+      return
+    }
+    const outcome = mutateConfig(current, (draft) => {
+      const index = draft.repos.findIndex((candidate) => candidate.repo === entry.repo)
+      if (index === -1) return { ok: false, message: `not registered: ${entry.repo}` }
+      /* The rest of the entry is kept. A clone is about where the working tree is, and
+         rebuilding the entry without its `bilibili` would unbind a video as a side
+         effect of pointing the console at a checkout. */
+      draft.repos[index] = { ...draft.repos[index], localPath: directory }
+      return { ok: true, owner: draft.owner, repos: draft.repos }
+    })
+    cache = null
+    if (outcome.ok !== true) {
+      /* The clone is on disk; only the bookkeeping failed. Saying which is the
+         difference between "clone it again" and "fix the config". */
+      writeJson(res, 502, {
+        ok: false,
+        code: 'config-failed',
+        message: `已克隆到 ${directory}，但写不进配置：${outcome.message}`,
+        value: { repo: entry.repo, path: directory, url },
+      })
+      return
+    }
+    writeJson(res, 200, { ok: true, value: { repo: entry.repo, path: directory, url, branch: null } })
+  }
+
   /** Unregister a repository. */
   const configRemoveHandler = async (req, res) => {
     if (!guard(req, res)) return
@@ -3920,16 +4112,75 @@ export function apply(ctx, rawConfig) {
     }
   }
 
+  /**
+   * Whether a comment Bilibili ACCEPTED can actually be read back.
+   *
+   * `code: 0` and an rpid mean the comment was taken, not that a reader can see it. Two
+   * of these comments were recorded as announced and then answered `12006 没有该评论`
+   * when looked up — a post that no one can find, filed as a success.
+   *
+   * Measured, so the waiting is not superstition: a freshly posted comment answers
+   * `12006` immediately and reads back from about four seconds. A single immediate check
+   * would therefore report a perfectly good comment as invisible, which is worse than not
+   * checking at all — so it asks, waits, and asks again.
+   *
+   * @returns {Promise<{visible: boolean, attempts: number, code: number|null, message: string}>}
+   */
+  const verifyVisible = async (cookie, aid, rpid, options = {}) => {
+    const client = bilibiliClient()
+    return await confirmVisible({
+      read: (video, comment) => client.readComment(cookie, video, comment),
+      aid,
+      rpid,
+      ...options,
+    })
+  }
+
   /** The comment one release would produce, in the configured template. */
-  const composeForEntry = (current, entry, release) => composeComment({
+  const composeForEntry = (current, entry, release, commits = null) => composeComment({
     label: entry.label !== '' ? entry.label : entry.repo,
     repo: entry.repo,
     tag: typeof release?.tag === 'string' ? release.tag : '',
     release,
+    commits,
     template: current.bilibiliTemplate,
     date: new Date().toISOString().slice(0, 10),
   })
 
+  /**
+   * What changed between the previous release and this one.
+   *
+   * The release itself cannot answer this for these repositories: their bodies are
+   * exactly `**Full Changelog**: <url>`, because the release workflow creates them with
+   * no notes. So the changes are read from the history GitHub already has — one compare
+   * call between the two tags — which is also the only source that is true rather than
+   * retyped.
+   *
+   * Best effort by design: an unreadable range is not a reason to hold back a comment
+   * that the release itself can still describe, so every failure answers with no commits
+   * and the composition falls back the way it always did.
+   *
+   * @returns {Promise<object[]>} compare entries, or an empty array.
+   */
+  const readReleaseChanges = async (current, entry, release) => {
+    const slug = resolveSlug(current.owner, entry.repo)
+    const tag = typeof release?.tag === 'string' ? release.tag : ''
+    if (slug === null || tag === '') return []
+    const list = await ghJson(ghPath, ['api', `repos/${slug}/releases?per_page=30`], current.requestTimeoutMs)
+    if (list.ok !== true || !Array.isArray(list.value)) return []
+    const published = list.value
+      .filter((item) => item !== null && typeof item === 'object' && item.draft !== true && typeof item.tag_name === 'string')
+      /* Newest first, sorted here rather than trusted: the API happens to return that
+         order, and the "previous release" this picks must not depend on a habit. */
+      .sort((left, right) => String(right.created_at ?? '').localeCompare(String(left.created_at ?? '')))
+    const at = published.findIndex((item) => item.tag_name === tag)
+    const previous = at >= 0 ? published[at + 1] : undefined
+    if (previous === undefined) return []
+    const compare = await ghJson(ghPath, ['api', `repos/${slug}/compare/${previous.tag_name}...${tag}`], current.requestTimeoutMs)
+    if (compare.ok !== true) return []
+    return Array.isArray(compare.value?.commits) ? compare.value.commits : []
+  }
+
   /**
    * Post one release's update note, and record what happened either way.
    *
@@ -3966,7 +4217,7 @@ export function apply(ctx, rawConfig) {
         value: { repo: entry.repo, bvid: binding.bvid },
       }
     }
-    const composed = composeForEntry(current, entry, release)
+    const composed = composeForEntry(current, entry, release, await readReleaseChanges(current, entry, release))
     const message = (text !== '' ? text : composed.text).trim()
     if (message === '') {
       return { ok: false, code: 'empty-comment', message: '评论内容是空的，没有发送。', value: { repo: entry.repo, tag: release.tag } }
@@ -3989,6 +4240,10 @@ export function apply(ctx, rawConfig) {
       bvid: binding.bvid,
       message,
     })
+    /* Accepted is not the same as readable. Ask, wait, ask again — see `verifyVisible`. */
+    const verified = posted.ok === true && posted.rpid !== null
+      ? await verifyVisible(cookieHeader(cookies), video.aid, posted.rpid)
+      : null
     const previous = findLedgerEntry(read.ledger, entry.repo, release.tag)
     const attempts = (Number.isFinite(previous?.attempts) ? Number(previous.attempts) : 0) + (posted.ok === true ? 0 : 1)
     const record = {
@@ -4005,6 +4260,13 @@ export function apply(ctx, rawConfig) {
       message: posted.message,
       failure: posted.ok === true ? null : posted.failure.kind,
       url: posted.ok === true && posted.rpid !== null ? `https://www.bilibili.com/video/${binding.bvid}/#reply${posted.rpid}` : null,
+      /*
+       * Whether a reader can find it, which is the fact the panel has been asserting
+       * without knowing. `null` means the question was never asked (the post failed), and
+       * an absent field means the same for entries written before this existed.
+       */
+      visible: verified === null ? null : verified.visible === true,
+      visibleCode: verified === null ? null : verified.code,
     }
     const stored = appendLedger(record)
     if (posted.ok !== true) {
@@ -4027,6 +4289,12 @@ export function apply(ctx, rawConfig) {
         account: account?.uname ?? '',
         video: video.title,
         trigger,
+        visible: record.visible,
+        /* Said in the answer rather than buried in the ledger: the panel has to be able
+           to tell "posted" from "posted and findable". */
+        note: record.visible === true
+          ? ''
+          : `已发送，但公开列表里读不到（B 站说：${String(verified?.message ?? '') === '' ? String(verified?.code ?? '') : String(verified?.message ?? '')}）——可能还在审核，也可能已被移除。可以稍后用【仍然发送】重发。`,
       },
     }
   }
@@ -4525,7 +4793,11 @@ export function apply(ctx, rawConfig) {
       ledger: read.ledger,
       force,
     })
-    const composed = release === null ? null : composeForEntry(current, target.entry, release)
+    /* The preview and the post read the same changes, so the sentence the panel shows is
+       the sentence that goes out — including the commit list. */
+    const composed = release === null
+      ? null
+      : composeForEntry(current, target.entry, release, await readReleaseChanges(current, target.entry, release))
 
     if (body?.dryRun === true) {
       writeJson(res, 200, {
@@ -4592,6 +4864,10 @@ export function apply(ctx, rawConfig) {
     [`${ROUTE_PREFIX}/auth-cancel`, authCancelHandler],
     [`${ROUTE_PREFIX}/auth-logout`, authLogoutHandler],
     [`${ROUTE_PREFIX}/repos-available`, reposAvailableHandler],
+    // A registered repository with no working tree cannot be released from here, so the
+    // console can fetch one: the address is derivable, and the destination is the root
+    // the rest of the panel already looks in.
+    [`${ROUTE_PREFIX}/clone`, cloneHandler],
     [`${ROUTE_PREFIX}/config-add`, configAddHandler],
     [`${ROUTE_PREFIX}/config-remove`, configRemoveHandler],
     // The third channel: an update note under the video that introduces the

package/lib/bilibili.mjs

@@ -42,8 +42,51 @@ export const REPLY_TYPE_VIDEO = 1
  * and a filtered comment looks exactly like a posted one from this side. The
  * release link is still available as `{url}` for anyone who wants it.
  */
+/**
+ * `{summary}` and not `{changes}`: the summary is the one that prefers whatever the
+ * release itself says, and only reaches for the commit list when the release is silent —
+ * which is what "介绍这次更新" wants in both cases. A template that would rather always
+ * show the commit subjects can say `{changes}`.
+ */
 export const DEFAULT_TEMPLATE = '【更新 {tag}】{summary}'
 
+/**
+ * How long a list of changes may be. Longer than a title, because this is the part that
+ * answers "更新了什么", and shorter than a comment can hold, because it is one line of
+ * a chat box rather than a changelog.
+ */
+export const MAX_CHANGES_LENGTH = 240
+
+/** What to say when the range held commits and none of them is news. */
+export const MAINTENANCE_NOTE = '本次更新为发布流程与工程维护，功能未变'
+
+/** Conventional-commit types, as words a viewer reads. */
+const CHANGE_LABELS = [
+  [/^feat(\(.+\))?!?:\s*/i, '新功能'],
+  [/^fix(\(.+\))?!?:\s*/i, '修复'],
+  [/^perf(\(.+\))?!?:\s*/i, '性能'],
+  [/^refactor(\(.+\))?!?:\s*/i, '重构'],
+]
+
+/**
+ * Types that describe the work rather than the plugin — including `docs`, which put
+ * "document the release procedure" in front of a viewer who came for the feature list.
+ */
+const BOOKKEEPING_SUBJECT = /^(ci|chore|test|build|style|revert|release|docs)(\(.+\))?!?:\s*/i
+
+/** `type(scope)!:` — the repository's convention, addressed to its authors. */
+const CONVENTIONAL_PREFIX = /^[A-Za-z]+(\([^)]*\))?!?:\s*/
+
+/** Sort key for a list that has room for three: what is new, before what was fixed. */
+function changeRank(entry) {
+  const raw = typeof entry === 'string' ? entry : String(entry?.commit?.message ?? '')
+  const subject = raw.split(/\r?\n/)[0]
+  if (/^(feat|perf)(\(.+\))?!?:\s*/i.test(subject)) return 0
+  if (/^(fix|refactor)(\(.+\))?!?:\s*/i.test(subject)) return 1
+  /* A subject with no conventional type is prose somebody wrote on purpose. */
+  return 0
+}
+
 /** The placeholders a template may use. Anything else is reported, not eaten. */
 export const TEMPLATE_KEYS = ['tag', 'version', 'label', 'repo', 'title', 'summary', 'url', 'date']
 
@@ -270,11 +313,21 @@ function isBoilerplate(line) {
  * @param {object} [options] - `{maxLength, fallback}`.
  * @returns {string} a plain-text summary, never longer than `maxLength`.
  */
-export function summarizeRelease(release, { maxLength = MAX_SUMMARY_LENGTH, fallback = '' } = {}) {
+export function summarizeRelease(release, { commits = null, names = [], maxLength = MAX_SUMMARY_LENGTH, fallback = '' } = {}) {
   const tag = typeof release?.tag === 'string' ? release.tag : ''
   const version = tag.replace(/^v/, '')
   const name = stripMarkdown(release?.name)
-  const nameIsNoise = name === '' || name === tag || name === version || name === `v${version}`
+  const nameIsNoise = name === '' || name === tag || name === version || name === `v${version}` ||
+    /* `<repo> v1.0.1` says exactly as much as `v1.0.1` does, and the release workflow
+       names every release that way — so treating it as a summary buries every real
+       change behind the one line that carries none. Which is what it did: the comments
+       read "【更新 v1.0.1】<repo> v1.0.1" and the commit list was never reached. */
+    names.some((candidate) => {
+      const base = stripMarkdown(candidate)
+      if (base === '') return false
+      return name === `${base} ${tag}` || name === `${base} ${version}` || name === `${base} v${version}` ||
+        name === `${base}: ${tag}` || name === `${base}: ${version}` || name === `${base}: v${version}`
+    })
   if (!nameIsNoise) return clamp(name, maxLength)
 
   const lines = String(release?.body ?? '')
@@ -283,9 +336,88 @@ export function summarizeRelease(release, { maxLength = MAX_SUMMARY_LENGTH, fall
     .filter((line) => !isBoilerplate(line))
   const joined = lines.slice(0, 3).join(' ').trim()
   if (joined !== '') return clamp(joined, maxLength)
+
+  /*
+   * The commits, when the release says nothing itself.
+   *
+   * This is the normal case for these repositories: their releases carry a body of
+   * exactly `**Full Changelog**: <url>` and nothing else, because the release workflow
+   * creates them without notes. So "介绍这次更新" cannot come from the release — the
+   * only place the changes exist is the history between the two tags.
+   */
+  const fromCommits = summarizeCommits(commits, { maxLength: MAX_CHANGES_LENGTH })
+  if (fromCommits !== '') return fromCommits
   return clamp(stripMarkdown(fallback), maxLength)
 }
 
+/**
+ * What changed, out of the commits between two releases.
+ *
+ * Subjects only, and the ones a reader of a video comment would recognise: a merge
+ * commit, a release chore or a `[skip ci]` marker is bookkeeping, not news. Joined with
+ * `；` rather than newlines because a Bilibili comment is a chat box, not a changelog.
+ *
+ * @param {unknown} commits - GitHub compare entries (`{commit: {message}, author}`) or plain strings.
+ * @param {object} [options] - `{max, maxLength}`.
+ * @returns {string} the summary, empty when nothing survives the filter.
+ */
+export function summarizeCommits(commits, { max = 3, maxLength = MAX_CHANGES_LENGTH } = {}) {
+  const list = Array.isArray(commits) ? commits : []
+  if (list.length === 0) return ''
+  const seen = new Set()
+  const kept = []
+  /*
+   * Newest first, and features before fixes.
+   *
+   * The compare API hands them oldest first, and taking the first three of that put the
+   * EARLIEST work of a release in the comment — for v0.5.0, three npm details, while the
+   * 提交 button, the Bilibili note and the one-page settings that the release is actually
+   * about were cut off the end. A version culminates in what it is for, and among equals
+   * a feature is what "what's new" means.
+   */
+  const ordered = [...list].reverse().sort((left, right) => changeRank(left) - changeRank(right))
+  for (const entry of ordered) {
+    const raw = typeof entry === 'string' ? entry : String(entry?.commit?.message ?? '')
+    const subject = raw.split(/\r?\n/)[0].trim()
+    if (subject === '') continue
+    if (/^merge\b/i.test(subject)) continue
+    /* A build tweak is not a change a viewer of the video can see. Filtering these out
+       is the difference between "what is new" and a wall of `ci:` — which is what the
+       first version of this produced, cut off mid-sentence at 90 characters. */
+    if (BOOKKEEPING_SUBJECT.test(subject)) continue
+    if (/\[skip ci\]/i.test(subject)) continue
+    let clean = stripMarkdown(subject).replace(/\s*\(#\d+\)\s*$/, '').trim()
+    if (clean === '') continue
+    /*
+     * `fix: stop the flashing` reads as a changelog line to its author and as jargon to
+     * everyone else, so a known type becomes a word. An UNKNOWN one still loses its
+     * prefix — `polish(bilibili): size the code` is a sentence with a scope in front of
+     * it, and the scope belongs to the repository's conventions, not to the viewer. The
+     * message itself is left exactly as written: these histories are in English, and
+     * translating them by machine would be inventing meaning.
+     */
+    let label = ''
+    for (const [pattern, text] of CHANGE_LABELS) {
+      if (pattern.test(clean)) {
+        label = text
+        break
+      }
+    }
+    clean = clean.replace(CONVENTIONAL_PREFIX, '').trim()
+    if (clean === '') continue
+    if (label !== '') clean = `${label}：${clean}`
+    if (seen.has(clean)) continue
+    seen.add(clean)
+    kept.push(clean)
+    if (kept.length >= Math.max(1, max)) break
+  }
+  /* Commits existed and none of them is news — that is itself worth saying, and it is
+     not the same as having no history to read (which answers '' and lets the caller fall
+     back). A version that only moved CI should not read as an empty announcement. */
+  if (kept.length === 0) return MAINTENANCE_NOTE
+  return clamp(kept.join('；'), maxLength)
+}
+
 /** Cut a string to a length, on a word boundary when there is one. */
 function clamp(value, maxLength) {
   const text = typeof value === 'string' ? value : ''
@@ -324,9 +456,16 @@ export function renderTemplate(template, vars) {
  * @param {object} params - `{label, repo, tag, release, template, date, fallback}`.
  * @returns {{text: string, unknown: string[], summary: string, truncated: boolean}} the comment and what it could not resolve.
  */
-export function composeComment({ label = '', repo = '', tag = '', release = null, template = '', date = '', fallback = '' } = {}) {
+export function composeComment({ label = '', repo = '', tag = '', release = null, template = '', date = '', fallback = '', commits = null } = {}) {
   const effectiveTag = tag !== '' ? tag : (typeof release?.tag === 'string' ? release.tag : '')
-  const summary = summarizeRelease({ ...release, tag: effectiveTag }, { fallback })
+  /* `{changes}` is the same material `{summary}` falls back to, exposed on its own so a
+     template can say "本版更新：{changes}" without depending on what the release body
+     happened to contain. */
+  const changes = summarizeCommits(commits)
+  /* The names a release title could be made of, so `dsh-ui-sound v0.1.1` counts as the
+     tag it repeats rather than as a description of the change. */
+  const names = [label !== '' ? label : repo, repo, String(repo).slice(String(repo).lastIndexOf('/') + 1)]
+  const summary = summarizeRelease({ ...release, tag: effectiveTag }, { commits, names, fallback })
   const rendered = renderTemplate(template, {
     tag: effectiveTag,
     version: effectiveTag.replace(/^v/, ''),
@@ -334,6 +473,7 @@ export function composeComment({ label = '', repo = '', tag = '', release = null
     repo,
     title: stripMarkdown(release?.name),
     summary,
+    changes,
     url: typeof release?.url === 'string' ? release.url : '',
     date,
   })
@@ -755,6 +895,44 @@ export function createBilibiliClient({ fetchImpl = globalThis.fetch, timeoutMs =
       }
     },
 
+    /**
+     * Read one comment back by its id.
+     *
+     * The only way to know a comment is really there: `x/v2/reply/add` answers `code: 0`
+     * with an rpid for a comment the public listing may not serve at all, and a removed
+     * comment and one still in review are indistinguishable through this endpoint —
+     * `12006 没有该评论` is Bilibili's answer to both. So the answer here is deliberately
+     * two-valued: it is readable, or it is not, and why not is Bilibili's own sentence.
+     *
+     * @param {string} cookie - the `Cookie:` header value.
+     * @param {number} aid - the video's oid.
+     * @param {string} rpid - the comment to look for.
+     * @returns {Promise<object>} `{ok, visible, code, message, text}`.
+     */
+    async readComment(cookie, aid, rpid) {
+      const query = `type=1&oid=${encodeURIComponent(String(aid))}&root=${encodeURIComponent(String(rpid))}&ps=20&pn=1`
+      const result = await get(`https://api.bilibili.com/x/v2/reply/reply?${query}`, {
+        cookie,
+        referer: 'https://www.bilibili.com/',
+      })
+      if (result.payload === null) {
+        return { ok: false, visible: false, code: null, message: result.error ?? `HTTP ${String(result.status)}`, text: '' }
+      }
+      const payload = result.payload
+      if (payload.code !== 0) {
+        return { ok: true, visible: false, code: Number(payload.code), message: String(payload.message ?? ''), text: '' }
+      }
+      const root = payload.data?.root ?? null
+      const visible = root !== null && root !== undefined && String(root.rpid ?? '') === String(rpid)
+      return {
+        ok: true,
+        visible,
+        code: 0,
+        message: visible ? '' : '这条评论不在公开列表里',
+        text: String(root?.content?.message ?? ''),
+      }
+    },
+
     /**
      * A device id, best effort.
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-cicd",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "发布台（Release Console）for DeepSeek Harness: a sidebar entry and a full main-panel page that show what each repository has built, what it has released, whether the local checkout is ahead of the release, whether the copy installed in this profile is the published artifact, and which version npm holds — with buttons to trigger a build, cut a release, publish a draft, push that version to npm, install the release into the profile, and hand a restart to dsh-plugin-restart. It also carries the third channel: when a repository's release goes public, one short update note is posted under the video that introduces the plugin, with the credential obtained from a Bilibili sign-in inside the panel. Reuses the machine's authenticated gh CLI and the Host's own package manager, so the plugin stores no GitHub or npm credential of its own; the one credential it does own is the Bilibili session it created, kept in its own directory and never echoed back.",
   "type": "module",
   "icon": "./icon.svg",