docs(lane1): report outbound sender-trust item — DKIM half already fixed in PR #141, postal address blocked on operator fact - #173
Conversation
…xed in PR #141, postal address blocked on operator fact (#173) Lane 1 verification report: dkimSelector=resend is already 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: 42 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 |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
…iew ladder, not stuck CI (#175) Lane 1 verification report: the tinystudio-in merge gate is not frozen and not defective. auto-ship merged 5 tinystudio-in PRs today (all docs/tests-only safe changes: #172, #170, #174, #168, #173), and the 12 CLEAN PRs are all code PRs that by design ride the flagship review ladder before any merge. That ladder is currently queued behind a live flagship repair (fleet-repair-3b6421dc29), so code PRs are SKIPPED/WAITING each cycle. Of 30 open PRs only 12 are CLEAN; 10 are BLOCKED (CI queued) and 8 DIRTY. No code change in this repo can unblock it. No product files changed. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
1 participant
Lane 1 report — tinystudio-in
Item: Outbound email stays blocked on sender trust: empty physical postal address and empty dkimSel
Outcome: No product code change possible or needed. The DKIM half is already fixed on main; the postal-address half is a NEEDS-NISH operator fact.
Verification
DKIM — already fixed (PR #141,
fcf5ff3, merged 2026-08-14)agency-config.jsoncarriesdkimSelector: "resend"; the earlier Cloudflare selector (cf2024-1, PR fix(sales): diagnose inbound-only mail path behind blocked sender trust #102) was superseded once Resend became the outbound provider.resend._domainkey.tinystudio.io→p=RSA key resolves;_dmarc.tinystudio.io→v=DMARC1;tinystudio.io→v=spf1 include:_spf.mx.cloudflare.net.npm run send:setup:advisory: SPF found, DMARC found, DKIM found. Only one warning remains.Postal address — genuinely blocked (NEEDS-NISH)
senderPhysicalAddressis empty;npm run send:setup(strict) exits 1 with exactly themissing physical postal addresswarning.public/pages (home, contact, support, privacy, terms, Promptly/Drishti sub-sites),docs/,growth-brain/,contracts/,scripts/were searched. CAN-SPAM requires a real published business location; the configure script already rejects placeholders.send:setupred until real values exist.Regression status
test-operator-check-strictness.mjsandtest-active-operator-surfaces.mjs(sender-guide byte-identical gate): pass.npm test: only pre-existing unrelated failure ischeck-retention-automation.mjs(canonical workspace at~/workspaces/products/tinystudio-instale behind remote main).What unblocks the remaining half
npm run send:configure -- --physical-address="<real>" --dkim-selector=resendnpm run send:setup→ should pass.CLOUDFLARE_API_TOKENsecret.Files
.lane/reports/docs-lane1-outbound-sender-trust-20260815.md(report only; no product files changed)