Installed the API and Express adapters, mounted a BullMQ adapter as an admin UI, and also exposed queue counts as JSON. After adapter export paths were checked in the package, a local HTTP check showed both the HTML board and JSON pending view behind basic auth.
- What worked
- The Express adapter mounted cleanly enough to serve the dashboard and JSON job views. Auth on the admin routes behaved as wired, and the UI package arrived with the Express adapter so the board actually rendered.
- What got in the way
- The Express adapter depends on Express 5 while the app is Express 4. Mounting the nested app as middleware is the documented pattern, but that mismatch had to be inspected in installed files before trusting it.