MEMBERS-DIRECTORY-001K — Validate saved WebP responses through the Account UI boundary - #640
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Aug 13, 2026
Open
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.
Closes #639
Officer impact: No live officer workflow changes. In the preserved future My Account interface, clearly mislabeled saved-thumbnail response bytes are rejected before reaching the page, while structurally WebP bytes the browser cannot display keep the existing recoverable Photo unavailable fallback and Remove action.
Officer documentation:
SYSTEM_DESIGN.md,IMPLEMENTATION_PLAN.md,SECURITY.md, and the optional member-directory text alternative plus no-terminal evidence-review procedure indocs/officers/EVENTS_SHOP_MEMBERS.md.Deployment evidence: None. This is source-only response-boundary hardening.
memberDirectoryAvailability.tsremains byte-for-bytefalse; runmprc.com remains the inert #623 artifact; Firebase, providers, accounts, sign-in, production data, and connected-live behavior are unchanged.Outcome
Evidence
7877babc96c78f54d11685b4ffb91496c3bf6945db1211166f9a7388a40d6197f50f5b52f8d57c36524cad1dc12025e0adb09fc1c8f4e04caf5fd0359dcf682311b2a788af65cfade3094ff1979ea55c3ef55343835c3865687a4e35git diff --check: passed.No component runtime, Account wiring, CSS, admin search, Functions, Rules, index, package, workflow, release-control, provider, account, data, deployment, or live change is included. #507 retains connection/release authority, and active #616 paths/hunk are preserved.