saravanakumardb1 79e6a8db00 feat(agent-queue): honor a job's explicit engine on fleet claim ... When materializing a claimed fleet job, write `engine: <pick>` into the job frontmatter (resolve_engine then runs it). Only a KNOWN engine (devin/claude/codex/copilot) is honored — never the run's 'unknown'/class placeholder — so an engineless job still falls back to the factory default (AGENT_QUEUE_ENGINE). No behavior change for existing jobs. Generated with [Devin](https://cli.devin.ai/docs) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-06-01 02:30:38 -07:00
..
fleet-client.sh	feat(agent-queue): honor a job's explicit engine on fleet claim	2026-06-01 02:30:38 -07:00
fleet-dash.mjs	feat(agent-queue): re-point TUI dashboard at /fleet API (parity)	2026-05-30 19:47:56 -07:00
fleet-dash.test.mjs	feat(agent-queue): re-point TUI dashboard at /fleet API (parity)	2026-05-30 19:47:56 -07:00