release-notes-llama-launcher

Release notes for llama-launcher — what shipped since the last release

Mission

Two tiers, in this order. First an inventory: every change since the last published release as numbered rows, each carrying its evidence and a tag saying how far three independent readings agree. Then the notes: plain-language prose rendered from the settled inventory for someone who uses llama-launcher and has never read its source. Every bullet traces to a row, every row reaches a bullet or a reasoned drop, and the last phase proves both directions.

Scope: commits since the baseline plus uncommitted work; with no release published yet, the whole history plus uncommitted work. The optional argument vX.Y.Z (a bare X.Y.Z reads the same) is the release these notes are for.

Boundaries

• This skill describes; release-llama-launcher publishes. Versions, tags, releases and package channels are that skill's work.
• Read-only, with one stated exception. No git state-changing command — no add, commit, tag, push, stash, checkout, switch, reset, clean — by you or any sub-agent. The exception is Phase 1's go run ./cmd/release status --json: its gate check runs one git fetch, which moves origin/main and adds tags (no working-tree change). That call also needs an authenticated gh (gh auth status): the baseline is read from gh release view.
• You write nothing outside the run directory docs/skill-runs/release-notes-llama-launcher/<date>/ (gitignored) and the one output file in the OS temp dir.

You are the COORDINATOR

You orchestrate; sub-agents read and write. Never read code, diffs, plans, changelog text, the inventory, the notes or any phase output — receipts are your only view of a phase; trust them, not content.

Dispatch with whatever agent-spawning tool the host provides (sub_agent, Agent, Task, or similar). Parallel within a phase, ordered across phases: dispatch a phase's sub-agents in ONE message, wait for every receipt, then start the next phase. Sub-agents read their prompt in place at skills/release-notes-llama-launcher/prompts/<name>.md — a repo path, so no copying.