Greptile Summary

This PR adds four new boolean routing conditions (has_image, has_video, has_document, has_audio) to the model-association "When" filter, allowing requests to be routed based on the media types present in their messages.

• Backend: Introduces detectRequestContentFeatures in the orchestrator, which scans message multi-part content for media parts and provides an early-exit optimisation via hasAll(). Named constants for all condition fields are centralised in objects/model.go, and validateStreamLeaf is refactored into the generic validateBoolEqualityLeaf so the new fields share the same validation path.
• Frontend: The four fields are registered in the filter-builder with type: 'boolean' and the isBooleanConditionField guard is extended to cover them, ensuring correct schema validation. Locale strings for both EN and ZH-CN are included.

Confidence Score: 5/5

Safe to merge — the new content-feature detection and routing logic is well-contained, correctly validated on both frontend and backend, and covered by targeted tests.

The change is additive: new condition fields go through the same validation pipeline as the existing boolean stream field (now unified in validateBoolEqualityLeaf), the orchestrator only pays the scanning cost when conditional candidates exist, and the hasAll() early-exit prevents redundant iteration. No existing behaviour is altered beyond signature changes to matchesAssociationWhen that are fully reflected in updated tests.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Incoming LLM Request] --> B{hasConditionalCandidates?}
    B -- No --> C[Return all candidates]
    B -- Yes --> D[Compute promptTokens, stream, requestFormat]
    D --> E[detectRequestContentFeatures]
    E --> F{Scan MultipleContent parts}
    F -- ImageURL != nil --> G[hasImage = true]
    F -- VideoURL != nil --> H[hasVideo = true]
    F -- Document != nil --> I[hasDocument = true]
    F -- InputAudio != nil --> J[hasAudio = true]
    G & H & I & J --> K{hasAll?}
    K -- Yes --> L[Early return features]
    K -- No --> F
    L --> M[matchesAssociationWhen]
    F -- Exhausted --> M
    M --> N{Evaluate Condition}
    N -- has_image / has_video / has_document / has_audio --> O[Compare bool feature flag]
    N -- prompt_tokens --> P[Numeric comparison]
    N -- stream --> Q[Bool comparison]
    N -- request_format --> R[String equality]
    N -- daily_time --> S[Time range check]
    O & P & Q & R & S --> T{Match?}
    T -- Yes --> U[Include candidate]
    T -- No --> V[Exclude candidate]

_{Reviews (2): Last reviewed commit: "feat: route with media condition, close ..." | Re-trigger Greptile}