feat(sponsors): add Atlas Cloud sponsor and sponsored tip

[kevincodex1]

Add Atlas Cloud (atlascloud.ai) to the README sponsors table with its banner asset, and add an Atlas Cloud sponsored tip to the tip catalog.

Summary by CodeRabbit

• New Features

  • Added Atlas Cloud as a featured sponsor with dedicated sponsored tip content.

• Documentation

  • Updated the sponsors section to include Atlas Cloud's logo and link.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 21a971d8-fd71-44cf-975c-3a84853e8840

📥 Commits

Reviewing files that changed from the base of the PR and between 11e46af and d70c98c.

⛔ Files ignored due to path filters (1)

• docs/assets/atlas-cloud-banner.png is excluded by !**/*.png, !**/*.png

📒 Files selected for processing (3)

• README.md
• src/services/tips/sponsoredTips.test.ts
• src/services/tips/sponsoredTips.ts

📜 Recent review details

⏰ Context from checks skipped due to timeout of 900000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: smoke-and-tests

🧰 Additional context used

📓 Path-based instructions (4)

**/*

⚙️ CodeRabbit configuration file

**/*: Apply the OpenClaude maintainer review rubric from AGENTS.md. Review the current diff, not stale discussion context. Separate real blockers from suggestions. Do not request changes for vague style churn. Treat approval as merge-ready from CodeRabbit's side, pending required human review and GitHub Checks. If checks are failing or unavailable, say so clearly instead of implying the PR is fully ready.

Files:

• README.md
• src/services/tips/sponsoredTips.ts
• src/services/tips/sponsoredTips.test.ts

{README.md,CONTRIBUTING.md,docs/**,.github/pull_request_template.md}

⚙️ CodeRabbit configuration file

{README.md,CONTRIBUTING.md,docs/**,.github/pull_request_template.md}: Review docs for accuracy against current code behavior. Flag security or provider claims that overpromise, stale install commands, missing setup caveats, and instructions that could push users toward unsafe credential handling. Keep purely wording-level suggestions non-blocking.

Files:

• README.md

**

⚙️ CodeRabbit configuration file

**: # Contributing to OpenClaude

Thanks for contributing.

OpenClaude is a fast-moving open-source coding-agent CLI with support for multiple providers, local backends, MCP, and a terminal-first workflow. The best contributions here are focused, well-tested, and easy to review.

Before You Start

• Search existing issues and discussions before opening a new thread.
• Check open pull requests for work that overlaps with your contribution. If a PR already exists that addresses the same change, open an issue or discussion first to align on direction — duplicate PRs may be closed without review.
• Use issues for confirmed bugs and actionable feature work.
• Use discussions for setup help, ideas, and general community conversation.
• For larger changes, open an issue first so the scope is clear before implementation.
• For security reports, follow SECURITY.md.

Pull Requests

Every PR needs a reason. Your PR description must include:

• what changed and why
• the user or developer impact
• the exact checks you ran
• a linked issue when one exists, using Fixes fix: skip assertMinVersion for third-party providers #123, `Closes `#123, or another clear link
• screenshots when the PR touches UI, terminal presentation, or the VS Code extension
• which provider path was tested when the PR changes provider behavior

The PR author is responsible for ensuring their PR is merge-ready. PRs with merge conflicts will not be reviewed or approved until the conflicts are resolved.

Issues are the recommended starting point for anything non-trivial — opening one first helps avoid wasted effort if the change is out of scope or already being worked on. Small fixes, doc corrections, and obvious improvements can stand on their own without a linked issue, as long as the PR description explains the intent.

What Gets Closed Without Review

PRs may be closed without review...

Files:

• README.md
• src/services/tips/sponsoredTips.ts
• src/services/tips/sponsoredTips.test.ts

{src/**/*.test.ts,src/**/*.test.tsx,tests/**,scripts/**/*.test.ts,vscode-extension/**/*.test.js}

⚙️ CodeRabbit configuration file

{src/**/*.test.ts,src/**/*.test.tsx,tests/**,scripts/**/*.test.ts,vscode-extension/**/*.test.js}: Review tests for meaningful coverage of the changed behavior, isolation of global/env/config state, async cleanup, fake timers, provider profile leaks, and Windows-compatible assumptions. Block when risky runtime changes lack focused regression coverage or tests assert implementation details while missing the user-visible behavior.

Files:

• src/services/tips/sponsoredTips.test.ts

🔇 Additional comments (6)

src/services/tips/sponsoredTips.ts (2)

32-35: LGTM!

---

159-170: LGTM!

src/services/tips/sponsoredTips.test.ts (3)

107-113: LGTM!

---

126-131: LGTM!

---

142-144: LGTM!

README.md (1)

42-46: Logo asset check: docs/assets/atlas-cloud-banner.png is present and tracked — the README’s <img src="docs/assets/atlas-cloud-banner.png" ...> points to an existing, version-controlled file; no missing asset issue.

---

📝 Walkthrough

Walkthrough

This PR adds a new sponsored tip for Atlas Cloud across the tips system, including the sponsor definition with URL, test validation for the tip and its metadata, and documentation of the sponsor in the README.

Changes

Atlas Cloud Sponsored Tip

Layer / File(s)	Summary
Atlas Cloud sponsor definition and tip entry src/services/tips/sponsoredTips.ts	New ATLAS_CLOUD sponsor constant with name and URL; new atlas-cloud-platform tip entry in the sponsoredTips array that uses the sponsor and generates rendered content via renderSponsoredTip.
Atlas Cloud tip test coverage src/services/tips/sponsoredTips.test.ts	Test assertions filter for tips with sponsor "Atlas Cloud", validate exactly one exists with the expected URL, and extend unique sponsor-prefixed id validation to accept atlas-cloud- prefix.
Sponsor documentation update README.md	Sponsors HTML table updated to include an Atlas Cloud sponsor tile with logo and link.

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 5 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and omits the required template structure, testing checklist, and impact assessment sections.	Expand the description to follow the template: add Summary (why changed), Impact section, Testing checklist, and Notes. This helps reviewers understand intent and testing coverage.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and accurately describes the main changes: adding Atlas Cloud as a sponsor and creating a corresponding sponsored tip entry.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Risk Surface Disclosed	✅ Passed	PR adds sponsor metadata only (static URL string for display). Does not touch auth, network behavior, permissions, startup config, MCP, CI, or release scripts.
No Hidden Policy Change	✅ Passed	Changes limited to sponsor metadata: README table, logo image, and sponsoredTips array entry. No modifications to trust-models, routing defaults, telemetry, or permission policies.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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