[ckaraca]

Updates the project status notice:

• The current hosted service moves to v1.plugged.in at the cutover and keeps running there until December 31, 2026 (replaces "announced at least 60 days in advance").
• Client repos: a release pointing to v1.plugged.in will ship before the cutover; after December 31, 2026, point clients at your own pluggedin-app instance.
• PROJECT_STATUS.md: moving an account to the new platform is opt-in; nothing moves without the user's consent. Content export is available on v1.plugged.in until December 31, 2026.
• The community is welcome to carry the projects on.

Summary by Sourcery

Documentation:

• Update the project status notice with the v1.plugged.in service transition, availability through December 31, 2026, client endpoint guidance, and continued community ownership.

[sourcery-ai]

Sorry @ckaraca, this account has used its review budget of 2,500,000 diff characters for the last 7 days.

You can request another review in 18 hours and 14 minutes by commenting @sourcery-ai review.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Revises the README project-status notice to document the v1.plugged.in transition through December 31, 2026, the planned client release, post-transition self-hosting expectations, and the project’s community-driven continuation.

File-Level Changes

Change	Details	Files
Update the project-status notice to describe the hosted-service transition, migration timeline, and continued community ownership.	Replace the 60-day cutover commitment with a notice that the date will be announced separately. State that the current hosted service will move to v1.plugged.in at cutover and remain available through December 31, 2026. Clarify that a client release targeting v1.plugged.in will ship before cutover, after which clients should use their own pluggedin-app instance. Reinforce that the repository remains open for community continuation, contributions, new maintainers, and self-hosting.	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Warning

Review limit reached

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

Next included review available in 15 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 83 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Team
• Run ID: bc4c2ef0-ee57-4d39-9721-a055b2275dc6

📥 Commits

Reviewing files that changed from the base of the PR and between 641311e and 4f92c4f.

📒 Files selected for processing (1)

• README.md

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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