cix-workspacelisted

# `cix workspace` — Cross-Project Research Workflow You usually work inside one repo — your **primary project** — the directory the user opened you in. Most tasks are fully contained there and `cix search` / `cix definitions` / `cix references` are the right tools. But some tasks are not contained. A request like "wire feature X through the platform" can touch a half-dozen repos in different languages, layers, and shapes — a service, a shared library, the infra manifests, an API spec. Reading the primary repo alone gives you 1/N of the picture. Worse, you don't know which N repos are actually involved until you look. `cix workspace` is the tool for that. It searches every repo in a named workspace at once and tells you: 1. **Which repos are actually relevant to this request.** 2. **Which code in those repos is the entry point.** 3. **What changes need to land in each, and in what order.** Those three questions are the *goal* of using this skill. Don't jump to implementation before you can answer all three with evidence. > **Prerequisite: a populated workspace.** This skill assumes the > workspace already exists and its repos are indexed. If it doesn't, > create and populate one first (owner/admin): `cix ws create "<name>"`, > then `cix ws "<name>" add <project>` for each already-indexed repo — or > clone new GitHub repos in via the dashboard. `cix ws` lists what's > available; the main `cix` skill has the full management verb reference. ## First: which server hosts th