fix: align CI workflows with pi-extension-template, bump 0.3.1

[eiei114]

Problem

CI workflows use non-existent action versions (@v6) and pinned SHAs, which will break when GitHub removes Node.js 20 from runners.

Changes

• ci.yml: @v6 → @v4, added branches: [main] to pull_request trigger
• auto-release.yml: pinned SHA → actions/checkout@v4
• publish.yml: pinned SHAs → @v4, fixed concurrency key to include inputs.ref
• Bumped 0.3.0 → 0.3.1

All 31 tests pass locally.

Summary by CodeRabbit

• Chores

  • Version bumped to 0.3.1
  • CI/CD workflows updated for more consistent release and build behavior

• Documentation

  • CHANGELOG updated with 0.3.1 entry
  • README enhanced with status/version badges

[coderabbitai]

Complex PR? Review this PR in Change Stack to move by importance, not file order.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d90a3935-b2d1-41f5-90ed-95c1936e81e5

📥 Commits

Reviewing files that changed from the base of the PR and between f1bf414 and 6b3caa7.

📒 Files selected for processing (1)

• README.md

✅ Files skipped from review due to trivial changes (1)

• README.md

---

📝 Walkthrough

Walkthrough

This PR standardizes GitHub Actions references to @v4 across workflows, updates the publish workflow to handle dispatched refs and concurrency correctly, and publishes release metadata: version bumped to 0.3.1, changelog entry added, and README badges inserted.

Changes

GitHub Actions and Release Updates

Layer / File(s)	Summary
GitHub Actions version standardization .github/workflows/auto-release.yml, .github/workflows/ci.yml	actions/checkout and actions/setup-node are updated to @v4 across auto-release and CI workflows, replacing pinned commit SHAs or older tags.
Publish workflow ref selection and concurrency .github/workflows/publish.yml	Concurrency group now incorporates `github.event.inputs.ref
Version bump, changelog, and README badges package.json, CHANGELOG.md, README.md	Package version bumped to 0.3.1, changelog entry 0.3.1 added listing workflow updates, and status/version badges added to the README.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• eiei114/pi-weighted-model-router#4: Related edits to publish.yml, including actions/checkout/actions/setup-node usage and publish flow changes.
• eiei114/pi-weighted-model-router#2: Related edits to auto-release.yml's actions/checkout usage and release automation.

Poem

🐰
Tiny paws tap keys in morning light,
Workflows tuned and badges bright,
Refs now chosen, versions neat,
v0.3.1—release complete! 🥕

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly summarizes the main changes: updating CI workflows to align with a template and bumping the package version to 0.3.1, which matches the primary content of the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/ci-align-template

---

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

[coderabbitai]

🧹 Nitpick comments (1)

CHANGELOG.md (1)

8-8: 💤 Low value

Consider standardizing version header format for consistency.

The new 0.3.1 entry uses [0.3.1] with brackets, while the existing 0.3.0 entry (line 17) uses 0.3.0 without brackets. For consistency across the changelog, either add brackets to all version headers or remove them from this one.

📝 Suggested standardization

Option 1: Remove brackets to match existing format

-## [0.3.1] - 2026-06-06
+## 0.3.1 - 2026-06-06

Option 2: Add brackets to all versions (would require updating line 17 as well)

-## 0.3.0 - 2026-05-31
+## [0.3.0] - 2026-05-31

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CHANGELOG.md` at line 8, The version header "## [0.3.1] - 2026-06-06" is
inconsistent with the existing "## 0.3.0" style; pick a consistent format and
update headers accordingly — either remove brackets from "[0.3.1]" to match
"0.3.0" or add brackets to all version headers (including the "0.3.0" header) so
every version line uses the same pattern; locate and edit the version header
strings (e.g., "[0.3.1]" and "0.3.0") in CHANGELOG.md to apply the chosen
standard.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CHANGELOG.md`:
- Line 8: The version header "## [0.3.1] - 2026-06-06" is inconsistent with the
existing "## 0.3.0" style; pick a consistent format and update headers
accordingly — either remove brackets from "[0.3.1]" to match "0.3.0" or add
brackets to all version headers (including the "0.3.0" header) so every version
line uses the same pattern; locate and edit the version header strings (e.g.,
"[0.3.1]" and "0.3.0") in CHANGELOG.md to apply the chosen standard.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9a8d65be-36a9-4f8b-b7bc-9e4707bbd75b

📥 Commits

Reviewing files that changed from the base of the PR and between cbf6afb and f1bf414.

📒 Files selected for processing (5)

• .github/workflows/auto-release.yml
• .github/workflows/ci.yml
• .github/workflows/publish.yml
• CHANGELOG.md
• package.json