docs: strip stale TUI references from guides and skills

Follows the code strip in the previous commit. Removes documentation
that describes a TUI surface the public release doesn't ship:

- docs/guides/config-migration.md: drop the "TUI settings" section
  (config keys nothing reads anymore); renumber remaining sections.
- examples/README.md: drop the `tui:` YAML block from the MCP section;
  keep the MCP explanation focused on the core `nooa[mcp]` extra and
  the stateless `MCPManager` factory.

Rewrote (rather than removed) references to primitives that still
exist in core but are no longer TUI-hosted:

- skills/nemo-oo-tools-and-skills/SKILL.md: `@slash_command` now
  points at the InteractiveAgent `slash_commands` queue rather than
  "the TUI"; MCP config points at `.mcp.json` only.
- skills/nemo-oo-self-extending/SKILL.md: same reword for slash
  commands.

Author: alessiodevoto

docs/guides/config-migration.md

@@ -18,60 +18,7 @@ wins). Here's everything you need to move.
 
 `NAT_CONFIG_DIR` is gone — use `NEMO_OO_USER_DIR` to relocate the user dir.
 
-## 2. TUI settings: `config.toml` → `settings.yaml`
-
-Project-only TOML becomes layered YAML (`<project>/.nooa/settings.yaml` or
-user-global `~/.config/nooa/settings.yaml`). **Hard switch — `config.toml`
-is no longer read.**
-
-**Before — `config.toml`**
-```toml
-[tui]
-model = "claude-opus-4-8"
-python = false
-vi = false
-trace = ".nooa/traces"
-mcp_auto_connect = ["maas"]
-
-[tui.mcp_servers.maas]
-url = "https://your-mcp-server.example.com/mcp"
-transport = "streamable-http"
-
-[tui.mcp_servers.maas.headers]
-Authorization = "Bearer ${MAAS_API_KEY}"
-```
-
-**After — `settings.yaml`**
-```yaml
-tui:
-  default_model: claude-opus-4-8
-  show_python: false
-  vi_mode: false
-  trace_dir: .nooa/traces
-  mcp_auto_connect: [maas]
-  mcp_servers:
-    maas:
-      url: https://your-mcp-server.example.com/mcp
-      transport: streamable-http
-      headers:
-        Authorization: "Bearer ${MAAS_API_KEY}"
-```
-
-Key renames (YAML uses the real field names):
-
-| `config.toml` | `settings.yaml` |
-|---------------|-----------------|
-| `[tui]` table | `tui:` mapping |
-| `model` | `default_model` |
-| `python` | `show_python` |
-| `vi` | `vi_mode` |
-| `trace` | `trace_dir` |
-| `libs_dirs`, `mcp_auto_connect` | *(unchanged)* |
-| `[tui.mcp_servers.<name>]` | `tui.mcp_servers.<name>:` |
-
-(`/config set model …` still works — friendly keys map to the field names.)
-
-## 3. API keys / secrets
+## 2. API keys / secrets
 
 | Before | After |
 |--------|-------|
@@ -88,14 +35,14 @@ A shell `export` still wins (non-clobber), so existing exports keep working —
 `secrets.yaml` just means you no longer *need* one. The installer writes this
 file for you.
 
-## 4. LLM aliases: `llm_config.yaml`
+## 3. LLM aliases: `llm_config.yaml`
 
 Same filename and format — just move it to the new dir:
 `~/.config/nat/oo/llm_config.yaml` → `~/.config/nooa/llm_config.yaml`
 (or `<project>/.nooa/llm_config.yaml`). `nooa config eject` regenerates
 a fresh copy in the new location.
 
-## 5. Environment variables → `NEMO_OO_` prefix
+## 4. Environment variables → `NEMO_OO_` prefix
 
 | Before | After |
 |--------|-------|

examples/README.md

@@ -476,32 +476,7 @@ uv run python examples/quickstart/10_skills.py
 
 ### MCP tools
 
-MCP (Model Context Protocol) tools let your agent call external services through a standard interface. The TUI ships MCP as a hard dependency (`self.mcp` and `/mcp` are always available). In the core library, MCP is an optional extra (`uv add 'nooa[mcp]'`).
-
-**TUI configuration** — declare MCP servers in `.nooa/settings.yaml`:
-
-```yaml
-tui:
-  mcp_auto_connect: ["maas-confluence-stg"]
-  mcp_servers:
-    maas-confluence-stg:
-      url: "https://your-mcp-server.example.com/mcp"
-      transport: "streamable-http"
-      headers:
-        Authorization: "Bearer ${MAAS_API_KEY}"
-```
-
-At startup the TUI attaches auto-connected servers to the agent, so `maas-confluence-stg` becomes `self.maas_confluence_stg`. A VS Code / Claude-style `.mcp.json` file is also supported via `mcp_file` or `--mcp-file`.
-
-Inside the TUI, servers are managed through `self.mcp` (an `MCPRegistry` skill that mirrors `self.skills`):
-
-- `self.mcp.discovered()` — configured server names
-- `await self.mcp.connect(["name"])` — open a server and attach it as `self.<name>`
-- `self.mcp.activate([...])` / `self.mcp.deactivate([...])` — control whether a connected server's tools are listed for the agent
-- `<mcp>` context block lists every server each turn under **Active**, **Connected but inactive**, or **Configured**
-- Slash commands: `/mcp list`, `/mcp connect <server>`, `/mcp disconnect <server>`
-
-**Library use** — no `self.mcp`; call the stateless `MCPManager` factory directly:
+MCP (Model Context Protocol) tools let your agent call external services through a standard interface. Install with `uv add 'nooa[mcp]'` and call the stateless `MCPManager` factory:
 
 ```python
 from nooa.mcp import MCPManager

skills/nemo-oo-self-extending/SKILL.md

@@ -60,7 +60,7 @@ await self.libs.list(); await self.libs.repo_tree()            # discovery
 
 ## Slash commands (`@slash_command`)
 
-Skills can ship user-typed `/commands` (dispatch: `nooa.slash_dispatch`; TUI surfaces them):
+Skills can ship user-typed `/commands` (dispatch: `nooa.slash_dispatch`; hosts driving `InteractiveAgent` surface them via the `slash_commands` queue):
 
 ```python
 from nooa.skill import Skill, slash_command

skills/nemo-oo-tools-and-skills/SKILL.md

@@ -72,7 +72,7 @@ class MyAgent(Agent, llm=llm):
 - `TextSkill` exposes `read_file(path)` and `await run_script(name, *args)` for files/scripts bundled with the SKILL.md.
 - SKILL.md frontmatter: required `name`, `description`; optional `compatibility`, `metadata`, `user-invocable`, `allowed-tools` — Claude-Code-compatible format.
 - Bulk discovery/activation is `SkillRegistry(agent)` + `discover_skills_dirs([...])` / `activate([...])`. **`SkillManager` does not exist** — `README`/`examples/quickstart/10_skills.py` referencing `SkillManager.install(...)` are stale.
-- `@slash_command` on a `Skill` method marks it user-invocable in the TUI.
+- `@slash_command` on a `Skill` method marks it user-invocable via a host that reads the agent's `slash_commands` queue (see `InteractiveAgent`).
 - Docstring conventions and the full guide: `docs/skills-guide.md`.
 
 ## MCP servers
@@ -93,7 +93,7 @@ class ConfluenceAgent(Agent, llm=llm):
         ...
 ```
 
-MCP tools appear alongside regular methods — the LLM calls them like any other attribute. Servers are configured in `.mcp.json` (VS Code/Claude Code format); in the TUI they instead live in `.nooa/config.toml` under `[tui.mcp_servers.*]` with `self.mcp` (an `MCPRegistry`) managing connect/activate. Transports: stdio, SSE, streamable-http; OAuth supported (`nooa.mcp.OAuthConfig`).
+MCP tools appear alongside regular methods — the LLM calls them like any other attribute. Servers are configured in `.mcp.json` (VS Code/Claude Code format). Transports: stdio, SSE, streamable-http; OAuth supported (`nooa.mcp.OAuthConfig`).
 
 ## Multimodal media