[Aaqibhafeezkhan]

Summary

Fix get_component returning Available: . when a project has no design-system components.

Changes

• Add a shared helper for the empty-component message used by get_component and list_components.
• Explain that no design-system components were found and point to the components globs and project root.
• Include onsystem inspect guidance when no components are found at a monorepo root.
• Preserve the existing error behavior, suggestions, and available-component output when components exist.
• Add a regression test using a fixture containing only package.json.
• Add a patch changeset for onsystem.

Resolves #220

[dgesteves]

Thanks for picking this up. The fix is in the right place, and the helper is what the issue asked for. One thing will fail CI: test/design-system-packages-docs.test.ts still expects the old text. list_components is matched against /^No components found/ (line 308) and get_component against /^No component named "Button"/ (line 312). That app has no components, so both now return your new sentence. Could you update those two assertions? Optional: a test for the monorepo-root branch of get_component, which nothing covers yet.

[dgesteves]

Thanks, both assertions are updated and everything is green.

[dgesteves]

Merged. It ships in the next onsystem release. Thanks for fixing #220.