docs: remove VECTOR_SYNC_ENABLED_APPS env var, use per-user database settings

Replace static VECTOR_SYNC_ENABLED_APPS environment variable with per-user
database storage for which apps to index. This allows each user to control
their own indexing preferences (e.g., enable notes and calendar but not
deck or files).

Rationale:
- Nextcloud doesn't support granular OAuth scopes at the app level
- Per-user settings provide flexibility for multi-user deployments
- Users control app enablement via nc_enable_vector_sync MCP tool
- Aligns with OAuth architecture where users manage their own settings

Changes:
- ADR-007: Remove VECTOR_SYNC_ENABLED_APPS from configuration section
- ADR-007: Update scanner implementation to read from database
- ADR-007: Add explanation of per-user app enablement mechanism
- ADR-007: Clarify that nc_enable_vector_sync tool manages this setting

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

docs/ADR-007-background-vector-sync-job-management.md

@@ -136,7 +136,7 @@ Concrete implementations for each app are registered in central registries (`SCA
 - `file`: WebDAV files with text extraction (leverages ADR-006 document processing)
 - `contact`: CardDAV contacts (VCARD)
 
-New apps can be added by implementing the three interfaces and registering the implementations—no changes to core sync logic are required. The `VECTOR_SYNC_ENABLED_APPS` environment variable controls which apps are actually indexed.
+New apps can be added by implementing the three interfaces and registering the implementations—no changes to core sync logic are required. Per-user settings stored in the backend database control which apps are actually indexed for each user (e.g., a user might enable notes and calendar but not deck or files).
 
 ### Change Detection: ETag and Modification Timestamps
 
@@ -562,8 +562,9 @@ async def scan_user_documents(
         username=user_id
     )
 
-    # Get list of enabled document types from configuration
+    # Get list of enabled apps for this user from database
-    enabled_apps = settings.vector_sync_enabled_apps  # ["note", "calendar_event", "deck_card", ...]
+    # Users configure this via nc_enable_vector_sync tool
+    enabled_apps = await get_enabled_apps_for_user(user_id)  # ["note", "calendar_event", "deck_card", ...]
 
     queued = 0
 
@@ -572,7 +573,7 @@ async def scan_user_documents(
         doc_type = scanner.get_doc_type()
 
         if doc_type not in enabled_apps:
-            continue  # Skip disabled apps
+            continue  # Skip apps this user hasn't enabled
 
         # Fetch all documents for this app
         documents = await scanner.get_all_documents(client)
@@ -865,7 +866,6 @@ async def _index_document(doc_task: DocumentTask, qdrant_client):
 ```bash
 # Vector Sync Configuration
 VECTOR_SYNC_ENABLED=true
-VECTOR_SYNC_ENABLED_APPS=note,calendar_event,calendar_todo,deck_card,file,contact  # Apps to index
 VECTOR_SYNC_SCAN_INTERVAL=3600  # Scanner runs every 3600 seconds (1 hour)
 VECTOR_SYNC_PROCESSOR_WORKERS=3  # Number of concurrent processor tasks
 VECTOR_SYNC_QUEUE_MAX_SIZE=10000  # Maximum documents in queue
@@ -880,6 +880,8 @@ OPENAI_API_KEY=<api-key>
 OPENAI_EMBEDDING_MODEL=text-embedding-3-small
 ```
 
+**Per-User App Enablement**: Which apps to index (notes, calendar, deck, files, contacts) is stored in the backend database on a per-user basis. Users control this via the `nc_enable_vector_sync` MCP tool, which can optionally specify which apps to enable. This allows different users to have different indexing preferences without requiring server-wide configuration.
+
 ### Docker Compose
 
 The simplified architecture requires only a single MCP server container: