new-api

History

zizi 0427cd067a Let Muse scene policy drive relay retries and model fallback

Muse now sends scene, routing policy, and degrade policy with each per-user request, so new-api should interpret those hints instead of leaving retry scope and fallback behavior implicit in static token settings alone.

This introduces a small Muse routing-policy interpreter, lets distributor switch quality-first traffic onto auto-group retry, and retries against lower-tier model candidates when the degrade policy allows it. The policy stays lightweight and still respects user-usable groups.

Constraint: Routing decisions must remain compatible with existing channel/group selection and not require schema changes
Constraint: Muse can hint policy, but new-api must still enforce only user-usable groups and channel availability
Rejected: Hardcoding physical channel/group choices inside Muse | would keep routing ownership outside new-api
Rejected: Expanding the policy into a full declarative DSL in phase 1 | overdesigned for the immediate routing/degrade handoff
Confidence: medium
Scope-risk: moderate
Reversibility: clean
Directive: Keep Muse routing policy interpretation small and observable; if more scenes appear, extend the helper rather than scattering policy branches across middleware
Tested: go test ./service -run MuseRoutingPolicy -count=1
Tested: go test ./service -count=1
Not-tested: Live relay selection against production channel inventory

2026-04-16 21:05:22 +08:00

auth.go

refactor(task): extract billing and polling logic from controller to service layer

2026-02-22 16:00:27 +08:00

body_cleanup.go

feat(file): unify file handling with a new FileSource abstraction for URL and base64 data

2026-02-04 18:23:17 +08:00

cache.go

feat: Improve backend multilingual support

2026-02-12 14:29:56 +08:00

cors.go

feat: disk request body cache (#2780 )