Repository navigation
Conversation
Contributor
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
404oops
force-pushed
the
fix/realtime-record-continuation
branch
from
November 1, 2026 18:26
08cd9be to
e11fd03
Compare
This branch has not been deployed
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.
Use the populated settled-credit predicate for post-record continuation. Positive fractional settled credit keeps the conversation open even while its own response hold is unreleased. New work still requires atomic admission including all outstanding holds. A failed/zero-result metering write does not turn a stale cached predicate into a fresh continuation decision.
Validation: regression tests cover a half-micro-cent remaining balance, exhausted-account closure and exact response-hold release. Existing atomic admission, stale/cold cache, provisional-plan and metering failure tests are retained. In the measured warm case, cached continuation made zero Redis hold-sum, KV-get and SQL-read calls; the headroom comparison made one Redis hold-sum call and zero KV/SQL reads. No fixed database-read count is assumed.
Final combined validation at
7adeb371e177a9532bac5d78a3f83318d1af4757: 625 backend tests, 122 SDK conversation/history/transport tests, 10 built-SDK mock-provider tests and 3 cross-platform API checks passed. Backend build, SDK declaration checks and lint passed; repository typecheck reports no new errors with 23 known baseline errors. No paid/live provider traffic or production rollout test was run.Stack: follow-up 6/7, overall 12/13. Based on #4455 (
fix/realtime-transcription-settlement). Review and merge bottom-up. The existing six-PR stack ends at #4441.