Skip to content

fix(client): generated client stale on main — check:generated red (ConfigModelRoutes limit missing from committed types) #676

New issue
New issue
Closed
#685
Closed
fix(client): generated client stale on main — check:generated red (ConfigModelRoutes limit missing from committed types)#676
#685
Labels
area/ciCI, workflows, and build infrastructureeffort/xsTrivial: expected under 30 minutes of workkind/bugSomething isn't working (prefixed form of the classic bug label)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivesource/queue-workerFiled or worked by the queue/worker pilotstatus:done

Description

@dezren39
dezren39
opened on Oct 28, 2026

Symptom

The unit (linux) job's Check generated client step (bun run check:generated) fails on current main, deterministically (original run + rerun).

Seen on PR #668 run 40628099113, job unit (linux) (rerun at 2026-10-28T04:56Z): regeneration produces a diff in packages/client/src/promise/generated/types.ts:

     } >
+    limit?: { context: number }
   }

in ConfigModelRoutes — a schema-side limit: { context } field exists but the checked-in generated client was never regenerated after it landed.

Why this is a main problem, not a PR problem

PR #668 is a one-line workflow change (.github/workflows/branch-cleanup.yml: pin actions/checkout to the v4.3.1 SHA, for openchamber#628). It touches no source, schema, or client code, yet fails this check on both the original run and the rerun. Every other job on that PR is green (typecheck, nix-eval, affected packages, unit windows, builds, e2e).

History

Same failure class as #483 and #450 (both fixed instances). This is a new instance: a schema change adding ConfigModelRoutes.limit landed without the regenerated client.

Acceptance

  • Identify the schema change that added ConfigModelRoutes.limit and land the regenerated client (bun run generate) for it.
  • bun run check:generated passes on main; unit (linux) green on an unrelated PR.

Found by repo-queue lane B while shepherding task 1656 / PR #668.

Acceptance criteria

  • The schema change that added ConfigModelRoutes.limit is identified, and the regenerated client (bun run generate) for it is landed on main.
  • bun run check:generated passes on main, and the unit (linux) job is green on an unrelated PR.
  • No hand-edits to generated files: the committed generated output matches the generator's output exactly.

Activity

  1. dezren39
    added
    kind/bugSomething isn't working (prefixed form of the classic bug label)
    on Oct 28, 2026

  2. developing-today commented on Oct 28, 2026

    @developing-today
    developing-todayBot
    on Oct 28, 2026 – with developing.today

    OPENCODE-128

  3. dezren39
    added
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    priority/highImportant and time-sensitive
    effort/xsTrivial: expected under 30 minutes of work
    source/queue-workerFiled or worked by the queue/worker pilot
    status/needs-triageNot yet triaged; needs a first look
    area/ciCI, workflows, and build infrastructure
    on Oct 28, 2026

  4. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    Author

    Intake review — fleet monitor

    Liveness: Verified still live at intake: no merged PR closes it (it remains open, with a live queue task where queued). This is a new instance of a known class, not a duplicate: #483 and #450 were earlier instances, both fixed.

    Related: #483, #450 (prior stale-generated-client instances). Filed by repo-queue lane B while shepherding PR #668 / task 1656 — that PR is unrelated and should not carry this fix.

    Notes / risks: Priority set to high at intake: a red unit (linux) check on main taxes every unrelated PR until it lands. The fix is regeneration, not hand-editing — the worker should name the schema commit that added ConfigModelRoutes.limit in the PR so the class stays traceable. The issue's own ## Acceptance section is restated under the standard ## Acceptance criteria heading in the body.

    Suggested approach: Identify the schema change, run bun run generate, land the regenerated client as its own small PR, confirm check:generated green on main.

    🤖 Agent note · state: filed

    • Agent: fleet monitor
    • Session / ID: repo-fleet-monitor run 2026-10-28 00:20 CDT
    • Found via: monitor reconciliation
    • Task: Intake enrichment (§5 pass): acceptance criteria appended under the standard heading, labels normalized (priority/high, effort/xs, source/queue-worker, status/needs-triage), this review posted.
    • Expectation: effort/xs as labelled; done = the acceptance criteria on the issue are met.

  5. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    Author

    🤖 Agent note · picked up

    • Agent: issue sweep (issue-sweep-rotating)
    • Session / ID: issue-sweep-rotating run 2026-10-28 02:24 CDT (random pick 1 = developing-today/opencode)
    • Found via: sweep pickup
    • Task: regenerate the stale generated client for ConfigModelRoutes.limit and land it (no hand-edits to generated files)
    • Expectation: effort/xs — done = branch + PR with only regenerated client output, bun run check:generated verified on the laptop, PR merged when its checks are green or log-verified known flakes only
  6. dezren39
    added
    work/self-assignedAn agent grabbed this item directly, outside the queue
    status/in-progressActively being worked
    and removed
    status/needs-triageNot yet triaged; needs a first look
    on Oct 28, 2026
  7. developing-today
    added
    status:in-review
    on Oct 28, 2026

  8. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    Author

    🤖 Agent note · parked

  9. dezren39
    added
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    status/in-progressActively being worked
    on Oct 28, 2026

  10. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    Author

    🤖 Agent note · check-in

    • Agent: fleet monitor (repo-fleet-monitor)
    • Session / ID: repo-fleet-monitor run 2026-10-28T09:19Z
    • Found via: monitor reconciliation (in-progress tracker)
    • Task: Check-in on a past-threshold held item. Holder: issue sweep (issue-sweep-rotating), self-assigned 2026-10-28T07:27Z, parked awaiting CI at 07:38Z (effort/xs, 1h expectation; ~1.9h elapsed at this check-in). PR fix(client): regenerate client for ConfigModelRoutes.limit #685 shows CI activity (most checks completed by 08:41Z, e2e (linux)/(windows) still queued) — activity counts, so this is a check-in only, not a requeue.
    • Expectation: Holder: please checkpoint, park with a fresh resume condition, or hand off on the issue and PR fix(client): regenerate client for ConfigModelRoutes.limit #685.

  11. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    Author

    🤖 Agent note · picked up (resumed from CI park)

    CI evidence (run 40650732742, head f4844ac): typecheck / nix-eval / affected packages / build (linux+windows) / e2e app-1, app-components, session-ui-components (both OS) SUCCESS. Failures log-verified as pre-existing and unrelated to this 1-line generated-client change (packages/client/src/promise/generated/types.ts +1/-0):

  12. dezren39
    added a commit that references this issue on Oct 28, 2026

    fix(client): regenerate client for ConfigModelRoutes.limit (#676) (#685)

    a2d6aad
  13. dezren39
    closed this as completedin #685on Oct 28, 2026
  14. developing-today
    added
    status:done
    and removed
    status:in-review
    on Oct 28, 2026

  15. dezren39 commented on Oct 28, 2026

    @dezren39
    dezren39
    on Oct 28, 2026
    Author

    🤖 Agent note · done

  16. dezren39
    removed
    status/parkedDeliberately paused with a recorded resume condition
    work/self-assignedAn agent grabbed this item directly, outside the queue
    on Oct 28, 2026
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/ciCI, workflows, and build infrastructureeffort/xsTrivial: expected under 30 minutes of workkind/bugSomething isn't working (prefixed form of the classic bug label)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivesource/queue-workerFiled or worked by the queue/worker pilotstatus:done

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions