[oschwald]

Adds two optional inputs to the minFraud request email object: verification_time (RFC 3339 date-time) and was_verification_successful (boolean). They describe the most recent verification of the email address. The request example and the bundled spec are updated.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Email requests can now include when the most recent email verification occurred and whether it succeeded. Verification timestamps outside the accepted range are ignored with a warning.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 1e5eb5ac-3912-4f1b-8806-bbf83027e059

📥 Commits

Reviewing files that changed from the base of the PR and between 2d8caaf and 90b80da.

📒 Files selected for processing: 2

• bundled/minfraud.yaml
• components/minfraud-request.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The minFraud Email request schema adds optional fields for the most recent email verification time and outcome. The schema descriptions specify timestamp limits and when to omit the outcome. The bundled schema and request examples include values for both fields.

Changes: Email verification fields

Layer / File(s)	Summary
Define and show email verification fields components/minfraud-request.yaml, bundled/minfraud.yaml, examples/minfraud/request.yaml	The Email schema adds an RFC 3339 verification_time and a boolean was_verification_successful. The descriptions specify that timestamps before 1970-01-01 or more than two days in the future are ignored with a warning, and that the outcome field should be omitted if verification was not performed. The request examples include values for both fields.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 90b80

The optional email verification fields are consistently defined and represented across the source specification, bundle, and example.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely identifies the main change: adding email verification inputs to the minFraud request.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

_{A rabbit checks the timestamp bright,
And marks the outcome, true or not.
The schema holds these fields in sight,
With examples showing what was sought.
Then hops away, content with the plot.}

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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.