fix(actionagent): resolve every engine constant under a host's inflections

[TonsOfFun]

1.2.1 fixed the api directory and nothing else. Seven files in this engine camelize differently once the host registers an acronym, and each raises Zeitwerk::NameError on first reference:

file	host with acronym expects	file defines
mcp_catalog.rb	MCPCatalog	McpCatalog
mcp_recording_middleware.rb	MCPRecordingMiddleware	McpRecordingMiddleware
playwright_mcp_client.rb	PlaywrightMCPClient	PlaywrightMcpClient
api_key.rb	APIKey	ApiKey
api_keys_controller.rb	APIKeysController	ApiKeysController
mcp_controller.rb	MCPController	McpController
mcp_servers_controller.rb	MCPServersController	McpServersController

Found by clicking through the mounted dashboard in a Rails 8.1 app that declares both inflect.acronym "API" and inflect.acronym "MCP". The Tools view is completely unreachable there — it 500s with uninitialized constant ActionAgent::ToolDiscovery::McpCatalog — as are the MCP endpoints and anything touching an API key. Those are not exotic acronyms to register; Rails documents the pattern, and any host with its own MCP integration will have hit this.

The fix

Rather than enumerate names, every path under this engine now camelizes with Zeitwerk's default inflector, ignoring whatever acronyms the host registered. It stays scoped by path, because the loader is shared with the host, whose own constants must keep their spelling.

INFLECTION_OVERRIDES carries any basename this engine wants spelled differently. It is empty today, which is the point: the engine names its files for the constants default camelization produces, and a file that wants a genuine acronym adds itself there rather than depending on the host.

The router half generalizes the same way. Routing does not consult the autoloader's inflector, so an acronym host asks for ActionAgent::API::MCPServersController. An all-caps run in a missing constant is now retried in the relaxed spelling (API → Api, MCPServersController → McpServersController) instead of aliasing each pair by hand.

Verification

Installed into that host and clicked every dashboard view. Before: Tools 500s. After: Tools renders (2 tools detected, 6 calls, 0 errors, attributed to the right telemetry spans), and MCP Services lists all 10 catalog entries — the view that reads McpCatalog directly. Traces, Interactions and Metrics render throughout.

Screenshots of the before/after are in the linked Sparkle PR.

Releases as 1.2.2

1.2.1 is already on RubyGems, so this ships as 1.2.2 — a host pinning >= 1.2.1 picks the fix up on its next bundle update. Until it is released, the Tools and MCP Services views 500 on any host that registers these acronyms; Traces, Interactions and Metrics are unaffected.

Note for whoever cuts the release: activeagent stays at 1.2.0 here, and the publish step added in 1.2.1 skips a version already on RubyGems, so a v1.2.2 tag publishes actionagent alone rather than failing on the duplicate.