Skip to content

lagger: free-provider paths (OpenCode Zen, Groq, Gemini) and key_state with reset tracking #13323

Open

Description

@gHashTag

The owner's tier order is 1 OpenCode Zen, 2 OpenRouter :free, 3 Groq, 4 Google AI Studio Flash, 5 z.ai GLM, 6 NVIDIA NIM, 7 DeepSeek, 8 Sonnet, 9 Opus. Today lagger has paths for z.ai (PATH_ZAI=0), OpenRouter free (1), NVIDIA free (2), LMS local (4) and DeepSeek (8, paid, unfunded); Zen and Groq have none and Gemini has a provider row only. PATH_MASK_MAX is 16: 9 existing paths plus 7 new make 16, so Sonnet and Opus cannot get their own paths without widening the mask; that is an open design question for the implementer to settle. This issue EXTENDS lagger.t27, model_route.t27 and keys.t27 and adds no second spec. It starts after draft PR #13317 (run budget guard), which currently edits lagger.t27, lands. Seals of all three specs must be re-saved by a master-built t27c. Refs #13260

Boundary

  • specs/t27os/lagger.t27
  • specs/claw/model_route.t27
  • specs/t27os/keys.t27

User Scenarios

  • Given a bulk task when the route is chosen then it is OpenCode Zen with OpenRouter :free as fallback.
  • Given an architecture task when routed then it is Opus with Sonnet as fallback; a critical fix or final review is Sonnet with Opus as fallback.
  • Given a provider key is rate limited when key_state is read then it shows status RATE_LIMITED and the next reset eta.
  • Given every free provider is exhausted when the owner is told then the only notice is FREE POOL EXHAUSTED with a per-provider status.

Requirements

  • FR-001: lagger.t27 MUST add free-provider paths for OpenCode Zen, Groq and Google AI Studio Flash in the owner's tier order.
  • FR-002: keys.t27 MUST define a key_state record with alias, provider, last_reset, next_reset_eta, reset_cards_available and status of OK, RATE_LIMITED or EXHAUSTED; it MUST hold aliases only and never a key value.
  • FR-003: model_route.t27 MUST map the task classes bulk, architecture, critical fix and final review to the primary and fallback tiers above.
  • FR-004: The owner notice MUST read FREE POOL EXHAUSTED with per-provider status and nothing else.
  • FR-005: The change MUST add no new spec file.

Success Criteria

  • t27c test-report specs/t27os/lagger.t27 exits 0, reports FAIL 0 and vacuous passes 0, and tests for the new paths appear.
  • t27c test-report specs/claw/model_route.t27 and t27c test-report specs/t27os/keys.t27 exit 0 and report FAIL 0, with tests for the task-class routes and key_state.
  • git diff --name-only origin/master lists 0 files outside the Boundary and the re-saved seals.

Activity

  1. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Spec created: specs/t27os/lagger_free_provider.t27 (typecheck OK, 1 test pass).

  2. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.

  3. gHashTag commented on Nov 17, 2026

    @gHashTag
    CollaboratorAuthor

    Specs created for M10 milestone. Typecheck OK.

  4. gHashTag commented on Nov 18, 2026

    @gHashTag
    CollaboratorAuthor

    Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions