refactor: remove toolkits and plugins

[kagol]

PR

• 迁移 packages/toolkits 到 tiny-cli-toolkits
• 迁移 packages/plugins 到 tiny-cli-plugins
• 迁移 pro 到 tiny-pro
• packages/cli 中的内容移到外层 packages 中

已验证 cli 的本地开发和构建流程不受影响。

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Chores

  • Consolidated configuration settings to streamline package management, ignore patterns, and developer tooling.
  • Removed obsolete and legacy configuration, localization, and formatting files.

• Refactor

  • Simplified the project’s workspace structure to enhance consistency and future scalability.

These updates improve overall project maintainability and performance without altering the product’s end-user experience.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The update broadens file‐ignore patterns in configuration files and revises package management settings. The dev script entry point is updated in the package configuration, while the lerna settings are consolidated. A large number of files related to the HWC plugin—including localization, configuration, command implementations, services, and type definitions—have been entirely removed. Similarly, various configuration and tooling files in the Link plugin and repo-level tool files (e.g. TypeScript and lint settings) have been deleted, streamlining the overall codebase.

Changes

File(s)	Change Summary
.eslintignore, .gitignore, .prettierignore (root)	Updated ignore pattern from /packages/cli/**/lib/* to /packages/**/lib/*
lerna.json, package.json	Modified package configuration: consolidated paths in lerna.json and updated the dev script entry point in package.json with new workspaces configuration
packages/plugins/hwc/{.editorconfig, .gitignore, .husky/pre-commit, .npmignore, .prettierignore, README.md, debug.js, package.json}	Removed configuration and metadata files for the HWC plugin
packages/plugins/hwc/src/... (locales, core, lib, etc.)	Removed HWC plugin source components: commands, services, validations, constants, types, and localization modules
packages/plugins/hwc/tiny.config.js, tsconfig.json, tslint.json	Deleted build and tooling configuration files
packages/plugins/link/{.editorconfig, .eslintignore, .gitattributes, .gitignore, .npmignore, .prettierignore, .prettierrc.js}	Removed configuration files for the Link plugin
packages/plugins/hwc/src/locales/{enUs.json, zhCn.json, index.ts}	Removed localization files for HWC
packages/plugins/hwc/src/lib/index.ts, packages/plugins/hwc/src/lib/list/index.ts	Removed aggregated exports and CLI listing entry points for HWC

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant NPM as npm
    participant Core as Core Entry
    Dev->>NPM: Run "npm run dev:local"
    NPM->>Core: Execute script at "./packages/core/src/index.ts"
    Core-->>NPM: Initialize application
    NPM-->>Dev: Application started

Loading

Poem

I hop through lines of code so neat,
Ignoring old files with rhythmic beat.
Configs revised and plugins shed,
New paths and workspaces now ahead.
With every deletion, a fresh start I greet,
A bunny’s joy in every optimized feat! 🐇

---

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.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai 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:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @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

Documentation and Community

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