[ruibaby]

Summary

Upgrade the generated plugin templates to target Halo 2.26 and make Vite the recommended UI build tool.

Changes

• update the Halo Gradle platform version to 2.26
• require Halo 2.26.0 or later in the generated plugin manifest
• update @halo-dev/api-client, @halo-dev/components, @halo-dev/ui-shared, and @halo-dev/ui-plugin-bundler-kit to 2.26.0
• place Vite first in the UI build tool prompt and mark it as recommended
• remove the recommended label from Rsbuild

Validation

• pnpm check
• pnpm test (the repository currently has no tests configured)
• node --check src/index.js
• git diff --check
• generated Vite and Rsbuild projects and verified their UI package versions
• generated a backend-only project and verified the Halo version requirement
• verified that all referenced @halo-dev/* 2.26.0 packages are published

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ca7495a96a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align the Gradle platform with Halo 2.26

Setting the development runtime to Halo 2.26 while leaving run.halo.tools.platform:plugin at 2.25.0 means every generated backend still compiles and tests against the Halo 2.25 API constraints. A newly scaffolded plugin therefore cannot compile against APIs introduced in 2.26 despite its manifest requiring 2.26 and its dev runtime using that version; update the platform dependency to 2.26.0 as part of this version bump.

Useful? React with 👍 / 👎.