feat: show naruon mailbox status fail-closed (v0.80.0)

[seonghobae]

Buyer impact

After login, Mailbox sits above Calendar. When naruon is unconfigured or HTTP is down, Demo Analyst sees Mailbox · naruon not available. When the published inbox envelope is accepted, thread subjects are listed. Click does not invent a source post. Never invent a thread.

Exact head

f717beab43ea3e9a6b5235fe312d82b65b8b2b2e on feat/naruon-mailbox-fail-closed-v0730.

Base: main @ 7464abb (merged #211 leftover pairs).

Review gate

• Do not mix into Role, responsibility, and agent ontology (v2.10.0) #74 or feat(ui): show business context on related-node chips (v0.75.0) #92.
• Independent exact-head APPROVE required before squash.
• Do not self-approve.
• Do not merge from this PR author.
• Owner/self COMMENT is not APPROVE.

Not in this slice

Leftover pairs landed as #211. TEPP is #214. ThreadWeave conversations are #219. RankWeave rankings are #220. Keyverse identity is #221. Mapping mailbox threads onto lineage posts stays reserved by ADR 0020.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 13 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ed48b5a4-6563-4c08-b1ce-3f7cd4a21031

📥 Commits

Reviewing files that changed from the base of the PR and between 8c020aa and 119251f.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (20)

• .env.example
• AGENTS.md
• ARCHITECTURE.md
• CHANGELOG.d/0.80.0-naruon-mailbox-fail-closed.md
• CHANGELOG.md
• README.md
• backend/app/config.py
• backend/app/main.py
• backend/tests/test_api.py
• docker-compose.yml
• docs/adr/0020-naruon-mailbox-fail-closed.md
• frontend/package.json
• frontend/src/App.test.tsx
• frontend/src/App.tsx
• frontend/src/api.ts
• lineageweave/__init__.py
• lineageweave/naruon_client.py
• pyproject.toml
• scripts/seed_demo_data.py
• tests/test_naruon_client.py

---

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.}

[seonghobae]

@cwl-noema-review

Independently review exact head 50eec7c763b67e357c785bd9ab23a7c80e3022b6.

Buyer-visible naruon mailbox: fail-closed when HTTP is down, no invented thread. Do not treat this comment as approval. Do not merge without an independent exact-head APPROVE plus green required checks on this SHA. Owner/self COMMENT is not APPROVE.

[seonghobae]

Write-first cycle 2026-08-17T09:05Z (KST 18:05).

Exact head 50eec7c still needs an independent exact-head APPROVE before squash. Owner/self COMMENT is not APPROVE. I will not self-approve and I will not merge this from the PR author.

Mailbox stays fail-closed: default transport raises NaruonNotAvailable; seed never invents a message; click does not invent a source_post. Next main-stack buyer gap is ThreadWeave conversations (v0.74.0), not a mailbox-on-#217 follow-up and not Keyverse IdP. Do not mix this into #74 or #92.

[seonghobae]

Exact head f717bea is waiting on independent current-head APPROVE. This COMMENT is not APPROVE and is not a merge. Do not self-approve. Do not invent a thread.

[seonghobae]

Rebased onto main@8c020aa (RankWeave v0.75.0). Version bumped 0.73.0 → 0.80.0 so this does not downgrade main. Rankings and Mailbox both stay. Independent exact-head APPROVE still required. Do not mix into #74 or #92.