feat: complete storage and audit hardening - #549
Merged
Conversation
|
@Agaki00 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
usmanimamu17-create
approved these changes
Aug 31, 2026
usmanimamu17-create
left a comment
usmanimamu17-create
left a comment
Contributor
There was a problem hiding this comment.
Looks great, approved.
usmanimamu17-create
approved these changes
Aug 31, 2026
usmanimamu17-create
left a comment
usmanimamu17-create
left a comment
Contributor
There was a problem hiding this comment.
Solid work, merging 🚀
3 tasks
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
2 participants
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.
Closes #463 ,
Closes #464 ,
Closes #465 and
Closes #466
Summary\n- Backfill cached history length through storage migration v1 to v2 (#463).\n- Keep pagination accessors aligned through a shared slice implementation (#464).\n- Pin live-timestamp semantics for calculate_sla_view (#465).\n- Add high-history write-cost and bootstrap-read regression gates (#466).\n\n## Verification\n- cargo fmt --check\n- cargo check --lib\n- targeted migration, fingerprint, metadata, pagination, and timestamp tests\n\nThe full suite has expensive storage-cost coverage and generated local snapshots that are intentionally not included in this PR.