Skip to content

port(omniroute): add provider and routing evaluation runs #1130

Closed as not planned

Description

@bloodf

Outcome

DurinDoor has tests and model probes, but no persisted evaluation runner and suites UI. Add repeatable operator-triggered comparisons with bounded cost.

Evidence and source state

DurinDoor baseline: 93f6de64c69b17d52f790d6f14d09a74cffc7fa5.

Implementation subtasks and acceptance criteria

  • Use deterministic suite versions and explicit model/account selection.
  • Record quality, latency, tokens, price source and failure separately.
  • Require opt-in live runs with budgets and cancellation; keep offline mode credential-free.

Dependencies

No hard predecessor. Complete source review and reproduction/discovery before implementation.

Parent epic: #1063. Roadmap: #1056. Priority P2. Stage 3.

Delivery contract

Planning ticket only. No implementation, runtime test, live-provider call, deployment or stored-data mutation was performed in this audit. Before a port, confirm a merged final upstream diff or a reachable source commit, compare local equivalents/tests, and preserve local auth/routing/quota/database contracts. Open upstream work remains a review candidate. Use port(omniroute): title and target a focused PR at bloodf/durindoor:main. Behavior changes require a focused test plus docs. Run npm run lint and cd tests && npm run test:ci; never add baseline failures. Pure docs/CI edits may skip runtime tests. Regenerate registry/agent indexes with their scripts. Preserve stored credentials and unrelated work.

Activity

  1. added
    enhancementNew feature or request
    portUpstream port work
    type:taskActionable roadmap work with acceptance criteria
    priority:P2Next: supported feature coverage and workflows
    source:omnirouteSource evidence from diegosouzapw/OmniRoute
    status:needs-triageSource comparison or product/runtime prerequisites remain
    area:observabilityUsage, telemetry and operator diagnostics
    on Oct 8, 2026
  2. added
    type:featureDefined new or extended capability
    and removed
    type:taskActionable roadmap work with acceptance criteria
    status:needs-triageSource comparison or product/runtime prerequisites remain
    on Oct 19, 2026
  3. bloodf commented on Nov 2, 2026

    @bloodf
    OwnerAuthor

    Evaluation 2026-11-01: PORT-LATER

    • Provider/routing evaluation runs. Fork: none; playground exists. Size L. Spend risk; needs budget caps.
    • Read-only check of OmniRoute source scope and local tree; nothing built or run.
  4. bloodf commented on Nov 3, 2026

    @bloodf
    OwnerAuthor

    Closing as not planned per the owner's decision: large OmniRoute feature ports are out of scope for V5. Reopen this issue if the work is picked up after V5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:observabilityUsage, telemetry and operator diagnosticsenhancementNew feature or requestportUpstream port workpriority:P2Next: supported feature coverage and workflowssource:omnirouteSource evidence from diegosouzapw/OmniRoutetype:featureDefined new or extended capability

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions