Skip to content

docs(lane1): reverify outbound sender-trust item — DKIM fixed on main (PR #141), postal address blocked on operator fact (#174) - #174

Merged
nish3451 merged 1 commit into
mainfrom
lane1-outbound-sender-trust-reverify-20260815-062532
Aug 15, 2026
Merged

docs(lane1): reverify outbound sender-trust item — DKIM fixed on main (PR #141), postal address blocked on operator fact (#174)#174
nish3451 merged 1 commit into
mainfrom
lane1-outbound-sender-trust-reverify-20260815-062532

Conversation

@nish3451

Copy link
Copy Markdown
Collaborator

Lane 1 reverification report — outbound sender trust

Item: Outbound email stays blocked on sender trust: empty physical postal address and empty dkimSel

Findings (verified live 2026-08-15)

  1. DKIM half already fixed on maingrowth-brain/ops/agency-config.json carries dkimSelector: "resend" (PR fix(sales): bind outbound sender trust to Resend DKIM selector #141, fcf5ff3). Live DNS confirms SPF found, DMARC found, and DKIM found at resend._domainkey.tinystudio.io. No dkimCandidates needed.
  2. Postal address half is a real operator fact (NEEDS-NISH)senderPhysicalAddress is ""; npm run send:setup (strict) exits 1 with exactly one warning: missing physical postal address. CAN-SPAM requires the operator's real published business address (or PO box / private mailbox); no code change can supply it, and scripts/configure-sender-setup.mjs already refuses placeholders.

Regression status

  • scripts/test-operator-check-strictness.mjs — passes
  • scripts/test-active-operator-surfaces.mjs — passes
  • npm run send:setup — still honestly red on the one postal-address warning

Unblock

npm run send:configure -- --physical-address="<real address>" --dkim-selector=resend

No product code changed. Report only (.lane/reports/lane1-outbound-sender-trust-reverify-20260815-062532.md).

… (PR #141), postal address blocked on operator fact (#174)

Lane 1 reverification report: dkimSelector=resend is already set on main
(PR #141) 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>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@coderabbitai

coderabbitai Bot commented Aug 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nish3451, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 15 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: f310eb3f-7e2e-4e74-8d05-952fdbaeb44b

📥 Commits

Reviewing files that changed from the base of the PR and between 230baa8 and d5b96d6.

📒 Files selected for processing (1)
  • .lane/reports/lane1-outbound-sender-trust-reverify-20260815-062532.md

Note

🎁 Summarized by CodeRabbit Free

Your 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 @coderabbitai help to get the list of available commands.

@nish3451
nish3451 merged commit 2570be9 into main Aug 15, 2026
2 checks passed
nish3451 added a commit that referenced this pull request Aug 15, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant