[github-actions]

Automated pm-github issue synchronization for unbraind/pm-http.

The import ran with --gate: the plan was verified for completeness and provenance idempotency before the write, and the proposed tracker change passed the fail-closed privacy gate before anything was committed. main is never pushed directly.

Tracker items changed:

• pm-http-33ck (proposed)

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This gated automation imports one GitHub issue into the project tracker, records its synchronization provenance, and moves the changelog entry to Unreleased without directly modifying main.

Sequence diagram for gated GitHub issue synchronization

sequenceDiagram
    participant GitHub as GitHub
    participant Gate as Privacy and provenance gate
    participant Tracker as Project tracker
    participant Changelog as CHANGELOG.md
    participant Branch as Automation branch

    GitHub->>Gate: Read issue
    Gate->>Gate: Verify plan completeness
    Gate->>Gate: Verify provenance idempotency
    Gate->>Gate: Pass fail-closed privacy gate
    Gate->>Branch: Prepare proposed tracker change
    Branch->>Tracker: Write pm-http-github-3c83aae34e57-5.toon
    Branch->>Tracker: Write synchronization history
    Branch->>Changelog: Move release heading to Unreleased
    Branch-->>GitHub: Open proposed change
    Note over Branch,Tracker: main is never pushed directly

Loading

File-Level Changes

Change	Details	Files
Adds a synchronized GitHub tracker item with provenance history and records the release state as unreleased.	Add the imported tracker issue in TOON format. Record synchronization history in JSONL format. Change the changelog heading from a dated release to Unreleased.	.agents/pm/issues/pm-http-github-3c83aae34e57-5.toon .agents/pm/history/pm-http-github-3c83aae34e57-5.jsonl CHANGELOG.md

---

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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 9a542fc9-52c6-4969-92a0-0e8db520d91d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

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

• X
• Mastodon
• LinkedIn
• Facebook

[unbraind]

Current-head CI evidence for c7896d574ea3bbda38afe5a406f5f025322a7b3d (checked 2026-11-02 12:23 UTC): both Node 22 and Node 26 fail at npm run changelog:check.

The reported mismatch is committed ## Unreleased versus generated ## 2026.10.29 - 2026-10-29. The top-level test summaries report zero failures and the jobs reach package packing before this consistency check fails; nested synthetic-failure output belongs to harness tests, not the failing gate.

Expected: the issue-sync generator and frozen CI checker produce the same changelog for this revision and equivalent complete tag history. Actual: their heading differs, blocking the PR's current CI. This is hosted-log evidence, not a new local reproduction or proof of a pm-changelog runtime defect. Generator/checker version, flags and tag-context causality remain unverified; publication is not inferred from packing.

Acceptance/regression checks: capture and align generation/check versions and flags, preserve correct released/unreleased attribution rather than merely silencing the check, pass Node 22/26 changelog consistency, and confirm repeated gated issue sync is idempotent.