chore(release): activeagent 1.5.1

[TonsOfFun]

Bumps activeagent to 1.5.1 and stamps the changelog. Tag v1.5.1 after this merges to publish.

actionagent is unchanged since 1.5.0 and stays there — release.yml skips a version already on RubyGems, so it rebuilds and is passed over.

Contents

#430 — Evals::ModelSpec.parse_all named a spec hash by its inspected form, so a dashboard-initiated scenario evaluation failed every scenario with HTTP 400 before reaching the model.

Verification

rake build_all produces activeagent-1.5.1.gem carrying the fix, and actionagent-1.5.0.gem unchanged.

Against a host application, the same three-scenario run before and after the fix:

	before	after
errors	3 × HTTP 400	0
tool calls	none	list_filters, search_providers
scores	0.0	0.68 – 0.875

[Copilot]

🟢 Approval recommended

No unresolved blocking issues were identified.

Pull request overview

Updates activeagent to 1.5.1 and documents the included model-spec fix; actionagent remains at 1.5.0.

Changes:

• Bumps the framework version to 1.5.1.
• Adds the 1.5.1 changelog entry.

File summaries

File	Description
lib/active_agent/version.rb	Updates the framework version.
CHANGELOG.md	Documents the 1.5.1 release and fix.

Review details

• Files reviewed: 2/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[TonsOfFun]

Sequencing note before merging this

As written, this bumps activeagent only and states that actionagent stays at 1.5.0. That is correct for its stated contents (#430, which is a lib/ fix).

But three of the other open PRs change actionagent:

PR	Gem touched
#434 — MCP discovery errors	actionagent
#435 — schema tools + registration seam	actionagent and lib/
#436 — VCR filters, MCP inflection	lib/ only

So if #434 or #435 merge before this, actionagent also needs a bump or the dashboard changes will not ship — release.yml skips a version already on RubyGems, so 1.5.0 would be rebuilt and passed over, exactly as this PR describes for the unchanged case.

Two orders that work:

1. Merge this first, tag v1.5.1, then land Surface MCP tool-discovery failures instead of running tool-less and silent #434/Schema-derived agent tools: generate a bounded tool roster from an ActiveRecord model #435/Stop nil VCR filters flaking replays, and spell the MCP plural #436 into a later 1.5.2 that bumps both gems.
2. Land Surface MCP tool-discovery failures instead of running tool-less and silent #434/Schema-derived agent tools: generate a bounded tool roster from an ActiveRecord model #435/Stop nil VCR filters flaking replays, and spell the MCP plural #436 first, then rewrite this to bump activeagent and actionagent, with a changelog covering all of them.

(2) is fewer releases if the intent is to ship the schema-tools work for testing. Either way the thing to avoid is merging #435 and then tagging this unchanged, which publishes a version of activeagent whose dashboard half is still 1.5.0 on RubyGems.

Worth noting a host app can consume all of it from the branch in the meantime — a github:/branch: pin with glob: "actionagent/*.gemspec" works today and is how this was tested end to end.