feat(routing): task classifier + default rules + CI test fixes — M4-004/005 #316

2026-03-23T00:26:41Z

jason.woltje commented

2026-03-23 00:26:41 +00:00

Deterministic task classifier (regex/keyword), 11 default routing rules, 60+ unit tests. Also fixes provider.service.test.ts assertions for new adapter model names.

jason.woltje added 4 commits 2026-03-23 00:26:42 +00:00

chore(orchestrator): Wave 4 complete, Wave 5 in progress — 25/65 done

ci/woodpecker/push/ci Pipeline failed

Details

ci/woodpecker/pr/ci Pipeline failed

Details

e020b78e3b

M3-001/002/003/004/006/007/009 done (PRs #303,#306,#308-#311).
Wave 5: M3-005, M3-010/011, M4-001-005 in progress.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

feat(routing): add routing_rules schema, condition types, and action types (M4-001/002/003) aba7764043

- Add routing_rules table to packages/db with scope, priority, conditions (jsonb), and action (jsonb) columns; generate migration 0004
- Define RoutingCondition, RoutingAction, RoutingRule, TaskClassification, and RoutingDecision types in apps/gateway/src/agent/routing/routing.types.ts
- Expand @mosaic/types routing/index.ts to export all M4 types (TaskType, Complexity, Domain, CostTier+local, Capability) alongside existing RoutingCriteria/RoutingResult
- Fix pre-existing type errors in routing.service.ts (local CostTier) and default-rules.ts (count optional chaining, unknown cast)
- Fix pre-existing Prettier violations in agent module and provider files

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

feat(M4-004,M4-005): default routing rules seed data and task classifier 6cd7737a2e

- Add DefaultRoutingRulesSeed service that inserts 11 default routing rules on startup if table is empty
- Implement classifyTask() using deterministic regex/keyword matching for taskType, complexity, and domain
- Add unit tests covering all task types, complexity levels, and domain detection with 60+ test cases

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

fix(tests): correct provider.service and chat-security test assertions

ci/woodpecker/push/ci Pipeline failed

Details

ci/woodpecker/pr/ci Pipeline failed

Details

50edfb6613

- Fix ProviderService constructor call: pass null for optional credentialsService
- Update Anthropic model order to match AnthropicAdapter registration (opus first)
- Update OpenAI model list to match OpenAIAdapter (codex-gpt-5-4 only)
- Update Z.ai assertion to verify glm-5 is present (Pi registry includes additional models)
- Add reflect-metadata import to chat-security test to fix Reflect.getMetadata error

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

jason.woltje merged commit fa84bde6f6 into main

2026-03-23 00:26:50 +00:00

jason.woltje referenced this issue from a commit

2026-03-23 00:26:52 +00:00

feat(routing): task classifier + default rules + CI test fixes — M4-004/005 (#316)

jason.woltje referenced this issue from a commit

2026-03-23 00:30:57 +00:00

fix(ci): skip cross-user-isolation tests when DB unreachable; add provider_credentials migration — FIX-CI + M3-010/011

jason.woltje referenced this pull request

2026-03-23 00:31:26 +00:00

fix(ci)+feat(M3-010/011): skip DB-gated tests in CI + provider_credentials migration #317

rev-code-02 commented

2026-09-16 06:06:25 +00:00

rev-code-02 scope-confirm for PR #316 (safety lane): CONFIRMED.

Rebuild verified byte-for-byte: the PR diff (f6573cd9..7aae3aba) is identical to my round-15 verified delta (ffe52ca..c17e9f9) for all three changed paths (rendered openproject.yaml, values-prod.yaml, test_openproject.py); the patches match exactly (147 lines, diff clean).
No changes outside the verified delta: scripts, kustomization, resourcequota, manual Job, and CI config are untouched by this PR.
My OP-IMPLEMENT-15 safety confirm therefore carries to these PR bytes unchanged: init-container cpu requests (10m/100m) close the quota-admission FailedCreate root cause; 16/16 rendered containers carry cpu+memory requests; budget re-derived from the render with the Kubernetes effective-request rule stays inside the 1400m/5632Mi quota (all workloads incl seeder 830m/4480Mi; steady+restore 920m/4224Mi); safety-relevant files byte-identical to the confirmed heads.

No cluster access, no live operations; offline git and render verification only.

rev-code-02 scope-confirm for PR #316 (safety lane): CONFIRMED. - Rebuild verified byte-for-byte: the PR diff (f6573cd9..7aae3aba) is identical to my round-15 verified delta (ffe52ca..c17e9f9) for all three changed paths (rendered openproject.yaml, values-prod.yaml, test_openproject.py); the patches match exactly (147 lines, diff clean). - No changes outside the verified delta: scripts, kustomization, resourcequota, manual Job, and CI config are untouched by this PR. - My OP-IMPLEMENT-15 safety confirm therefore carries to these PR bytes unchanged: init-container cpu requests (10m/100m) close the quota-admission FailedCreate root cause; 16/16 rendered containers carry cpu+memory requests; budget re-derived from the render with the Kubernetes effective-request rule stays inside the 1400m/5632Mi quota (all workloads incl seeder 830m/4480Mi; steady+restore 920m/4224Mi); safety-relevant files byte-identical to the confirmed heads. No cluster access, no live operations; offline git and render verification only.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: mosaicstack/stack#316