@nocobase/plugin-ai 2.2.0-alpha.1 → 2.2.0-alpha.11

package/dist/ai/docs/nocobase/ops-management/release-management/index.md

@@ -1,52 +1,139 @@
+---
+title: "Release Management"
+description: "Operations release best practices: use version control to record development checkpoints, multi-app architecture to split business modules, Backup Manager for disaster recovery, and Migration Manager to publish across development, staging, and production environments."
+keywords: "Release Management,Release,multi-environment deployment,version control,multi-app,Backup Manager,Migration Manager,development staging production,NocoBase"
+---
+
 # Release Management
 
 ## Introduction
 
-In real-world applications, to ensure data security and application stability, multiple environments are typically deployed, such as a development environment, a pre-release environment, and a production environment. This document provides examples of two common no-code development processes and explains in detail how to implement release management in NocoBase.
+Release management standardizes how an application moves from development to production. It is not a single operation. It is a repeatable, verifiable, and recoverable release process.
+
+Keep production stable. Complete configuration changes in development first, validate them in staging, then publish them to production. Migration files, backups, execution logs, and validation results generated during release should be retained for troubleshooting and rollback.
+
+Recommended environments:
+
+```text
+Development environment -> Staging environment -> Production environment
+```
+
+Development is used for configuration and adjustment. Staging restores production constraints and validates the release result. Production carries real business traffic. Clear responsibilities make the release process easier to manage.
+
+## Release Model
+
+NocoBase release management usually combines five capabilities.
+
+| Capability | Problem solved | Stage |
+| --- | --- | --- |
+| Version control | Saves key checkpoints during development and provides rollback points for configuration changes | Development |
+| Variables and secrets | Isolates environment-specific configuration and sensitive information | Development, staging, and production release |
+| Multi-app | Splits system boundaries by business module and reduces release impact between modules | Architecture planning and team collaboration |
+| Backup Manager | Saves a recoverable production state for release failures and daily incidents | Before release and daily disaster recovery |
+| Migration Manager | Publishes configuration and structure changes to the target environment | Staging and production release |
+
+## Environment Configuration: Use Variables and Secrets
+
+Variables and secrets isolate environment-specific configuration and sensitive information. Development, staging, and production should use their own variables and secrets.
+
+Identify environment-related configuration during development. Database connections, third-party service addresses, test accounts, access tokens, API keys, and webhook URLs should not be hardcoded in pages, workflows, or plugin settings. Reference them through variables and secrets whenever possible. When migrating to staging or production, you only need to complete missing target-environment values as prompted, and production secrets will not be written into migration content.
+
+Related documentation: [Variables and Secrets](../variables-and-secrets/index.md).
+
+## Development Stage: Record Recoverable Checkpoints
+
+Development changes frequently. Use version control to save key checkpoints. Before a major configuration change, create a version. After adjusting data models, pages, permissions, workflows, or plugin settings, create another version.
+
+Write version descriptions with clear business meaning. For example, “adjust customer follow-up page and field permissions,” “add ticket escalation workflow,” or “optimize asset request approval flow.” Clear descriptions make later validation, comparison, and recovery easier.
+
+Version control mainly serves the development process. It is suitable for undoing a configuration change or preserving a milestone. After entering the release stage, synchronize configuration changes through Migration Manager. Use Backup Manager when production needs recovery.
+
+Related documentation: [Version control](../version-control/index.md).
+
+## Module Splitting: Control Release Boundaries
+
+For small systems, start with a single app. A single app is simple to deploy and works well for prototypes, small internal systems, and early-stage projects.
 
-## Installation
+As business complexity grows, one app may contain more pages, tables, permissions, and workflows. One configuration change may affect several teams. One release may involve several modules. At that point, consider splitting business boundaries with multi-app architecture.
 
-Three plugins are essential for release management. Please ensure all of the following plugins are activated.
+Multi-app works well when split by business responsibility, such as CRM, tickets, assets, HR, reports, and operations backend. Each app can be developed, tested, released, and rolled back independently. High-change modules, high-risk modules, and modules serving different user groups are often better separated.
 
-### Environment Variables
+Plan shared capabilities before splitting. Users, organizations, authentication, permissions, and cross-app shared data all affect later release methods. Clearer boundaries make release impact easier to control.
 
-- Built-in plugin, installed and activated by default.
-- Provides centralized configuration and management of environment variables and keys, used for sensitive data storage, reusable configuration data, environment-based isolation, etc. ([View Documentation](../variables-and-secrets/index.md)).
+A split release chain usually looks like this:
 
-### Backup Manager
+```text
+CRM app: Development environment -> Staging environment -> Production environment
+Ticket app: Development environment -> Staging environment -> Production environment
+Asset app: Development environment -> Staging environment -> Production environment
+```
 
-- Available only in the Professional edition or higher ([Learn more](https://www.nocobase.com/en/commercial)).
-- Supports backup and restoration, including scheduled backups, ensuring data security and quick recovery. ([View Documentation](../backup-manager/index.mdx)).
+Related documentation: [Multi-app management](../../multi-app/multi-app/index.md).
 
-### Migration Manager
+## Pre-release Preparation: Confirm Recovery Capability
 
-- Available only in the Professional edition or higher ([Learn more](https://www.nocobase.com/en/commercial)).
-- Used to migrate application configurations from one application environment to another ([View Documentation](../migration-manager/index.md)).
+Backup is the safety baseline for production release. Create a pre-release backup before publishing to production. For important releases, verify that the backup can be restored in an independent environment.
 
-## Common No-Code Development Processes
+Pre-release backups and scheduled daily backups serve different purposes. Scheduled backups handle misoperation, data corruption, and infrastructure failures. Pre-release backups support quick recovery after release failure. Both should be part of the production operations strategy.
 
-### Single Development Environment, One-Way Release
+Before release, confirm that the backup task has completed and that the backup file can be downloaded or accessed. For important releases, perform a restore verification in an independent environment.
 
-This approach suits simple development processes. There is one development environment, one pre-release environment, and one production environment. Changes flow from the development environment to the pre-release environment and are finally deployed to the production environment. In this process, only the development environment can modify configurations—neither the pre-release nor the production environment allows modifications.
+Backups should cover the database, user-uploaded files, and storage content required by the application runtime. Database-only records are not enough for full recovery.
+
+Related documentation: [Backup Manager](../backup-manager/index.mdx).
+
+## Release Execution: Migrate to the Target Environment
+
+Migration Manager publishes application configuration from one environment to another. Common migration content includes application configuration, table structures, plugin configuration, and some data that needs to be migrated.
+
+Publish to staging first. After the migration file passes staging validation, use the same file for production release.
 
 ![20250106234710](https://static-docs.nocobase.com/20250106234710.png)
 
-When configuring migration rules, select **“Overwrite”** for built-in tables in the core and plugins if needed; for all others, you can keep the default settings if there are no special requirements.
+### Publish to Staging
 
-![20250105194845](https://static-docs.nocobase.com/20250105194845.png)
+After generating a migration file from development, execute it in staging first. Staging should be as close to production as possible, including core version, plugin versions, variables, secrets, permission configuration, and external-system connection methods. After execution, validate core pages, permission rules, workflows, and external integrations.
+
+After staging validation passes, keep the same migration file for production release. Do not modify the migration file right before production. If changes are needed, go back to development, regenerate the file, and validate it again in staging.
+
+### Publish to Production
+
+Schedule a maintenance window for production release. Notify users before the release, stop user access or switch to a maintenance page, and avoid new business data writes during migration. In cluster or multi-node deployments, scale the application down to one node before migration.
+
+After confirming that the pre-release backup has completed, execute the migration file that passed staging validation. After migration, validate core business flows first, then restore user access. In multi-node deployments, restore the node count after validation passes.
 
-### Multiple Development Environments, Merged Release
+Migration files, backups, and execution logs are stored in their respective features. Internal release records can add release time, executor, validation result, and backup information for later troubleshooting and rollback.
 
-This approach suits multi-person collaboration or complex projects. Several parallel development environments can be used independently, and all changes are merged into a single pre-release environment for testing and verification before being deployed to production. In this process, only the development environment can modify configurations—neither the pre-release nor the production environment allows modifications.
+### Migration Rules
 
-![20250107103829](https://static-docs.nocobase.com/20250107103829.png)
+Migration rules decide how tables and records are handled in the target environment. Common strategies include overwrite, schema-only, and skip. Before configuring rules, first distinguish application and plugin built-in tables from user-defined tables.
 
-When configuring migration rules, select **“Insert or Update”** for built-in tables in the core and plugins if needed; for all others, you can keep the default settings if there are no special requirements.
+Application and plugin built-in tables usually follow the default strategy and use overwrite first. Examples include pages, menus, blocks, permissions, and workflows. During release, development configuration is usually treated as the source of truth and synchronized to staging and production.
 
-![20250105194942](https://static-docs.nocobase.com/20250105194942.png)
+User-defined tables should be judged by business purpose. Tables that carry real business data usually migrate structure only and use schema-only, avoiding overwrites of production data. Some user-defined tables that store metadata such as configuration, categories, templates, or rules can use overwrite depending on the business scenario.
 
-## Rollback
+For the tables behind default strategies, see [Built-in tables for applications and major plugins](../migration-manager/built-in-tables.md).
 
-Before executing a migration, the system automatically creates a backup of the current application. If the migration fails or the results are not as expected, you can roll back and restore via the [Backup Manager](../backup-manager/index.mdx).
+![20250105194845](https://static-docs.nocobase.com/20250105194845.png)
+
+Migration Manager mainly handles application configuration and data in the main database. External data sources, sub-app data, and some storage-directory content should be handled separately according to the actual situation.
+
+Related documentation: [Migration Manager](../migration-manager/index.md).
+
+## Rollback and Recovery
+
+When a release fails, first use the pre-release backup through the Backup Manager plugin. Before restoring, confirm that the backup file is available and follow the UI prompts to complete restoration.
+
+If the current production environment can still access Backup Manager and only the migration execution failed, restore the pre-release backup directly in the current environment. After recovery, record the failure cause and handling result to avoid repeating the same issue in later releases.
+
+If the current environment is unstable, or you want to reduce the risk of repeated repair attempts in a faulty environment, prepare an independent environment and restore the pre-release backup there. After restoration, validate core business flows first, then switch traffic to the recovered environment.
 
 ![20250105195029](https://static-docs.nocobase.com/20250105195029.png)
+
+## Related Documentation
+
+- [Variables and Secrets](../variables-and-secrets/index.md)
+- [Version control](../version-control/index.md)
+- [Multi-app management](../../multi-app/multi-app/index.md)
+- [Backup Manager](../backup-manager/index.mdx)
+- [Migration Manager](../migration-manager/index.md)

package/dist/ai/docs/nocobase/ops-management/version-control/index.md

@@ -1,12 +1,13 @@
 ---
+pkg: '@nocobase/plugin-version-control'
 title: "Version control"
-description: "Version control plugin guide: create versions, restore versions, configure retention, set shortcuts, and include user collections in saved versions."
-keywords: "Version control,ops management,create version,restore version,NocoBase"
+description: "Version control plugin guide: automatically save versions during AI Builder sessions, create and restore versions manually, configure retention, set shortcuts, and include user collections in saved versions."
+keywords: "Version control,ops management,AI Builder,nocobase-revision,nb revision create,create version,restore version,NocoBase"
 ---
 
 # Version control
 
-In NocoBase, **Version control** lets you save a restorable version of the current application. You can create versions manually, restore the application to a saved version when needed, and use the plugin settings to control how many versions to keep, which shortcut to use, and which user collections should be saved with the version.
+In NocoBase, **Version control** lets you save a restorable version of the current application. You can create versions manually, restore the application to a saved version when needed, and let AI Builder automatically save versions after meaningful milestones.
 
 Version control depends on [Backup manager](../backup-manager/index.mdx) to save and restore application states. Before using Version control, enable Backup manager first.
 
@@ -16,17 +17,31 @@ Community and Standard editions do not include the Version control plugin. If yo
 
 :::
 
+## AI auto-saved versions
+
+After the Version control plugin is enabled, AI Builder gets an extra rollback safeguard. When an AI Agent starts working on a request, it checks the NocoBase Skills available to the current application. If it finds the `nocobase-revision` skill, it can save key building milestones as restorable versions.
+
+![AI detects the nocobase-revision skill when building starts](https://static-docs.nocobase.com/20260611115845.png)
+
+When AI completes a piece of work that can be reviewed on its own, such as building a page, creating a set of collections, or configuring a workflow, it runs `nb revision create` through the NocoBase CLI. You do not need to click 「Create version」 manually each time, and small adjustments will not create noisy version records.
+
+![AI creates a version after building](https://static-docs.nocobase.com/20260611115804.png)
+
+These versions appear in the versions list. If later changes do not match your expectations, you can restore to the previous clear building milestone and continue adjusting from there.
+
 ## Open the plugin
 
-You can open the plugin from 「System settings」 → 「Version control」. A Version control button also appears in the top bar. Click it to create a version directly or jump to the versions list. The default shortcut for creating a version is `Ctrl + K`, and you can change it in the settings tab.
+After the plugin is enabled, a 「Version control」 menu appears in the top bar. You can create a version directly from there or open the versions list.
+
+You can also open the plugin from 「System settings / Version control」. The default shortcut for creating a version is `Ctrl + K`, and you can change it in the settings tab.
 
-![](https://static-docs.nocobase.com/20260526220402.png)
+![Version control menu](https://static-docs.nocobase.com/20260611112317.png)
 
 ## Create a version
 
 Click 「Create version」, enter a description, and save it. The description can be up to 2000 characters. It is useful for recording the background of the change, such as “Adjusted approval fields and permissions”.
 
-![](https://static-docs.nocobase.com/20260526220510.png)
+![Create version](https://static-docs.nocobase.com/20260611112739.png)
 
 After you click save, the list first shows a temporary “Saving” entry. When the task finishes, the saved version appears in the list.
 
@@ -77,3 +92,4 @@ If you include a user collection, NocoBase also includes related collections aut
 - [Backup manager](../backup-manager/index.mdx) — the underlying capability required by Version control
 - [Migration manager](../migration-manager/index.md) — move application configuration across environments
 - [Release management](../release-management/index.md) — plan release workflows with backups, migrations, and variables
+- [AI Builder quick start](../../ai-builder/index.md) — use natural language to complete data modeling, page configuration, and workflow orchestration

package/dist/ai/docs/nocobase/plugin-development/client/index.md

@@ -29,6 +29,7 @@ Specifically:
 1. **[Plugin](./plugin)**: The plugin entry class. Register routes, models, and other resources in lifecycle methods like `load()`.
 2. **[Router](./router)**: Register page routes via `router.add()` and plugin settings pages via `pluginSettingsManager`.
 3. **[Component](./component/index.md)**: Routes mount React components. Just use React + Antd by default -- no different from regular frontend development.
+| Find reusable form, filter, and table components       | [Shared Components](/shared-components/)                 |
 4. **[Context](./ctx/index.md)**: In plugins, access context via `this.context`; in components, use `useFlowContext()` to get the context. This gives you access to NocoBase capabilities -- making requests (`ctx.api`), internationalization (`ctx.t`), logging (`ctx.logger`), etc.
 5. **[FlowEngine](./flow-engine/index.md)**: If your components need to appear in the "Add Block / Field / Action" menus and support visual configuration by users, you need to wrap them with FlowModel.
 

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-acl/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Access Control"
+title: "Access control"
+keywords: "Users & permissions"
+displayName: "Access control"
 packageName: '@nocobase/plugin-acl'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Based on roles, resources, and actions, Access Control can precisely manage Interface Configuration permissions, data operation permissions, menu access permissions, and plugin permissions.
+  Based on roles, resources, and actions, access control can precisely manage interface configuration permissions, data operation permissions, menu access permissions, and plugin permissions.
 isFree: true
 builtIn: true
 defaultEnabled: true
 editionLevel: 0
 ---
 
-# Access Control
+# Access control

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-bulk-edit/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Action: Bulk edit"
+title: "Action: Batch edit"
+keywords: "Actions"
+displayName: "Action: Batch edit"
 packageName: '@nocobase/plugin-action-bulk-edit'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Bulk edit all or selected data.
+  Batch edit all records or selected records.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Bulk edit
+# Action: Batch edit

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-bulk-update/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Action: Bulk update"
+title: "Action: Batch update"
+keywords: "Actions"
+displayName: "Action: Batch update"
 packageName: '@nocobase/plugin-action-bulk-update'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Bulk update all or selected records.
+  Batch update all records or selected records.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Bulk update
+# Action: Batch update

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-custom-request/index.md

@@ -1,14 +1,17 @@
 ---
+title: "Action: Custom request"
+keywords: "Actions"
 displayName: "Action: Custom request"
 packageName: '@nocobase/plugin-action-custom-request'
 supportedVersions:
   - 1.x
+  - 2.x
 description: |
-  Sends requests to any HTTP service and supports sending context data to the target service.
+  Sending a request to any HTTP service supports sending context data to the target service.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Custom request
+# Action: Custom request

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-duplicate/index.md

@@ -1,15 +1,17 @@
 ---
+title: "Action: Duplicate record"
+keywords: "Actions"
 displayName: "Action: Duplicate record"
 packageName: '@nocobase/plugin-action-duplicate'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Duplicate a record. You can either duplicate it into a form and edit it before submitting, or you can duplicate it directly to generate a new record.
+  Duplicate a record, you can either duplicate it into a form and edit it before saving it, or you can duplicate it directly to generate a new record.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Duplicate record
+# Action: Duplicate record

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-export/index.md

@@ -1,15 +1,17 @@
 ---
+title: "Action: Export records"
+keywords: "Actions"
 displayName: "Action: Export records"
 packageName: '@nocobase/plugin-action-export'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Export filtered records to Excel, you can configure which fields to export.
+  Export filtered records to excel, you can configure which fields to export.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Export records
+# Action: Export records

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-export-pro/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Action: Export records Pro"
+keywords: "Actions"
 displayName: "Action: Export records Pro"
 packageName: '@nocobase/plugin-action-export-pro'
 supportedVersions:
@@ -12,4 +14,4 @@ defaultEnabled: false
 editionLevel: 1
 ---
 
-# Action: Export records Pro
+# Action: Export records Pro

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-import/index.md

@@ -1,15 +1,17 @@
 ---
+title: "Action: Import records"
+keywords: "Actions"
 displayName: "Action: Import records"
 packageName: '@nocobase/plugin-action-import'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Import records using Excel templates. You can configure which fields to import and templates will be generated automatically.
+  Import records using excel templates. You can configure which fields to import and templates will be generated automatically.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Import records
+# Action: Import records

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-import-pro/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Action: Import records Pro"
+keywords: "Actions"
 displayName: "Action: Import records Pro"
 packageName: '@nocobase/plugin-action-import-pro'
 supportedVersions:
@@ -12,4 +14,4 @@ defaultEnabled: false
 editionLevel: 1
 ---
 
-# Action: Import records Pro
+# Action: Import records Pro

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-print/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Action: Print"
+keywords: "Actions"
 displayName: "Action: Print"
 packageName: '@nocobase/plugin-action-print'
 description: |
@@ -9,4 +11,4 @@ defaultEnabled: false
 editionLevel: 0
 ---
 
-# Action: Print
+# Action: Print

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-action-template-print/index.md

@@ -1,15 +1,17 @@
 ---
-displayName: "Print Template"
+title: "Template print"
+keywords: "Actions"
+displayName: "Template print"
 packageName: '@nocobase/plugin-action-template-print'
 supportedVersions:
   - 1.x
   - 2.x
 description: |
-  Supports printing templates within NocoBase applications.
+  It supports users in printing templates within the NocoBase application.
 isFree: false
 builtIn: false
 defaultEnabled: false
 editionLevel: 2
 ---
 
-# Print Template
+# Template print

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-ai/index.md

@@ -1,6 +1,10 @@
 ---
-displayName: "AI Employee"
+title: "AI employees"
+keywords: "AI"
+displayName: "AI employees"
 packageName: '@nocobase/plugin-ai'
+supportedVersions:
+  - 2.x
 description: |
   Create AI employees with diverse skills to collaborate with humans, build systems, and handle business operations.
 isFree: true
@@ -9,4 +13,4 @@ defaultEnabled: false
 editionLevel: 0
 ---
 
-# AI Employee
+# AI employees

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-ai-gigachat/index.md

@@ -1,4 +1,6 @@
 ---
+title: "AI LLM: GigaChat"
+keywords: "AI"
 displayName: "AI LLM: GigaChat"
 packageName: '@nocobase/plugin-ai-gigachat'
 supportedVersions:
@@ -11,4 +13,4 @@ defaultEnabled: false
 editionLevel: 0
 ---
 
-# AI LLM: GigaChat
+# AI LLM: GigaChat

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-ai-knowledge-base/index.md

@@ -1,4 +1,6 @@
 ---
+title: "AI: Knowledge base"
+keywords: "AI"
 displayName: "AI: Knowledge base"
 packageName: '@nocobase/plugin-ai-knowledge-base'
 supportedVersions:

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-api-doc/index.md

@@ -1,5 +1,7 @@
 ---
-displayName: "API Documentation"
+title: "API documentation"
+keywords: "API documentation,Plugin,NocoBase"
+displayName: "API documentation"
 packageName: '@nocobase/plugin-api-doc'
 description: |
   An OpenAPI documentation generator for NocoBase HTTP API.
@@ -9,4 +11,4 @@ defaultEnabled: false
 editionLevel: 0
 ---
 
-# API Documentation
+# API documentation

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-api-keys/index.md

@@ -1,12 +1,14 @@
 ---
-displayName: "Authentication: API keys"
+title: "Auth: API keys"
+keywords: "Authentication"
+displayName: "Auth: API keys"
 packageName: '@nocobase/plugin-api-keys'
 description: |
-  Allows users to use API keys to access the application's HTTP API
+  Allows users to use API key to access application's HTTP API
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Authentication: API keys
+# Auth: API keys

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-app-sso/index.md

@@ -0,0 +1,16 @@
+---
+title: "App SSO"
+keywords: "Authentication"
+displayName: "App SSO"
+packageName: '@nocobase/plugin-app-sso'
+supportedVersions:
+  - 2.x
+description: |
+  Application-to-application single sign-on for multi-app deployments.
+isFree: false
+builtIn: false
+defaultEnabled: false
+editionLevel: 3
+---
+
+# App SSO

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-app-supervisor/index.md

@@ -1,14 +1,16 @@
 ---
-displayName: "App Supervisor"
+title: "App supervisor"
+keywords: "Architecture"
+displayName: "App supervisor"
 packageName: '@nocobase/plugin-app-supervisor'
 supportedVersions:
   - 2.x
 description: |
-  The App Supervisor plugin is used for the unified supervision and scheduling of multiple NocoBase application instances, providing application discovery and application runtime management capabilities.
+  The App Supervisor plugin provides unified supervision and orchestration of multiple NocoBase application instances, offering application discovery and runtime management capabilities.
 isFree: false
 builtIn: false
 defaultEnabled: false
 editionLevel: 3
 ---
 
-# App Supervisor
+# App supervisor

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-async-task-manager/index.md

@@ -1,12 +1,14 @@
 ---
-displayName: "Asynchronous Task Manager"
+title: "Async task manager"
+keywords: "Async task manager,Plugin,NocoBase"
+displayName: "Async task manager"
 packageName: '@nocobase/plugin-async-task-manager'
 description: |
-  Manage and monitor asynchronous tasks such as data import/export. Supports task progress tracking and notification.
+  Manage and monitor asynchronous tasks such as data import/export. Support task progress tracking and notification.
 isFree: true
 builtIn: true
 defaultEnabled: false
 editionLevel: 0
 ---
 
-# Asynchronous Task Manager
+# Async task manager

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-audit-logger/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Audit logs"
+keywords: "Logging and monitoring"
 displayName: "Audit logs"
 packageName: '@nocobase/plugin-audit-logger'
 supportedVersions:

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-audit-logs/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Audit logs (deprecated)"
+keywords: "System & security"
 displayName: "Audit logs (deprecated)"
 packageName: '@nocobase/plugin-audit-logs'
 description: |
@@ -12,4 +14,4 @@ editionLevel: 0
 
 # Audit logs (deprecated)
 
-> Note: This plugin is deprecated.
+> Note: This plugin is deprecated.

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-auth/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Authentication"
+keywords: "Authentication,Security"
 displayName: "Authentication"
 packageName: '@nocobase/plugin-auth'
 description: |
@@ -9,4 +11,4 @@ defaultEnabled: false
 editionLevel: 0
 ---
 
-# Authentication
+# Authentication

package/dist/ai/docs/nocobase/plugins/@nocobase/plugin-auth-cas/index.md

@@ -1,4 +1,6 @@
 ---
+title: "Auth: CAS"
+keywords: "Authentication"
 displayName: "Auth: CAS"
 packageName: '@nocobase/plugin-auth-cas'
 supportedVersions:
@@ -12,4 +14,4 @@ defaultEnabled: false
 editionLevel: 2
 ---
 
-# Auth: CAS
+# Auth: CAS