release: bump version to 0.66.0

docs/technical/en/agents-aiprovider.md

@@ -101,7 +101,7 @@ The AI settings page uses:
 
 These endpoints require an authenticated user. The `secrets` endpoint is only used when the settings page reveals a key or token; hiding the field restores the masked preview.
 
-Admin Next keeps the AI page aligned with the legacy information architecture:
+Admin keeps the AI page aligned with the legacy information architecture:
 
 - `Model Providers`
   - Manages provider, wire adapter, default model, LLM API key, proxy URL, proxy token, model refresh, set-as-default, and lightweight connectivity testing.
@@ -272,7 +272,7 @@ Each provider has its own key slot. Resolution order is:
 
 `.env` is only a fallback. After the settings page saves successfully, or after the connection test succeeds, PostgreSQL becomes the global default source.
 
-Admin Next must compute key status per provider or tool:
+Admin must compute key status per provider or tool:
 
 - If the database has a key for the current provider/tool, show `configured`.
 - If the database has no key but the fallback provider, model, or tool matches the current item, show the fallback masked preview.
@@ -283,7 +283,7 @@ Tool keys follow the same rule. WebSearch and OCR must match the current tool an
 
 ### Lightweight Connectivity Testing
 
-The Admin Next plug button performs a lightweight connectivity check and does not save configuration. Common API-platform practice is two-tiered:
+The Admin plug button performs a lightweight connectivity check and does not save configuration. Common API-platform practice is two-tiered:
 
 - Check a provider catalog or low-cost endpoint to validate base URL, authentication, and model reachability.
 - Send full model requests only when the user explicitly runs Playground or a business task.