Ln 62 Release Publisher

Release Publisher

Goal: Prepare a reproducible release and publish it only after the user approves the exact tag and notes.

Execution contract: The checklist defines completion. Track each item internally as PENDING, PROVEN with evidence, CLEARED with evidence its condition is absent, or UNPROVEN with a gap; reading, delegation, tool failure, a zero exit status, or a self-reported success is not proof; only the observed outcome is. Reconcile after each section. Before returning, resolve all PENDING, count only PROVEN and CLEARED, and apply verdict and approval rules to every gap. Preserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. When no one can answer during the run, state the exact question and apply the skill's verdict for the remaining gap instead of waiting or guessing. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method. Accept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims. On continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority. Prepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution.

Tool Routing

When publishing through a shell, use a temporary notes file so Markdown, quotes, and code blocks are not reinterpreted. Keep credentials in the host credential store and never echo them.

Do not browse for generic release advice when repository policy and previous comparable releases answer the question. Use official host documentation only for current API or CLI behavior.

Checklist

Establish scope and evidence

• Confirm the user explicitly requested a release and identify the repository, release target, and intended audience.
• Read repository release rules before selecting a version, tag shape, files, or publication sequence.
• Verify an authenticated GitHub release capability, repository access, and permission to create releases.
• Require a clean worktree or explicitly exclude unrelated changes before release preparation.
• Fetch tags and the target branch; confirm local HEAD is synchronized with the remote release branch.
• Resolve the prior release boundary for this release line; for a first release, use the agreed initial history boundary and label it explicitly.
• Inspect commits and full commit bodies from the previous release boundary to the proposed release commit.
• Read the affected manifests, authoritative documentation, installation instructions, configured catalogs, and user-facing migration notes when present.
• Treat commits and source diffs as evidence; use existing release notes only as secondary context.

Version and Scope

• Use the repository's declared versioning policy; do not impose CalVer, SemVer, or a shared catalog version when none is specified.
• If the release target or tag is ambiguous, stop and ask instead of inventing a convention.
• Check the proposed tag locally and remotely. For a resumed approved release, verify its exact target and existing release state before continuing; otherwise treat a collision as a blocker, never overwrite it.
• Prepare version changes only in canonical fields identified by repository instructions; keep them local and reviewable until proposal approval.
• Update only packages, plugins, or components included in the release; do not bump unrelated manifests for visual consistency.
• Keep a new distribution unit at its approved initial version unless this release explicitly advances it.
• Ensure the tag, release title, and notes describe the same release unit; require manifest-version alignment only for versioned manifests included in that unit.
• Document breaking installation or behavior changes in the repository's required migration surface.

Release Notes

• Read the most recent comparable releases and preserve useful house style without copying stale structure.
• Group changes by user outcome, not by file list or internal implementation chronology.
• Lead with why the release matters, then state the concrete behavior users receive.
• Include exact install or update commands only after verifying them against the current authoritative documentation and applicable distribution metadata.
• Include migration steps for every confirmed breaking change, with old and new behavior clearly separated.
• Mention removed behavior plainly; do not disguise removal as simplification.
• Credit external contributors by verified handle and omit a contributors section for solo work.
• Link to canonical documentation and repository paths that exist at the release commit.
• Exclude claims about adoption, performance, compatibility, or counts that cannot be reproduced.
• Distinguish measured facts from interpretation and future intent.