chore: release v1.49.0

[Esquetta]

Summary

• bump package metadata to 1.49.0
• publish corpus metrics regression diff release notes
• update GitHub Action examples to v1.49.0

Verification

• 597 tests passed, including Docker runtime integration
• TypeScript build passed
• npm audit found 0 vulnerabilities
• npm pack dry run passed with 171 files

[qodo-code-review]

PR Summary by Qodo

Release v1.49.0 (docs + action examples + package version bump)

📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Bump npm package metadata to v1.49.0.
• Publish v1.49.0 changelog entries for corpus metrics regression diff.
• Update GitHub Action usage docs/examples to pin v1.49.0.

Diagram

graph TD
  A["GitHub workflow (consumer)"] --> B["CodexPluginDoctor Action v1.49.0"] --> C["codex-plugin-doctor npm v1.49.0"]
  D["README.md"] --> A
  E["docs/guides/github-action.md"] --> A
  F["CHANGELOG.md"] --> C
  G["docs/architecture/corpus-metrics-regression-diff.md"] --> C

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Automate releases with Changesets (or similar)

• ➕ Automates version bump + changelog generation from merged changes
• ➕ Reduces manual doc/version drift across README and guides
• ➕ Provides consistent release artifacts and reviewable release PRs
• ➖ Adds tooling and workflow complexity
• ➖ May require repo-wide conventions for changeset discipline

2. Single source of truth for version in docs (templating)

• ➕ Avoids repeating version strings across multiple docs
• ➕ Makes future release bumps a single change (or scripted update)
• ➖ Requires a docs build step or pre-commit hook to render templates
• ➖ Can make local doc editing less straightforward

3. Point docs at major tag (v1) and pin npm version only where needed

• ➕ Less churn in documentation on every patch/minor release
• ➕ Action consumers still get compatible updates automatically
• ➖ Reduces strict reproducibility for consumers
• ➖ Not suitable if the action behavior changes within v1 and consumers expect pinning

Recommendation: For this PR, the current manual bump + doc pinning is appropriate and low-risk for a release branch. Longer term, consider automating the bump/changelog (e.g., Changesets) and/or templating version strings to prevent missed updates across README and guides.

Files changed (5) +36 / -22

Documentation (4) +35 / -21

CHANGELOG.mdAdd v1.49.0 release notes +14/-0

Add v1.49.0 release notes

• Adds a new 1.49.0 section describing newly shipped corpus metrics regression diff capabilities and related security constraints/behavior.

CHANGELOG.md

README.mdUpdate GitHub Action example to v1.49.0 +2/-2

Update GitHub Action example to v1.49.0

• Pins the README workflow example to use the v1.49.0 action ref and package version string.

README.md

corpus-metrics-regression-diff.mdMark corpus metrics regression diff as shipped +1/-1

Mark corpus metrics regression diff as shipped

• Updates the status line from planned to shipped for the v1.49.0 release.

docs/architecture/corpus-metrics-regression-diff.md

github-action.mdBump all action guide snippets to v1.49.0 +18/-18

Bump all action guide snippets to v1.49.0

• Updates all referenced action refs and version inputs in the guide examples from 1.48.0 to 1.49.0 to match the release.

docs/guides/github-action.md

Other (1) +1 / -1

package.jsonBump package version to 1.49.0 +1/-1

Bump package version to 1.49.0

• Updates the npm package version field from 1.48.0 to 1.49.0 for publishing.

package.json

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Changelog missing diff args 🐞 Bug ⚙ Maintainability

Description

The 1.49.0 changelog advertises doctor corpus metrics diff --before --after without the required
report-path arguments, but the CLI requires --before <metrics.json> and --after <metrics.json>.
Users copying the changelog snippet will not be able to run the command as written.

Code

CHANGELOG.md[11]

+- added `doctor corpus metrics diff --before --after` for deterministic precision, recall, and reviewed false-positive share comparisons

Evidence

The changelog bullet introduces the diff command but omits the required <metrics.json> arguments.
The CLI parser enforces that --before and --after must each be followed by a path, and the
output-contract documentation shows the correct command form with placeholders.

CHANGELOG.md[7-12]
src/run-cli.ts[2134-2168]
src/core/output-contract.ts[171-174]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The changelog’s new 1.49.0 entry includes a `doctor corpus metrics diff` example that omits required values for `--before` and `--after`, making the command snippet non-runnable.

## Issue Context
The CLI implementation requires explicit paths for both flags (`--before <metrics.json>` and `--after <metrics.json>`), and the public output contract doc also shows placeholders.

## Fix Focus Areas
- CHANGELOG.md[7-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Changelog missing diff args 🐞 Bug ⚙ Maintainability

The 1.49.0 changelog advertises doctor corpus metrics diff --before --after without the required
report-path arguments, but the CLI requires --before <metrics.json> and --after <metrics.json>.
Users copying the changelog snippet will not be able to run the command as written.

Agent Prompt

## Issue description
The changelog’s new 1.49.0 entry includes a `doctor corpus metrics diff` example that omits required values for `--before` and `--after`, making the command snippet non-runnable.

## Issue Context
The CLI implementation requires explicit paths for both flags (`--before <metrics.json>` and `--after <metrics.json>`), and the public output contract doc also shows placeholders.

## Fix Focus Areas
- CHANGELOG.md[7-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools