@nocobase/plugin-ai 2.2.0-beta.1 → 2.2.0-beta.2

package/dist/ai/docs/nocobase/ai/windows-wsl.md

@@ -0,0 +1,409 @@
+---
+title: Set Up a Local Development Environment on Windows with WSL
+description: Prepare Ubuntu, Docker Desktop, Node.js, Yarn, and Codex CLI with WSL 2 on Windows for NocoBase local development and AI Agent workflows.
+---
+
+# Set Up a Local Development Environment on Windows with WSL
+
+For local NocoBase development on Windows, we recommend preparing WSL 2 first. This lets Node.js, Yarn, NocoBase CLI, Docker commands, and AI Agents run in the same Linux shell, with paths, permissions, and native dependency builds closer to common Linux deployment environments.
+
+If you are not sure whether you need WSL, see [Local Development Setup](./local-development-setup.md) first.
+
+## Before You Start
+
+Before installing WSL, check your Windows version and virtualization status.
+
+### Check the Windows Version
+
+Press `Win + R`, enter `winver`, and confirm that your system meets one of the following requirements:
+
+- Windows 11
+- Windows 10 version 2004 or later, Build 19041 or later
+
+If your version is older, upgrade Windows before continuing.
+
+### Check Virtualization
+
+Open Task Manager, go to Performance / CPU, and confirm that Virtualization is shown as Enabled.
+
+If virtualization is not enabled, enable it in BIOS / UEFI. The option name varies by vendor, such as Intel VT-x, Intel Virtualization Technology, AMD-V, or SVM Mode.
+
+## Step 1: Install WSL 2
+
+Open PowerShell as administrator:
+
+1. Open the Windows Start menu
+2. Search for `PowerShell`
+3. Right-click and choose Run as administrator
+
+Run:
+
+```powershell
+wsl --install
+```
+
+Restart your computer after installation.
+
+By default, this command installs Ubuntu. When Ubuntu starts for the first time, it asks you to create a Linux username and password. This username and password are only used inside WSL and do not need to match your Windows account.
+
+To install a specific distribution, list the available distributions first:
+
+```powershell
+wsl --list --online
+```
+
+Then install a distribution, such as Ubuntu:
+
+```powershell
+wsl --install -d Ubuntu
+```
+
+## Step 2: Confirm the WSL Version
+
+Run the following command in PowerShell:
+
+```powershell
+wsl --list --verbose
+```
+
+The output should look like this:
+
+```text
+  NAME      STATE           VERSION
+* Ubuntu    Running         2
+```
+
+Confirm that `VERSION` is `2`. If a distribution is still using WSL 1, convert it to WSL 2:
+
+```powershell
+wsl --set-version Ubuntu 2
+```
+
+We also recommend setting WSL 2 as the default version for newly installed distributions:
+
+```powershell
+wsl --set-default-version 2
+```
+
+You can also update WSL once:
+
+```powershell
+wsl --update
+```
+
+## Step 3: Install Docker Desktop
+
+If you plan to install or run NocoBase with Docker, install Docker Desktop for Windows.
+
+Download the installer from the Docker documentation:
+
+- [Install Docker Desktop on Windows](https://docs.docker.com/desktop/setup/install/windows-install/)
+
+During installation, pay attention to these options:
+
+1. Usually, choose `Per-user` for personal local development
+2. On the configuration page, select `Use WSL 2 instead of Hyper-V`
+3. After installation, start Docker Desktop from the Windows Start menu
+4. On first launch, read and accept the Docker Desktop Subscription Service Agreement
+
+## Step 4: Enable Docker WSL Integration
+
+After Docker Desktop starts, first confirm that the WSL 2 backend is enabled:
+
+1. Go to Docker Desktop / Settings / General
+2. Confirm that Use the WSL 2 based engine is enabled
+3. Click Apply
+
+![Docker Desktop WSL 2 engine](https://static-docs.nocobase.com/2026-06-12-19-10-41.png)
+
+Then enable distribution integration:
+
+1. Go to Docker Desktop / Settings / Resources / WSL Integration
+2. Enable Enable integration with my default WSL distro
+3. Find the distribution you want to use, such as `Ubuntu`
+4. Enable the switch for that distribution
+5. Click Apply & restart or Apply
+
+![Docker Desktop WSL integration](https://static-docs.nocobase.com/2026-06-12-19-11-09.png)
+
+If WSL Integration does not appear under Resources, Docker Desktop is usually in Windows containers mode. Click the Docker icon in the Windows system tray, switch to Linux containers, and check again.
+
+## Step 5: Verify Docker
+
+First verify from PowerShell:
+
+```powershell
+wsl --list --verbose
+docker version
+docker compose version
+docker run hello-world
+```
+
+Then enter WSL:
+
+```powershell
+wsl
+```
+
+Run the following commands inside WSL:
+
+```bash
+docker version
+docker compose version
+docker run hello-world
+```
+
+If the `hello-world` container is pulled and runs successfully, Docker Desktop and WSL 2 integration are working.
+
+## Step 6: Install Node.js and Yarn in WSL
+
+WSL itself is not a Node.js runtime environment. Ubuntu installed through `wsl --install` usually does not include Node.js or npm, so install them inside the WSL distribution.
+
+Enter WSL from PowerShell:
+
+```powershell
+wsl
+```
+
+All commands below are run in the WSL terminal.
+
+First check whether Node.js is already installed:
+
+```bash
+node -v
+npm -v
+```
+
+If you see `command not found`, install Node.js with one of the following methods.
+
+### Option A: Install Node.js 22 with NodeSource
+
+If this WSL environment only needs one shared Node.js version, NodeSource is recommended.
+
+```bash
+sudo apt update
+sudo apt install -y curl
+curl -fsSL https://deb.nodesource.com/setup_22.x -o nodesource_setup.sh
+sudo -E bash nodesource_setup.sh
+sudo apt install -y nodejs
+```
+
+Verify the installation:
+
+```bash
+node -v
+npm -v
+npx -v
+```
+
+### Option B: Install Node.js 22 with nvm
+
+If you need to switch Node.js versions across projects, or if a project uses `.nvmrc` to pin the version, use nvm.
+
+```bash
+sudo apt update
+sudo apt install -y curl ca-certificates
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.5/install.sh | bash
+source ~/.bashrc
+nvm install 22
+nvm use 22
+```
+
+Verify the installation:
+
+```bash
+node -v
+npm -v
+npx -v
+```
+
+If the project root needs to pin Node.js 22, create `.nvmrc`:
+
+```bash
+echo "22" > .nvmrc
+nvm install
+nvm use
+```
+
+Later, run this command after entering the project directory:
+
+```bash
+nvm use
+```
+
+This switches to the version specified by the project.
+
+:::warning Note
+
+Choose either NodeSource or nvm. We do not recommend mixing both Node.js management methods in the same WSL user environment.
+
+:::
+
+### Install Yarn 1.x
+
+NocoBase local development requires Yarn 1.x. After Node.js is installed, you can enable Yarn through Corepack:
+
+```bash
+corepack enable
+corepack prepare yarn@1.22.22 --activate
+yarn -v
+```
+
+If Corepack is not available in your environment, install Yarn with npm:
+
+```bash
+npm install -g yarn@1.22.22
+yarn -v
+```
+
+## Step 7: Install Codex CLI
+
+Codex CLI can also be used in the native Windows command line. In this guide, it is installed inside WSL so Codex and the NocoBase local toolchain stay in the same Linux environment. When Codex runs commands such as `nb`, `yarn`, or `docker`, it uses the same file paths, shell syntax, and runtime environment.
+
+Confirm that you are currently inside WSL:
+
+```bash
+echo $WSL_DISTRO_NAME
+```
+
+If it outputs a distribution name such as `Ubuntu`, you are inside WSL.
+
+Run the Codex CLI installer inside WSL:
+
+```bash
+curl -fsSL https://chatgpt.com/codex/install.sh | sh
+```
+
+For non-interactive installation, use:
+
+```bash
+curl -fsSL https://chatgpt.com/codex/install.sh | CODEX_NON_INTERACTIVE=1 sh
+```
+
+After installation, run:
+
+```bash
+codex
+```
+
+The first run prompts you to sign in. Follow the prompts and authenticate with a ChatGPT account or OpenAI API key.
+
+Verify that the Codex command is available:
+
+```bash
+codex --version
+```
+
+We recommend starting Codex from a project directory inside WSL:
+
+```bash
+mkdir -p ~/projects
+cd ~/projects/my-app
+codex
+```
+
+:::tip Note
+
+Because Codex is installed inside WSL, run `codex` from the WSL terminal afterward. If you run `codex` from Windows PowerShell, it uses the native Windows command-line environment, which is not the same environment prepared in this guide.
+
+:::
+
+## Where to Put Project Files
+
+We recommend putting project files inside the WSL filesystem, for example:
+
+```bash
+~/projects/my-app
+```
+
+Avoid using the Windows mounted path as the default project location, for example:
+
+```bash
+/mnt/c/Users/<your-name>/projects/my-app
+```
+
+This usually gives better filesystem performance and reduces symlink and permission issues. The difference is especially visible for projects with many dependency files, such as Node.js, Python, Java, or Go projects.
+
+To access WSL files from Windows Explorer, open:
+
+```text
+\\wsl$\Ubuntu\home\<your-name>
+```
+
+## FAQ
+
+### WSL Says the docker Command Is Not Found
+
+First confirm that the distribution uses WSL 2:
+
+```powershell
+wsl --list --verbose
+```
+
+If it is WSL 1, convert it to WSL 2:
+
+```powershell
+wsl --set-version Ubuntu 2
+```
+
+Then return to Docker Desktop, go to Settings / Resources / WSL Integration, enable integration for the corresponding distribution, and apply the change.
+
+### WSL Integration Is Missing
+
+Usually, Docker Desktop is currently in Windows containers mode.
+
+You can handle it like this:
+
+1. Click the Docker icon in the Windows system tray
+2. Choose Switch to Linux containers
+3. Wait for Docker Desktop to restart
+4. Go to Settings / Resources / WSL Integration again
+
+### Docker Desktop Fails to Start or WSL Looks Abnormal
+
+Try this first:
+
+```powershell
+wsl --shutdown
+wsl --update
+```
+
+Then restart Docker Desktop.
+
+### Docker Engine Was Manually Installed in WSL
+
+Docker recommends uninstalling Docker Engine or Docker CLI that was installed directly inside the WSL Linux distribution before installing Docker Desktop. Otherwise, it may conflict with Docker Desktop WSL integration.
+
+Usually, uninstall `docker-ce`, `docker-ce-cli`, `containerd.io`, and related packages inside the WSL distribution, and then use the Docker CLI integration provided by Docker Desktop.
+
+### WSL Says the codex Command Is Not Found
+
+First confirm that you are running the command inside WSL, not PowerShell:
+
+```bash
+echo $WSL_DISTRO_NAME
+```
+
+Then check whether Codex is in `PATH`:
+
+```bash
+which codex
+```
+
+If it cannot be found, reopen the WSL terminal or run the installer again:
+
+```bash
+curl -fsSL https://chatgpt.com/codex/install.sh | sh
+```
+
+## Official References
+
+- [Microsoft Learn: How to install Linux on Windows with WSL](https://learn.microsoft.com/en-us/windows/wsl/install)
+- [Microsoft Learn: Install Node.js on Windows Subsystem for Linux](https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl)
+- [Docker Docs: Install Docker Desktop on Windows](https://docs.docker.com/desktop/setup/install/windows-install/)
+- [Docker Docs: Docker Desktop WSL 2 backend on Windows](https://docs.docker.com/desktop/features/wsl/)
+- [Docker Docs: Change your Docker Desktop settings](https://docs.docker.com/desktop/settings-and-maintenance/settings/)
+- [OpenAI Developers: Codex CLI](https://developers.openai.com/codex/cli)
+- [OpenAI Developers: Codex on Windows](https://developers.openai.com/codex/windows)
+- [nvm: Node Version Manager](https://github.com/nvm-sh/nvm)
+- [npm Docs: Downloading and installing Node.js and npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm/)

package/dist/ai/docs/nocobase/ai/workbuddy/index.md

@@ -70,7 +70,7 @@ Before starting, make sure you have the following environment ready:
 
 - WorkBuddy account ([registration portal](https://www.codebuddy.cn))
 - Node.js >= 22 (for running NocoBase CLI and Skills)
-- If you already have a NocoBase instance, **AI capabilities are evolving rapidly and only the latest beta version provides the full experience. Minimum version >= 2.1.0-beta.20, latest version strongly recommended.**
+- If you already have a NocoBase instance, **AI capabilities are evolving rapidly. The minimum required version is NocoBase 2.1.0, and we recommend updating to the latest version.**
 
 :::warning Note
 
@@ -91,7 +91,7 @@ Help me install NocoBase CLI and complete initialization: https://docs.nocobase.
 ### Manual Installation
 
 ```bash
-npm install -g @nocobase/cli@beta
+npm install -g @nocobase/cli
 nb init --ui
 ```
 

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

@@ -23,7 +23,7 @@ Help me install NocoBase CLI and complete initialization: https://docs.nocobase.
 ### Manual Installation
 
 ```bash
-npm install -g @nocobase/cli@beta
+npm install -g @nocobase/cli
 nb init --ui
 ```
 
@@ -95,13 +95,27 @@ The AI first outputs a design plan, then builds everything at once after confirm
 
 To learn more about building complete systems, see [Solutions](./dsl-reconciler).
 
+### Build a milestone, and the AI saves a restorable version for you
+
+After finishing a page, a set of data tables, or a workflow, let the AI save the current state as a version — if a configuration goes wrong, you can always roll back to the last clear milestone.
+
+```
+Save the current build as a version: completed customer management page, filter area, and edit form configuration
+```
+
+![AI creates a version after building](https://static-docs.nocobase.com/20260611115804.png)
+
+The AI won't save a version every time it changes a field; it only saves after completing and verifying a clear milestone, which keeps the version list easy to read and makes it easier to decide where to roll back to.
+
+To learn more about version control, see [Version Control](./version-control).
+
 ## Security & Audit
 
 Before letting an AI Agent operate NocoBase, we recommend understanding the authentication methods, permission controls, and operation auditing — ensuring the AI only does what it should, with every step recorded. See [Security & Audit](./security).
 
 ## NocoBase Skills
 
-[NocoBase Skills](https://github.com/nocobase/skills) are domain knowledge packages that can be installed into AI Agents, enabling AI to understand NocoBase's configuration system. NocoBase provides 8 Skills covering the entire building workflow:
+[NocoBase Skills](https://github.com/nocobase/skills) are domain knowledge packages that can be installed into AI Agents, enabling AI to understand NocoBase's configuration system. NocoBase provides 9 Skills covering the entire building workflow:
 
 - [Environment Management](./env-bootstrap) — Environment checks, installation, deployment, upgrades, and troubleshooting
 - [Data Modeling](./data-modeling) — Create and manage data tables, fields, and relationships
@@ -111,6 +125,7 @@ Before letting an AI Agent operate NocoBase, we recommend understanding the auth
 - [Solutions](./dsl-reconciler) — Batch-build entire business systems from YAML
 - [Plugin Management](./plugin-manage) — View, enable, and disable plugins
 - [Release Management](./publish) — Cross-environment releases, backup & restore, and migration
+- [Version Control](./version-control) — Save restorable versions after completed milestones
 
 :::tip
 

package/dist/ai/docs/nocobase/ai-builder/version-control.md

@@ -0,0 +1,120 @@
+---
+title: "Version Control"
+description: "The Version Control Skill (nocobase-revision) creates restorable application versions after AI Builder completes milestone work."
+keywords: "AI Builder,version control,nocobase-revision,nb revision create,restore version"
+---
+
+# Version Control
+
+:::tip Prerequisites
+
+- Before reading this page, install the NocoBase CLI and complete initialization as described in [AI Builder Quick Start](./index.md)
+- Enable the Backup Management and Version Control plugins
+- Community and Standard editions do not include the Version Control plugin. If you only need a rollback point before key changes, use [Backup Management](../ops-management/backup-manager/index.mdx)
+
+:::
+
+## Introduction
+
+The Version Control Skill (`nocobase-revision`) creates a restorable application version after AI Builder completes a meaningful milestone. For example, after building a page, creating a group of collections, or configuring a workflow, AI can run `nb revision create` to save the current state.
+
+It does not create a version for every field change. By default, it saves only after a clear milestone is completed and verified, so the version list stays readable and rollback points are easier to choose.
+
+For version lists, manual version creation, restore operations, and retention settings, see the [Version Control plugin guide](../ops-management/version-control/index.md).
+
+## Capabilities
+
+Can do:
+
+- Create a version after a building milestone is completed and verified
+- Write a concise description that explains what was saved
+- Create versions using the current CLI environment
+
+Cannot do:
+
+- Replace the underlying save and restore capabilities of the Backup Management plugin
+- Create versions when the Version Control plugin is not enabled
+- Restore to a version automatically. Use the [Version Control plugin](../ops-management/version-control/index.md) to restore versions
+
+## Prompt Examples
+
+### Scenario A: Save a completed page configuration
+
+```text
+Save the current build as a version: completed customer management page, filter area, and edit form configuration
+```
+
+The Skill turns the description into a concise version note and creates a version.
+
+Command mode:
+
+```bash
+nb revision create "Completed customer management page, filter area, and edit form configuration"
+```
+
+### Scenario B: Save data model and workflow milestones
+
+```text
+The supplier collections and purchase approval workflow have been verified. Create a version for me.
+```
+
+This fits work that spans multiple capabilities. For example, create collections with [Data Modeling](./data-modeling), configure an approval process with [Workflow Management](./workflow), verify the result, then save a version.
+
+### Scenario C: Create a version in a specified environment
+
+```text
+In the dev environment, save a version: completed ticket management page and SLA field configuration
+```
+
+If the specified environment is not the current CLI environment, the Skill confirms the target environment first to avoid saving the version to the wrong application.
+
+Command mode:
+
+```bash
+nb revision create --env dev --yes "Completed ticket management page and SLA field configuration"
+```
+
+## How to Write Version Descriptions
+
+A version description should say what has been completed, not just use a vague label.
+
+Recommended:
+
+- `Completed customer ledger, detail page, and approval submission flow`
+- `Completed supplier collections, purchase request form, and approval workflow`
+- `完成客户台账、详情页与审批提交流程配置`
+
+Not recommended:
+
+- `snapshot`
+- `backup`
+- `test`
+- `version 2`
+- Date or timestamp only
+
+Also, do not include tokens, URLs, passwords, or other sensitive information. Descriptions appear in the version list and should stay clear, readable, and auditable.
+
+## FAQ
+
+**When should I create a version?**
+
+Create one after a milestone that can be reviewed on its own. For example, a page opens and edits correctly, collection relationships have been verified, or a workflow has been saved and its node chain checked.
+
+**Why not create a version after every AI adjustment?**
+
+Too many tiny versions quickly make the list hard to read. A version should usually represent a point you can restore to and continue working from, not a single field rename or button position change.
+
+**Should the result be verified before creating a version?**
+
+Yes. The Version Control Skill is for saving completed and verified work. If a page still errors or a workflow is not confirmed, ask AI to fix and verify it before creating a version.
+
+**Where do I restore a version after it is created?**
+
+Restore it in the version list of the Version Control plugin. Restoring overwrites the current application configuration and the data included in that version. Read the [Version Control plugin guide](../ops-management/version-control/index.md) before operating.
+
+## Related Links
+
+- [Version Control plugin guide](../ops-management/version-control/index.md) — manually create versions, restore versions, and configure version rules
+- [Backup Management](../ops-management/backup-manager/index.mdx) — the underlying capability required by Version Control
+- [AI Builder Overview](./index.md) — overview and installation guide for all AI Builder Skills
+- [Release Management](./publish.md) — cross-environment releases, backup restore, and migration

package/dist/ai/docs/nocobase/ai-dev/index.md

@@ -25,7 +25,7 @@ Help me install NocoBase CLI and complete initialization: https://docs.nocobase.
 ### Manual Installation
 
 ```bash
-npm install -g @nocobase/cli@beta
+npm install -g @nocobase/cli
 nb init --ui
 ```
 

package/dist/ai/docs/nocobase/api/cli/init.md

@@ -74,7 +74,7 @@ By default, the CLI organizes local files under `app-path` using the following c
 
 Typically:
 
-- `source/` mainly corresponds to the local app directory for npm / Git envs. For Docker envs, the CLI also keeps this default path derivation, but most of the time you do not need to care about it manually
+- `source/` mainly corresponds to the local app directory for npm / Git envs. For Docker envs, the CLI also keeps this default path derivation, but most of the time you do not need to care about it manually. Pay special attention during upgrades: the `source/` directory will be deleted and downloaded again, so do not put files you need to keep here
 - `storage/` is used for runtime data, such as built-in database data, plugins, logs, and more
 - `.env` is an optional app environment variable file. You only need to add it in `<app-path>/.env` when you want to customize environment variables; if this file exists, Docker, npm, and Git install sources will all read it by default
 

package/dist/ai/docs/nocobase/api/cli/plugin/import.md

@@ -71,4 +71,4 @@ You do not need to extract anything into `storage/plugins` by hand. `nb plugin i
 
 - [`nb app restart`](../app/restart.md)
 - [`nb plugin enable`](./enable.md)
-- [`Install and upgrade third-party plugins`](../../../quickstart/plugins/third-party.md)
+- [`Install and upgrade third-party plugins`](../../../nocobase-cli/plugins/third-party.md)

package/dist/ai/docs/nocobase/get-started/how-nocobase-works.mdx

@@ -3,4 +3,11 @@
 <video controls width="100%" poster="https://static-docs.nocobase.com/video-cover-home.png">
   <source src="https://static-docs.nocobase.com/nocobase-2-main-1080p-en-v2.mp4" type="video/mp4" />
   Your browser does not support video playback.
-</video>
+</video>
+
+## What's Next
+
+If you've finished the video and want to start right away, there are usually two common paths:
+
+1. If you want to compare installation methods and version channels first, continue with [Installation and Version Comparison](/ai/quickstart)
+2. If you want to install the app right away, continue with [Install NocoBase App](/ai/install-nocobase-app)

package/dist/ai/docs/nocobase/get-started/quickstart.md

@@ -55,4 +55,9 @@ You can install NocoBase in different ways.
 | **Scenarios** | No-code users; users who want to quickly deploy to a server. | Front-end/full-stack developers; team projects; low-code development. | Technical developers; users who want to try unreleased versions. |
 | **Technical Requirement** | ★☆☆☆☆ | ★★★☆☆ | ★★★★★ |
 | **Upgrade Method** | Pull the latest image and restart the container. | Update dependencies with yarn. | Synchronize updates through Git. |
-| **Tutorials** | [<code>Installation</code>](#) [<code>Upgrade</code>](#) [<code>Deployment</code>](#) | [<code>Installation</code>](#) [<code>Upgrade</code>](#) [<code>Deployment</code>](#) | [<code>Installation</code>](#) [<code>Upgrade</code>](#) [<code>Deployment</code>](#) |
+
+![2026-06-11-20-09-54](https://static-docs.nocobase.com/2026-06-11-20-09-54.png)
+
+## What's Next
+
+If you've already picked an installation method, the next step is [Install NocoBase App](/ai/install-nocobase-app). It walks you through installing NocoBase CLI and finishing the app installation and initialization.

package/dist/ai/docs/nocobase/get-started/system-requirements.md

@@ -11,6 +11,14 @@ Except for functionality validation or purely experimental scenarios, **we stron
 
 The system configuration and capacity planning of those services must be evaluated and tuned separately based on the **actual data size, workload, and concurrency level**.
 
+## Operating System
+
+For production environments, Linux servers are recommended, such as Ubuntu LTS, Debian, Rocky Linux, or AlmaLinux. Docker, reverse proxy, process management, logging, and backup workflows are more mature on Linux and are easier to integrate with common cloud server environments.
+
+NocoBase can also be installed on Windows Server. If you choose Windows Server, confirm Node.js, database, reverse proxy, process supervision, backup, file permissions, firewall, and related operations based on your actual deployment method.
+
+macOS is usually more suitable for local development and testing, and is not recommended as a production server. If you are setting up NocoBase locally for development or AI Agent usage, see [Local Development Setup](../ai/local-development-setup.md).
+
 ## Single-Node Deployment Mode
 
 Single-node deployment mode means the NocoBase application service runs on a single server or container instance.
@@ -85,4 +93,4 @@ In cluster mode, the recommended hardware configuration for each application nod
 Recommendations for production environments:
 
 - Adjust the node count dynamically based on monitoring metrics (CPU, memory, request latency, and so on).
-- Reserve a resource buffer to handle traffic spikes.
+- Reserve a resource buffer to handle traffic spikes.