Skip to content

Certify PM CLI and SDK 2026.9.7 compatibility - #105

Merged
unbraind merged 3 commits into
mainfrom
chore/certify-pm-cli-2026-9-7
Sep 8, 2026
Merged

Certify PM CLI and SDK 2026.9.7 compatibility#105
unbraind merged 3 commits into
mainfrom
chore/certify-pm-cli-2026-9-7

Conversation

@unbraind

@unbraind unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Certify the package against the published PM CLI/SDK 2026.9.7 and pm-changelog 2026.9.6. The exact development pin changes; the established consumer compatibility floor remains enforced.

Validation: npm run release:check passed locally.

ℹ tests 115
ℹ pass 115
ℹ fail 0
ℹ skipped 0
ℹ all files |  74.13 |    80.30 |   82.61 | 

These are the metrics reported by the current gate. They do not establish four-dimensional coverage of every executable source file or clear independent historical privacy and production-readiness requirements.

PM: pm-linear-bi97.

Summary by Sourcery

Update development dependencies and certification records for the PM CLI and changelog releases.

Enhancements:

  • Certify compatibility with the published PM CLI 2026.9.7 and pm-changelog 2026.9.6 releases while preserving the existing consumer compatibility floor.

Chores:

  • Add PM chore metadata and history tracking for the compatibility certification.

Summary by cubic

Pins @unbrained/pm-cli to 2026.9.7 and pm-changelog to 2026.9.6, certifying compatibility against the published releases while keeping the existing consumer compatibility floor and quality gates unchanged.

  • Adds the pm-linear-bi97 chore and history tracking files.
  • npm run release:check passes locally (115 tests, 0 failed), but the local strict-health gate still fails on merge_receipts_pending:2; receipts and history remain preserved.
  • The certification does not cover unmeasured source files, the absent statement metric, historical privacy, or production integration with every external provider; exact-head CI and review are pending.

Written for commit 0a07f82. Summary will update on new commits.

Review in cubic

Pin the development runtime and SDK together and adopt pm-changelog 2026.9.6. Record package-local validation and remaining independent release limitations in pm-linear-bi97. Existing compatibility floors and quality thresholds remain enforced.

Validation: npm run release:check passed; tests 115 pass 115 fail 0 skipped 0 all files |  74.13 |    80.30 |   82.61 |
@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

@greptileai review

/gemini review

@coderabbitai full review

@sourcery-ai review

@cubic-dev-ai review

Please review the current pushed head and every changed area using the available free allowance. Check the actual dependency types and lockfile, PM history integrity, and compatibility evidence. Earlier-head results are historical evidence; report remaining findings against this head.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 6 days and 15 hours by commenting @sourcery-ai review. Upgrade to get a review now.

@cubic-dev-ai

cubic-dev-ai Bot commented Sep 7, 2026

Copy link
Copy Markdown

@greptileai review

/gemini review

@coderabbitai full review
...

@unbraind cubic can't start this review because your workspace has reached its free monthly review limit. cubic has reviewed 40,392 of the 40,000 allowed lines of code this month. Reviews resume on 1 October 2026 (in 24 days). Paid plans include much higher monthly review limits. Upgrade now to resume reviews.

To help optimise your usage, you can tune cubic to get the most out of your usage limits:

Learn more →

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown

Review Change Stack

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: 84906fe2-2338-44e4-929e-292265f322af

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 071187c1-57ff-412a-b7ea-416c97aa752c

📥 Commits

Reviewing files that changed from the base of the PR and between ee83a0c and 8ae0122.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • .agents/pm/chores/pm-linear-bi97.toon
  • .agents/pm/history/pm-linear-bi97.jsonl
  • package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


Summary by CodeRabbit

  • Chores
    • Updated development tooling to CLI version 2026.9.7 and changelog package version 2026.9.6.
    • Added release certification records for CLI and SDK version 2026.9.7.
    • Verified release checks passed with 115 tests passing and no failures.
    • Documented coverage results and validation limitations, including a separate strict-health check that remains unresolved.

Walkthrough

The PR updates the PM CLI and changelog development dependencies. It records the PM 2026.9.7 certification chore, validation results, release link, acceptance criteria, associated files, test entry, and event history.

Changes

PM 2026.9.7 release certification

Layer / File(s) Summary
Dependency version alignment
package.json
The PM CLI version changes to 2026.9.7. The pm-changelog version changes to 2026.9.6.
Certification record and history
.agents/pm/chores/pm-linear-bi97.toon, .agents/pm/history/pm-linear-bi97.jsonl
The PR adds the certification chore, exact-version and validation criteria, npm run release:check evidence, coverage and privacy limitations, strict-health results, release documentation, associated files, a test entry, and eight chained history events.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 8ae01

This updates development tooling to the certified PM CLI/SDK and changelog versions while retaining the consumer compatibility floor. Current validation and dependency records support merging without an identified production-impacting risk.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: compatibility certification for PM CLI and SDK version 2026.9.7.
Description check ✅ Passed The description directly explains the dependency updates, compatibility certification, validation results, and known limitations.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/certify-pm-cli-2026-9-7

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

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

@sourcery-ai

sourcery-ai Bot commented Sep 7, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The PR certifies the package against PM CLI/SDK 2026.9.7 and pm-changelog 2026.9.6 by updating exact development pins and the lockfile, while preserving the existing consumer compatibility floor. It also records the work in PM task artifacts; the stated release gate passes all 115 tests, with reported aggregate coverage of 74.13% lines, 80.30% functions, 82.61% branches, and 80.30% statements.

File-Level Changes

Change Details Files
Updates development-tooling pins to certify compatibility with the published PM CLI/SDK and changelog versions.
  • Pins the PM CLI/SDK to 2026.9.7.
  • Pins pm-changelog to 2026.9.6.
  • Refreshes the lockfile to match the dependency changes.
package.json
package-lock.json
Adds PM task tracking artifacts for the compatibility-certification work.
  • Adds the chore definition and corresponding PM history entry.
.agents/pm/chores/pm-linear-bi97.toon
.agents/pm/history/pm-linear-bi97.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

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown

@unbraind I will review the current pushed head of #105. I will check all changed areas, dependency types, lockfile consistency, PM history integrity, and compatibility evidence. I will treat earlier-head results as historical evidence only.

✅ Action performed

Full review finished.

@greptile-apps

greptile-apps Bot commented Sep 7, 2026

Copy link
Copy Markdown

Greptile Summary

Certifies development against @unbrained/pm-cli 2026.9.7 and pm-changelog 2026.9.6 while preserving the existing consumer compatibility floor. Subsequent release automation also aligned the package, lockfile, manifest, extension declaration, and changelog at version 2026.9.8.

  • Updates exact development-tool pins and lockfile integrity metadata.
  • Adds the compatibility-certification chore and append-only planning history.
  • Keeps all release identity locations and the version-derived changelog date aligned.
  • No new actionable issues were identified.

Confidence Score: 5/5

The PR appears safe to merge because the dependency certification and subsequent release metadata remain internally consistent, with no outstanding actionable findings.

The exact development pins are reflected correctly in the lockfile, the public compatibility floor remains unchanged, and all required release identity and changelog locations agree on version 2026.9.8.

Important Files Changed

Filename Overview
package.json Pins the certified PM CLI and changelog development versions and advances the package release identity consistently.
package-lock.json Locks the requested tooling versions and keeps root package metadata aligned at 2026.9.8.
.agents/pm/chores/pm-linear-bi97.toon Records the certification scope, validation evidence, and known limitations.
.agents/pm/history/pm-linear-bi97.jsonl Preserves the chore’s creation, claim, validation, file linkage, and health-gate history.
manifest.json Advances the host-facing extension version consistently with the package release.
index.ts Advances the runtime extension declaration to the same release version.
CHANGELOG.md Replaces the pending heading with the correctly dated 2026.9.8 release heading.

Reviews (3): Last reviewed commit: "Merge branch 'main' into chore/certify-p..." | Re-trigger Greptile

@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Review dispositions for the retrieved head fc0b038:

  • reviews 5135170051: Recorded as unavailable or summary-only review, not approval. Free-only operation is retained; no paid review is requested.
  • comments 5575504946: Recorded as unavailable or summary-only review, not approval. Free-only operation is retained; no paid review is requested.
  • comments 5575505062: Read and acknowledged. Compatibility evidence is scoped to the identified commit and current test gate; it does not clear separate whole-source coverage, historical privacy, hosted deployment or unavailable-review requirements.
  • comments 5575505682: The coverage dimensions in this guide are incorrect. The Node table reports lines, branches, functions; it does not report statements. For pm-linear these are 74.13%, 80.30%, 82.61%; for pm-presets 80.20%, 88.15%, 69.39%. Those remain below complete certification.
  • comments 5575506624: Read and acknowledged. Compatibility evidence is scoped to the identified commit and current test gate; it does not clear separate whole-source coverage, historical privacy, hosted deployment or unavailable-review requirements.
  • comments 5575519561: Read and acknowledged. Compatibility evidence is scoped to the identified commit and current test gate; it does not clear separate whole-source coverage, historical privacy, hosted deployment or unavailable-review requirements.

…gate

Preserve historical receipts and append-only item history after the supported dry-run refuses snapshots it cannot prove. A successful release check is recorded separately from strict workspace health.
@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

@greptileai review

/gemini review

@coderabbitai full review

@sourcery-ai review

@cubic-dev-ai review

Please review the current pushed head and every changed area using the available free allowance. Check the actual dependency types and lockfile, PM history integrity, and compatibility evidence. Earlier-head results are historical evidence; report remaining findings against this head.

@cubic-dev-ai

cubic-dev-ai Bot commented Sep 7, 2026

Copy link
Copy Markdown

@greptileai review

/gemini review

@coderabbitai full review
...

@unbraind cubic can't start this review because your workspace has reached its free monthly review limit. cubic has reviewed 40,392 of the 40,000 allowed lines of code this month. Reviews resume on 1 October 2026 (in 24 days). Paid plans include much higher monthly review limits. Upgrade now to resume reviews.

To help optimise your usage, you can tune cubic to get the most out of your usage limits:

Learn more →

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown

Rate Limit Exceeded

@unbraind have exceeded the limit for the number of chat messages per hour. Please wait 26 minutes and 5 seconds before sending another message.

@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Review dispositions for the retrieved head 8ae0122:

  • comments 5575505062: Recorded as unavailable or summary-only review, not approval. Free-only operation is retained; no paid review is requested.
  • comments 5575519561: Read and acknowledged. Compatibility evidence is scoped to the identified commit and current test gate; it does not clear separate whole-source coverage, historical privacy, hosted deployment or unavailable-review requirements.
  • comments 5575818938: Recorded as unavailable or summary-only review, not approval. Free-only operation is retained; no paid review is requested.
  • comments 5575820545: Recorded as unavailable or summary-only review, not approval. Free-only operation is retained; no paid review is requested.

@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

@coderabbitai full review

Please review the current head 8ae0122 under included free OSS capacity only. Do not use usage-based billing. Earlier-head results do not clear this head; report any remaining actionable findings or explicitly state an availability limit.

@coderabbitai

coderabbitai Bot commented Sep 7, 2026

Copy link
Copy Markdown
🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '== checked-out commit =='
git rev-parse HEAD
echo '== refs containing requested commit =='
git branch -a --contains 8ae012298dac23bf50ed982f4c5965c521e97fe8 || true
echo '== merge base and changed files =='
base="$(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main)"
printf 'merge-base=%s\n' "$base"
git diff --name-status "$base"...HEAD
echo '== stat =='
git diff --stat "$base"...HEAD

echo '== package structure =='
ast-grep outline package.json --json=stream 2>/dev/null || true
echo '== package dependency and lockfile entries =='
rg -n -C 3 '"(`@unbrained/pm-cli`|pm-changelog)"' package.json package-lock.json

echo '== PM files =='
fd -a . .agents/pm 2>/dev/null | sort
echo '== PM chore =='
cat -n .agents/pm/chores/pm-linear-bi97.toon 2>/dev/null || true
echo '== PM history =='
cat -n .agents/pm/history/pm-linear-bi97.jsonl 2>/dev/null || true

echo '== project metadata, release command, and test/coverage configuration =='
for f in package.json README.md; do
  if [ -f "$f" ]; then
    echo "-- $f --"
    rg -n -C 3 '"(release:check|test|coverage)"|coverage|engines|peerDependencies|`@unbrained/pm-cli`|pm-changelog' "$f" || true
  fi
done
fd -a -t f '(vitest|jest|nyc|c8|coverage|release)' . -E node_modules -E .git | sort | head -100

Length of output: 31834


🏁 Script executed:

#!/bin/bash
set -euo pipefail

base="$(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main)"

echo '== complete PR diff =='
git diff --find-renames --find-copies --no-ext-diff "$base"...HEAD -- \
  package.json package-lock.json \
  .agents/pm/chores/pm-linear-bi97.toon \
  .agents/pm/history/pm-linear-bi97.jsonl

echo '== selected lockfile records and dependency edges =='
python3 - <<'PY'
import json
from pathlib import Path

lock = json.loads(Path("package-lock.json").read_text())
for name in (
    "node_modules/@unbrained/pm-cli",
    "node_modules/pm-changelog",
    "node_modules/pm-ops",
):
    record = lock["packages"].get(name)
    print(f"{name}:")
    if record is None:
        print("  MISSING")
        continue
    for key in ("version", "resolved", "integrity", "dev", "dependencies", "peerDependencies", "engines"):
        print(f"  {key}: {record.get(key)!r}")
PY

echo '== JSONL validity and intra-stream hash continuity =='
python3 - <<'PY'
import json
from pathlib import Path

path = Path(".agents/pm/history/pm-linear-bi97.jsonl")
events = [json.loads(line) for line in path.read_text().splitlines() if line.strip()]
print(f"events={len(events)}")
errors = []
for index, event in enumerate(events, 1):
    for key in ("before_hash", "after_hash", "record_hash", "item_hash_version", "record_hash_version"):
        if key not in event:
            errors.append(f"event {index}: missing {key}")
    if index > 1 and event["before_hash"] != events[index - 2]["after_hash"]:
        errors.append(f"event {index}: before_hash does not equal prior after_hash")
print("continuity=" + ("OK" if not errors else "; ".join(errors)))
print("final_after_hash=" + events[-1]["after_hash"])
PY

echo '== comparable PM chore status and history endings =='
for f in .agents/pm/chores/*.toon; do
  printf '%s: ' "$f"
  rg -n '^status:|^updated_at:' "$f" | tr '\n' ' '
  printf '\n'
done | head -80

echo '== current PR checks =='
gh pr checks 105 --repo unbraind/pm-linear --json name,state,workflow,link 2>&1 || true

Length of output: 22145


@unbraind Full review completed for current head 8ae012298dac23bf50ed982f4c5965c521e97fe8 under the available OSS review capacity.

I found no actionable findings.

  • The development dependency pins and lockfile resolutions match exactly.
  • The installed @unbrained/pm-cli@2026.9.7 satisfies the peer requirements of pm-changelog@2026.9.6 and pm-ops@2026.9.7.
  • The consumer peer compatibility floor remains >=2026.8.15.
  • The new PM history JSONL is valid and has a continuous before_hash/after_hash chain.
  • The PM chore records the pending strict-health receipt limitation. It does not misrepresent that limitation as passing validation.
  • Current GitHub CI checks for Node 22 and Node 26 are successful.

The compatibility evidence is correctly scoped to the exact installed 2026.9.7 dependency set and the documented validation gate. It does not establish the separate limitations listed in the chore.

✅ Action performed

Full review finished.

@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Review dispositions for the retrieved head 8ae0122:

  • comments 5575505062: Read and acknowledged. Compatibility evidence is scoped to the identified commit and current test gate; it does not clear separate whole-source coverage, historical privacy, hosted deployment or unavailable-review requirements.
  • comments 5576118318: Accepted as an exact-head static review of 8ae0122. Local release checks passed; strict health still refuses the two historical pending receipts, which the supported reconcile preview cannot prove against current projections. No receipt or history record was discarded.

1 similar comment
@unbraind

unbraind commented Sep 7, 2026

Copy link
Copy Markdown
Owner Author

Review dispositions for the retrieved head 8ae0122:

  • comments 5575505062: Read and acknowledged. Compatibility evidence is scoped to the identified commit and current test gate; it does not clear separate whole-source coverage, historical privacy, hosted deployment or unavailable-review requirements.
  • comments 5576118318: Accepted as an exact-head static review of 8ae0122. Local release checks passed; strict health still refuses the two historical pending receipts, which the supported reconcile preview cannot prove against current projections. No receipt or history record was discarded.

@unbraind
unbraind merged commit d14608b into main Sep 8, 2026
10 checks passed
@unbraind
unbraind deleted the chore/certify-pm-cli-2026-9-7 branch September 8, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant