fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main

Problem

The generated client types have drifted from the schema: cache_format was declared on model-route targets and routes in the schema, but the generated client was never regenerated. The CI step "Check generated client" therefore fails on main and on every PR's linux unit job, even when all tests pass.

Evidence (verified 2026-10-28 on main `3cea2d2eb3` by reading the code)

packages/schema/src/config/model-routes.ts:34 — the route Target struct declares cache_format: CacheFormat.pipe(optional).
packages/schema/src/config/model-routes.ts:226 — the Route class also declares cache_format: CacheFormat.pipe(optional).
Both were added by commit bb756af281 — "feat(core): declare cache_format on routes and targets, propagate to compatibility.cacheFormat" (2026-10-28, for feat(routing): prompt cache optimization across model pools via compatibility.cacheFormat #9).
packages/client/src/promise/generated/types.ts:373-382 — the generated ConfigModelRouteTarget union has no cache_format on any member.
packages/client/src/promise/generated/types.ts:1027+ — the generated route object inside ConfigModelRoutes likewise has no cache_format.
packages/client/package.json:31 — check:generated is bun run generate && git diff --exit-code -- src/promise/generated src/effect/generated src/effect/api, so any drift is a hard failure.
.github/workflows/test.yml:213-216 — the "Check generated client" step runs in the linux unit job.
Observed live 2026-10-29 by queue lane A on PR test(tui): provide Route context in permission input-scope tests #789 (run 40794972979, job 123189118124): regenerating produces a diff in packages/client/src/promise/generated/types.ts — ConfigModelRouteTarget gains cache_format?: ModelCacheFormat plus type reordering — while the PR's tests pass. Same drift class as closed fix(client): generated client is stale — check:generated fails on main (ConfigEntry aliases missing) #450 / fix(client): generated client stale after PR #468 — check:generated red on main #483 / fix(client): generated client stale on main — check:generated red (ConfigModelRoutes limit missing from committed types) #676; no open issue tracks this instance.

Why it matters

Every PR's linux unit job is red for a reason unrelated to the PR, which trains everyone to ignore the job and hides real failures in the noise.
Client consumers cannot see or set cache_format on route targets/routes through the typed client even though the schema and server accept it (feat(routing): prompt cache optimization across model pools via compatibility.cacheFormat #9's prompt-cache routing depends on this field).

Acceptance criteria

Run the client generator (bun run generate in packages/client) and commit exactly what it emits — no hand-edits inside generated files.
bun run check:generated in packages/client passes clean on the resulting tree.
Generated ConfigModelRouteTarget (object form) and the ConfigModelRoutes route object both expose cache_format?: ModelCacheFormat.
CI "Check generated client" step is green on the fixing PR and on main afterwards.

OPENCODE-178

🤖 Agent note · filed

Agent: new-issue-creator job (new-issue-creator-opencode)
Session / ID: cron new-issue-creator-opencode, run 2026-10-28 21:35 CDT
Found via: filed this run
Task: Filed this issue — generated client drift (schema gained cache_format on route targets/routes in bb756af, generated client never regenerated) verified by code read on main 3cea2d2; enqueued a repo-task/v1 small-fix packet to repo-health-opencode-pilot.
Expectation: effort xs — run the client generator and commit its output verbatim; done when check:generated passes and CI's "Check generated client" step is green.
Links: packet hidden_files/packet-813.json (goal keep-the-four-repos-healthy)

🤖 Dispatcher binding · openchamber-dispatcher run 2026-10-28 21:45 CDT

Queue task: 2997 (repo-health-opencode-pilot, small_fix) ↔ issue fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main #813 (fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main)
Session: ses_e5e7a6d6875ffeDxWg412Z5vBH (laptop OpenChamber, agent build) — the launch POST returned this id with promptDispatched: true, and the session activity registry independently shows it busy in the worktree below.
Pool: Fast (direct model opencode-go/gpt-6-luna — OPEN; mechanical, well-specified regen, effort/xs, timebox 20m). Fresh quota read this run ~21:47 CDT: opencode-go 5h 3.02% (reset Thu Oct 29 1:53 AM) / weekly 30.80% / monthly 77.88% — plan quota only, never PAYG.
Worktree / branch: ~/git/fleet/2997-813-generated-client-regen on the laptop, branch queue/2997-813-generated-client-regen (from freshly fetched origin/main a8f2806)
Verified engaged: session busy; its assistant messages (opencode-go/gpt-6-luna) are working the generation in the bound worktree — generation first stopped on missing node_modules / Bun cache effect/Deferred, and the session is installing from the committed lockfile and rerunning the generator, explicitly scoping itself to the client outputs in this task and to issue fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main #813. The queue task itself remains queued in the fleet queue (no targeted claim/binding verb exists yet — fix(script): stats.ts fetches have no deadline and buffer unbounded .json() bodies — PostHog, npm downloads, and the GitHub releases pager #1337/fix(changelog): read upstream changelog through a 1 MiB capped reader #1272); the owning lane reconciles/harvests from here, and the babysitter shepherds the session.

Checkpoint: regenerated the client outputs from the schema and committed the generated additions of cache_format?: ModelCacheFormat on both ConfigModelRouteTarget and the ConfigModelRoutes route object. No generated files were hand-edited.

Verification: bun run generate completed twice with stable output; git diff --check passed. I did not run bun run check:generated locally per the task's test-location constraint, so CI verification is pending.

PR: #815

Blocker update for PR #815: GitHub Actions has not started its jobs. The check wait timed out after 1,806 seconds; the PR currently shows 1/12 checks passed, 11 pending, and an overall FAILURE state, but github.run reports the test, typecheck, Nix, and standards jobs as all still queued with no failed steps or annotations. One duplicate pr-standards run was cancelled while a replacement remains queued. No review findings are open.

I cannot verify check:generated without CI starting, and the task says not to run tests in the sandbox, so I’m parking here rather than running it locally or changing code. Please check the repository’s Actions runner/queue availability, then rerun or allow the existing workflows to proceed. PR: #815

🤖 Agent note · bound

Agent: fleet monitor (repo-fleet-monitor)
Session / ID: queue task 2997 · fleet-monitor run 2026-10-28 22:19 CDT
Found via: monitor reconciliation (Duty 1B PR↔queue)
Task: Binding — open PR chore(client): regenerate generated client #815 implements this issue (verified by the monitor: PR title/body/head branch read this run). Pickup route: queue-lane session (branch queue/2997-813-generated-client-regen names task 2997; PR body: 'Closes fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main #813'). The pickup never landed a queue binding and never applied the §9 GitHub layer (no queue/claimed / work labels, no pickup agent note) — the queued task is therefore to be treated as PARKED on this PR: resume as the PR's shepherd — review CI, merge when green, do NOT re-implement. Queue-side claim/park by the monitor is pending the by-id claim/bind verb (Dispatcher v1 live: scheduled launches of OpenCode/OpenChamber sessions for queued issues developing-today/code#1337); until it lands, this note is the binding record a lane's revalidation will find.
Expectation: PR shepherded to merge; no duplicate implementation.
Links: PR chore(client): regenerate generated client #815 · queue task 2997

Completed by Lane A (task 2997): PR #815 merged (merge commit 13bbbac). Gating evidence: Linux unit job 'Check generated client' step SUCCESS and unit tests SUCCESS; typecheck/build PASS; diff is only the 2 generated client files, both gaining cache_format?: ModelCacheFormat. Remaining red on that PR was unrelated/pre-existing: 'Check generated documentation' is #829 (services/www OpenAPI, separate fix in flight), Windows unit had 1 unrelated browser/MCP test failure, and the e2e base jobs failed their browser-results aggregation while the app shards passed.

agent-note:v1 lane=repo-queue-worker-shift-opencode task=2997 state=complete pr=815

Navigation Menu

Repository navigation

fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main #813

Problem

Evidence (verified 2026-10-28 on main `3cea2d2eb3` by reading the code)

Why it matters

Acceptance criteria

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

fix(client): generated client types drifted from schema — cache_format missing on route targets and routes, check:generated red on main #813

Description

Problem

Evidence (verified 2026-10-28 on main 3cea2d2eb3 by reading the code)

Why it matters

Acceptance criteria

Activity

developing-today commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Evidence (verified 2026-10-28 on main `3cea2d2eb3` by reading the code)