[mintlify]

Summary

Documents that every @wolfstar/plugin-* module now reads its options from a top-level stars.config key (meta.configKey).

Changes

• Plugin pages (api, broker, i18next, logger, scheduled-tasks) show the key form first and explain that the [specifier, options] tuple still works and wins over the key.
• Note the @wolfstar/kit ^0.2.0 requirement and the optional @wolfstar/schema peer that types the keys. Users import the module in stars.config.ts to load that type.
• cache, gateway, sharder, and subcommands-advanced pages note that their key is reserved and takes no options yet.
• Broker page clarifies that redis stays in ClientOptions.broker.
• Added a package-to-key table in the plugins guide.

Context

• feat: set meta.configKey in every module plugins#259

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
stars-components	🟢 Ready	View Preview	Oct 22, 2026, 7:13 AM

[coldtea-pr-lens]

Note

mintlify[bot] opened this pull request, so PR Lens left it undrawn. Comment @pr-lens draw to draw it

_{github.comment.notice: false in .github/pr-lens.yml turns this note off}

[pullfrog]

The Semantic Pull Requests check fails because the title has no Conventional Commits type(scope): prefix. I can't rename the PR myself: no available tool edits a PR title.

Proposed title:

docs(packages): configure plugins via stars.config keys

The PR mostly changes plugin pages under documentation/packages. The only guide change is the package-to-key table in the plugins guide. If you prefer the guide scope, docs(guide): configure plugins via stars.config keys is also valid.

Next step: edit the title in the GitHub UI. The check re-runs when the title changes. No commits were pushed.

  ^{｜ View workflow run ｜ via Pullfrog ｜ Using claude-sonnet-5-5 ｜ 𝕏}