feat(opencode) plugin commands

[dev4s]

feat: Plugin Commands - Allow plugin tools to be exposed as slash commands

Summary

This PR adds a new experimental feature that allows plugin tools to optionally appear as slash commands in the autocomplete, with support for direct execution (without AI processing).

Problem

Currently, plugin tools can only be invoked by the AI. Users cannot directly invoke plugin functionality from the command input without going through the AI, which:

• Adds latency and token costs for simple operations
• Requires AI involvement for tasks that don't need it
• Limits plugin utility for status checks, statistics, and other quick queries

Backwards Compatibility

• Fully backwards compatible - Existing plugins work unchanged
• command defaults to false, so existing tools remain AI-only
• Feature is behind experimental.pluginCommands flag
• Plugin tools are still registered in ToolRegistry regardless of command setting

Related Issues

This PR also includes a fix for plugin tool registration timing (ToolRegistry.state() now initializes after Plugin.init() in bootstrap.ts).

[github-actions]

Hey! Your PR title [FEATURE] plugin commands doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

I found a potentially related PR:

Related PR:

• feat(plugin commands): allows for code execution on plugin registered slash commands #4411 - feat(plugin commands): allows for code execution on plugin registered slash commands

This PR appears to be addressing a very similar feature - allowing plugin registered slash commands to execute code. This is closely related to the current PR #7563, which adds plugin commands with direct execution capabilities. These PRs may be addressing the same or overlapping functionality, so they should be compared to ensure no duplicate efforts.

[PhilippPolterauer]

i would really love seeing one of these plugin command PRs merged!