chore: remove unnecessary code and dependencies

[keito4]

Remove unnecessary code and dependencies identified through comprehensive analysis:

Changes

• Remove empty supabase/ directory (placeholder only)
• Remove unused npm dependencies:
  • @semantic-release/github (not used in .releaserc.json)
  • conventional-changelog-conventionalcommits (not referenced)

Closes #106

Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Streamlined development setup by removing unused release tooling dependencies, reducing maintenance overhead with no impact on build or runtime behavior.
  • Repository cleanup to simplify project management without affecting application functionality.

• Documentation

  • Removed outdated Supabase configuration README content to avoid confusion and keep docs current.
  • No changes to features, UI, or performance; user-facing guidance elsewhere remains unchanged.

[coderabbitai]

Walkthrough

Removed two devDependencies from package.json and deleted the content of supabase/README.md. No other files or scripts were changed.

Changes

Cohort / File(s)	Summary of Changes
Dev tooling dependencies cleanup package.json	Removed devDependencies: @semantic-release/github and conventional-changelog-conventionalcommits.
Documentation cleanup supabase/README.md	Removed all README content.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Remove unnecessary code (#106)	✅

Assessment against linked issues: Out-of-scope changes

Code Change	Explanation
Removed Supabase README content (supabase/README.md, lines 1–end)	The issue targets removal of unnecessary code; documentation deletion is not explicitly covered.

Possibly related PRs

• refactor: remove unnecessary code references #53 — Also modifies release-related tooling; this PR removes semantic-release-related devDependencies, while that one adjusts release config.

Poem

In burrows of code, I twitch my nose,
Snipped two vines where the changelog grows.
README hush in the Supabase glade,
Lighter packs for the release parade.
Thump-thump! says the reviewer’s heart—
Fewer carrots, cleaner cart. 🥕✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 73f29aa and d315194.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• package.json (0 hunks)
• supabase/README.md (0 hunks)

💤 Files with no reviewable changes (2)

• supabase/README.md
• package.json

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch claude/issue-106-20250828-1625

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

🎉 This PR is included in version 1.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀