Certify pm CLI 2026.9.17

[unbraind]

Pins @unbrained/pm-cli to 2026.9.17, pm-ops to 2026.9.13, and pm-changelog to 2026.9.16.

CI runs the repository-pinned binaries, so the pin decides what every gate exercises. Releases 2026.9.13-2026.9.17 fix telemetry consent/DO_NOT_TRACK handling, telemetry event loss under concurrent queue rewrites, a lock reclaimed during owner-metadata init, oversized item reads losing content without a receipt, and merge-driver launchers breaking after a runtime upgrade. pm-changelog 2026.9.16 derives release dates in UTC. pm-ops 2026.9.13 publishes the canonical lifecycle policy contract.

Tracking item: https://github.com/unbraind/pm-ts-starter/blob/main/.agents/pm/chores/pm-ts-starter-dtup.toon

release:check: 193/193 tests passed, all gates passed.

Summary by Sourcery

Certify the repository against the latest pm CLI and supporting tooling releases.

Enhancements:

• Pin the repository’s pm tooling to the certified 2026.9.13–2026.9.17 releases used by CI gates.

Chores:

• Record the certification work in the changelog and pm tracking history.

---

Summary by cubic

Pins the pm CLI toolchain so every CI gate runs the fixed releases. @unbrained/pm-cli moves 2026.9.12 → 2026.9.17, pm-changelog 2026.9.13 → 2026.9.16, and pm-ops ^2026.9.11 → 2026.9.13, now pinned exactly.

• The 2026.9.13-2026.9.17 releases fix telemetry consent/DO_NOT_TRACK handling, event loss under concurrent queue rewrites, a lock reclaimed during owner-metadata init, oversized item reads losing content without a receipt, and merge-driver launchers breaking after a runtime upgrade.
• pm-changelog 2026.9.16 derives release dates in UTC; pm-ops 2026.9.13 publishes the canonical lifecycle policy contract.
• release:check passes with 193/193 tests.

^{Written for commit 9e60e23. Summary will update on new commits.}

[sourcery-ai]

Sorry @unbraind, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 3 days and 19 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: a8d18976-0ea9-41b5-831f-524618e8b352

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR certifies the repository against pm CLI 2026.9.17 by pinning the PM toolchain and lockfile, documenting the resulting release, and recording the associated tracking and execution metadata. The stated validation completed successfully with 193/193 tests passing and all release gates passing.

File-Level Changes

Change	Details	Files
Pin the repository’s PM tooling to certified releases so CI exercises the intended CLI, operations, and changelog behavior.	Updated the PM CLI, pm-ops, and pm-changelog development dependency versions. Regenerated the lockfile to match the exact version pins. The certified releases include fixes for telemetry handling, concurrent queue rewrites, lock ownership initialization, oversized-item receipts, merge-driver launchers, UTC release dates, and the lifecycle policy contract.	package.json package-lock.json
Record the certification work in project tracking and release documentation.	Added an Unreleased changelog entry linking to the tracking item. Created the PM chore definition and execution history records.	CHANGELOG.md .agents/pm/chores/pm-ts-starter-dtup.toon .agents/pm/history/pm-ts-starter-dtup.jsonl

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the requested tool pins, lockfile resolutions, tracker records, and changelog entry are mutually consistent.

Summary

This PR certifies updated repository tooling by exactly pinning @unbrained/pm-cli 2026.9.17, pm-ops 2026.9.13, and pm-changelog 2026.9.16.

• Keeps dependency declarations and lockfile resolutions synchronized.
• Records the completed certification and its validation evidence in project-management history.
• Adds the certification item to the generated Unreleased changelog.

_{Reviews (1) · Last reviewed commit: "Pin pm CLI to 2026.9.17, pm-ops to 2026...."}

[unbraind]

Context for the review bots on this class of change (pin-certification PRs), so future reviews can be sharper:

What a certify PR is. CI runs the pm binary the repository pins, not the one installed on the runner, so the pin decides what every gate exercises. The PR therefore has to move package.json to an exact version (never ^/~), have package-lock.json resolve it, and prove npm run release:check exits 0 on the new pin. A pin that a range merely admits is not certified.

Two ordering traps that produced most of the red CI in this wave — both are real and worth flagging if you see them:

1. The changelog is generated from pm items. Closing or commenting on a pm item after running the generator leaves CHANGELOG.md behind its own generator and changelog:check fails. Also, npm run changelog (mode prepend) can never satisfy changelog:check (mode replace --all-release-tags) — only changelog:full can. And the generator must run after git fetch --tags, or a worktree without the newest tag files new entries under the already-published heading.
2. In pm-vcs only, self-host:write reads the committed tree, not the index. A bundle regenerated before its own source commit cannot contain those files, so the gate fails with "absent from the bundle" and re-running the write produces a byte-identical bundle — which reads like a broken writer but is the gate correctly reading HEAD. The converging order is: finish every pm write → changelog:full → commit source → self-host:write → commit the bundle.

On acceptance criteria. These items close inside their own PR, before CI runs, so their acceptance criteria deliberately state only facts verified at close time and never "CI is green". Flagging a missing CI assertion here is a false positive; flagging an actual_result that claims more than was measured is not — one such overclaim was caught in this wave (a pm-vcs item asserted the self-host bundle was byte-identical at HEAD when CI had just proved it was not) and was corrected on the item rather than by rewriting its history.

Every bot comment in this wave has been read and voted on.