fix(proof): bound accessibility attestation size - #512
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe accessibility-tree sanitization flow now uses v2 node-based HMAC attestations. A regression test covers a 1,000-node tree, attestation validity, node retention, and privacy-safe serialization. ChangesAccessibility tree attestation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Note This review was completed with usage-based billing: files reviewed beyond your plan's included limits are billed at $0.25/file. Track spend and usage in your billing settings. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/product-proof-screenshot-privacy.test.mjs`:
- Around line 375-378: Strengthen the assertions around the v2 attestation in
the tree test: recompute the expected aggregate from differentiated tree.nodes
and compare it with tree.attestation_hmac_sha256, then verify that reordering
the input nodes changes the attestation while sanitized node indexes retain the
original input order. Preserve the existing retention, digest-format, and
secret-redaction checks.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: ecf2ad4a-f30a-4f55-8b62-43108c894fb4
📒 Files selected for processing (2)
scripts/product-proof-screenshot-privacy.mjsscripts/product-proof-screenshot-privacy.test.mjs
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/product-proof-screenshot-privacy.test.mjs`:
- Around line 375-403: Strengthen the assertions around
sanitizeProductProofAccessibilityTree by deriving each expected node_hmac_sha256
from the raw nodes, then compare the complete ordered node sequence for both the
normal and reversed inputs. Build the v2 aggregate using the fixed raw-node
digests in reverse order and assert it differs from expectedAttestation,
ensuring node retention, per-node digest correctness, and digest-list ordering
are independently verified.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 817da1b9-4b72-49da-ad08-fbc7eeb0a3fb
📒 Files selected for processing (1)
scripts/product-proof-screenshot-privacy.test.mjs
Purpose
Repair the governed product-proof accessibility privacy attestation for policy-valid large accessibility trees.
Included scope
Explicit exclusions
Architecture placement
Current owner / directory: existing product-proof screenshot privacy sanitizer and its tests under
scripts/.Dependencies and duplicate-system check: reuses the existing HMAC and canonicalization primitives; no new evidence subsystem.
Security and tenancy impact
Data impact
Verification
Release safety
fd99746c9fc4c50fab5b21952a8bccb890edea40, manifest29257b0d0ce5b447d61195a526dc52ee4272dc092ccbf3ac84dd81e841327b58.Documentation and generated files
Completion check
origin/main.Policy exceptions (leave blank when none apply)
PR-size exception rationale:
Retained branch reason / owner / review date / maximum retention date:
Summary by CodeRabbit
Security & Privacy
Bug Fixes