Part of an ActiveAgent + actionagent dashboard functional review (multi-agent, adversarially verified). Severity: 🟠 Major.
Findings
Engine reference host (test/dummy) can't serve the dashboard standalone: routes crash and assets 404
- Where:
test/dummy/Gemfile · severity: major · kind: dx · repo: activeagent
- What breaks: Two defects make the engine's own demo host unable to render the dashboard when booted on its own bundle: (1) test/dummy/Gemfile pins
gem "activeagent", path: "../../.." but never depends on actionagent, so booting the dummy on its own BUNDLE_GEMFILE raises uninitialized constant ActionAgent when config/routes.rb draws mount ActionAgent::Engine. It only works today because the repo-root gemfiles pull actionagent in transitively. (2) The dummy host configures neither propshaft nor sprockets, so the engine's assets initializer (lib/action_agent/engine.rb:126-146) no-ops, and the mounted dashboard serves a blank page with /javascripts/action_agent.js and /stylesheets/action_agent.css 404ing.
- Evidence: Booting test/dummy under its own Gemfile:
bundle exec rails routes -> "uninitialized constant ActionAgent (NameError) ... mount ActionAgent::Engine". Booting under gemfiles/rails8.gemfile (which does carry actionagent) the dashboard renders but the browser sweep recorded 404s for /javascripts/action_agent.js and /stylesheets/action_agent.css until the builds were hand-copied into public/. Ties to the assets initializer no-op documented in the README asset-pipeline finding.
- Suggested fix: Add
gem "actionagent", path: "../../actionagent" to test/dummy/Gemfile so the reference host resolves the engine standalone, and add an asset pipeline (propshaft) to the dummy — or a static-file fallback for the two prebuilt bundles — so mount ActionAgent::Engine actually paints in the shipped demo. This is also the minimum needed for an e2e/browser test of the engine dashboard.
Verification
Each finding above was produced by a dedicated per-feature review agent, then confirmed by an independent adversarial verifier (all rated high-confidence; zero rejected in this set). File:line citations are against the current main/HEAD of each repo; many were reproduced live against a booted dashboard.
Findings
Engine reference host (test/dummy) can't serve the dashboard standalone: routes crash and assets 404
test/dummy/Gemfile· severity: major · kind: dx · repo:activeagentgem "activeagent", path: "../../.."but never depends on actionagent, so booting the dummy on its own BUNDLE_GEMFILE raisesuninitialized constant ActionAgentwhen config/routes.rb drawsmount ActionAgent::Engine. It only works today because the repo-root gemfiles pull actionagent in transitively. (2) The dummy host configures neither propshaft nor sprockets, so the engine's assets initializer (lib/action_agent/engine.rb:126-146) no-ops, and the mounted dashboard serves a blank page with/javascripts/action_agent.jsand/stylesheets/action_agent.css404ing.bundle exec rails routes-> "uninitialized constant ActionAgent (NameError) ... mount ActionAgent::Engine". Booting under gemfiles/rails8.gemfile (which does carry actionagent) the dashboard renders but the browser sweep recorded 404s for /javascripts/action_agent.js and /stylesheets/action_agent.css until the builds were hand-copied into public/. Ties to the assets initializer no-op documented in the README asset-pipeline finding.gem "actionagent", path: "../../actionagent"to test/dummy/Gemfile so the reference host resolves the engine standalone, and add an asset pipeline (propshaft) to the dummy — or a static-file fallback for the two prebuilt bundles — somount ActionAgent::Engineactually paints in the shipped demo. This is also the minimum needed for an e2e/browser test of the engine dashboard.Verification
Each finding above was produced by a dedicated per-feature review agent, then confirmed by an independent adversarial verifier (all rated high-confidence; zero rejected in this set). File:line citations are against the current
main/HEAD of each repo; many were reproduced live against a booted dashboard.