Use quota- and Jev-aware crew dispatch

[Futuri-Risk]

Parent

#1

What to build

Make one complete dispatch path use FirstMate's existing task-rule selection, Jev/System One classification and fallback, quota-axi evidence, and candidate ranking to choose among available ZCode/Codex/OpenCode worker profiles.

Do not recreate the retired standalone model-router service. The user's detailed pool preferences remain normal FirstMate configuration that can evolve later.

Cloud implementation requirement: Complete all implementation, repository changes, tests, fixtures, static/contract verification, and integration analysis possible from the GitHub/chat environment. Do not defer implementation merely because final production binaries or private services are unavailable. Clearly identify only the minimal runtime observations that require later local certification.

Acceptance criteria

• The implementation uses FirstMate's existing dispatch/profile mechanisms rather than introducing a parallel router service.
• Jev/System One is enabled through the upstream integration path.
• If Jev is unavailable, errors, or returns insufficient confidence, normal FirstMate classification continues to work.
• quota-axi is used as the quota evidence source for candidate eligibility/ranking where supported.
• Missing or unavailable quota evidence follows FirstMate's intended fallback behavior rather than crashing dispatch.
• A dispatch rule can resolve to a ZCode ACP worker profile as well as native Codex/OpenCode alternatives.
• The implementation leaves future model/effort preference tuning in configuration rather than hard-coding one fixed pool.
• Tests cover successful Jev routing, Jev fallback, usable quota evidence, missing quota evidence, and candidate selection without depending on live paid APIs.

Blocked by

• Dispatch ZCode crewmates through ACPx #3 Dispatch ZCode crewmates through ACPx