Repository navigation
perf(ai): avoid full root execution hydration for history usage - #318
Merged
Merged
Conversation
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.
Refs #264. This slice removes unnecessary payload hydration from the built-in History.usage(include_children=True) root admission. It reuses the existing metadata projection, preserving tenant authorization, stored-owner comparison, pending/fresh handling, and per-execution usage authorization. Custom repositories preserve their existing read contract. No new cache, public API, or schema; fresh pending terminal handling may still read the result where required.
Scoped evidence on base
c9f92ebd: 27 tests passed (memory and SQLite plus existing owner, source and pending guards); configured Ruff and diff check passed. Matched cold SQLite root+child with 128 KB stored input: 9 → 9 SELECTs, projected SQL result text/binary bytes 93,254 → 19,438; input projection rows 4 → 3 and same UsageSummary. Bytes are measured by replaying captured queries, not network/disk bytes or elapsed time. MySQL and PostgreSQL were not run. Further consumer/backend work remains under #264; this PR does not close the issue.