@nocobase/plugin-ai 2.1.0-alpha.30 → 2.1.0-alpha.31

package/dist/ai/docs/nocobase/ai-builder/security.md

@@ -91,7 +91,7 @@ nb env auth local
 
 `nb env auth` launches the browser login flow. After success, the CLI saves the authentication information to the current environment configuration, and you can then continue having the AI Agent call `nb api`.
 
-The validity periods of OAuth access tokens and refresh tokens follow the system [Token policy](/security/token-policy/) configuration.
+The validity periods of OAuth access tokens and refresh tokens follow the system [Token policy](../security/token-policy/index.md) configuration.
 
 - OAuth access tokens have the same validity period as system Tokens, with a default of **1 day**
 - OAuth refresh tokens have the same validity period as system sessions, with a default of **7 days**

package/dist/ai/docs/nocobase/interface-builder/blocks/data-blocks/details.md

@@ -79,7 +79,7 @@ For more details, see [Linkage Rules](/interface-builder/linkage-rule)
 
 ### Field template
 
-Field templates let you reuse the field section configuration (selected fields, layout, and field settings) in Details blocks. See [Field template](/interface-builder/fields/field-template).
+Field templates let you reuse the field section configuration (selected fields, layout, and field settings) in Details blocks. See [Field template](../../ui-templates.md).
 
 ![field-template-menu-20251228](https://static-docs.nocobase.com/field-template-menu-20251228.png)
 

package/dist/ai/docs/nocobase/interface-builder/blocks/data-blocks/form.md

@@ -73,7 +73,7 @@ The Form block supports two layout modes, which can be set via the `layout` attr
 
 ### Field Template
 
-Field templates are used to reuse field area configurations in Form blocks. For details, see [Field Template](/interface-builder/fields/field-template).
+Field templates are used to reuse field area configurations in Form blocks. For details, see [Field Template](../../ui-templates.md).
 
 ![field-template-menu-20251228](https://static-docs.nocobase.com/field-template-menu-20251228.png)
 

package/dist/ai/docs/nocobase/plugin-development/client/examples/custom-block.md

@@ -107,7 +107,7 @@ Key points:
 
 - **`renderComponent()`** -- Renders the block UI, reading HTML content via `this.props.html`
 - **`define()`** -- Sets the display name in the "Add Block" menu. `tExpr()` is used for deferred translation because `define()` executes at module load time, when i18n hasn't been initialized yet
-- **`registerFlow()`** -- Adds a configuration panel. `uiSchema` defines the form using JSON Schema (syntax reference: [UI Schema](../../../../flow-engine/ui-schema)), `handler` writes user-filled values to `ctx.model.props`, and `renderComponent()` can read them
+- **`registerFlow()`** -- Adds a configuration panel. `uiSchema` defines the form using JSON Schema (syntax reference: [UI Schema](../../../flow-engine/ui-schema.md)), `handler` writes user-filled values to `ctx.model.props`, and `renderComponent()` can read them
 
 ## Step 3: Add Multilingual Files
 
@@ -194,7 +194,7 @@ Capabilities used in this example:
 - [Writing Your First Plugin](../../write-your-first-plugin) -- Create a plugin skeleton from scratch
 - [FlowEngine Overview](../flow-engine/index.md) -- FlowModel basic usage and registerFlow
 - [FlowEngine -> Block Extension](../flow-engine/block) -- BlockModel, DataBlockModel, CollectionBlockModel
-- [UI Schema](../../../../flow-engine/ui-schema) -- uiSchema syntax reference
+- [UI Schema](../../../flow-engine/ui-schema.md) -- uiSchema syntax reference
 - [Component vs FlowModel](../component-vs-flow-model) -- When to use FlowModel
 - [Plugin](../plugin) -- Plugin entry point and load() lifecycle
 - [i18n Internationalization](../component/i18n) -- Translation file conventions and tExpr usage

package/dist/ai/docs/nocobase/solution/crm/guide/guide-customers-emails.md

@@ -175,4 +175,4 @@ Activity records also appear in the calendar view on the Overview dashboard.
 - [CRM User Guide](./index.md)
 - [Lead Management](./guide-leads) — Leads automatically create customers and contacts upon conversion
 - [Opportunity Management](./guide-opportunities) — Opportunities linked to customers
-- [AI Employees](./guide-ai)
+- [AI Employees](../../../ai-employees/index.md)

package/dist/ai/docs/nocobase/solution/crm/guide/guide-overview.md

@@ -201,10 +201,10 @@ Drill-through comes in two forms:
 
 ---
 
-After understanding the system layout and dashboards, go back to the [User Guide](./guide) for subsequent chapters.
+After understanding the system layout and dashboards, go back to the [User Guide](./index.md) for subsequent chapters.
 
 ## Related Pages
 
-- [CRM User Guide](./guide)
+- [CRM User Guide](./index.md)
 - [Solution Overview](../index)
 - [Installation](../installation)

package/dist/ai/docs/nocobase/tutorials/v2/01-getting-started.md

@@ -19,7 +19,7 @@ Compared to other no-code tools, NocoBase has a few core principles:
 
 - **Data model driven**: Define your data structure first, then use [blocks](/interface-builder/blocks) to display data, then [actions](/interface-builder/actions) to process it — UI and data are fully decoupled
 - **WYSIWYG**: Pages are your canvas. Click anywhere to edit, as intuitive as building a Notion page
-- **Everything is a plugin**: All features are [plugins](/development/plugin), similar to WordPress — install what you need
+- **Everything is a plugin**: All features are [plugins](../../plugins/index.mdx), similar to WordPress — install what you need
 - **AI built into your workflow**: Built-in [AI employees](/ai-employees/quick-start) that can perform analysis, translation, data entry, and more
 - **Open source + self-hosted**: Core code is fully open source, all data stays on your own server
 

package/dist/ai/docs/nocobase/tutorials/v2/03-building-pages.md

@@ -181,7 +181,7 @@ This way, newly submitted tickets always appear at the top, making them easier t
 Viewing a list isn't enough — we also need to click into tickets to see details and make edits.
 
 1. In the actions column, click the second "+" icon.
-2. Click to add actions: **View**, **[Edit](/interface-builder/actions/edit)**, **[Delete](/interface-builder/actions/delete)**.
+2. Click to add actions: **View**, **[Edit](../../interface-builder/actions/types/edit.md)**, **[Delete](../../interface-builder/actions/types/delete.md)**.
 3. Each row will now have "View", "Edit", and "Delete" buttons in the actions column.
 
 ![03-building-pages-2026-03-13-09-42-42](https://static-docs.nocobase.com/03-building-pages-2026-03-13-09-42-42.png)
@@ -211,7 +211,7 @@ Remember the "Categories" collection we created in Chapter 2? It's a **tree tabl
 
 Once enabled, the table will display categories in an indented hierarchy showing parent-child relationships, instead of listing all records flat.
 
-3. Check the fields you want to display (e.g., Name, Description), and configure row actions ([Add new](/interface-builder/actions/add-new), Edit, Delete).
+3. Check the fields you want to display (e.g., Name, Description), and configure row actions ([Add new](../../interface-builder/actions/types/add-new.md), Edit, Delete).
 4. **Layout tip**: Put "Name" in the first column and "Actions" in the second. The categories table doesn't have many fields, so a two-column layout is more compact and user-friendly.
 
 [Screenshot: Categories tree table configured]

package/dist/ai/docs/nocobase/tutorials/v2/04-forms-and-details.md

@@ -1,6 +1,6 @@
 # Chapter 4: Forms & Details — Input, Display, All in One
 
-In the last chapter, we built the ticket list and used a quick form to enter test data. In this chapter, we'll **refine the form experience** — optimize [Form block](/interface-builder/blocks/data-blocks/form) field layouts, add [Details blocks](/interface-builder/blocks/data-blocks/details), configure [linkage rules](/interface-builder/linkage-rules), and use [change history](https://docs.nocobase.com/record-history/) to track every modification.
+In the last chapter, we built the ticket list and used a quick form to enter test data. In this chapter, we'll **refine the form experience** — optimize [Form block](/interface-builder/blocks/data-blocks/form) field layouts, add [Details blocks](/interface-builder/blocks/data-blocks/details), configure [linkage rules](../../interface-builder/linkage-rule.md), and use [change history](https://docs.nocobase.com/record-history/) to track every modification.
 
 :::tip
 Section 4.4 "Change History" requires the [Professional edition](https://www.nocobase.com/en/commercial). Skipping it won't affect later chapters.
@@ -15,7 +15,7 @@ In the last chapter, we quickly created a working "Add new" form. Now let's refi
 1. Make sure you're in [UI Editor](/get-started/how-nocobase-works) mode (top-right toggle is on).
 2. Go to the "All Tickets" page, and click **"[Actions](/interface-builder/actions)"** above the Table block.
 3. Check the **"Add new"** action button.
-4. An "Add new" button will appear above the table. Clicking it opens a [popup](/interface-builder/actions/pop-up).
+4. An "Add new" button will appear above the table. Clicking it opens a [popup](../../interface-builder/actions/types/pop-up.md).
 
 ![04-forms-and-details-2026-03-13-09-43-54](https://static-docs.nocobase.com/04-forms-and-details-2026-03-13-09-43-54.png)
 
@@ -268,7 +268,7 @@ In this chapter, we completed the full data lifecycle:
 - **Form** — Users can submit new tickets with default values and validation
 - **Linkage rules** — Urgent tickets automatically require a description
 - **Details block** — Clearly displays a ticket's complete information
-- **[Change history](/collection-templates/audit-log)** — Automatically tracks every modification for worry-free auditing (commercial plugin, optional)
+- **[Change history](../../record-history/index.md)** — Automatically tracks every modification for worry-free auditing (commercial plugin, optional)
 
 From "visible" to "enterable" to "traceable" — our ticket system now has basic usability.
 
@@ -276,4 +276,4 @@ From "visible" to "enterable" to "traceable" — our ticket system now has basic
 
 - [Form Block](/interface-builder/blocks/data-blocks/form) — Form block configuration guide
 - [Details Block](/interface-builder/blocks/data-blocks/details) — Details block setup
-- [Linkage Rules](/interface-builder/linkage-rules) — Field linkage configuration
+- [Linkage Rules](../../interface-builder/linkage-rule.md) — Field linkage configuration

package/dist/ai/docs/nocobase/tutorials/v2/06-workflows.md

@@ -34,7 +34,7 @@ NocoBase offers several trigger types, which you select when creating a workflow
 |---------|-------------|-----------------|
 | **[Collection event](/workflow/triggers/collection)** | Fires when a record is created, updated, or deleted | New ticket notification, status change logging |
 | **[Schedule](/workflow/triggers/schedule)** | Fires on a Cron expression or fixed time | Daily reports, periodic data cleanup |
-| **[Post-action event](/workflow/triggers/action)** | Fires after a user performs a UI action | Send notification after form submission |
+| **[Post-action event](../../workflow/triggers/post-action.md)** | Fires after a user performs a UI action | Send notification after form submission |
 | **Approval** | Initiates an approval flow with multi-level support | Leave requests, purchase approvals |
 | **Custom action** | Bound to a custom button, fires on click | One-click archiving, batch operations |
 | **Pre-action event** | Intercepts a user action synchronously before it completes | Pre-submit validation, auto-fill fields |

package/dist/ai/docs/nocobase/workflow/nodes/javascript.md

@@ -8,7 +8,7 @@ pkg: '@nocobase/plugin-workflow-javascript'
 
 The JavaScript Script node allows users to execute a custom server-side JavaScript script within a workflow. The script can use variables from upstream in the workflow as parameters, and its return value can be provided to downstream nodes.
 
-The script runs in a worker thread on the NocoBase application's server. By default, it uses a secure sandbox (isolated-vm) that does not support `require` or Node.js built-in APIs. For details, see [Execution Engine](#execution-engine) and [Feature List](#feature-list).
+The script runs in a worker thread on the NocoBase application's server. By default, it uses a secure sandbox (QuickJS, powered by WebAssembly) that does not support `require` or Node.js built-in APIs. For details, see [Execution Engine](#execution-engine) and [Feature List](#feature-list).
 
 ## Create Node
 
@@ -50,7 +50,7 @@ The JavaScript script node supports two execution engines, automatically selecte
 
 ### Safe Mode (Default)
 
-When `WORKFLOW_SCRIPT_MODULES` is **not configured**, scripts run using the [isolated-vm](https://github.com/laverdet/isolated-vm) engine. This engine executes code in an isolated V8 environment with the following characteristics:
+When `WORKFLOW_SCRIPT_MODULES` is **not configured**, scripts run using the [QuickJS](https://bellard.org/quickjs/) engine compiled to WebAssembly. This engine executes code in an isolated JavaScript runtime with the following characteristics:
 
 - **Does not support** `require` — no modules can be imported
 - **Does not support** Node.js built-in APIs (such as `process`, `Buffer`, `global`, etc.)