feat: mid-stream continuation plumbing — strict completions knobs + c… - #1445
Draft
hachall wants to merge 1 commit into
Draft
feat: mid-stream continuation plumbing — strict completions knobs + c…#1445hachall wants to merge 1 commit into
hachall wants to merge 1 commit into
Conversation
Deploying control-layer with
|
| Latest commit: |
02a5ca3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5eb97178.control-layer.pages.dev |
| Branch Preview URL: | https://feat-continuation-plumbing.control-layer.pages.dev |
…ontinuation key purpose Two mechanical prerequisites for the resume middleware: Strict onwards completions schema gains the generation-control fields a token-id resume replay needs: ignore_eos, min_tokens, stop_token_ids, skip_special_tokens, include_stop_str_in_output. The strict router previously dropped these on re-serialization, silently breaking resume semantics on the prod (strict) path. Round-trip + absent-by-default tests included; token-id prompt forms already supported. ApiKeyPurpose gains Continuation: a hidden per-user key purpose (like batch/playground) the resume middleware will issue continuation legs on. The purpose is what model_traffic_rules keys on to steer resume traffic to a model's continuation deployment; it also authenticates the internal request through onwards and carries per-key rate limits as a resume throttle. Wired through is_inference_purpose + both onwards key-sync SQL mirrors, hidden-key creation, tariff purpose mapping, and the manual-key- creation guard (reserved for internal use, like batch/playground). No migration needed: purpose columns are VARCHAR throughout. .sqlx cache regenerated (workspace, PG18) for the touched sync queries.
hachall
force-pushed
the
feat/continuation-plumbing
branch
from
August 5, 2026 21:56
9c51643 to
02a5ca3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ontinuation key purpose
Two mechanical prerequisites for the resume middleware:
Strict onwards completions schema gains the generation-control fields a token-id resume replay needs: ignore_eos, min_tokens, stop_token_ids, skip_special_tokens, include_stop_str_in_output. The strict router previously dropped these on re-serialization, silently breaking resume semantics on the prod (strict) path. Round-trip + absent-by-default tests included; token-id prompt forms already supported.
ApiKeyPurpose gains Continuation: a hidden per-user key purpose (like batch/playground) the resume middleware will issue continuation legs on. The purpose is what model_traffic_rules keys on to steer resume traffic to a model's continuation deployment; it also authenticates the internal request through onwards and carries per-key rate limits as a resume throttle. Wired through is_inference_purpose + both onwards key-sync SQL mirrors, hidden-key creation, tariff purpose mapping, and the manual-key- creation guard (reserved for internal use, like batch/playground). No migration needed: purpose columns are VARCHAR throughout.
.sqlx cache regenerated (workspace, PG18) for the touched sync queries.