get_component answers "Available: ." in a project with no components #220

What happens

In a project where onsystem finds no design-system components, get_component answers with an empty list. Start the server in a folder with only a package.json and call get_component { "name": "Button" }. It returns No component named "Button". Available: . In the same project, list_components says No components found. Check the "components" globs in the config (root: ...).

Where

• src/server/index.ts:516-532: the error text in a single project, built from ds.roots(), which is empty here
• src/server/index.ts:486-494: the same pattern at a monorepo root, built from catalog.roots()
• src/server/render.ts:176-185 and :240-244: what list_components says when there are no components, in a project and at a monorepo root
• test/server.test.ts:152-163: "get_tokens says when the project has no tokens at all", the test to copy

Done when

• With no components, get_component says the project has no design-system components and points at the components globs and the root, as list_components does (and, at a monorepo root, at onsystem inspect)
• It still returns isError: true, and with components the "Did you mean" and "Available" text is unchanged
• A new test in test/server.test.ts calls get_component on a fixture with only a package.json and checks the text
• pnpm test, pnpm lint and pnpm typecheck pass, and the PR has a patch changeset (pnpm changeset)

Hint

Copy the fixture and client setup from the get_tokens test at test/server.test.ts:152. Put the sentence in a small helper next to renderComponentList in src/server/render.ts, so both tools say the same thing. #199 (in review) also edits src/server/render.ts: if it merges first, rebase onto it.

Out of scope

What search_components says when nothing matches.

Status: ready for a contributor. Comment before you start.