v0.6.1

Each Version now reaches npm and installs with npm install -g ticket-runner, and the conflict Stage works with mattpocock-skills 1.3.1.

npm

• Each cut Version is published to npm, and the pipeline names npm install -g ticket-runner (#216)
• The package's npm page carries keywords and a homepage (#219)

Fixes

• The conflict Stage runs without a skill, so mattpocock-skills 1.3.1 no longer breaks it (#222)

Docs

• The README shows the npm Version and the licence as badges (#217)
• The wiki's diagrams read in the light theme (#218)
• The Running page compares /implement-spec with a Run (#222)
• Version notes open with a summary, and the Install page points upgrades at them (#220)

After upgrading

Run ticket-runner init in each Target to refresh the Operator's skill, which now installs from npm. The GitHub tag install keeps working.

v0.6.0

ticket-runner

• The pipeline is ticket-runner in its package, command, branches, files and markers, under MIT (#202)
• ticket-runner remove takes the pipeline out of a Target, refusing while work is in flight (#204)
• The package leaves out the tests and their fakes (#214)

Runs

• ticket-runner run 12 13 works only the Tickets it names (#205)
• A Note is posted as a bold summary, then its Evidence, Impact and Next (#195)

Fixes

• A pull request takes the title its Stages answer, not its first commit's subject (#206)
• A Stage is told it runs in the pipeline's checkout only in the pipeline's own repository (#213)

Docs

• A wiki at https://jjongs2.github.io/ticket-runner/, and a README rewritten for newcomers (#207)
• ADR-0004, -0006 and -0008 read as decisions in force (#211)

After upgrading

Nothing reads the old name, so move each Target by hand, while no Run holds it and no Ticket is in-progress:

1. npm uninstall -g agent-pipeline, then npm install -g "github:jjongs2/ticket-runner#semver:*"
2. Rename agent-pipeline.json to ticket-runner.json, and .agent-pipeline/ to .ticket-runner/ in the directory and its .gitignore line
3. Delete .claude/skills/agent-pipeline/, and write ticket-runner for agent-pipeline in the CLAUDE.md section that points at the conventions document
4. Copy the State branch, when there is one, then delete both old branches: git push origin origin/agent-pipeline/state:refs/heads/ticket-runner/state and git push origin --delete agent-pipeline/state agent-pipeline/lock
5. Run ticket-runner init

v0.5.2

Progress comments

• A Ticket's Progress comment keeps each Run's own section, and drops another Run's footer from an earlier one (#185, #192)

Fixes

• A Host without gh installed is told so, instead of being asked to log in (#190)
• A Stage installs the Target's dependencies and keeps them past its clean-worktree check (#191)
• A conflicting pull request hands off as a conflict, without waiting out the grace period (#183)
• init counts a label GitHub already has as present, instead of failing (#182)
• A pull request body names only the transcripts that outlive the Host (#181)

Versions

• /cut-a-version confirms the number and the notes with the maintainer before opening the Version PR (#184)
• Attended work too small for a Ticket opens a pull request on human/<slug>, without one (#184)

After upgrading

• Run agent-pipeline init again in every Target: the Operator's skill's gh wording and its dependency-install line both changed.

v0.5.1

Fixes

• A Ticket branches from, and rebases onto, the remote's Base branch, not the checkout's (#177)

After upgrading

• Run agent-pipeline init again in every Target, so a cloud Host installs this Version rather than the one stamped before.

v0.5.0

Cloud Host

• ADR-0008 records the cloud Host as a Claude Code cloud session; CONTEXT.md defines Host and Operator (#145)
• The Tracker reads and writes issues, pull requests and the default branch over REST (#158, #159, #170)
• The Operator's skill starts a Run or a Ticket in the background and installs gh when missing (#166, #172)

Run lock and resume state

• The Run lock and a Ticket's resume state move to GitHub, behind a new Workspace port (#160, #164, #162)
• A Ticket's branch pushes after every committing Stage and resumes from the remote, transcripts included (#161, #163)

After upgrading

• Run agent-pipeline init again in every Target; readiness now refuses one missing branch deletion, a Version stamp, or the Operator's skill.

v0.4.5

Fixes

• The Checks now catch uncommitted work left in the worktree and spend the fix budget on it (#143)
• The implement Stage's review now lands before it answers, and a later answer keeps every earlier Note (#141)

After upgrading

• nothing

v0.4.4

Stages

• A Stage runs claude-opus-5-5 by default, and a Target can set its effort (#136)

Hand-off

• A handed-off Ticket resumes from where it stopped, not from the start (#135)
• The conventions document now says a handed-off Ticket keeps its State file too (#138)

After upgrading

• Run agent-pipeline init again in every Target; the conventions document's State file line now covers a handed-off Ticket too.

v0.4.3

Notes

• A Stage is told the bar a Note must clear before writing one, and the verify Stage holds itself to the same evidence standard (#129)

After upgrading

• nothing

v0.4.2

Notes

• A Note that reaches triage becomes a comment on one standing issue instead of opening a new one (#124)
• The verify Stage can put what it finds outside the Acceptance Criteria in a Note (#125)

Fixes

• The Run lock checks a recycled pid against the holder's recorded start time (#126)

After upgrading

• nothing

v0.4.1

Fixes

• A pull request whose checks GitHub registers late waits out a grace instead of a hand-off (#120)
• A hand-off comment left by an earlier Run is marked history when the Ticket is claimed again (#118)
• An unknown option answers with the usage, not a stack trace (#115)
• The usage explains the pipeline in plain words, and -v says the Version (#117)

Repository

• A node_modules symlink is ignored like the directory, and the broken one on main is gone (#112)
• Version notes carry a link definition for every pull request they name (#110)

After upgrading

• Nothing is required; a Target whose Actions queue registers checks slowly can raise ciGraceMinutes, which defaults to 5.