feat(FN-3313): add plugin slot registry, planning mode rewind, and docker n

This merge lands five features spanning the Fusion stack: research settings key renaming (FN-3313, Steps 2–7) across types, defaults, CLI, and engine packages; static plugin slot-host rendering contract documentation (FN-3260); Docker node provisioning routes with a planning modal (FN-3116); plannin

Fusion-Task-Id: FN-3313
This commit is contained in:
Fusion
2026-05-04 20:14:46 -07:00
committed by gsxdsm
parent f5268019f9
commit a02b42106d
16 changed files with 118 additions and 90 deletions

View File

@@ -53,14 +53,14 @@ This also reveals the **Research Defaults** and **Research** settings sections i
### 2. Configure a web search provider
Set `researchWebSearchProvider` in global settings to one of the supported backends:
Set `researchGlobalWebSearchProvider` in global settings to one of the supported backends:
| Provider | Required settings |
|---|---|
| `"searxng"` | `researchSearxngUrl` — URL of your SearXNG instance |
| `"brave"` | `researchBraveApiKey` — Brave Search API key |
| `"google"` | `researchGoogleSearchApiKey` + `researchGoogleSearchCx` — Google Custom Search credentials |
| `"tavily"` | `researchTavilyApiKey` — Tavily API key |
| `"searxng"` | `researchGlobalSearxngUrl` — URL of your SearXNG instance |
| `"brave"` | `researchGlobalBraveApiKey` — Brave Search API key |
| `"google"` | `researchGlobalGoogleSearchApiKey` + `researchGlobalGoogleSearchCx` — Google Custom Search credentials |
| `"tavily"` | `researchGlobalTavilyApiKey` — Tavily API key |
| `"none"` | Disables web search (other sources still work) |
API keys are stored through Fusion's auth credential pipeline (`/api/auth/api-key`), not in settings JSON directly.