Fix OpenCut logo in README

[Aspenini]

ik that this isn't a critical bug, but the logo wasn't showing in the readme

Summary by CodeRabbit

• Documentation
  • Updated the project header image reference in README.

[vercel]

@Aspenini is attempting to deploy a commit to the OpenCut OSS Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0a9be8e3-5efe-425f-86f8-30fdde5e92d0

📥 Commits

Reviewing files that changed from the base of the PR and between 26d523e and cfc9b4e.

📒 Files selected for processing (1)

• README.md

---

📝 Walkthrough

Walkthrough

The README.md file is updated to reference a different logo file for the header image, changing from a PNG in the 1k directory to an SVG file at the root of the logos directory.

Changes

Cohort / File(s)	Summary
Documentation README.md	Updated header image source path from apps/web/public/logos/opencut/1k/logo-white-black.png to apps/web/public/logos/opencut/icon.svg.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix(style): README.md header section #134: Modifies the README header image/section structure and sizing, complementary to this logo source update.
• style(README): insert logo in header #42: Updates README header logo usage with layout adjustments, shares similar header image modification scope.
• Github readme logo fix. #699: Previously modified the same logo reference path that this PR is now changing from.

Poem

🐰 A new logo springs forth so bright,

SVG replaces the old PNG sight,

Header now gleams in vector delight,

OpenCut's icon takes its rightful flight! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description does not follow the required template structure and lacks necessary sections such as issue reference or maintainer approval for bug fixes.	Follow the template: confirm an issue was opened first, provide evidence of maintainer approval, and acknowledge that critical bug approval is required per the template guidelines.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating the logo reference in the README file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

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 and usage tips.}

Tip

CodeRabbit can enforce grammar and style rules using `languagetool`.

Configure the reviews.tools.languagetool setting to enable/disable rules and categories. Refer to the LanguageTool Community to learn more.