release-skill 0.6.2 → 0.7.0

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "release-skill",
       "source": "./",
-      "version": "0.6.2",
+      "version": "0.7.0",
       "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
       "author": {
         "name": "广州市风荷科技有限公司"

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.6.2",
+  "version": "0.7.0",
   "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.6.2",
+  "version": "0.7.0",
   "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.6.2",
+  "version": "0.7.0",
   "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.6.2.",
+      "Prepare a release plan for version 0.7.0.",
       "Help me understand the release workflow."
     ]
   }

package/.kimi-plugin/plugin.json

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

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.7.0 locale=en baseline=sha256:a4d6989dd03d562c498344baf0dc1d0e1d0a225aecf0d48a7c4f9850c495b0ef -->
+## [0.7.0] - 2026-08-22
+
+v0.7.0 closes the release architecture gaps identified after v0.6.3. Private postPublish inputs are now frozen into the approved plan, checkpoint approvals must be consumed from their authoritative immutable path, and downstream projection reuses the published Skill Family Foundation 0.8.0 contracts instead of workspace-local substitutes.
+
+### Added
+
+- **Frozen postPublish execution bundles**: release units can declare private `executionFiles`; prepare freezes their exact bytes and resource closure into the immutable plan, and distribute or postVerify installs only that verified bundle into the detached execution worktree. Live workspace edits after approval cannot change the executed command.
+- **Authoritative checkpoint approval consumption**: postPublish approvals are accepted only from the canonical path derived from the plan digest and hook id. The consumer rechecks the plan digest, approval digest, strict file bytes, and symlink-free authority chain before any hook or external write.
+- **Foundation-managed downstream projection**: postPublish payload projection now uses the published `skill-family-engineering-kit` projection compiler and runner, with strict reads and resource-closure verification from `skill-family-harness-node`.
+
+### Changed
+
+- **Separated workspace roles**: preset execution now distinguishes the maintainer's `releaseWorkspaceRoot` from the detached `executionWorktreeRoot`; ambiguous legacy root fallback is rejected, and presets cannot target the release workspace itself.
+- **Exact Foundation 0.8.0 baseline**: `skill-family-contracts`, `skill-family-harness-node`, and `skill-family-engineering-kit` are pinned to 0.8.0. The package runtime is pinned to Node.js `>=22.22.2 <23`.
+- **Explicit distribute authority**: `distribute` requires the plan-bound release approval record; postPublish hook approvals remain separate checkpoint records.
+
+### Fixed
+
+- **Credential-bearing Git URL rejection and redaction**: configured Git remotes reject URL userinfo at schema and runtime boundaries. Errors, evidence, and summaries pass through the shared redaction path so embedded credentials are not persisted.
+- **Fail-closed production gates**: `NODE_TEST_CONTEXT` can no longer exempt derived-artifact gates, adapter behavior is explicit for each plan version, and Node.js 22 test-reporter output is accepted without weakening assertions.
+- **Public packaging and license closure**: the workspace documentation and public package now agree on Apache-2.0, and the public bundle carries the required Apache-2.0 and MIT license texts.
+<!-- release-skill:changelog:end version=0.7.0 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.6.3 locale=en baseline=sha256:a1b8f98d720cae60e0855677b22dd3fd75f6c43eb31123951a5129d149626e70 -->
+## [0.6.3] - 2026-08-20
+
+v0.6.3 adds the postPublish hooks v2 registration mechanism with six built-in presets, checkpoint-level approval records for hooks that write downstream, a postVerify stage that runs hooks only after the main run reaches VERIFIED, an append-only setup proposal flow that drafts postPublish hook declarations for already-configured projects, the O1-O7 release-cycle speed-ups, and release-skill's own dogfood hub-entry proposal declaration — which this release delivers to the public skill-family-hub repository during its postVerify phase under its own checkpoint approval.
+
+### Added
+
+- **postPublish hooks v2 and six presets**: `releaseUnit.postPublish` now accepts a declarative `hooks` array alongside the existing `targets`; each hook is a named preset or a custom command hook following the prepare-hook rules (executable/argument arrays, relative cwd, timeout, environment allowlist — shell strings rejected). Six built-in presets ship with the bundle and are enumerated by `release-skill distribute --list-presets`: `git-mirror` and `marketplace-index-render` (declared in `targets` form), plus `proposal-inbox`, `marketplace-registry-entry`, `docs-refresh`, and `notify-handoff` (declared in `hooks` form); writing presets share `remoteUrl`/`workspace` dual downstream addressing, `proposal-inbox` without a target degrades to `notify-handoff` behavior instead of failing, and `notify-handoff` is the zero-write floor rendering a deterministic manual sync checklist. Every declaration is normalized into the frozen plan, so a hook change changes the plan digest and invalidates existing approvals; existing `targets` configurations stay valid with unchanged execution semantics.
+- **Checkpoint-level hook approval**: a hook with `requiresApproval: true` (the default for public-write presets; projects may tighten, never loosen) parks at `AWAITING_APPROVAL` with zero remote writes until its own checkpoint approval is minted with `release-skill approve --plan <plan> --hook <hookId> --actor <name>` and consumed via `distribute --hook-approval` or `ship --hook-approval`. Approval records follow the new `postpublish-approval-record` schema bound to `(planDigest, hookId)` with the 24-hour expiry; a hook configuration change changes the plan digest and invalidates the approval. The run schema gains the `AWAITING_APPROVAL` checkpoint status, and the approval interface displays the normalized entry summary of each approved hook.
+- **postVerify stage**: hooks declared with `phase: postVerify` run only after the main run reaches VERIFIED; `ship` routes them into an independent postVerify run whose hook context carries the verification evidence (`verifyEvidence`, present in this phase only). A failed postVerify run stays PARTIAL and can be reconciled, but it never rolls the main run back from VERIFIED — the failure is recorded prominently in evidence, never silently.
+- **Setup incremental hook proposal**: for already-configured projects, `setup --discover-downstream` performs read-only discovery of downstream candidates (git remotes, marketplace/docs repository clues, `artifact-graph` configuration, foundation profiles) and `setup --propose-hooks` drafts postPublish hook declarations for human review; after human confirmation of the `setupDigest` the flow appends only the hooks section and never rewrites any other part of the configuration. The create-once boundary is preserved: an existing configuration is never regenerated.
+- **Dogfood hub proposal declaration**: release-skill's own project configuration declares a `proposal-inbox` (git-push) hub-entry proposal toward the public `skill-family-hub` repository, delivered during this release's postVerify phase under its own checkpoint approval; delivery plus the deterministic manual sync prompt in evidence is the closure criterion — hub-side consumption is out of scope for this release.
+
+### Changed
+
+- **Release-cycle speed optimizations (O1-O7)**: `build-adapters --check` and the self-bootstrap fact-pin suite are now fail-closed prepare pre-gates that run before hooks and the full-test gate (a fast pre-gate, not a replacement for full tests); a new one-click derived-artifact sync command validates and rebuilds the version/docs/bundle/adapters/manifest/public-files areas in dependency order and never writes src or test pins; `build-adapters --apply` is the supported rebuild path for existing drifted adapters; the `ship` happy end now orchestrates `prepare --production --online` by default with explicit remediation prompts for non-production and offline plans; online production prepare reports a warning-level observation when the local branch leads origin (non-blocking); `verify --run` accepts a run directory and resolves its `release-run.json` automatically (file form unchanged); and the `generate-platform-manifest --check` baseline drift is fixed.
+
+### Fixed
+
+- **Production CLI distribute adapter registration**: both production CLI adapter registries now register the distribute-git adapter; before this fix the production `distribute`/`ship` auto-distribution path failed with `no distribute adapter registered`. The state-machine reference completes the `DISTRIBUTING`/`DISTRIBUTED` states and their transitions.
+<!-- release-skill:changelog:end version=0.6.3 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.6.2 locale=en baseline=sha256:103dcbd11e52542a07da9a1220eb246cf812de79ede19ff63a374785393580b7 -->
 ## [0.6.2] - 2026-08-19
 

package/CONTRIBUTING.md

@@ -29,7 +29,7 @@ on the next regeneration.
 |---|---|---|
 | `references/` | `standards/` (workspace root) | `pnpm public:render` (workspace root) |
 | `schemas/` | `standards/` (workspace root) | `pnpm public:render` (workspace root) |
-| `adapters/` | `src/` + `skills-src/` | `npm run build:adapters` (this directory) |
+| `adapters/` | `src/` + `skills-src/` | `npm run build:adapters:apply` (this directory; rebuilds existing targets, `build:adapters` creates fresh ones) |
 | `skills/` | `skills-src/` | `npm run sync:skills` (this directory) |
 
 To update a generated artifact:

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.6.2 -->
+<!-- release-skill:release-version: 0.7.0 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -114,7 +114,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.6.2
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.7.0
    /plugins reload
    ```
 
@@ -317,6 +317,51 @@ native prebuild shipped in v0.1.3. Other platforms fail closed with
 `SAFE_WRITE_UNAVAILABLE`; keep the dry-run report and create the reviewed file
 manually instead of enabling an unsafe pathname fallback.
 
+### Incremental postPublish hook proposals (existing configs)
+
+An already-configured project never reruns create-once setup. Instead, setup
+offers a strictly read-only downstream discovery and an append-only hook
+proposal mode. Discovery reports git remote mirror candidates, marketplace and
+docs clues in the workspace and its immediate neighbors,
+`artifact-graph.config.yaml` presence, and the foundation profile metadata.
+It never writes:
+
+```bash
+PROJECT=/path/to/your/project
+"${CLI[@]}" setup --root "$PROJECT" --discover-downstream --json
+```
+
+The proposal dry-run renders legal postPublish hook declaration drafts plus the
+candidate evidence, and binds the existing configuration bytes, the discovery
+facts, and the selection into a `setupDigest`:
+
+```bash
+PROJECT=/path/to/your/project
+PROPOSAL_REPORT="$(mktemp "${TMPDIR:-/tmp}/release-hooks-proposal.XXXXXX")"
+"${CLI[@]}" setup --root "$PROJECT" --propose-hooks --json > "$PROPOSAL_REPORT"
+node -e 'const fs=require("node:fs");const r=JSON.parse(fs.readFileSync(process.argv[1],"utf8"));if(!r.setupDigest){console.error("setupDigest missing");process.exit(2)}process.stdout.write(JSON.stringify({status:r.status,targetUnitId:r.targetUnitId,appendableHookIds:r.appendableHookIds,conflicts:r.conflicts,setupDigest:r.setupDigest},null,2)+"\n")' "$PROPOSAL_REPORT"
+```
+
+`--select-hooks <ids>` narrows the selection to the listed proposal ids;
+`--foundation-profile <path>` adds an explicit foundation profile (proposal
+input only — never auto-applied); `--unit <id>` chooses the release unit when
+several declare the postPublish base. After one human review of the drafts,
+the exact confirmed digest authorizes an append-only write of ONLY
+`releaseUnits[<target>].postPublish.hooks`; the create-once boundary is never
+touched by this mode:
+
+```bash
+"${CLI[@]}" setup --root "$PROJECT" --propose-hooks \
+  --write --confirm-setup <confirmed-setupDigest> --json
+```
+
+The write returns `HOOKS_APPENDED`, or `HOOKS_NO_CHANGE` with zero writes when
+nothing is appendable. A wrong or stale digest fails closed with
+`SETUP_DIGEST_MISMATCH`; rerun the dry-run and review the new digest again.
+The incremental append requires the target release unit to already declare the
+postPublish materialize/commitIdentity distribute base, and it re-validates the
+merged declaration before any write.
+
 After the config exists, check release readiness:
 
 ```bash

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.6.2 -->
+<!-- release-skill:release-version: 0.7.0 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -104,7 +104,7 @@ Kimi Code 有交互式插件市场，但**没有可脚本化的非交互安装
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.6.2
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.7.0
    /plugins reload
    ```
 
@@ -272,6 +272,33 @@ node -e 'require("node:fs").rmSync(process.argv[1],{recursive:true,force:false})
 
 自动 create-once 写入使用 v0.1.3 随包提供、带摘要登记的 `darwin-arm64` 原生预构建。其他平台以 `SAFE_WRITE_UNAVAILABLE` 失败关闭；此时保留只读报告，由人工首次创建经审阅的文件，不得启用不安全的路径写入兜底。
 
+### 增量 postPublish hook 提案（已有配置）
+
+已完成配置的项目不会重跑 create-once setup。setup 另外提供严格只读的下游发现与仅追加的 hook 提案模式。发现阶段报告 git 远端镜像候选、工作区及其直接邻居中的 marketplace 与 docs 线索、`artifact-graph.config.yaml` 存在性以及 foundation profile 元信息，全程不写入：
+
+```bash
+PROJECT=/path/to/your/project
+"${CLI[@]}" setup --root "$PROJECT" --discover-downstream --json
+```
+
+提案 dry-run 渲染合法的 postPublish hook 声明草案与候选证据，并把现有配置字节、发现事实与选择集合绑定进 `setupDigest`：
+
+```bash
+PROJECT=/path/to/your/project
+PROPOSAL_REPORT="$(mktemp "${TMPDIR:-/tmp}/release-hooks-proposal.XXXXXX")"
+"${CLI[@]}" setup --root "$PROJECT" --propose-hooks --json > "$PROPOSAL_REPORT"
+node -e 'const fs=require("node:fs");const r=JSON.parse(fs.readFileSync(process.argv[1],"utf8"));if(!r.setupDigest){console.error("setupDigest missing");process.exit(2)}process.stdout.write(JSON.stringify({status:r.status,targetUnitId:r.targetUnitId,appendableHookIds:r.appendableHookIds,conflicts:r.conflicts,setupDigest:r.setupDigest},null,2)+"\n")' "$PROPOSAL_REPORT"
+```
+
+`--select-hooks <ids>` 将选择收窄到列出的提案 id；`--foundation-profile <path>` 追加显式 foundation profile（仅作为提案输入，绝不自动应用）；当多个发布单元声明了 postPublish 基础时，`--unit <id>` 选定目标发布单元。人工审阅草案一次之后，精确确认的摘要授权一次仅追加 `releaseUnits[<target>].postPublish.hooks` 的写入；该模式绝不触碰 create-once 边界：
+
+```bash
+"${CLI[@]}" setup --root "$PROJECT" --propose-hooks \
+  --write --confirm-setup <已确认的 setupDigest> --json
+```
+
+写入返回 `HOOKS_APPENDED`；没有可追加内容时返回 `HOOKS_NO_CHANGE` 且零写入。错误或过期的摘要以 `SETUP_DIGEST_MISMATCH` 失败关闭；重跑 dry-run 并重新审阅新的摘要。增量追加要求目标发布单元已声明 postPublish 的 materialize/commitIdentity 分发基础，且写入前会重新校验合并后的声明。
+
 配置存在后，检查发布就绪度：
 
 ```bash

package/README.md

@@ -2,7 +2,7 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.6.2 -->
+<!-- release-skill:release-version: 0.7.0 -->
 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,25 +14,34 @@ 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.6.2** (2026-08-19)
+**0.7.0** (2026-08-22)
 
-v0.6.2 promotes the skill resource closure checker to a fail-closed release gate spanning prepare, publish, and verify, closes the five gaps (G1–G5) confirmed by the clause-by-clause gate audit, and fixes lineage commit-identity parsing that corrupted rebuilt commits: missing or drifted skill resources, home-directory search paths, and undeclared host surfaces now block a release before plan freeze, and commit identities are parsed with an anchored regex that fails closed instead of fabricating identity fields.
+v0.7.0 closes the release architecture gaps identified after v0.6.3. Private postPublish inputs are now frozen into the approved plan, checkpoint approvals must be consumed from their authoritative immutable path, and downstream projection reuses the published Skill Family Foundation 0.8.0 contracts instead of workspace-local substitutes.
 
 **Added**
 
-- **Skill-resource-closure v2 release gate**: the closure checker is now a fail-closed release gate across all three phases — prepare scans the frozen snapshot and blocks plan freeze on any finding with `GATE_FAILED` (error code 13), publish Gate 2c recomputes closure against the verified frozen snapshots for production plans, and verify validates the real npm install tree and marketplace install directories with per-host receipts. Receipts now carry `unitId`, host/surface detail, digests, `checkerVersion` (`skill-resource-closure-v2`), and counts; the platform registry declares each adapter's host surface as an explicit adapter directory name, and the receipt schema is bound in all six release-plan schema copies. A version mismatch between an old frozen plan and the new checker fails closed.
-- **Closure gate gap closure (G1–G5)**: source-only (`SOURCE_ONLY_NOT_SHIPPED`) exemptions are now listed per reference in the receipt projection and in the prepare evidence — auditable and non-blocking; `~/`, `$HOME/`, and `${HOME}/` search paths inside code spans, fences, and link targets fail closed as `HOME_DIRECTORY_SEARCH`; identical surface-relative resources whose contents diverge across surfaces fail closed as `RESOURCE_DRIFT` with cross-surface reference locations; unreferenced regular files inside adapter skill closure directories fail closed as `STALE_RESOURCE`; every declared plugin distribution must be backed by a receipt host surface with at least one skill (declared-host reconciliation), so a dropped adapter tree can no longer skip the gate silently; and frozen receipts bind a deterministic `preparedAt` freeze timestamp (never a wall-clock sample) plus `exitCode: 0`, so identical sources freeze byte-identical receipts on every re-prepare.
+- **Frozen postPublish execution bundles**: release units can declare private `executionFiles`; prepare freezes their exact bytes and resource closure into the immutable plan, and distribute or postVerify installs only that verified bundle into the detached execution worktree. Live workspace edits after approval cannot change the executed command.
+- **Authoritative checkpoint approval consumption**: postPublish approvals are accepted only from the canonical path derived from the plan digest and hook id. The consumer rechecks the plan digest, approval digest, strict file bytes, and symlink-free authority chain before any hook or external write.
+- **Foundation-managed downstream projection**: postPublish payload projection now uses the published `skill-family-engineering-kit` projection compiler and runner, with strict reads and resource-closure verification from `skill-family-harness-node`.
+
+**Changed**
+
+- **Separated workspace roles**: preset execution now distinguishes the maintainer's `releaseWorkspaceRoot` from the detached `executionWorktreeRoot`; ambiguous legacy root fallback is rejected, and presets cannot target the release workspace itself.
+- **Exact Foundation 0.8.0 baseline**: `skill-family-contracts`, `skill-family-harness-node`, and `skill-family-engineering-kit` are pinned to 0.8.0. The package runtime is pinned to Node.js `>=22.22.2 <23`.
+- **Explicit distribute authority**: `distribute` requires the plan-bound release approval record; postPublish hook approvals remain separate checkpoint records.
 
 **Fixed**
 
-- **Lineage commit-identity parsing (lineage-ident)**: `lineage rebuild` parsed author/committer ident lines with `split(/\s+>/)`, which never matched a legal ident line and corrupted the identities written to rebuilt commits (names containing spaces or `>` were mis-parsed as well). Idents are now parsed with an anchored regex whose greedy name capture lets the last `<email> ts tz` group win; unparseable lines fail closed instead of fabricating identity fields. Commit messages are fed to `commit-tree` via `-F -` stdin from untrimmed `cat-file` output, preserving arbitrary message bytes including trailing whitespace and blank lines.
-- **Assess npm-transport test stability (test-only)**: the assess npm-transport test flaked when the npm lifecycle injected a silent loglevel setting and ambient proxy variables into the child environment — emptying npm stderr and letting a released ephemeral localhost port be hijacked. The test now strips ambient npm-config-namespace environment keys and proxy variables (`isolateNpmTransportEnv`), holds the localhost port for the whole test (`startConnectionResetRegistry`), and asserts `ECONNRESET|ECONNREFUSED` deterministically. No production behavior changed.
+- **Credential-bearing Git URL rejection and redaction**: configured Git remotes reject URL userinfo at schema and runtime boundaries. Errors, evidence, and summaries pass through the shared redaction path so embedded credentials are not persisted.
+- **Fail-closed production gates**: `NODE_TEST_CONTEXT` can no longer exempt derived-artifact gates, adapter behavior is explicit for each plan version, and Node.js 22 test-reporter output is accepted without weakening assertions.
+- **Public packaging and license closure**: the workspace documentation and public package now agree on Apache-2.0, and the public bundle carries the required Apache-2.0 and MIT license texts.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.6.2 is the current source candidate; v0.4.1 remains
-> the latest published release (v0.2.2 previously held
-> published status before the platform verification convergence fix was added).
+> **Current boundary:** v0.7.0 is the current source candidate; v0.6.3 remains
+> the latest published release. v0.4.1 was an earlier published milestone;
+> v0.2.2 previously held published status before the platform verification
+> convergence fix was added.
 > v0.1.1 completed a real production release to GitHub and npm — the first
 > production-verified milestone — followed by
 > exact npm installation and Claude/Codex consumer installation verification
@@ -49,8 +58,8 @@ v0.6.2 promotes the skill resource closure checker to a fail-closed release gate
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.6.2 is the current
-> source candidate and v0.4.1 is the latest published release.** The npm-installed CLI is the supported user entry. Source checkout
+> **Production path verified since the v0.1.1 milestone; v0.7.0 is the current
+> source candidate and v0.6.3 is the latest published release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
 > **Start here:**
@@ -62,6 +71,52 @@ v0.6.2 promotes the skill resource closure checker to a fail-closed release gate
 > **Distribute maturity v1.0 (W2 closure):** postPublish distribution is available as a separate `distribute` command for mirror and marketplace-index actions. After `publish` reaches PUBLISHED status, run `ship distribute` or manually invoke `release-skill distribute --plan <path> --approval <path> --json`. The distribute action implements fail-closed semantics: NO_CHANGE on empty diff (no commit/tag/push), REMOTE_CONFLICT on tag move attempts (never force-push), AUTH_MISSING when external writes are not authorized. Supported modes: `--dry-run` (local commit+tag only), `--json` (structured output), `--help` (command reference). Tag commitment guarantees version consistency — distributed plugin.json.version must match input tag. See [docs/design/2026-08-17-postpublish-distribution.md](../../docs/design/2026-08-17-postpublish-distribution.md) for detailed architecture.
 <!-- release-skill:capability:distribute -->
 
+<!-- release-skill:maturity:postpublish-hooks-v2 -->
+<!-- release-skill:capability:postpublish-hooks -->
+> **postPublish hooks v2:** `releaseUnit.postPublish` accepts a declarative
+> `hooks` array alongside the existing `targets`. Each hook is either a named
+> preset or a custom command hook; custom command hooks follow the same rules
+> as prepare hooks — executable/argument arrays, relative cwd, timeout, and an
+> environment allowlist, with shell strings rejected — and, like all
+> configured hooks and gates, they run as unsandboxed processes. Every
+> declaration is normalized into the frozen plan, so a hook change changes the
+> plan digest and invalidates existing approvals. A hook with
+> `requiresApproval: true` (the default for public-write presets; projects may
+> tighten this, never loosen it) needs its own checkpoint-level approval
+> before execution: mint one with
+> `release-skill approve --plan <plan> --hook <hookId> --actor <name>`, then
+> consume it with `distribute --hook-approval <record>` or
+> `ship --hook-approval <record>` (24-hour expiry, bound to the plan digest
+> and the hook id). Git credentials come only from the host credential
+> helper / OS keychain; release-skill never reads, stores, or prints them.
+<!-- release-skill:capability:postpublish-hooks -->
+
+<!-- release-skill:capability:postpublish-presets -->
+> **postPublish presets:** six built-in presets ship with the bundle and are
+> enumerated by `release-skill distribute --list-presets`: `git-mirror` and
+> `marketplace-index-render` (declared in `targets` form), plus
+> `proposal-inbox`, `marketplace-registry-entry`, `docs-refresh`, and
+> `notify-handoff` (declared in `hooks` form). `proposal-inbox` delivers a
+> machine-readable update proposal through a git-push or local-file transport
+> for autonomous downstream consumption; without a target it degrades to
+> `notify-handoff` behavior instead of failing. `notify-handoff` is the
+> zero-write floor: it only renders a deterministic manual sync checklist.
+> release-skill dogfoods this capability: this repository's own project
+> configuration declares a `proposal-inbox` (git-push) hub-entry proposal
+> toward the public `skill-family-hub` repository, to be delivered during the
+> v0.7.0 release in the postVerify phase under its own checkpoint approval.
+<!-- release-skill:capability:postpublish-presets -->
+
+<!-- release-skill:capability:postverify-stage -->
+> **postVerify stage:** hooks declared with `phase: postVerify` run only after
+> the main run reaches VERIFIED; `ship` routes them into an independent
+> postVerify run whose hook context carries the verification evidence
+> (`verifyEvidence`, present in this phase only). A failed postVerify run
+> stays PARTIAL and can be reconciled, but it never rolls the main run back
+> from VERIFIED — the failure is recorded prominently in evidence, never
+> silently.
+<!-- release-skill:capability:postverify-stage -->
+
 <!-- release-skill:maturity:v0.1-boundary -->
 <!-- release-skill:maturity:boundary -->
 > **Safe defaults:** the recommended path is `help → assess → prepare --offline →
@@ -200,6 +255,17 @@ ACTOR=your-name
    Add a project-specific hook or gate only after human review: edit
    `projectConfig.hooks`, or edit `verificationGates` and add the same id to
    `selectedGateIds`, then rerun the bound dry-run.
+   Downstream postPublish guidance is also read-only until confirmed:
+   `setup --discover-downstream` enumerates downstream candidates (git
+   remotes, neighboring marketplace/docs repositories,
+   `artifact-graph.config.yaml`, and a foundation profile when present), and
+   `setup --propose-hooks` turns those cues into postPublish hook declaration
+   drafts bound by a `setupDigest`. For an already-configured project,
+   `setup --propose-hooks --write --confirm-setup <digest>` appends only the
+   target release unit's `postPublish.hooks` block and never regenerates or
+   rewrites any other part of the configuration (create-once is untouched). A
+   foundation profile is one proposal input among several and never
+   auto-applies.
    See [INSTALL.md](INSTALL.md#first-use-setup) for the full multi-step flow.
 3. **assess** — read-only readiness:
    ```bash
@@ -480,6 +546,65 @@ Hooks run when `prepare` is invoked; the command call itself authorizes
 execution. Gates are the controlled extension point for release calibration
 (see `references/02-project-config.md`).
 
+### postPublish hooks
+
+`postPublish.hooks` declares downstream delivery actions that run after
+`publish`; each entry is a named preset or a custom command hook and follows
+the same command rules as above (executable/argument arrays, not shell
+strings). Presets receive a read-only projection of the frozen plan; custom
+command hooks run in the frozen tag worktree. The `materialize` hook is
+optional: when it is omitted, `distribute` stages the payload from the
+release unit's frozen `publicFiles` mapping through a Foundation managed
+projection — a fresh payload root with full preflight, zero-write refusal,
+and complete closure rollback — and live project configuration is never
+re-read after the plan is frozen:
+
+```yaml
+postPublish:
+  materialize:
+    command: [node, scripts/materialize-payload.mjs]
+    cwd: .
+    timeoutMs: 600000
+    outputMarker: "payload dir: "
+  commitIdentity:
+    name: release-bot
+    email: mzdbxqh@example.com
+  hooks:
+    - id: mirror-downstream
+      preset: git-mirror
+      config:
+        target:
+          remoteUrl: https://gitlab.example.internal/team/my-project.git
+          branch: main
+    - id: hub-entry-proposal
+      preset: proposal-inbox
+      phase: postVerify
+      requiresApproval: true
+      config:
+        delivery: git-push
+        target:
+          remoteUrl: https://github.com/example/hub.git
+          branch: main
+    - id: custom-notify
+      command: [node, scripts/notify-downstream.mjs]
+      timeoutMs: 300000
+      envAllowlist: [CI]
+```
+
+A hook with `requiresApproval: true` parks at `AWAITING_APPROVAL` until a
+checkpoint approval is minted and consumed. The approval record is bound to
+the plan digest and the hook id, and expires after 24 hours:
+
+```bash
+release-skill approve --plan "$PLAN_PATH" --hook hub-entry-proposal --actor "$ACTOR" --json
+release-skill ship --root "$PROJECT" --hook-approval "$HOOK_APPROVAL_PATH" --json
+```
+
+For an already-configured project, `setup --discover-downstream` and
+`setup --propose-hooks` draft these declarations for human review; the
+append-only incremental flow is described in the setup step above and in
+[INSTALL.md](INSTALL.md#first-use-setup).
+
 ## Skills
 
 - `release-help`: environment check and next-step guidance.