generated provenance: duplicate exception logging sweep (#1612/#1698)

[seonghobae]

Current authority — 2026-09-18

• protected base: develop@042b0c70531b229af3acbd0421a2f23098d848b3
• generated predecessor: 40b296926f12e1b759df00553730aac312167533
• ordinary corrective child / exact current head: 30af5fb57e8afd3ca8774afef43cce8535490c8e
• exact current tree: 8fde14381aaa430eeaaf61151dab6f6800127cd3 — byte-identical to protected develop
• fresh compare base → head: ahead 2 / behind 0 / zero changed files
• lifecycle: Draft / zero-effective-delta generated provenance / canonical security owners fix(security): stabilize exception-redaction successor #1612 + security(logging): stop treating exc_info tracebacks as exception-detail redaction #1698/fix(security): bound exception telemetry without raw traceback #1700 / do not merge or close until succession is verified

Verified finding in the generated predecessor

The generated commit correctly noticed raw exception interpolation such as f"...{e}", but its blanket replacement with static text plus exc_info=True did not establish exception-detail confidentiality. Standard Python traceback formatting still renders the exception type/value when exc_info=True is attached to the LogRecord. The generated .jules/sentinel.md claim that this preserves full traceback details while avoiding exception-message leakage was therefore internally contradictory.

The same generated sweep also changed the exact production paths already owned by canonical exception-redaction successor #1612: backend/api/emails.py, backend/api/prompts.py, backend/import_fixtures.py, backend/scripts/import_fixtures.py, backend/services/imap_worker.py, backend/services/llm_service.py, and backend/services/pop3_worker.py. #1612 additionally owns the shared backend/core/safe_logging.py contract and focused confidentiality tests. Its LLM paths already replace raw exception values with redacted_exception_info(...) and raise generic LLMServiceError outside the sensitive exception chain, which is strictly stronger than the generated exc_info=True rewrite.

Issue #1698 explicitly records this exact class of failure: treating exc_info=True as redaction is not a complete CWE-532 mitigation. #1700 is the structured telemetry foundation successor and removes raw exception values/original traceback while retaining bounded exception class + one-way failure-site fingerprint; sink-specific migrations are stacked from that owner rather than copied into a new broad sweep.

Corrective action

The generated predecessor was not force-rewritten or simply closed. Ordinary child 30af5fb... preserves the generated commit in ancestry while restoring the protected develop tree byte-for-byte. This removes the weaker duplicate implementation from the effective PR delta without discarding its provenance.

No #1612/#1698/#1700 source, test, helper, doctoring, or prior evidence is copied into this branch. No hosted receipt produced by this zero-effective-delta provenance may transfer to those canonical owners.

Lifecycle boundary

Keep this PR open and Draft as provenance until #1612 or a verified complete successor reaches protected ancestry and a fresh succession audit confirms that every valid security/public-error delta represented by the generated predecessor is already covered by the canonical lineage. Only then may this PR retire under the verified-succession rule.

Do not restore the generated blanket exc_info=True sweep, add a second sanitizer, self-approve, fabricate statuses, manufacture a wake/no-op commit, force-push, destructively rebase, or weaken the canonical security gates.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}