Summary

The repository and onboarding experience still mention unsupported or descoped items such as local models, Brev integration, plugin workflows, and broader platform support.

Problem

Users are being told or shown that capabilities exist when they are not part of the current release. This sets the wrong expectations and makes real failures look like broken features instead of unsupported ones.

Expected behavior

The docs and CLI copy should clearly state the current supported scope before users start installation.

Acceptance criteria

• The docs homepage and quickstart clearly state supported platforms and supported workflows.
• Unsupported or deferred features are removed from primary docs or marked clearly as not yet supported.
• Onboarding output does not imply support for descoped capabilities.
• Release notes include a short current-scope statement.