PERF: Optimize attack and scenario history - #2583
Draft
Richard Lundeen (richlundeen) wants to merge 1 commit into
Draft
PERF: Optimize attack and scenario history#2583Richard Lundeen (richlundeen) wants to merge 1 commit into
Richard Lundeen (richlundeen) wants to merge 1 commit into
Conversation
Promote attack operator and operation metadata to indexed fields, add query-aligned history indexes, and reduce duplicate latest-message lookups. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7540877a-bdf5-4309-97e1-14469bc817e7
Richard Lundeen (richlundeen)
marked this pull request as draft
September 5, 2026 03:44
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
1 participant
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.
Summary
operatorandoperationmetadata to bounded, indexed first-class fields while preserving arbitrary labelsValidation
uv run --no-sync pre-commit run --all-filesRollout
This PR has not connected to or changed any test or production database. It should be reviewed and tested locally before merge. The migration and application changes must deploy together; database rollout should happen separately only after approval.