feat(rename): complete searchSpace to workspace transition across frontend and backend

- Introduced a comprehensive specification for renaming `searchSpace` to `workspace` in `surfsense_web` and `surfsense_desktop`, ensuring all TypeScript identifiers, React props, and local data structures are updated.
- Implemented migration shims for persisted local state to prevent data loss during the transition.
- Updated observability metrics and IPC channels to reflect the new naming convention.
- Removed legacy `active-search-space` module and replaced it with `active-workspace` to maintain consistency.
- Ensured no behavioral changes or data loss for users during the renaming process.

surfsense_web/content/docs/connectors/baidu-search.mdx

@@ -93,7 +93,7 @@ Baidu Search does not create indexed documents in your knowledge base. It runs w
 
 **No Baidu results appear**
 
-- Confirm the Baidu Search connector is active in the current search space.
+- Confirm the Baidu Search connector is active in the current workspace.
 - Try a Chinese query with clear search intent, for example `百度智能云千帆 AppBuilder 最新功能`.
 - Check whether other web search engines are returning results. If none are, review the general [Web Search](/docs/how-to/web-search) setup.
 

surfsense_web/content/docs/connectors/circleback.mdx

@@ -44,7 +44,7 @@ The Circleback connector uses a **webhook-based integration**. Unlike other conn
 3. Click **Connect** to create the connector
 
 <Callout type="info" title="No Credentials Needed">
-Circleback uses webhooks, so no API key or authentication is required. The webhook URL is unique to your search space.
+Circleback uses webhooks, so no API key or authentication is required. The webhook URL is unique to your workspace.
 </Callout>
 
 ### Step 2: Copy Your Webhook URL
@@ -57,7 +57,7 @@ After creating the connector:
 
 The webhook URL looks like:
 ```
-https://your-surfsense-url/api/v1/webhooks/circleback/{search_space_id}
+https://your-surfsense-url/api/v1/webhooks/circleback/{workspace_id}
 ```
 
 ### Step 3: Configure Circleback Automation
@@ -101,7 +101,7 @@ Once configured, new meetings will automatically appear in SurfSense after Circl
 
 1. Attend or process a meeting with Circleback
 2. Wait for Circleback to complete processing (usually a few minutes after the meeting ends)
-3. Check your SurfSense search space for the new meeting document
+3. Check your SurfSense workspace for the new meeting document
 
 Each meeting document includes:
 - A direct link to view the meeting on Circleback

surfsense_web/content/docs/connectors/obsidian.mdx

@@ -29,7 +29,7 @@ This works for cloud and self-hosted deployments, including desktop and mobile c
 3. In Obsidian, open **Settings → SurfSense**.  
 4. Paste your SurfSense API token from the user settings section.
 5. Paste your Server URL in the plugin setting: either your SurfSense main domain (if `/api/v1` rewrites are enabled) or your direct backend URL.
-6. Choose the Search Space in the plugin, then the first sync should run automatically.
+6. Choose the Workspace in the plugin, then the first sync should run automatically.
 7. Confirm the connector appears as **Obsidian - <vault>** in SurfSense.
 
 ## Install via BRAT (recommended)
@@ -55,7 +55,7 @@ If you previously used the legacy Obsidian connector architecture, migrate to th
 ## Troubleshooting
 
 **Plugin connects but no files appear**
-- Verify the plugin is pointed to the correct Search Space.
+- Verify the plugin is pointed to the correct Workspace.
 - Trigger a manual sync from the plugin settings.
 - Confirm your API token is valid and not expired.