setup --host rejects cursor and slate, but both are registered in ALL_HOST_CONFIGS

[dep0we]

hosts/index.ts line 21 registers ten hosts:

export const ALL_HOST_CONFIGS: HostConfig[] = [claude, codex, factory, kiro, opencode, slate, cursor, openclaw, hermes, gbrain];

setup accepts only eight of them. Lines 88 and 139 both enumerate claude, codex, kiro, factory, opencode, openclaw, hermes, gbrain, or auto. Passing --host cursor or --host slate exits with Unknown --host value.

Both have full host configs (hosts/cursor.ts, hosts/slate.ts) and bun run gen:skill-docs --host cursor works, so the generator supports them and only the installer doesn't.

Practical effect: there is no documented way to install gstack for Cursor, even though Cursor is a supported host. Since Cursor discovers skills by scanning for .claude/skills, .cursor/skills, .agents/skills, and .codex/skills anywhere on disk, it finds the generated per-host bundles inside the gstack checkout and lists the same ~55 skills many times over. On my machine that showed as 664 SKILL.md files under ~/.claude/skills, where roughly 80 are real. Deleting the nine gitignored bundles brought it to 167.

Two things that would help, either one on its own:

1. Add cursor and slate to the --host list in setup so the installer matches the host registry.
2. Have setup clear stale generated bundles for hosts other than the one being installed, so a single checkout does not multiply into every scanner's view.