release-skill 0.9.12 → 0.9.14

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.12",
+  "version": "0.9.14",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codebuddy-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.12",
+  "version": "0.9.14",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.12",
+  "version": "0.9.14",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"
@@ -19,7 +19,7 @@
     ],
     "defaultPrompt": [
       "Assess this project for release readiness.",
-      "Prepare a release plan for version 0.9.12.",
+      "Prepare a release plan for version 0.9.14.",
       "Help me understand the release workflow."
     ]
   }

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.12",
+  "version": "0.9.14",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/CHANGELOG.md

@@ -1,5 +1,50 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.14 locale=en baseline=sha256:48b2f41bd292f3357b3cf7433de1a2191b84d86a5074c9786ac952f62d4279be -->
+## [0.9.14] - 2026-09-05
+
+0.9.14 is a local source candidate that bounds retained production prepare runs and adds explicit Hub-backed host follow-ups after post-verification. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Retention reuses Foundation path containment and existing plan and run lineage checks. It deletes whole run directories, preserves uncertain evidence, and never turns a cleanup failure into a prepare failure.
+- Hub-backed guidance does not run Git, GitHub, Hub, or host commands and does not probe local installation state. Plugin identity must match the frozen public manifests, and Hub-backed targets are not passed to `updateLocalHostPlugins()`.
+- Skill Family Hub updates remain compare-and-swap operations against the observed branch head. A partial Hub publication is never rolled back or force-pushed.
+
+### Added
+
+- Production prepare now runs retention under the existing project lock. It keeps the current run, the newest verified complete lineage, and every non-terminal, partial, damaged, ambiguous, or validation-failing run; only superseded complete lineages and sealed failed prepares without external-write evidence are eligible for best-effort removal.
+- A release unit may declare `postPublish.localHostUpdate` with the plugin identity, target hosts, and project-selected Hub repository and ref. Prepare freezes that declaration into the immutable plan and binds it through `planDigest`.
+- After postVerify reaches `DISTRIBUTED`, the CLI and `release-finish` show host-specific manual installation or upgrade guidance for Hub-backed targets. Hub-only targets remain unavailable to the automatic local updater.
+- The project-private postVerify hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
+
+### Upgrade Notes
+
+Upgrade from 0.9.13 to bound completed production run history and receive post-verification Hub-backed host guidance. Declare `localHostUpdate` independently for each release unit that needs it. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing executable `externalActions` targets retain their current update path; Hub-backed targets remain manual in 0.9.14.
+<!-- release-skill:changelog:end version=0.9.14 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.13 locale=en baseline=sha256:86e8ee0d0aeb161c7fc652f85976b300b649ee6da04d29f9274ebcc69a8eab10 -->
+## [0.9.13] - 2026-09-05
+
+0.9.13 is a local source candidate that prevents new CodeBuddy release configurations from silently inheriting another product family's marketplace. It also brings the README black-box scenario versions under the existing version synchronization command. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Already-frozen historical plans without `marketplace` retain the legacy interpretation for deterministic reconcile. New configuration validation changes do not weaken frozen-plan identity, approval, publish, verification, or recovery checks. Skill Family Hub updates remain compare-and-swap operations; a partial Hub publication is never rolled back or force-pushed, and release-skill does not introduce a second Hub registry or state machine.
+
+### Fixed
+
+- New `codebuddy-plugin` distributions must declare `marketplace` explicitly, so each project selects its own Hub instead of inheriting the legacy `artifact-skill-set` default.
+- The first-user and security-reviewer README black-box prompts now receive their candidate version from `sync-version`, preventing their assertions from drifting behind the package version.
+- The project-private postVerify hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
+
+### Upgrade Notes
+
+Upgrade from 0.9.12 before preparing a new CodeBuddy release configuration. Add the intended Hub name to every new `codebuddy-plugin` distribution through its `marketplace` field. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing frozen plans remain recoverable, and other distribution types are unaffected.
+<!-- release-skill:changelog:end version=0.9.13 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.12 locale=en baseline=sha256:c2511de86192c1798c17e579bed689c57c450516b10bd85d6a508b0b6e5e19b1 -->
 ## [0.9.12] - 2026-09-04
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.12 -->
+<!-- release-skill:release-version: 0.9.14 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -110,7 +110,7 @@ tag pinned to the exact version (never the bare repository URL, which installs
 the latest release or default branch), confirm the trust prompt, then reload:
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.12
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.14
    /plugins reload
    ```
 

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.12 -->
+<!-- release-skill:release-version: 0.9.14 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -101,7 +101,7 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.12
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.14
    /plugins reload
    ```
 

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.12 -->
+<!-- release-skill:release-version: 0.9.14 -->
 Release preparation for Claude Code, CodeBuddy, WorkBuddy, Codex, and Kimi Code, with human-edited files kept intact.
 
 release-skill helps a maintainer answer three questions: what will be released,
@@ -14,26 +14,30 @@ Setup surfaces only the deterministic `compactSummary` review view; the full
 report stays in a temporary session directory.
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.12** (2026-09-04)
+**0.9.14** (2026-09-05)
 
-0.9.12 is a local source candidate that fixes the frozen postVerify execution closure used to publish verified releases into Skill Family Hub. It retains the 0.9.11 first-release baseline and GitHub-only distribution changes, with the three Foundation dependencies still pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+0.9.14 is a local source candidate that bounds retained production prepare runs and adds explicit Hub-backed host follow-ups after post-verification. The three Foundation dependencies remain pinned to the exact 0.17.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
 
 **Security**
 
-- The repair does not weaken the frozen execution-bundle boundary: the hook still runs from the verified tag plus the digest-bound private script. Hub branch updates remain compare-and-swap operations; a partial Hub publication is retained for recovery and is never rolled back or force-pushed.
+- Retention reuses Foundation path containment and existing plan and run lineage checks. It deletes whole run directories, preserves uncertain evidence, and never turns a cleanup failure into a prepare failure.
+- Hub-backed guidance does not run Git, GitHub, Hub, or host commands and does not probe local installation state. Plugin identity must match the frozen public manifests, and Hub-backed targets are not passed to `updateLocalHostPlugins()`.
+- Skill Family Hub updates remain compare-and-swap operations against the observed branch head. A partial Hub publication is never rolled back or force-pushed.
 
-**Fixed**
+**Added**
 
-- The Hub postVerify hook now imports proposal projection from a dependency-free public module. A detached frozen-tag worktree can load the module without node_modules, while runtime proposal transports continue to use the same implementation through a compatibility re-export.
-- The project-private postVerify hook continues to publish verified entries and public snapshots to Skill Family Hub through GitHub's Git Data API.
+- Production prepare now runs retention under the existing project lock. It keeps the current run, the newest verified complete lineage, and every non-terminal, partial, damaged, ambiguous, or validation-failing run; only superseded complete lineages and sealed failed prepares without external-write evidence are eligible for best-effort removal.
+- A release unit may declare `postPublish.localHostUpdate` with the plugin identity, target hosts, and project-selected Hub repository and ref. Prepare freezes that declaration into the immutable plan and binds it through `planDigest`.
+- After postVerify reaches `DISTRIBUTED`, the CLI and `release-finish` show host-specific manual installation or upgrade guidance for Hub-backed targets. Hub-only targets remain unavailable to the automatic local updater.
+- The project-private postVerify hook continues to publish the verified release-skill entry and public snapshot to Skill Family Hub through GitHub's Git Data API.
 
 **Upgrade Notes**
 
-Upgrade from 0.9.11 before relying on the bundled `hub-api-publish` postVerify hook. Remove any `release-skill` standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Releases that do not use this hook are unaffected.
+Upgrade from 0.9.13 to bound completed production run history and receive post-verification Hub-backed host guidance. Declare `localHostUpdate` independently for each release unit that needs it. Remove any release-skill standalone marketplace registration, add or update `ifoohoo/skill-family-hub`, and use `release-skill@skill-family-hub`. Existing executable `externalActions` targets retain their current update path; Hub-backed targets remain manual in 0.9.14.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.9.12 is the current source candidate. This README
+> **Current boundary:** v0.9.14 is the current source candidate. This README
 > records intended scope and verification boundaries; it is not evidence of
 > publication, consumer-installation verification, or independent acceptance.
 > Release availability must be established from the corresponding release records
@@ -57,7 +61,7 @@ Upgrade from 0.9.11 before relying on the bundled `hub-api-publish` postVerify h
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.9.12 is the current
+> **Production path verified since the v0.1.1 milestone; v0.9.14 is the current
 > source candidate. Its README does not establish publication,
 > consumer-installation verification, or independent acceptance.**
 > The npm-installed CLI is the supported user entry. Source checkout
@@ -86,7 +90,7 @@ checkpoints remain intact and use matching-version recovery. Evidence v1 stays
 read-only; v2 uses a closed top level with phase extensions in `details`.
 Summaries and recovery suggestions are diagnostic, never publication authority.
 
-The current 0.9.12 candidate includes the narrow R-05 Hook cache v2 consumer
+The current 0.9.14 candidate includes the narrow R-05 Hook cache v2 consumer
 path, the public `postverify` path, and the stable isolated install-tree record
 path (A2/A3). It also removes the repository's own marketplace indexes and
 uses Skill Family Hub as the single marketplace source. It still
@@ -783,10 +787,30 @@ unsupported. When a plan declares postVerify hooks, release-finish must receive
 the completed postVerify run produced by `ship`, rather than the earlier verify
 run. The core prepare, publish, and verify workflow remains cross-platform.
 
-A `codebuddy-plugin` distribution may optionally declare `marketplace` (and
-`marketplaceSource`, the URL consumers use to add the marketplace) to override
-the default unified marketplace `artifact-skill-set`; undeclared distributions
-keep the default and produce byte-identical frozen plans.
+A release unit may also declare `postPublish.localHostUpdate` for a plugin that
+is delivered through a project-selected Hub by a `postVerify` hook. After that
+hook reaches `DISTRIBUTED`, `ship`, `verify`, `post-release`, and
+`release-finish` display the declared Hub, plugin, and hosts. These Hub-backed
+targets are manual in 0.9.14 (`promptRequired: true`, `available: false`): the
+prompt does not query the Hub, inspect the host, or run host commands. Claude
+and Codex use their existing marketplace management entry; Kimi uses the
+frozen GitHub Release and its existing confirmation path; CodeBuddy and
+WorkBuddy remain manual because this flow cannot pin a Hub ref. Existing
+executable targets derived from frozen plugin-install actions remain available.
+
+Production `prepare` also performs one best-effort retention pass after its new
+run evidence exists and before expensive snapshot and hook work. It removes
+only superseded complete run lineages and sealed failed prepare directories
+that have no valid plan or external-write trace. The current plan, the newest
+complete lineage, and every non-terminal, partial, corrupt, ambiguous, or
+out-of-bounds lineage remain protected. Retention failures never change the
+prepare result.
+
+New `codebuddy-plugin` project configurations must declare `marketplace`
+explicitly so product families cannot silently inherit another family's Hub.
+`marketplaceSource`, the URL consumers use to add that marketplace, remains
+optional. Only already-frozen historical plans that lack `marketplace` retain
+the legacy `artifact-skill-set` interpretation so reconcile can replay them.
 
 For every npm distribution, `prepare` statically checks the exact packed
 tarball against concrete `package.json` entry targets. `publish` and

package/README.zh-CN.md

@@ -2,32 +2,36 @@
 
 [English](README.md) · 安装指南：[中文](INSTALL.zh-CN.md) / [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.12 -->
+<!-- release-skill:release-version: 0.9.14 -->
 面向 Claude Code、CodeBuddy、WorkBuddy、Codex 和 Kimi Code 的发布准备工具，完整保留人工维护的文件内容。
 
 release-skill 帮助维护者回答三个问题：准备发布什么、还有哪些检查未通过、最终发布的内容是什么。它不重新生成、也不回写项目源文件。`prepare` 把每个配置的公开文件复制到隔离快照并验证字节——先冻结并供人工审阅，再从同一份冻结产物发布。`setup` 只显示确定性的 `compactSummary` 审阅视图，完整报告保留在临时会话目录中。
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.9.12** (2026-09-04)
+**0.9.14** (2026-09-05)
 
-0.9.12 是修复冻结 postVerify 执行闭包的本地源码候选，用于把已验证版本发布到 Skill Family Hub；它保留 0.9.11 的首次发布基线与 GitHub-only 分发能力，三项 Foundation 依赖仍精确固定在已发布的 0.17.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
+0.9.14 是限制 production prepare 历史 run 保留数量、并在发布后验证完成后给出 Hub-backed 宿主操作提示的本地源码候选。三项 Foundation 依赖仍精确固定在已发布的 0.17.0。本说明不代表已经发布、完成真实宿主验收、完成消费者安装验证或通过独立验收。
 
 **安全**
 
-- 本次修复不放宽冻结执行包边界：hook 仍由已验证标签与摘要绑定的私有脚本共同执行。Hub 分支更新继续采用比较后写入；Hub 局部发布会保留为可恢复状态，不回滚、不覆盖，也不强推。
+- run 清理复用 Foundation 的路径收容能力，以及现有计划与 run 谱系校验。清理会删除整个 run 目录，保留无法确定的证据；清理失败不会导致 prepare 失败。
+- Hub-backed 提示不运行 Git、GitHub、Hub 或宿主命令，也不探测本机安装状态。插件身份必须与冻结的公开清单一致，Hub-backed 目标不会传给 `updateLocalHostPlugins()`。
+- Skill Family Hub 更新继续根据已观察的分支头比较后写入。Hub 局部发布不回滚、不覆盖，也不强推。
 
-**修复**
+**新增**
 
-- Hub postVerify hook 现在从无包依赖的公开模块导入提案投影。detached 冻结标签工作树无需 node_modules 即可加载；运行时提案传输仍通过兼容转出复用同一实现。
-- 项目私有的 postVerify hook 继续通过 GitHub Git Data API，把已验证条目和公开快照发布到 Skill Family Hub。
+- production prepare 现在会在现有项目锁内清理旧 run。它保留本轮、最近一条经过验证的完整终态谱系，以及所有非终态、部分成功、损坏、身份含糊或校验失败的 run。只有被更新完成谱系取代的旧目录，以及没有外部写入证据的 sealed failed prepare，才会进入尽力删除范围。
+- 发布单元可以通过 `postPublish.localHostUpdate` 声明插件身份、目标宿主，以及项目自行选择的 Hub 仓库与 ref。prepare 会把声明冻结进不可变计划，并由 `planDigest` 绑定。
+- postVerify 达到 `DISTRIBUTED` 后，CLI 和 `release-finish` 会按宿主显示 Hub-backed 人工安装或升级提示。只有 Hub-backed 目标时，自动本机更新入口仍不可用。
+- 项目私有的 postVerify hook 继续通过 GitHub Git Data API，把已验证的 release-skill 条目和公开快照发布到 Skill Family Hub。
 
 **升级说明**
 
-依赖内置 `hub-api-publish` postVerify hook 前，应从 0.9.11 升级到本版本。删除各宿主中独立的 `release-skill` 市场登记，添加或更新 `ifoohoo/skill-family-hub`，并使用 `release-skill@skill-family-hub`；未使用该 hook 的发布不受影响。
+从 0.9.13 升级到本版本后，production prepare 会限制已完成 run 的保留数量，发布后验证完成时也会显示 Hub-backed 宿主操作提示。需要该提示的发布单元应各自声明 `localHostUpdate`。删除各宿主中独立的 `release-skill` 市场登记，添加或更新 `ifoohoo/skill-family-hub`，并使用 `release-skill@skill-family-hub`。现有 `externalActions` 可执行目标继续使用原更新路径；0.9.14 的 Hub-backed 目标仍由维护者人工处理。
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **当前边界：** v0.9.12 只是当前源码候选。本 README 记录预期范围与验证边界，
+> **当前边界：** v0.9.14 只是当前源码候选。本 README 记录预期范围与验证边界，
 > 不代表已经发布、完成消费者安装验证或通过独立验收。
 > 版本可用性以对应发布记录及发布后验证结果为准。
 > v0.4.1 是更早的已发布里程碑（v0.2.2 曾处于已发布状态，后因平台验证收敛修复而更新）。
@@ -43,7 +47,7 @@ release-skill 帮助维护者回答三个问题：准备发布什么、还有哪
 > 远端唯一性检查在 `publish` 全局预检执行。
 
 <!-- release-skill:capability:safe-first-command -->
-> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.12 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
+> **生产路径自 v0.1.1 里程碑起已完成真实生产验证；v0.9.14 是当前源码候选，本 README 不证明该候选已经发布、完成消费者安装验证或通过独立验收。**
 > npm 安装的 CLI 是受支持的用户入口；源码 checkout 保留为开发/贡献者路径。
 >
 > **第一条命令：**
@@ -61,7 +65,7 @@ marketplace 委托目标工作区发布的边界不变。
 
 旧 production 计划缺少 `sourceAuthority` 时，在外部写入前拒绝。未发生外部写入的计划必须重新 prepare 并批准新摘要，不能补写旧计划或迁移批准。已有 `PARTIAL` 保留检查点，走匹配版本的恢复路径。evidence v1 只读；v2 顶层封闭，阶段扩展放在 `details`。摘要和恢复建议只作诊断，不构成发布权威。
 
-当前 0.9.12 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
+当前 0.9.14 候选包含窄范围的 R-05 Hook cache v2 消费路径、公开 `postverify`
 路径和稳定隔离安装树记录路径（A2/A3），并删除仓库自有市场索引，统一以
 Skill Family Hub 为市场来源。当前仍不包含 R-02 安全整树盘点、R-10 历史发布验证
 的产品实现、真实 Kimi/WorkBuddy 公开市场安装与调用门禁或 Audit 公开离线发布记录
@@ -665,7 +669,20 @@ WorkBuddy 本机更新仅支持 macOS；其他平台返回不支持并跳过。
 release-finish 必须接收 `ship` 产出的已完成 postVerify run，不能直接使用较早的
 verify run；核心 prepare、publish、verify 流程仍跨平台。
 
-`codebuddy-plugin` 分发可以可选地声明 `marketplace`（以及 `marketplaceSource`，即消费者添加市场所用的 URL）来覆盖默认统一市场 `artifact-skill-set`；未声明的分发保持默认值，冻结计划字节不变。
+如果插件由项目选定的 Hub 通过 `postVerify` Hook 交付，发布单元还可以声明
+`postPublish.localHostUpdate`。Hook 达到 `DISTRIBUTED` 后，`ship`、`verify`、
+`post-release` 和 `release-finish` 会显示声明中的 Hub、插件和宿主。0.9.14 对这类
+目标只提供人工入口（`promptRequired: true`、`available: false`）：提示不会访问 Hub、
+探测宿主或运行宿主命令。Claude 和 Codex 使用各自已有的 marketplace 管理入口；Kimi
+使用冻结 GitHub Release 和现有人工确认路径；CodeBuddy 与 WorkBuddy 因无法固定 Hub
+ref 而继续人工处理。由冻结插件安装动作派生的原有可执行目标不受影响。
+
+生产 prepare 还会在本轮运行证据建立后、高成本快照和 Hook 之前执行一次尽力清理。
+它只删除已被更新完整谱系取代的终态运行目录，以及没有有效计划或外部写入迹象的封口
+失败 prepare。当前计划、最近完整谱系，以及所有非终态、部分成功、损坏、含糊或越界
+谱系都受保护。清理失败不会改变 prepare 结果。
+
+新的 `codebuddy-plugin` 项目配置必须显式声明 `marketplace`，避免不同产品线误用同一市场；`marketplaceSource`（消费者添加市场所用的 URL）仍可按需声明。只有已经冻结、且未携带该字段的历史计划会继续按旧规则解释为 `artifact-skill-set`，以保证 reconcile 可以重放原计划。
 
 每个 npm 分发在 `prepare` 时都会针对精确封装的 tarball 静态校验
 `package.json` 声明的具体入口。`publish` 与 `reconcile` 在任何远端动作前对同一

package/adapters/claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.12",
+  "version": "0.9.14",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"