semble-setuplisted

# Semble > Lifecycle router for **`semble_code`** — a semantic code-search MCP server (semble `0.5.4`, pinned) registered at **user scope** with `alwaysLoad: true`, indexing the corpus named by `SEMBLE_CONTENT_ARGS` into a **code-only cache root**. This skill decides the **mode**, prints the state **before** touching anything, and delegates every mutation to the scripts under `scripts/`. No mutation logic lives in this file. Two tools become available once it is wired: | Tool | Purpose | |------|---------| | `mcp__semble_code__search` | find code by intent / behavior / name | | `mcp__semble_code__find_related` | neighbors of a KNOWN location, after a useful seed | Both take a **required `repo`** parameter — the absolute project root, or an explicit `https://`/`http://` git URL. It is never inferred. Results carry `file_path`, `start_line`, `end_line`, `score` and optional `content` — **there is no `line` field**. MCP defaults are `top_k=5`, `max_snippet_lines=10`. ## Honest limits — state these to the user, never oversell | Fact | Consequence | |------|-------------| | **There is no watcher and no daemon.** semble 0.5.4 has no background thread, no service, nothing to start or stop. | Never report a daemon as running, starting or stopped. Staleness is re-checked *inside each tool call*, behind a `3x last-build-duration` cooldown. | | The embedding model is pre-loaded when the MCP server starts, and tool calls block until it is ready | The **first query on a cold cache d