chore(release): activeagent and actionagent 1.5.2

[TonsOfFun]

Bumps both gems to 1.5.2 and stamps the changelog. Tag v1.5.2 after this merges to publish.

Why 1.5.2 and not 1.5.1

#437 bumped activeagent to 1.5.1 and deliberately held actionagent at 1.5.0, which was correct for its own contents (#430, a lib/ fix). But #434, #435 and #436 merged alongside it, and two of those change actionagent.

v1.5.1 was never tagged. Had it been, release.yml would have skipped actionagent as already on RubyGems and published a release whose entire dashboard half — schema tools, the registration seam, MCP discovery errors — stayed invisible.

The 1.5.1 heading is kept in the changelog marked superseded rather than deleted; it is the record of what that bump contained.

Contents

PR	What
#435	Schema-derived agent tools, the AgentToolbox/editor registration seam (closes #438), directory discovery and scope_by_policy (refs #440)
#434	MCP tool-discovery failures reported instead of running tool-less and silent (closes #425)
#436	Nil VCR filters no longer flake replays; MCP plural spelling
#430	Evals::ModelSpec.parse_all names a spec hash's model rather than stringifying it (carried from the untagged 1.5.1)

Verification

rake build_all produces activeagent-1.5.2.gem and actionagent-1.5.2.gem. Checked inside both archives rather than trusting the build output:

• activeagent — lib/active_agent/schema_tools.rb present, scope_by_policy in it
• actionagent — discovered_schema_tools in lib/action_agent.rb, discovery_errors in mcp_tool_dispatcher.rb, and the rebuilt app/assets/builds/action_agent.js (the dashboard ships a precompiled bundle, so a stale one would silently omit the selectable tool cards)

Installed activeagent-1.5.2 into a clean GEM_HOME and loaded SchemaTools from the installed copy.

Against a host application on both built gems:

activeagent=1.5.2 actionagent=1.5.2
discovered=["MilestoneTools", "TaskTools", "TicketTools"]   # no config.schema_tools declared
available_tools=22                                          # 13 built-ins + 9 generated
call={:count=>6}                                            # real data, through the host's Pundit scope

Its suite is green on the built gems.

Publishing

rake build_all prints the order it needs: activeagent before actionagent, which depends on it.