@morehao/dsh-github-trending 0.5.2 → 0.6.0

package/lib/index.js

@@ -8,7 +8,7 @@ import {
   createTrendingRunTool,
   createUpdateService,
   readPluginInfo
-} from "./chunk-6HITSHK6.js";
+} from "./chunk-WDBZAMWN.js";
 import "./chunk-R7BK7SJK.js";
 
 // src/index.ts
@@ -57,6 +57,10 @@ function apply(ctx, config = {}) {
       const summary = await runner.run({ trigger: "schedule", period });
       log("schedule.run", { period, ok: summary.ok, skipped: summary.skipped, error: summary.error?.code });
     },
+    runReleases: async () => {
+      const record = await runner.runReleases({ trigger: "schedule" });
+      log("schedule.release", { id: record.id, status: record.status, checked: record.checked, changed: record.changed });
+    },
     onError: (error) => ctx.logger?.warn?.(`[dsh-github-trending] \u5B9A\u65F6\u8FD0\u884C\u5931\u8D25\uFF1A${error instanceof Error ? error.message : String(error)}`)
   });
   const pluginInfo = readPluginInfo();

package/lib/internal.d.ts

@@ -112,6 +112,46 @@ interface RunOutcome {
     durationMs: number;
     coreVersion: string;
 }
+/**
+ * 契约 0.4.0（核心 0.7.0）新增的 wire 类型。
+ *
+ * 契约包尚未发布：npm 上的 `@morehao/trendradar-contract` 还停在 0.3.0，
+ * 因此这三块按 `contract/schema/releases.v2.json` 原样在本地声明，等 0.4.0 发布后
+ * 改回 `@morehao/trendradar-contract` 的 `import type`。除这里列出的字段外，
+ * 不补任何契约里没有的东西——本地声明只是「包还没发」的临时载体，不是第二份契约。
+ */
+type SubscriptionStatus = 'baseline' | 'ok' | 'no_change' | 'rate_limited' | 'failed';
+/** 订阅表的一行：只放列表展示需要的字段，正文在 `SubscriptionDoc` 里（首屏体积预算）。 */
+interface SubscriptionItem {
+    fullName: string;
+    url?: string;
+    latestTag?: string;
+    latestSummaryAt?: string;
+    lastCheckedAt?: string;
+    status: SubscriptionStatus;
+}
+/** 发版文档的一卷：每册都带两位序号，index N 是 `<repo>-0N.md`（第 1 册是 `-01`）。 */
+interface SubscriptionVolume {
+    index: number;
+    file: string;
+    from?: string;
+    to?: string;
+    lines?: number;
+}
+/** 一个仓库某卷的发版文档；`markdown` 是文件原文，面板逐字渲染、不再二次摘要。 */
+interface SubscriptionDoc {
+    fullName: string;
+    volume: number;
+    volumes?: SubscriptionVolume[];
+    updatedAt?: string;
+    markdown: string;
+}
+declare function isSubscriptionStatus(value: unknown): value is SubscriptionStatus;
+/**
+ * `SubscriptionDoc` 的运行时守卫：缺 fullName/volume/markdown 的负载宁可抛
+ * `IPC_INVALID`，也不要让界面拿到半份文档（正文缺失时渲染会崩，比报错更难查）。
+ */
+declare function isSubscriptionDoc(value: unknown): value is SubscriptionDoc;
 declare class IpcError extends Error {
     readonly code: string;
     constructor(code: string, message: string);
@@ -139,24 +179,27 @@ interface ParseRunOptions {
  * 当成功写进状态。
  */
 declare function parseRunResult(text: string, options: ParseRunOptions): RunOutcome;
-/** 订阅命令的结果：list 带回 repos，add/remove 只看 ok/error。 */
+/** 订阅命令的结果：list 带回 repos/items，releases 带回 doc，add/remove 只看 ok/error。 */
 interface SubscribeOutcome {
     ok: boolean;
     repos: string[];
+    /** list 的逐仓库明细（契约 0.4.0）；旧核心不返回时为 undefined。 */
+    items?: SubscriptionItem[];
+    /** `action=releases` 读到的发版文档；其它 action 没有。 */
+    doc?: SubscriptionDoc;
     error?: RunError;
 }
 /** 订阅命令的一个动作（契约 `RunRequest.action`）。 */
-type SubscribeAction = 'list' | 'add' | 'remove';
+type SubscribeAction = 'list' | 'add' | 'remove' | 'releases';
 /**
  * 解析核心 `subscribe --json` 的 stdout。
  *
- * 核心先由 `runSubscribe` 把 `list` 的结果**逐行**打到 stdout（每行一个 owner/repo），
- * 再由 `emitSubscribeResult` 把契约 RunResult 信封打到 stdout（`command:"subscribe"`，
- * 只带 `ok/error`，**不含 repos**）。因此：
- *   - 信封是**最后一段 JSON**；它前面的非空行才是 list 的仓库列表；
- *   - 信封 `command` 是 `"subscribe"`（不在契约 RunResult 枚举里，故不能直接用
- *     `validators.runResult` 校验），这里只按 envelope 必需字段做轻量校验。
- * 任何形状不对都抛 `IPC_INVALID`：订阅结果读错会把失败当成功。
+ * 契约 0.4.0 起 payload 进了结果信封：`{command:"subscribe", subscriptions?, subscriptionDoc?}`。
+ * 这里**优先**读信封；旧核心（0.6.x 及以前）把 `list` 的结果逐行打到信封之前、信封里只有
+ * `ok/error`，因此保留逐行兜底——两种都能读，但绝不「猜字段」：
+ *   - 信封不是 `ipcSchema=2` 的对象 → `IPC_INVALID`；
+ *   - `subscriptions` 存在但形状不对 → `IPC_INVALID`（不是空列表）；
+ *   - `subscriptionDoc` 存在但不满足契约 → `IPC_INVALID`（界面不能拿到半份文档）。
  */
 declare function parseSubscribeResult(text: string): SubscribeOutcome;
 
@@ -178,16 +221,22 @@ declare const ipc_State: typeof State;
 declare const ipc_StateRun: typeof StateRun;
 type ipc_SubscribeAction = SubscribeAction;
 type ipc_SubscribeOutcome = SubscribeOutcome;
+type ipc_SubscriptionDoc = SubscriptionDoc;
+type ipc_SubscriptionItem = SubscriptionItem;
 declare const ipc_SubscriptionList: typeof SubscriptionList;
+type ipc_SubscriptionStatus = SubscriptionStatus;
+type ipc_SubscriptionVolume = SubscriptionVolume;
 declare const ipc_Usage: typeof Usage;
 type ipc_VersionInfo = VersionInfo;
+declare const ipc_isSubscriptionDoc: typeof isSubscriptionDoc;
+declare const ipc_isSubscriptionStatus: typeof isSubscriptionStatus;
 declare const ipc_isVersionInfo: typeof isVersionInfo;
 declare const ipc_parseJsonObject: typeof parseJsonObject;
 declare const ipc_parseRunResult: typeof parseRunResult;
 declare const ipc_parseSubscribeResult: typeof parseSubscribeResult;
 declare const ipc_parseVersionInfo: typeof parseVersionInfo;
 declare namespace ipc {
-  export { ipc_ErrorCode as ErrorCode, ipc_ErrorInfo as ErrorInfo, ipc_FileArtifact as FileArtifact, ipc_IPC_SCHEMA_VERSION as IPC_SCHEMA_VERSION, ipc_IpcError as IpcError, type ipc_ParseRunOptions as ParseRunOptions, ipc_ReleasesReport as ReleasesReport, type ipc_RunError as RunError, type ipc_RunOutcome as RunOutcome, ipc_RunRequest as RunRequest, ipc_RunResult as RunResult, ipc_SUPPORTED_CONTRACT_MAJOR as SUPPORTED_CONTRACT_MAJOR, ipc_SUPPORTED_DIGEST_SCHEMA as SUPPORTED_DIGEST_SCHEMA, ipc_State as State, ipc_StateRun as StateRun, type ipc_SubscribeAction as SubscribeAction, type ipc_SubscribeOutcome as SubscribeOutcome, ipc_SubscriptionList as SubscriptionList, ipc_Usage as Usage, type ipc_VersionInfo as VersionInfo, ipc_isVersionInfo as isVersionInfo, ipc_parseJsonObject as parseJsonObject, ipc_parseRunResult as parseRunResult, ipc_parseSubscribeResult as parseSubscribeResult, ipc_parseVersionInfo as parseVersionInfo };
+  export { ipc_ErrorCode as ErrorCode, ipc_ErrorInfo as ErrorInfo, ipc_FileArtifact as FileArtifact, ipc_IPC_SCHEMA_VERSION as IPC_SCHEMA_VERSION, ipc_IpcError as IpcError, type ipc_ParseRunOptions as ParseRunOptions, ipc_ReleasesReport as ReleasesReport, type ipc_RunError as RunError, type ipc_RunOutcome as RunOutcome, ipc_RunRequest as RunRequest, ipc_RunResult as RunResult, ipc_SUPPORTED_CONTRACT_MAJOR as SUPPORTED_CONTRACT_MAJOR, ipc_SUPPORTED_DIGEST_SCHEMA as SUPPORTED_DIGEST_SCHEMA, ipc_State as State, ipc_StateRun as StateRun, type ipc_SubscribeAction as SubscribeAction, type ipc_SubscribeOutcome as SubscribeOutcome, type ipc_SubscriptionDoc as SubscriptionDoc, type ipc_SubscriptionItem as SubscriptionItem, ipc_SubscriptionList as SubscriptionList, type ipc_SubscriptionStatus as SubscriptionStatus, type ipc_SubscriptionVolume as SubscriptionVolume, ipc_Usage as Usage, type ipc_VersionInfo as VersionInfo, ipc_isSubscriptionDoc as isSubscriptionDoc, ipc_isSubscriptionStatus as isSubscriptionStatus, ipc_isVersionInfo as isVersionInfo, ipc_parseJsonObject as parseJsonObject, ipc_parseRunResult as parseRunResult, ipc_parseSubscribeResult as parseSubscribeResult, ipc_parseVersionInfo as parseVersionInfo };
 }
 
 type Provider = string;
@@ -261,6 +310,18 @@ interface SummarizeSettings {
     enrichTimeoutSeconds: number;
     enrichBudgetSeconds: number;
 }
+/**
+ * 每周发版运行的插件侧节奏（核心没有这个字段，**绝不**写进核心 YAML）。
+ * 与榜单调度（`schedule.*`）完全独立：两者各有自己的开关与时间点。
+ */
+interface ReleaseScheduleSettings {
+    enabled: boolean;
+    /** ISO 星期：1=周一 … 7=周日（和 `Intl` 的 0=周日 不同，避免调用方来回换算）。 */
+    weekday: number;
+    /** `HH:MM[:SS]`（本地墙钟，按 timezone 解释）。 */
+    time: string;
+    timezone: string;
+}
 /**
  * 发版订阅阶段的行为参数（核心 `releases.*`）。
  * 阶段**常开**（`releases.enabled` 恒为 true，不出现在设置里）：有没有产出只由订阅列表决定，
@@ -273,10 +334,24 @@ interface ReleasesSettings {
     includeDrafts: boolean;
     fallbackToTags: boolean;
     baselineOnFirstRun: boolean;
+    /** 文档**列出**多少个版本（核心 0.7.0 起不再限制抓取条数，摘要覆盖全周）。 */
     perRepoLimit: number;
     maxNotesChars: number;
-    /** 发版摘要周期，独立默认 daily，不与 trending.since 联动。 */
+    /** 每仓库每周一条中文摘要的字数上限（核心 `releases.summaryMaxChars`）。 */
+    summaryMaxChars: number;
+    /** 每仓库文档的行数预算，超了核心才开新卷（核心 `releases.docMaxLines`）。 */
+    docMaxLines: number;
+    /** 订阅检查并发；`auto` 由插件按订阅数解析成 1–8 的数字（核心只认数字）。 */
+    concurrency: 'auto' | number;
+    /** 订阅阶段的模型预算秒数；`auto` 由插件按订阅数解析（核心只认数字）。 */
+    budgetSeconds: 'auto' | number;
+    /**
+     * 发版摘要周期。核心 0.7.0 只实现 `weekly`（一个 ISO 周一次模型调用），
+     * 因此这里保留枚举类型只为让校验能明确告诉用户「daily/monthly 已不支持」。
+     */
     period: Period;
+    /** 插件侧每周触发节奏；核心配置里只用到它的 `timezone`（切周口径），不写整个对象。 */
+    schedule: ReleaseScheduleSettings;
 }
 interface ScheduleSettings {
     enabled: boolean;
@@ -385,7 +460,13 @@ interface CoreConfig {
         baselineOnFirstRun: boolean;
         perRepoLimit: number;
         maxNotesChars: number;
-        period: string;
+        summaryMaxChars: number;
+        docMaxLines: number;
+        timezone: string;
+        weekStart: 'monday';
+        concurrency: number;
+        budgetSeconds: number;
+        period: 'weekly';
     };
     output: {
         dir: string;
@@ -397,8 +478,12 @@ interface CoreConfig {
  * 生成核心配置。`apiKey` 单独传入：它只能来自宿主凭据或用户当次输入，
  * 绝不来自 settings.json。`period` 是本次运行的标的周期；核心 `run --period`
  * 会用它覆盖 `trending.since`，这里同步写入以免旧核心/调试时口径不一致。
+ *
+ * `repoCount` 只用于把发版订阅的 `auto` 解析成数字（核心 0.7.0 的 YAML 只认整数）：
+ * 并发 = clamp(4, ceil(n/10), 8)，预算 = min(300, 30+3n)。显式数字永远优先。
+ * 不发版调度对象——`releases.schedule` 是纯插件概念，写进 YAML 核心会当成未知字段。
  */
-declare function toCoreConfig(settings: Settings, apiKey: string, baseURLOverride?: string, period?: Period): CoreConfig;
+declare function toCoreConfig(settings: Settings, apiKey: string, baseURLOverride?: string, period?: Period, repoCount?: number): CoreConfig;
 /**
  * 极简 YAML 序列化：只覆盖「对象/数组/字符串/数字/布尔」。
  * 字符串一律用 JSON 双引号形式——JSON 字符串是合法 YAML 标量，且能避免
@@ -421,6 +506,7 @@ type config_PRSettings = PRSettings;
 type config_Period = Period;
 type config_Problem = Problem;
 type config_Provider = Provider;
+type config_ReleaseScheduleSettings = ReleaseScheduleSettings;
 type config_ReleasesSettings = ReleasesSettings;
 type config_RepoSettings = RepoSettings;
 declare const config_SETTINGS_SECTIONS: typeof SETTINGS_SECTIONS;
@@ -441,7 +527,7 @@ declare const config_toCoreConfig: typeof toCoreConfig;
 declare const config_toYaml: typeof toYaml;
 declare const config_validateSettings: typeof validateSettings;
 declare namespace config {
-  export { type config_AuthMode as AuthMode, config_CORE_PROVIDERS as CORE_PROVIDERS, type config_CommitMode as CommitMode, type config_CoreConfig as CoreConfig, config_DEFAULT_SETTINGS as DEFAULT_SETTINGS, type config_Enrich as Enrich, type config_GithubSettings as GithubSettings, type config_ModelSettings as ModelSettings, type config_OutputSettings as OutputSettings, config_PERIODS as PERIODS, config_PROVIDER_BASE_URLS as PROVIDER_BASE_URLS, type config_PRSettings as PRSettings, type config_Period as Period, type config_Problem as Problem, type config_Provider as Provider, type config_ReleasesSettings as ReleasesSettings, type config_RepoSettings as RepoSettings, config_SETTINGS_SECTIONS as SETTINGS_SECTIONS, type config_ScheduleSettings as ScheduleSettings, type config_Settings as Settings, type config_SettingsSection as SettingsSection, type config_Since as Since, type config_SummarizeSettings as SummarizeSettings, type config_TrendingSettings as TrendingSettings, config_effectiveBaseURL as effectiveBaseURL, config_isEnrich as isEnrich, config_isPeriod as isPeriod, config_isValidTimezone as isValidTimezone, config_mergeSettingsSection as mergeSettingsSection, config_normalizeSettings as normalizeSettings, config_sectionOfField as sectionOfField, config_toCoreConfig as toCoreConfig, config_toYaml as toYaml, config_validateSettings as validateSettings };
+  export { type config_AuthMode as AuthMode, config_CORE_PROVIDERS as CORE_PROVIDERS, type config_CommitMode as CommitMode, type config_CoreConfig as CoreConfig, config_DEFAULT_SETTINGS as DEFAULT_SETTINGS, type config_Enrich as Enrich, type config_GithubSettings as GithubSettings, type config_ModelSettings as ModelSettings, type config_OutputSettings as OutputSettings, config_PERIODS as PERIODS, config_PROVIDER_BASE_URLS as PROVIDER_BASE_URLS, type config_PRSettings as PRSettings, type config_Period as Period, type config_Problem as Problem, type config_Provider as Provider, type config_ReleaseScheduleSettings as ReleaseScheduleSettings, type config_ReleasesSettings as ReleasesSettings, type config_RepoSettings as RepoSettings, config_SETTINGS_SECTIONS as SETTINGS_SECTIONS, type config_ScheduleSettings as ScheduleSettings, type config_Settings as Settings, type config_SettingsSection as SettingsSection, type config_Since as Since, type config_SummarizeSettings as SummarizeSettings, type config_TrendingSettings as TrendingSettings, config_effectiveBaseURL as effectiveBaseURL, config_isEnrich as isEnrich, config_isPeriod as isPeriod, config_isValidTimezone as isValidTimezone, config_mergeSettingsSection as mergeSettingsSection, config_normalizeSettings as normalizeSettings, config_sectionOfField as sectionOfField, config_toCoreConfig as toCoreConfig, config_toYaml as toYaml, config_validateSettings as validateSettings };
 }
 
 declare const PLUGIN_DIR_NAME = "github-trending";
@@ -548,6 +634,38 @@ interface PendingPr {
     /** 该 PR 对应的 digest 日期（YYYY-MM-DD）；用于判断「同日重跑」是否真的会撞分支。 */
     date?: string;
 }
+/**
+ * 一次发版订阅运行的记录（与榜单的 `RunRecord` 分开）。
+ *
+ * 为什么不复用 `history.json`：发版文档按周累积、一跑就是十几次 GitHub 请求 + 每周一次
+ * 模型调用，它的失败/限流节奏与榜单完全无关；混在一起会污染「今天榜单有没有产出」的判断。
+ * 计数语义由契约 `ReleasesReport` 定义：checked=检查过的仓库数，changed=真正写了文档的仓库数。
+ */
+interface ReleaseRunRecord {
+    id: string;
+    /** ISO 时间（UTC）。 */
+    startedAt: string;
+    /** ISO 时间（UTC）。 */
+    finishedAt: string;
+    status: 'ok' | 'failed' | 'skipped' | 'cancelled';
+    checked: number;
+    changed: number;
+    newTags: number;
+    summarized: number;
+    degraded: number;
+    failed: number;
+    rateLimited: number;
+    durationMs: number;
+    tokens?: number;
+    commit?: string;
+    prUrl?: string;
+    branch?: string;
+    errorCode?: string;
+    errorMessage?: string;
+    coreVersion?: string;
+}
+/** 发版运行记录上限：一周一次的话正好留半年，够复盘又不会让 state.json 膨胀。 */
+declare const RELEASE_RUN_LIMIT = 30;
 interface PluginState {
     lastRunAt?: string;
     /** 最近一次成功（ok=true，含 skipped）的运行时间；工具与界面读它。 */
@@ -557,6 +675,12 @@ interface PluginState {
     lastDigest?: DigestIdentity;
     lastResult?: RunRecord;
     pendingPr?: PendingPr;
+    /** 最近 30 次发版运行，最新在前；旧 state 里没有这个字段。 */
+    releaseRuns?: ReleaseRunRecord[];
+    /** 最近一次发版运行结束时间（失败也算）。 */
+    lastReleaseAt?: string;
+    /** 最近一次**成功**发版运行所属的 ISO 周（如 `2026-W44`），周去重键。 */
+    lastReleaseWeek?: string;
 }
 interface HistoryFile {
     records: RunRecord[];
@@ -597,6 +721,13 @@ declare class Store {
     private readHistoryRaw;
     /** 记录一次运行：历史裁剪到 HISTORY_LIMIT 条，state 同步更新。 */
     recordRun(record: RunRecord, next?: Partial<PluginState>): void;
+    /**
+     * 记录一次发版运行：只写 `state.json`（不发版记录进 `history.json`，两者节奏不同）。
+     * 记录裁剪到 RELEASE_RUN_LIMIT 条，`next` 用来顺带更新 lastReleaseAt/lastReleaseWeek。
+     */
+    appendReleaseRun(record: ReleaseRunRecord, next?: Partial<PluginState>): void;
+    /** 读发版运行记录；缺失/损坏（不是数组或行不是对象）一律按空数组处理，不让界面崩。 */
+    readReleaseRuns(): ReleaseRunRecord[];
     newLogPath(id: string): string;
     appendLog(file: string, line: string): void;
     hasLog(file: string): boolean;
@@ -631,6 +762,8 @@ declare const state_PREVIEW_MAX_BYTES: typeof PREVIEW_MAX_BYTES;
 type state_PendingPr = PendingPr;
 type state_PluginState = PluginState;
 type state_PreviewMeta = PreviewMeta;
+declare const state_RELEASE_RUN_LIMIT: typeof RELEASE_RUN_LIMIT;
+type state_ReleaseRunRecord = ReleaseRunRecord;
 type state_ReleasesSummary = ReleasesSummary;
 type state_RunRecord = RunRecord;
 type state_Store = Store;
@@ -640,7 +773,7 @@ declare const state_newRunId: typeof newRunId;
 declare const state_sumTokens: typeof sumTokens;
 declare const state_writeJsonAtomic: typeof writeJsonAtomic;
 declare namespace state {
-  export { state_CONTENT_HASH_ALGO_V2 as CONTENT_HASH_ALGO_V2, type state_DigestIdentity as DigestIdentity, state_HISTORY_LIMIT as HISTORY_LIMIT, type state_HistoryFile as HistoryFile, type state_LegacyMigrationResult as LegacyMigrationResult, state_PREVIEW_LIMIT as PREVIEW_LIMIT, state_PREVIEW_MAX_BYTES as PREVIEW_MAX_BYTES, type state_PendingPr as PendingPr, type state_PluginState as PluginState, type state_PreviewMeta as PreviewMeta, type state_ReleasesSummary as ReleasesSummary, type state_RunRecord as RunRecord, state_Store as Store, type state_StoreOptions as StoreOptions, state_newRunId as newRunId, state_sumTokens as sumTokens, state_writeJsonAtomic as writeJsonAtomic };
+  export { state_CONTENT_HASH_ALGO_V2 as CONTENT_HASH_ALGO_V2, type state_DigestIdentity as DigestIdentity, state_HISTORY_LIMIT as HISTORY_LIMIT, type state_HistoryFile as HistoryFile, type state_LegacyMigrationResult as LegacyMigrationResult, state_PREVIEW_LIMIT as PREVIEW_LIMIT, state_PREVIEW_MAX_BYTES as PREVIEW_MAX_BYTES, type state_PendingPr as PendingPr, type state_PluginState as PluginState, type state_PreviewMeta as PreviewMeta, state_RELEASE_RUN_LIMIT as RELEASE_RUN_LIMIT, type state_ReleaseRunRecord as ReleaseRunRecord, type state_ReleasesSummary as ReleasesSummary, type state_RunRecord as RunRecord, state_Store as Store, type state_StoreOptions as StoreOptions, state_newRunId as newRunId, state_sumTokens as sumTokens, state_writeJsonAtomic as writeJsonAtomic };
 }
 
 interface CoreRelease {
@@ -876,6 +1009,13 @@ interface RunCoreOptions {
     trigger?: 'manual' | 'schedule';
     /** 回环代理地址：覆盖配置里的 model.baseURL（代理模式专用）。 */
     baseURLOverride?: string;
+    /**
+     * 只跑指定阶段（核心 `run --stages`）。缺省 = 跑所有已启用阶段；
+     * `['releases']` 就是「只跑发版订阅」——不抓榜单、不渲染 digest、也不合并订阅 pending。
+     */
+    stages?: string[];
+    /** 订阅仓库数：用于把配置里的 `auto` 并发/预算解析成数字（发版运行传入）。 */
+    repoCount?: number;
     signal?: AbortSignal;
     timeoutMs?: number;
     onStderr?: (line: string) => void;
@@ -892,6 +1032,7 @@ declare function buildCoreArgs(channelPath: string, options: {
     dryRun: boolean;
     date?: string;
     period?: Period;
+    stages?: string[];
 }): string[];
 declare function runCore(options: RunCoreOptions): Promise<RunCoreResult>;
 
@@ -1422,6 +1563,37 @@ declare class Runner {
     runMany(options: RunRequestOptions & {
         periods?: Period[];
     }): Promise<RunSummary[]>;
+    /**
+     * 只跑发版订阅阶段（`run --stages releases`）。
+     *
+     * 与榜单运行共用同一把 `active` 锁：两条路径都会写同一份产物、读同一份订阅，
+     * 并发跑会互相踩分支。和 `run()` 的区别只有三点：不带 dryRun、写完只落
+     * `state.releaseRuns`（不碰 history.json）、自己**不**合并订阅 pending 队列
+     * （`--stages releases` 让核心跳过那一步，合并只在完整 run 里发生）。
+     */
+    runReleases(options: {
+        trigger: 'manual' | 'schedule';
+    }): Promise<ReleaseRunRecord>;
+    /** 发版运行用哪一天：发版调度时区下的「今天」（不是榜单调度时区，两者可独立配置）。 */
+    private releaseDate;
+    /** 订阅仓库数（best-effort，只影响 auto 解析）：任何失败都当 0，不阻塞发版运行。 */
+    private subscriptionCount;
+    /**
+     * 解析模型钥匙并（代理模式下）起回环代理。
+     *
+     * 榜单运行与发版运行共用这一段：代理的一次性 token 语义（空 key 会让核心静默降级成
+     * 英文/离线假模型）只写一次，避免两份实现漂移。
+     */
+    private openModelChannel;
+    /** 把 `run --json` 的发版阶段结果投影成一条发版运行记录并落盘。 */
+    private recordReleaseRun;
+    /** 运行在拿到信封之前就失败（定位/握手/模型/代理/超时/取消）：也要留一条可复盘记录。 */
+    private recordReleaseFailure;
+    /**
+     * 落盘发版运行：只写 state（history.json 是榜单的），顺带推进 lastReleaseAt；
+     * 只有 ok/skipped 才锁 `lastReleaseWeek`——失败不锁，调度下一 tick 才有机会重试。
+     */
+    private persistReleaseRun;
     private summarize;
     private failureSummary;
     /**
@@ -1453,6 +1625,11 @@ declare namespace runner {
 
 /** 订阅命令超时：核心只做一次 GitHub 请求/本地文件读写，8 s 足够。 */
 declare const SUBSCRIBE_TIMEOUT_MS = 8000;
+/**
+ * `releases` 要真的读一份可能几百行的文档文件、并在缺失时回退到卷索引，
+ * 比 list/add/remove 重得多；给它 30 s，避免大仓库文档被判成「无输出」。
+ */
+declare const RELEASES_TIMEOUT_MS = 30000;
 declare function isValidRepo(repo: string): boolean;
 interface SubscribeDeps {
     store: Store;
@@ -1461,20 +1638,23 @@ interface SubscribeDeps {
     corePath?: string;
 }
 /**
- * 执行一次 subscribe 命令：`action=list` 读列表，`add/remove` 改 pending 队列。
- * 返回 `{ ok, repos, error? }`；非 ok 由调用方（路由）决定转成 `SUBSCRIBE_FAILED`。
+ * 执行一次 subscribe 命令：`action=list` 读列表，`add/remove` 改 pending 队列，
+ * `releases` 读某个仓库的发版文档。
+ * 返回 `{ ok, repos, items?, doc?, error? }`；非 ok 由调用方（路由）决定转成 `SUBSCRIBE_FAILED`。
  */
 declare function runSubscribe(input: {
     action: SubscribeAction;
     repo?: string;
+    volume?: number;
 }, deps: SubscribeDeps): Promise<SubscribeOutcome>;
 
+declare const subscribe_RELEASES_TIMEOUT_MS: typeof RELEASES_TIMEOUT_MS;
 declare const subscribe_SUBSCRIBE_TIMEOUT_MS: typeof SUBSCRIBE_TIMEOUT_MS;
 type subscribe_SubscribeDeps = SubscribeDeps;
 declare const subscribe_isValidRepo: typeof isValidRepo;
 declare const subscribe_runSubscribe: typeof runSubscribe;
 declare namespace subscribe {
-  export { subscribe_SUBSCRIBE_TIMEOUT_MS as SUBSCRIBE_TIMEOUT_MS, type subscribe_SubscribeDeps as SubscribeDeps, subscribe_isValidRepo as isValidRepo, subscribe_runSubscribe as runSubscribe };
+  export { subscribe_RELEASES_TIMEOUT_MS as RELEASES_TIMEOUT_MS, subscribe_SUBSCRIBE_TIMEOUT_MS as SUBSCRIBE_TIMEOUT_MS, type subscribe_SubscribeDeps as SubscribeDeps, subscribe_isValidRepo as isValidRepo, subscribe_runSubscribe as runSubscribe };
 }
 
 interface PluginInfo {
@@ -1500,6 +1680,10 @@ interface ScheduleConfig {
     /** 自动产出的周期；每个周期只在「它自己的触发日」跑（日=每天、周=周日、月=月末）。 */
     periods: Period[];
 }
+/** 每周发版行程的开关/时间点（纯插件概念，核心没有对应字段）。 */
+type ReleaseScheduleConfig = ReleaseScheduleSettings;
+/** 发版行程的补跑窗口：超过 6 h 就放弃本周（下一周那次会同时覆盖两周的内容）。 */
+declare const RELEASE_CATCH_UP_MINUTES: number;
 /** 目标时区的墙上时间 → UTC 时刻（按 DST 修正一次，够用且可测）。 */
 declare function zonedTimeToUtc(year: number, month: number, day: number, hour: number, minute: number, second: number, timezone: string): Date;
 declare function parseClock(time: string): {
@@ -1513,6 +1697,15 @@ declare function zonedDateString(date: Date, timezone: string): string;
 declare function nextOccurrence(now: Date, schedule: ScheduleConfig): Date;
 /** 今天这一次是否已过点且在补跑窗口内。 */
 declare function isDue(now: Date, schedule: ScheduleConfig): boolean;
+/** 某时刻在 `timezone` 下的 ISO 周键；发版周去重就用它。 */
+declare function isoWeekKey(date: Date, timezone: string): string;
+/** 下一次发版运行时刻：ISO 星期匹配 `cfg.weekday`、当天的墙钟 `cfg.time`，严格晚于 now。 */
+declare function nextReleaseOccurrence(now: Date, cfg: ReleaseScheduleConfig): Date;
+/**
+ * 发版行程此刻是否该跑：星期匹配、已过点、且迟到不超过 6 h。
+ * 超过窗口就**放弃本周**——下周那次会同时覆盖两周的内容（核心按周累积，不需要补跑）。
+ */
+declare function isReleaseDue(now: Date, cfg: ReleaseScheduleConfig): boolean;
 declare function daysInMonth(year: number, month: number): number;
 /** 该时刻是否落在某个周期的结算日（按 timezone 的本地日历）。 */
 declare function isPeriodTriggerDay(period: Period, now: Date, timezone: string): boolean;
@@ -1521,6 +1714,8 @@ declare function nextOccurrenceFor(period: Period, now: Date, schedule: Schedule
 interface SchedulerDeps {
     store: Store;
     run: (trigger: 'schedule', period: Period) => Promise<unknown>;
+    /** 每周发版行程：与榜单 `run` 共享 Runner 的单跑锁（Runner 自己会拒绝并发）。 */
+    runReleases: (trigger: 'schedule') => Promise<unknown>;
     isRunning: () => boolean;
     getTimer: () => {
         interval?: (fn: () => void, ms: number) => unknown;
@@ -1534,16 +1729,39 @@ declare class Scheduler {
     private stopped;
     /** 当天已尝试次数与时间；只在内存里，进程重启后重新计数。 */
     private readonly attempts;
+    /** 发版行程的尝试计数（键 = ISO 周 + 本地日期）；理由同榜单：失败不能每分钟重试。 */
+    private readonly releaseAttempts;
     constructor(deps: SchedulerDeps);
     start(): void;
     stop(): void;
-    /** 公开给测试：判断此刻是否该跑，并按需触发一次。 */
+    /**
+     * 公开给测试：判断此刻是否该跑，并按需触发。
+     *
+     * 每个 tick 都**同时**评估榜单与发版两条行程（interval 已经是 60 s）。返回值合并规则
+     * 保证老调用方不受影响：真的跑了 → `ran`；否则有人占着锁 → `busy`；再否则只要有
+     * 一条行程是禁用状态就沿用旧的 `disabled`；都没有 → `skipped`。
+     */
     tick(now?: Date): Promise<'skipped' | 'ran' | 'disabled' | 'busy'>;
+    /** 榜单行程（原 tick 的逻辑，不改）。 */
+    private tickDigest;
+    /**
+     * 发版行程：每周一次、只跑 `--stages releases`。
+     *
+     * 跳过条件（全部满足才跑）：开启、星期/时间命中且迟到 ≤ 6 h、本周尚未成功过
+     * （`state.lastReleaseWeek`）、当前没有别的运行占锁。
+     * 失败**不锁本周**，但也只有 2 次机会（间隔 5 min）——否则一个坏 token 会在 6 h 的
+     * 补跑窗口里每分钟 spawn 一次核心、白白打 GitHub API。
+     */
+    private tickReleases;
     /** 该周期今天是否已经成功过（含无变更跳过）。 */
     private succeededToday;
     private readSchedule;
+    /** 发版行程的节奏来自 `settings.releases.schedule`（与榜单 `schedule.*` 相互独立）。 */
+    private readReleaseSchedule;
     /** 下一次运行（取所有已启用周期里最近的一次；禁用时为 undefined）。 */
     next(): Date | undefined;
+    /** 下一次发版运行（禁用/非法时为 undefined）。 */
+    nextRelease(now?: Date): Date | undefined;
     describe(state: PluginState, now?: Date): {
         enabled: boolean;
         time: string;
@@ -1553,9 +1771,19 @@ declare class Scheduler {
         lastRunDate?: string;
         catchUpMinutes: number;
         source: 'timer';
+        releaseEnabled: boolean;
+        releaseWeekday: number;
+        releaseTime: string;
+        releaseTimezone: string;
+        nextReleaseAt?: string;
+        lastReleaseAt?: string;
+        lastReleaseWeek?: string;
+        releaseCatchUpMinutes: number;
     };
 }
 
+declare const schedule_RELEASE_CATCH_UP_MINUTES: typeof RELEASE_CATCH_UP_MINUTES;
+type schedule_ReleaseScheduleConfig = ReleaseScheduleConfig;
 type schedule_ScheduleConfig = ScheduleConfig;
 type schedule_Scheduler = Scheduler;
 declare const schedule_Scheduler: typeof Scheduler;
@@ -1563,13 +1791,16 @@ type schedule_SchedulerDeps = SchedulerDeps;
 declare const schedule_daysInMonth: typeof daysInMonth;
 declare const schedule_isDue: typeof isDue;
 declare const schedule_isPeriodTriggerDay: typeof isPeriodTriggerDay;
+declare const schedule_isReleaseDue: typeof isReleaseDue;
+declare const schedule_isoWeekKey: typeof isoWeekKey;
 declare const schedule_nextOccurrence: typeof nextOccurrence;
 declare const schedule_nextOccurrenceFor: typeof nextOccurrenceFor;
+declare const schedule_nextReleaseOccurrence: typeof nextReleaseOccurrence;
 declare const schedule_parseClock: typeof parseClock;
 declare const schedule_zonedDateString: typeof zonedDateString;
 declare const schedule_zonedTimeToUtc: typeof zonedTimeToUtc;
 declare namespace schedule {
-  export { type schedule_ScheduleConfig as ScheduleConfig, schedule_Scheduler as Scheduler, type schedule_SchedulerDeps as SchedulerDeps, schedule_daysInMonth as daysInMonth, schedule_isDue as isDue, schedule_isPeriodTriggerDay as isPeriodTriggerDay, schedule_nextOccurrence as nextOccurrence, schedule_nextOccurrenceFor as nextOccurrenceFor, schedule_parseClock as parseClock, schedule_zonedDateString as zonedDateString, schedule_zonedTimeToUtc as zonedTimeToUtc };
+  export { schedule_RELEASE_CATCH_UP_MINUTES as RELEASE_CATCH_UP_MINUTES, type schedule_ReleaseScheduleConfig as ReleaseScheduleConfig, type schedule_ScheduleConfig as ScheduleConfig, schedule_Scheduler as Scheduler, type schedule_SchedulerDeps as SchedulerDeps, schedule_daysInMonth as daysInMonth, schedule_isDue as isDue, schedule_isPeriodTriggerDay as isPeriodTriggerDay, schedule_isReleaseDue as isReleaseDue, schedule_isoWeekKey as isoWeekKey, schedule_nextOccurrence as nextOccurrence, schedule_nextOccurrenceFor as nextOccurrenceFor, schedule_nextReleaseOccurrence as nextReleaseOccurrence, schedule_parseClock as parseClock, schedule_zonedDateString as zonedDateString, schedule_zonedTimeToUtc as zonedTimeToUtc };
 }
 
 /**

package/lib/internal.js

@@ -25,7 +25,7 @@ import {
   subscribe_exports,
   tools_exports,
   update_exports
-} from "./chunk-6HITSHK6.js";
+} from "./chunk-WDBZAMWN.js";
 import {
   exec_exports
 } from "./chunk-R7BK7SJK.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@morehao/dsh-github-trending",
-  "version": "0.5.2",
+  "version": "0.6.0",
   "description": "GitHub 趋势日报插件：每天定时 spawn 本地 trendradar 核心，抓取 Trending、生成中文简介与总结，提交到你的仓库并自动合并 PR。",
   "type": "module",
   "main": "lib/index.js",
@@ -59,7 +59,7 @@
     },
     "core": {
       "repo": "morehao/trendradar",
-      "version": "0.6.0"
+      "version": "0.7.0"
     },
     "client": {
       "platform": "web",