chore: update versions

[vland-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@rrlab/cli@1.2.0

Minor Changes

• #235 c82191d Thanks @rqbazan! - Decouple the CLI into framework-agnostic layers and redesign the help surface.

  Every command body becomes a free-function action (src/actions/*) that takes a single <Name>ActionConfig object; commander commands are thin wrappers that resolve their service via the ctx.plugins facade (throwing MissingPluginError when no configured plugin provides the capability) and delegate to exactly one action. Actions depend only on services/render/lib, never on the CLI framework. The plugin SDK moves to src/lib/plugin/*, ad-hoc errors become domain error classes (src/errors/* for kernel errors, src/lib/plugin/errors.ts for SDK errors), and a plugin's ui label is now derived from a single color function it provides — plugins no longer hard-code their own ui string. The plugins command monolith is split into actions/plugins/*, and the official plugin list is reshaped into src/lib/plugin/directory.ts (PLUGINS_DIRECTORY + allPluginNames/isPluginName).

  The help surface is rebuilt on commander's native formatter instead of a bespoke help class: the root program is a RunRunCmd subclass that groups commands (Code quality: / Build: / Maintenance: / Meta:) and attaches a banner and an installed/available plugins footer via addHelpText. Unknown commands now use commander's native showSuggestionAfterError "Did you mean?" output. --about credits, per-command Powered by: / See also: lines (auto-derived from each command's declared capabilities by the Cmd base class in src/program/base.ts), the installed/available plugins footer (render/footer.ts), a rr config plugins table (package + version), and a small table/line builder (render/lines.ts) round out the rendering layer.

Patch Changes

• #237 b761f03 Thanks @rqbazan! - Refresh the README for the microkernel model.

  Drop the stale, hand-maintained Toolbox section (it still listed rimraf, which isn't a plugin) and fold the tool list into the Plugins section as the single source of truth. The official plugins are now named there — biome, oxc, ts, tsdown — each linked to the tool it wraps, framed as capabilities added via plugins rather than a flat bag of tools.

• Updated dependencies [c82191d]:

  • @vlandoss/clibuddy@0.7.1

@rrlab/biome-plugin@1.1.1

Patch Changes

• #235 c82191d Thanks @rqbazan! - Decouple the CLI into framework-agnostic layers and redesign the help surface.

  Every command body becomes a free-function action (src/actions/*) that takes a single <Name>ActionConfig object; commander commands are thin wrappers that resolve their service via the ctx.plugins facade (throwing MissingPluginError when no configured plugin provides the capability) and delegate to exactly one action. Actions depend only on services/render/lib, never on the CLI framework. The plugin SDK moves to src/lib/plugin/*, ad-hoc errors become domain error classes (src/errors/* for kernel errors, src/lib/plugin/errors.ts for SDK errors), and a plugin's ui label is now derived from a single color function it provides — plugins no longer hard-code their own ui string. The plugins command monolith is split into actions/plugins/*, and the official plugin list is reshaped into src/lib/plugin/directory.ts (PLUGINS_DIRECTORY + allPluginNames/isPluginName).

  The help surface is rebuilt on commander's native formatter instead of a bespoke help class: the root program is a RunRunCmd subclass that groups commands (Code quality: / Build: / Maintenance: / Meta:) and attaches a banner and an installed/available plugins footer via addHelpText. Unknown commands now use commander's native showSuggestionAfterError "Did you mean?" output. --about credits, per-command Powered by: / See also: lines (auto-derived from each command's declared capabilities by the Cmd base class in src/program/base.ts), the installed/available plugins footer (render/footer.ts), a rr config plugins table (package + version), and a small table/line builder (render/lines.ts) round out the rendering layer.

• Updated dependencies [c82191d]:

  • @vlandoss/clibuddy@0.7.1

@rrlab/oxc-plugin@1.1.1

Patch Changes

• #235 c82191d Thanks @rqbazan! - Decouple the CLI into framework-agnostic layers and redesign the help surface.

  Every command body becomes a free-function action (src/actions/*) that takes a single <Name>ActionConfig object; commander commands are thin wrappers that resolve their service via the ctx.plugins facade (throwing MissingPluginError when no configured plugin provides the capability) and delegate to exactly one action. Actions depend only on services/render/lib, never on the CLI framework. The plugin SDK moves to src/lib/plugin/*, ad-hoc errors become domain error classes (src/errors/* for kernel errors, src/lib/plugin/errors.ts for SDK errors), and a plugin's ui label is now derived from a single color function it provides — plugins no longer hard-code their own ui string. The plugins command monolith is split into actions/plugins/*, and the official plugin list is reshaped into src/lib/plugin/directory.ts (PLUGINS_DIRECTORY + allPluginNames/isPluginName).

  The help surface is rebuilt on commander's native formatter instead of a bespoke help class: the root program is a RunRunCmd subclass that groups commands (Code quality: / Build: / Maintenance: / Meta:) and attaches a banner and an installed/available plugins footer via addHelpText. Unknown commands now use commander's native showSuggestionAfterError "Did you mean?" output. --about credits, per-command Powered by: / See also: lines (auto-derived from each command's declared capabilities by the Cmd base class in src/program/base.ts), the installed/available plugins footer (render/footer.ts), a rr config plugins table (package + version), and a small table/line builder (render/lines.ts) round out the rendering layer.

• Updated dependencies [c82191d]:

  • @vlandoss/clibuddy@0.7.1

@rrlab/ts-plugin@1.1.1

Patch Changes

• #235 c82191d Thanks @rqbazan! - Decouple the CLI into framework-agnostic layers and redesign the help surface.

  Every command body becomes a free-function action (src/actions/*) that takes a single <Name>ActionConfig object; commander commands are thin wrappers that resolve their service via the ctx.plugins facade (throwing MissingPluginError when no configured plugin provides the capability) and delegate to exactly one action. Actions depend only on services/render/lib, never on the CLI framework. The plugin SDK moves to src/lib/plugin/*, ad-hoc errors become domain error classes (src/errors/* for kernel errors, src/lib/plugin/errors.ts for SDK errors), and a plugin's ui label is now derived from a single color function it provides — plugins no longer hard-code their own ui string. The plugins command monolith is split into actions/plugins/*, and the official plugin list is reshaped into src/lib/plugin/directory.ts (PLUGINS_DIRECTORY + allPluginNames/isPluginName).

  The help surface is rebuilt on commander's native formatter instead of a bespoke help class: the root program is a RunRunCmd subclass that groups commands (Code quality: / Build: / Maintenance: / Meta:) and attaches a banner and an installed/available plugins footer via addHelpText. Unknown commands now use commander's native showSuggestionAfterError "Did you mean?" output. --about credits, per-command Powered by: / See also: lines (auto-derived from each command's declared capabilities by the Cmd base class in src/program/base.ts), the installed/available plugins footer (render/footer.ts), a rr config plugins table (package + version), and a small table/line builder (render/lines.ts) round out the rendering layer.

• Updated dependencies [c82191d]:

  • @vlandoss/clibuddy@0.7.1

@rrlab/tsdown-plugin@1.1.1

Patch Changes

• #235 c82191d Thanks @rqbazan! - Decouple the CLI into framework-agnostic layers and redesign the help surface.

  Every command body becomes a free-function action (src/actions/*) that takes a single <Name>ActionConfig object; commander commands are thin wrappers that resolve their service via the ctx.plugins facade (throwing MissingPluginError when no configured plugin provides the capability) and delegate to exactly one action. Actions depend only on services/render/lib, never on the CLI framework. The plugin SDK moves to src/lib/plugin/*, ad-hoc errors become domain error classes (src/errors/* for kernel errors, src/lib/plugin/errors.ts for SDK errors), and a plugin's ui label is now derived from a single color function it provides — plugins no longer hard-code their own ui string. The plugins command monolith is split into actions/plugins/*, and the official plugin list is reshaped into src/lib/plugin/directory.ts (PLUGINS_DIRECTORY + allPluginNames/isPluginName).

  The help surface is rebuilt on commander's native formatter instead of a bespoke help class: the root program is a RunRunCmd subclass that groups commands (Code quality: / Build: / Maintenance: / Meta:) and attaches a banner and an installed/available plugins footer via addHelpText. Unknown commands now use commander's native showSuggestionAfterError "Did you mean?" output. --about credits, per-command Powered by: / See also: lines (auto-derived from each command's declared capabilities by the Cmd base class in src/program/base.ts), the installed/available plugins footer (render/footer.ts), a rr config plugins table (package + version), and a small table/line builder (render/lines.ts) round out the rendering layer.

• Updated dependencies [c82191d]:

  • @vlandoss/clibuddy@0.7.1

@vlandoss/clibuddy@0.7.1

Patch Changes

• #235 c82191d Thanks @rqbazan! - Drop the muted token from palette and route its callers through palette.dim.

  muted (a fixed #a8afb5 gray) overlapped with dim for the secondary-text role it was used in ($ command prefix, v<version>, the vland init "Next steps" / source path). Consolidating on dim keeps a single secondary tone and lets it follow the terminal's dim attribute. @vlandoss/vland's banner, --usage hint, and init output move to dim accordingly.

@vlandoss/vland@0.3.2

Patch Changes

• #235 c82191d Thanks @rqbazan! - Drop the muted token from palette and route its callers through palette.dim.

  muted (a fixed #a8afb5 gray) overlapped with dim for the secondary-text role it was used in ($ command prefix, v<version>, the vland init "Next steps" / source path). Consolidating on dim keeps a single secondary tone and lets it follow the terminal's dim attribute. @vlandoss/vland's banner, --usage hint, and init output move to dim accordingly.

• Updated dependencies [c82191d]:

  • @vlandoss/clibuddy@0.7.1