fix(dispatcher): keep unclassified work on configured worker role #503
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/classifier-worker-fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Concrete Minerva latency evidence
All four occupied worker slots were observed on homelab-main/deepseek-v4-flash/medium, with classifierReceipt.phase=abandoned, despite configured dedicated Qwen worker roles. Thus worker, Main and validator traffic compete on DeepSeek. An isolated fast dispatcher probe does not reveal this productive routing fallback.
Fix for NEW, not-yet-intended work
Three new tests cover unknown, invalid and already-abandoned classifiers, one classification at most, no invented verdict, correct durable worker pair and no settled-effect replay after reload. Existing role/pin/stop/cancel/recovery tests remain.
Typecheck/build, 33 focused tests and independent review PASS. Exact rebased full suite:2642 passed, one existing optional skip, zero failures. Exact-head CI pending at last check.
End-to-end Minerva latency is not claimed fixed by this source PR: old productive route bindings and backend prefill/cache contention still require safe reconciliation/drain, not a silent runtime model switch.