Repository navigation
Scope curve reads and bound async result memory - #321
Merged
Merged
Conversation
Load exact curve dependencies and hydrate catalog metadata separately. Preserve original input and publication checks. Enforce the async result budget during UTF-8 serialization and stream calendar pin decoding. Signed-off-by: zerodrift <zerodrift@users.noreply.github.com>
Signed-off-by: zerodrift <zerodrift@users.noreply.github.com>
zerodrift
enabled auto-merge
November 19, 2026 03:31
Signed-off-by: zerodrift <zerodrift@users.noreply.github.com>
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.
Changes
Verification
The same 76-point synthetic power curve and four closes were measured in Release builds on loopback. The full and dependency-scoped reads returned identical results.
At 12,031 contracts the API median improved by 21–115 ms across two runs. Cold hydration, multi-user capacity and hosted latency remain open.
See D429 and D430 in the verification and decision records for workload details and limits.