Release pm-context v2026.09.09

[github-actions]

Automated daily release metadata for v2026.09.09. The release gate passed before this PR was created; npm publication and tagging remain blocked until this protected PR is merged. Tracking: pm-context-b7ub.

Summary by Sourcery

Release pm-context version 2026.9.9.

Build:

• Update package and lockfile metadata for the 2026.9.9 release.

Chores:

• Bump the pm-context version from 2026.9.8 to 2026.9.9 across source, distribution, and manifest metadata.

---

Summary by cubic

Bumps pm-context to v2026.09.09 across all package files, syncing the release metadata.

No behavior changes; the diff only updates the version string from 2026.9.8 to 2026.9.9. npm publication and tagging remain blocked until this PR is merged.

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

[greptile-apps]

PR author is in the excluded authors list.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR updates pm-context from v2026.09.08 to v2026.09.09 by synchronizing version metadata in the source extension, generated bundle, manifest, npm package files, and lockfile; no functional behavior changes are included.

File-Level Changes

Change	Details	Files
Bump the package release version consistently across source, built output, and package metadata.	Update the extension version from 2026.9.8 to 2026.9.9 in the TypeScript source and generated distribution. Synchronize npm manifest and lockfile version metadata for the new release.	index.ts dist/index.js manifest.json package.json package-lock.json

---

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.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="package.json" line_range="3" />
<code_context>
 {
   "name": "pm-context",
-  "version": "2026.9.8",
+  "version": "2026.9.9",
   "description": "Generate deterministic pm context packs for agent handoffs, reviews, and status briefs",
   "author": "@unbraind",
</code_context>
<issue_to_address>
**issue:** The version is bumped to `2026.9.9` without adding the corresponding `## 2026.9.9 - 2026-09-09` section to `CHANGELOG.md`; `npm run changelog:check` derives the expected heading from `package.json` and fails because the changelog still starts at `2026.9.8`.

**Triggers:** When the protected PR's CI runs the configured changelog check.

**Suggested fix:** Generate and commit the `2026.9.9` changelog section, or change the release-PR workflow so the check intentionally runs only after release-time changelog generation.
</issue_to_address>

Sourcery assessment

Needs a human reviewer. 1 finding to address first, and this only changes the package version metadata, so a mistaken value would mainly cause release or dependency-tooling confusion rather than data loss or a security issue. Reverting fixes the repository, but an already published package version cannot be fully erased and would need a bounded follow-up release or registry correction.

Blocking findings: package.json:3

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook