pipeline-digest

# Pipeline Digest Delta-gated wrapper over the pipeline facts `/release-status` reports in full. A quiet day costs one script call and sends nothing. ## Steps ### 1. Collect ```bash bun .claude/skills/pipeline-digest/scripts/digest.ts .claude-code-hermit ``` Run from the repo root. Two possible outputs: - `NOCHANGE` — the pipeline is exactly where it was last time. Say so in one line and stop. Do not send anything. - `CHANGED|<hash>` followed by the digest body — continue. ### 2. Report and notify Print the digest body in the conversation. Then send it to the operator: ```bash .claude-code-hermit/bin/hermit-run channel-send .claude-code-hermit --notice ``` with `{"maintainer": "<the digest, channel-voiced>"}` on stdin. The `hermit-run` dispatcher resolves the installed plugin itself — do not try to derive a plugin root from this skill's Base directory, which points at `.claude/`, not the plugin. Channel voice: plain language, no file paths, no slash commands, no cron strings. Plugin names and versions are fine — the maintainer chat is the technical audience. Lead with what the operator can act on. ### 3. Commit the hash ```bash bun .claude/skills/pipeline-digest/scripts/digest.ts .claude-code-hermit commit <hash> ``` Commit **only when the digest reached the operator, or when there was nobody to send it to.** Read the JSON on stdout — the exit code alone is not enough, because the script exits 1 whenever `delivered` is false, `no_channel` included: | Send resul...