docs(lane1): reverify outbound sender-trust item — DKIM fixed on main (PR #141), postal address blocked on operator fact - #179
Conversation
… (PR #141), postal address blocked on operator fact (#177) Lane 1 third re-verification report: dkimSelector=resend is set on main (PR #141, fcf5ff3) and the live resend._domainkey.tinystudio.io record resolves; SPF, DMARC, and DKIM all verify. The only remaining sender warning is the empty senderPhysicalAddress, which requires a real published business address (CAN-SPAM) that no code change can supply. No product files changed. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
1 participant
Lane 1 third re-verification report for the outbound sender-trust item.
Verification (live, 2026-08-15)
dkimSelector: "resend"is set on main (PR fix(sales): bind outbound sender trust to Resend DKIM selector #141, fcf5ff3) and the liveresend._domainkey.tinystudio.iorecord resolves.npm run send:setup:advisory(live DNS): SPF found, DMARC found, DKIM found.npm run send:setup(strict) exits 1 with exactly one warning:missing physical postal address—senderPhysicalAddressis""ingrowth-brain/ops/agency-config.json.node scripts/test-operator-check-strictness.mjspasses (exit 0).Why no product code change
The DKIM half is already merged and verified live. The postal-address half is a NEEDS-NISH operator fact: CAN-SPAM requires the real published business location (or PO box / private mailbox), which cannot be invented by code. The configure script already refuses placeholders and requires a real-looking address, so no code gap remains.
Unblock
npm run send:configure -- --physical-address="<real address>" --dkim-selector=resendnpm run send:setup— should pass with SPF, DMARC, DKIM, and the address verified.No product files changed; this PR contains only the lane report.