release-skill 0.1.6 → 0.1.8

package/README.md

@@ -2,8 +2,8 @@
 
 [简体中文](README.zh-CN.md) · Installation: [English](INSTALL.md) / [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.1.6 -->
-Release preparation for Claude Code and Codex, with human-edited files kept intact.
+<!-- release-skill:release-version: 0.1.8 -->
+Release preparation for Claude Code, Codex, and Kimi Code, with human-edited files kept intact.
 
 release-skill helps a maintainer answer three questions: what will be released,
 which checks still fail, and which exact bytes will reach users. It freezes the
@@ -11,80 +11,29 @@ reviewed artifacts first and publishes those same artifacts later; it does not
 regenerate a README or re-pack the live workspace at the last step.
 
 <!-- release-skill:managed:start id=latest-release -->
-**0.1.6** (2026-07-22)
-
-v0.1.6 is a release-preparation snapshot that closes the release-docs automation loop. A single structured release-notes source drives deterministic, multilingual CHANGELOG and README refresh behind a two-phase, digest-bound write protocol and a prepare-time documentation freshness gate, while terminal transaction receipts are bounded and the CLI lifecycle, path safety, and error-output redaction are hardened.
-
-**Added**
-
-- **Structured release-notes-driven document refresh (`docs refresh`)**: a single
-  structured release-notes source (`release-notes/0.1.6.yaml`) now drives
-  deterministic, multilingual refresh of the managed CHANGELOG and README
-  regions. Refresh runs as a two-phase protocol: a read-only planning phase
-  renders every candidate and freezes an `inputDigest` (binding the canonical
-  notes and the notes-source bytes) plus a `refreshDigest` (binding the protocol
-  version, unit, version, configuration projection, and per-file old/new
-  digests), and a separate write phase commits the changed targets only when all
-  three authorizations are present (`--write`, an exact `--confirm-refresh
-  <refreshDigest>` match, and `--ack-local-document-write`). The write phase
-  re-plans under the exclusive lock; a diverging digest converges to
-  `RELEASE_DOCS_REFRESH_STALE` with zero writes, and a clean plan is a zero-write
-  no-op. A prepare-time documentation freshness gate makes version drift between
-  the package version and the public docs fail closed before a release plan is
-  frozen.
-- **Bounded terminal transaction receipts with recovery safety**: terminal
-  (committed / rolled-back) transactions now persist a summary-only receipt
-  instead of full payload, capped at 256 KB per receipt
-  (`TERMINAL_RECEIPT_SIZE_CAP`), under a retention cap of 50 terminal records
-  (`DEFAULT_TRANSACTION_RETENTION_MAX`). Retention pruning only ever removes
-  terminal records and never prunes `RECOVERY_CONFLICT` records or any
-  non-terminal (recovery-relevant) record, so recovery evidence is preserved even
-  when the count cap is reached; a retention failure never aborts an in-flight
-  commit.
-- **Strict `docs refresh` parameter validation (fail closed)**: the `docs`
-  command validates every parameter before invoking the refresh service, so
-  precise stable parameter errors surface even without project configuration or a
-  safe-fs backend. The `--flag=value` equals form routes through exactly the same
-  validation as the space-separated form; duplicated flags fail closed with
-  `DUPLICATE_PARAMETER` before any service call, config read, lock, or
-  transaction; and bare positional arguments and single-dash flags (such as `-w`)
-  are rejected as unrecognized. Write-authorization flags supplied without
-  `--write`, or `--write` without its full authorizations, fail closed with
-  precise reasons rather than silently proceeding.
-
-**Fixed**
-
-- **Bundle entry lifecycle settles with real exit codes**: the self-contained
-  bundle now owns the command lifecycle. Its entry awaits command completion and
-  exits with the real business exit code for success, business errors, handled
-  async rejections, and unknown commands, so the launcher no longer leaves an
-  unsettled top-level await (Node exit code 13). When the bundle is missing or
-  cannot be evaluated, the launcher fails closed with static text only and never
-  interpolates machine-specific paths, usernames, or host layout, because
-  module-load failure messages carry absolute paths.
-- **Fail-closed path canonicalization with stable diagnostics**: artifact path
-  canonicalization requires POSIX separators and rejects absolute paths in POSIX
-  (`/`), Windows drive-letter, and UNC spellings, along with traversal, Windows
-  reserved device names, and colons, failing closed with `PATH_UNSAFE` rather
-  than normalizing an unsafe spelling into a different public path. Error-output
-  redaction now distinguishes real filesystem paths from strict RFC 6901 JSON
-  Pointer diagnostic coordinates (such as `/units/0/version`): absolute
-  POSIX/Windows/UNC paths collapse to a stable `<redacted-path>` placeholder
-  while diagnostic pointers are preserved verbatim, keeping failures diagnosable
-  without leaking host paths.
-- **Self public-boundary redaction**: the centralized redaction authority
-  (`core/redact.mjs`) now closes the self public boundary so runtime error
-  outputs and detail structures never carry the release-skill workspace's own
-  absolute path, nor the macOS `Users`, Linux home, macOS `private`/`var` alias,
-  temp, or CI checkout realms. Redaction runs fail-closed through the
-  `ReleaseError` choke point: any two-or-more-segment `/`-led token that is not a
-  strict diagnostic JSON Pointer is replaced with `<redacted-path>`, so
-  self-releasing never leaks private filesystem layout into public outputs.
+**0.1.8** (2026-07-23)
+
+v0.1.8 adds Kimi Code as a first-class plugin host without rewriting the already-published v0.1.7 artifacts. Kimi delivery uses a generated self-contained adapter and a fail-closed, plan-bound manual installation attestation because Kimi Code has no scriptable non-interactive plugin installation interface. The npm package name (`release-skill`), publishing identity (`publisher: mzdbxqh`), public repository (`ifoohoo/release-skill`), and corporate maintainer remain unchanged.
+
+**Changed**
+
+- **Kimi Code plugin delivery and verification**: v0.1.8 adds the root
+  `.kimi-plugin/plugin.json`, a generated self-contained `adapters/kimi/` bundle,
+  and public installation guidance. Because Kimi Code exposes no scriptable
+  non-interactive plugin installation interface, production publish emits a
+  version-pinned manual installation requirement and enters `PARTIAL`; an
+  isolated `KIMI_CODE_HOME` installation and a trusted attestation bound
+  independently to the frozen plan digest and payload digest are required before
+  `reconcile` can reach `PUBLISHED` and `verify` can reach `VERIFIED`.
+- **Immutable v0.1.7 history preserved**: the existing v0.1.7 Git tag,
+  GitHub Release, npm version, and public commit remain untouched. The v0.1.8
+  production plan binds the published v0.1.7 commit
+  `fe5897456d4166a2ec60e99405836b122562b80d` as its previous public baseline.
 <!-- release-skill:managed:end id=latest-release -->
 
 <!-- release-skill:capability:external-write-boundary -->
-> **Current boundary:** v0.1.6 is the current release (v0.1.5 previously held
-> this status after completing real production verification).
+> **Current boundary:** v0.1.8 is the current release (v0.1.7 previously held
+> published status before the Kimi Code distribution 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
@@ -101,7 +50,7 @@ v0.1.6 is a release-preparation snapshot that closes the release-docs automation
 > publish global preflight.
 
 <!-- release-skill:capability:safe-first-command -->
-> **Production path verified since the v0.1.1 milestone; v0.1.6 is the current
+> **Production path verified since the v0.1.1 milestone; v0.1.8 is the current
 > release.** The npm-installed CLI is the supported user entry. Source checkout
 > is the development/contributor fallback.
 >
@@ -632,7 +581,18 @@ syntax.
 Production prepare seals a standalone Git commit/tree for every public snapshot
 and creates a fixed tarball for every npm unit. Publish globally preflights all
 actions, then executes and observes public branch, tag, npm, GitHub Release,
-and configured Claude/Codex marketplace installation checkpoints. `verify`
+and configured Claude/Codex marketplace installation checkpoints. Kimi Code has
+no scriptable install API, so its checkpoint **fails closed** and `publish`
+lands in `PARTIAL` after the automated writes, emitting a version-pinned manual
+install requirement. The operator then launches Kimi Code with the requirement's
+isolated `KIMI_CODE_HOME`, runs the pinned `/plugins install <release-tag URL>`,
+writes a trusted attestation (binding the frozen **plan** digest and the
+snapshot **payload** digest) into the plan-digest-keyed directory
+`.release-skill/kimi-attestations/<planDigest>/<plugin>/`, and re-runs
+`reconcile` (→ `PUBLISHED`) and `verify` (→ `VERIFIED`); both read the
+attestation from that same stable location. An install into the ordinary
+`~/.kimi-code` is not accepted. See `INSTALL.md` for the full procedure and the
+attestation JSON fields. `verify`
 installs every exact npm `package@version` in an isolated directory; when
 `smokeBin` is configured it also runs the CLI and validates output. Only when
 all evidence matches does the run reach `VERIFIED`.
@@ -747,8 +707,8 @@ target first; never widen the write scope to resolve them.
 
 ### Parent workspace with npm + plugin sub-units
 
-When a monorepo produces both an npm package and a Claude/Codex plugin from
-different directories, define separate release units. Only add a plugin
+When a monorepo produces both an npm package and a Claude/Codex/Kimi Code
+plugin from different directories, define separate release units. Only add a plugin
 distribution when the unit actually ships a plugin with manifest, marketplace,
 and entry Skill:
 
@@ -824,6 +784,10 @@ releaseUnits:
         marketplace: my-plugin
         entrySkill: my-plugin-help
         timeoutMs: 300000     # optional; range 30000-900000; default 300000
+      - type: kimi-plugin
+        plugin: my-plugin
+        entrySkill: my-plugin-help
+        timeoutMs: 300000     # optional; range 30000-900000; default 300000 (Kimi has no install command; bounds read-only verification)
     publicFiles:
       - from: packages/plugin/.claude-plugin/plugin.json
         to: .claude-plugin/plugin.json
@@ -834,6 +798,9 @@ releaseUnits:
       - from: packages/plugin/.codex-plugin/plugin.json
         to: .codex-plugin/plugin.json
         mode: preserve
+      - from: packages/plugin/.kimi-plugin/plugin.json
+        to: .kimi-plugin/plugin.json
+        mode: preserve
       - from: packages/plugin/.agents/plugins/marketplace.json
         to: .agents/plugins/marketplace.json
         mode: preserve
@@ -853,6 +820,7 @@ releaseUnits:
       - .claude-plugin/plugin.json
       - .claude-plugin/marketplace.json
       - .codex-plugin/plugin.json
+      - .kimi-plugin/plugin.json
       - .agents/plugins/marketplace.json
       - skills/my-plugin-help/SKILL.md
       - README.md
@@ -865,7 +833,8 @@ releaseUnits:
       releaseTitleTemplate: "{unit} {version}"
 ```
 
-Each plugin unit **must** list its Claude/Codex `plugin.json`, `marketplace.json`,
+Each plugin unit **must** list its Claude/Codex/Kimi Code `plugin.json`, the
+Claude/Codex `marketplace.json` files (Kimi Code has no marketplace manifest),
 the entry Skill, and all required public files. A CLI smoke (`smokeBin`) is
 optional for plugin units and only applies when the published npm package
 exposes a CLI binary.
@@ -929,7 +898,10 @@ Successful reconcile returns `PUBLISHED`, not `VERIFIED`; only the fresh
 - publishes only frozen Git objects and npm tarballs, then checks remote
   commit/tree/tag/integrity;
 - installs configured Claude/Codex plugins from the frozen Git ref and proves
-  the entry Skill and payload digest in fresh isolated consumer homes;
+  the entry Skill and payload digest in fresh isolated consumer homes; for Kimi
+  Code (no scriptable install API) it emits a version-pinned manual install
+  requirement and proves the entry Skill and payload digest only from a trusted
+  attestation bound to the frozen plan digest;
 - distinguishes `PUBLISHED` (writes completed) from `VERIFIED` (remote and
   consumer installation evidence completed);
 - stops subsequent checkpoints on failure and writes a separate run record
@@ -996,8 +968,8 @@ the exact installed distribution; gates cannot borrow tests, development
 dependencies, or `node_modules` from the parent workspace.
 
 `snapshot-verify` runs in a disposable writable copy of the frozen public
-snapshot. `consumer-verify` runs from an exact isolated npm/Claude/Codex install
-root. Both use executable arrays instead of shell strings; definitions and
+snapshot. `consumer-verify` runs from an exact isolated npm/Claude/Codex/Kimi
+Code install root. Both use executable arrays instead of shell strings; definitions and
 results enter digest-bound evidence, and prepare/verify require
 `--acknowledge-gate-side-effects`. Gates are still project processes without a
 network sandbox, so release-skill cannot promise that they will not write files