OBS-001A3: remove raw frontend console error payloads - #143
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
8 tasks
daliu
marked this pull request as ready for review
July 13, 2026 11:07
daliu
force-pushed
the
codex/issue-142-console-privacy
branch
from
July 13, 2026 11:09
299ed2c to
bcb8b35
Compare
This was referenced Jul 13, 2026
Closed
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.
Outcome
The remaining browser diagnostics covered by #111 no longer pass caught errors, provider objects, or React component stacks to
console. Five fixed outcome identifiers are the only application/public runtime console path, and a broken console cannot alter the underlying member flow.Tracks #142. Parent tracker: #111.
Security invariant and failure behavior
ErrorBoundarystill sends the original error through OBS-001A1 — Disable Sentry replay and fail closed for personal data #134's sanitized Sentry wrapper; only its raw console copy is removed.Scope
src/services/monitoring/clientDiagnostics.tsand focused testsrc/components/ErrorBoundary.tsxsrc/components/MembersOnly.jsxsrc/services/identity/Identity.tssrc/services/firebase/FirebaseResources.tsSECURITY.mdandOPERATIONS_RUNBOOK.mdExcluded: Sentry sanitizer/config, Analytics, signup/profile/Auth Functions, Stripe/webhooks, Strava/OAuth, Rules, provider consoles, production data, cookies/history, and sitemap.
Test evidence
Node 20.20.2 on exact rebased head
bcb8b353f60b34f874371da5ee94826439fc615b, base2e3228acc7be649e0b154b450f7bac362e8dfb83:--max-warnings=0: passed.git diff --check: passed.29245243743passed frontend, Functions, and Firestore Rules on this exact head. Netlify created a review-only deploy preview; that is not production evidence. Earlier run29244983108is historical evidence only.4d0f4aeba1e32fb708991611eee9a3621206b7c2b329c7749815091e86dff28c.Tests use mocks, static runtime-source inspection, and synthetic privacy canaries. They make no Firebase, Sentry, or other provider call.
Compatibility / rollback
No dependency, schema, route, storage, permission, provider, or public-content change. Existing error UI/state and promise behavior remain unchanged. Rollback would restore raw caught objects to browser consoles and requires privacy review.
Officer impact: None — member/officer tasks and screens behave the same; only diagnostic payloads change.
Officer documentation: None — no officer procedure, navigation, permission, or collected field changes. Engineering security/operations evidence is updated.
Deployment evidence:
runmprc.comverification: not performed; no exact revision is claimed live.