Repository navigation
Fix read-only email audit authorization transport - #9
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.
The first live email-audit pilot failed before its permission check reached WordPress: the generic GET serializer rejects arrays of site records. Encode only the qualified, read-only email-audit authorization contract as indexed PHP query parameters; preserve every other nested-query restriction and existing HTTP, permission, URL and tool-policy gate.
Fleet ACL checks now use bounded batches, check every site and reject a changed actor or denied later batch before persisting or exporting evidence. HTTP-only inventory identities can be authorized on the HTTPS Dashboard while their child inspection remains explicitly failed.
Validation: reproduced the original failure first; 3,231 tests across 45 files, TypeScript, ESLint and build pass. MRN QA passes with two synthetic security-test files reviewed separately: all six secret-scanner findings are unchanged dummy strings from the baseline. No PHP/UI changes; corresponding PHP and browser/accessibility/performance rows are inapplicable. The authorized company-only native pilot completed through the repaired GET path and retained explicit incomplete-coverage findings. No other child site or settings writes were made.