tower-studio 0.1.0 → 0.1.2

package/.next/standalone/tower/docs/en/modules/task.md

@@ -0,0 +1,82 @@
+---
+title: Task
+description: Core work unit with status flow, labels, executions, and messages
+---
+
+# Task Module
+
+**Slug:** `task`
+
+## Overview
+
+Tasks are the core work unit in Tower, displayed as Kanban cards on the board. Each task moves through 5 status states (TODO, IN_PROGRESS, IN_REVIEW, DONE, CANCELLED) to represent workflow progress, and can be assigned one of 4 priority levels (LOW, MEDIUM, HIGH, CRITICAL). Tasks support custom labels for flexible categorization and can be pinned to stay at the top of their column.
+
+When creating a task, you can set a base branch for Git worktree isolation — each task execution then works on an independent branch without affecting the main codebase. Clicking "Execute" on a task spawns a PTY terminal running Claude CLI in that isolated environment. On completion, Tower auto-generates an execution summary and Dreaming insights that capture what was accomplished and learned.
+
+## Details
+
+- **Status workflow**: Tasks flow through 5 columns on the Kanban board. Dragging a card between columns or using the context menu updates the status.
+- **Priority levels**: LOW, MEDIUM, HIGH, and CRITICAL. Priority badges are visible on task cards for quick scanning.
+- **Labels**: Assigned from the workspace's label pool. Label assignment is a full replacement — pass the complete set of desired labels each time.
+- **Worktree isolation**: When `useWorktree` is enabled and a `baseBranch` is specified, each task execution runs in a separate Git worktree with its own branch.
+- **Execution lifecycle**: Each task can have multiple execution records tracking agent runs, with session IDs for resumption support.
+
+## Data Model
+
+```
+Task (id, title, description?, status, priority, order)
+  ├── TaskLabel[] → Label
+  ├── TaskExecution[]
+  └── TaskMessage[]
+```
+
+- `status`: `TODO` | `IN_PROGRESS` | `IN_REVIEW` | `DONE` | `CANCELLED`
+- `priority`: `LOW` | `MEDIUM` | `HIGH` | `CRITICAL`
+- `order`: Sorting within Kanban columns (ascending, lower values appear higher)
+- `projectId`: FK to Project, cascade delete
+
+## File Reference
+
+### Server Actions (`src/actions/task-actions.ts`)
+
+| Function | Description |
+|----------|-------------|
+| `createTask({ title, projectId, ... })` | Create task |
+| `updateTask(taskId, data)` | Update task |
+| `updateTaskStatus(taskId, status)` | Status transition |
+| `deleteTask(taskId)` | Delete task |
+| `getProjectTasks(projectId)` | Get all tasks for a project |
+
+### Pages
+
+| Route | File | Description |
+|-------|------|-------------|
+| `/workspaces/[id]/tasks/[taskId]` | `task-page-client.tsx` | Task detail page |
+
+### Components (`src/components/task/`)
+
+| Component | Description |
+|-----------|-------------|
+| `task-detail-panel.tsx` | Task metadata panel |
+| `task-terminal.tsx` | Terminal UI |
+| `task-diff-view.tsx` | Git diff view |
+| `task-merge-confirm-dialog.tsx` | Merge confirmation |
+| `code-editor.tsx` | Code editor |
+| `file-tree.tsx` | File tree |
+| `execution-timeline.tsx` | Execution history timeline |
+
+### MCP Tools (`src/mcp/tools/task-tools.ts`)
+
+- `list_tasks` / `create_task` / `update_task` / `move_task` / `delete_task`
+
+### Label Subsystem
+
+- Server Actions: `src/actions/label-actions.ts`
+- MCP Tools: `src/mcp/tools/label-tools.ts`
+- `set_task_labels` / `setTaskLabels` perform a full replacement (not a merge)
+
+## Constraints
+
+- The `order` field controls Kanban sorting; do not break existing ordering when creating tasks
+- Label replacement is a full replacement operation; pass the complete `labelIds` array
+- Deleting a task cascades to its Messages and Executions

package/.next/standalone/tower/docs/en/modules/terminal.md

@@ -0,0 +1,73 @@
+---
+title: Terminal
+description: PTY terminal system providing independent Claude CLI sessions per task
+---
+
+# Terminal Module
+
+**Slug:** `terminal`
+
+## Overview
+
+Each task gets its own terminal session rendered via xterm.js directly in the browser. Terminal I/O flows in real time over WebSocket with full ANSI rendering — colors, progress bars, cursor movement, and all standard terminal escape sequences are supported. You can type directly into the terminal for interactive keyboard input, enabling live conversation with Claude CLI.
+
+When a client disconnects, the session stays alive with auto-keepalive (2 hours while running, 5 minutes after the process exits). Multiple clients can view the same terminal session simultaneously — for example, the task detail page and the Missions monitoring panel can both display the same live terminal output.
+
+## Details
+
+- **Architecture**: The browser-side xterm.js terminal connects via WebSocket to a Node.js server (`ws-server.ts`), which bridges to a real PTY session managed by node-pty. The `session-store.ts` module keeps an in-memory registry of all active sessions indexed by task ID.
+- **One session per task**: Each task can only have one active PTY session at a time. Starting a new session for a task that already has one will fail.
+- **Concurrency limit**: The maximum number of simultaneous PTY sessions is controlled by the `system.maxConcurrentExecutions` config setting (default 20).
+- **Environment injection**: Every PTY session automatically receives `AI_MANAGER_TASK_ID` and `CALLBACK_URL` environment variables. Additional env vars come from the active CLI Profile.
+- **Internal HTTP bridge**: Since MCP runs as a separate stdio process, it cannot access in-memory PTY sessions directly. Instead, it uses localhost-only HTTP endpoints to read terminal output and send input.
+
+## Architecture
+
+```
+Client (xterm.js) <-> WebSocket <-> ws-server.ts <-> PTY Session (node-pty)
+                                                         |
+                                                    session-store.ts
+```
+
+## File Reference
+
+### Core Library (`src/lib/pty/`)
+
+| File | Description |
+|------|-------------|
+| `pty-session.ts` | PTY session management (node-pty wrapper) |
+| `session-store.ts` | In-memory PTY session store, indexed by taskId |
+| `ws-server.ts` | WebSocket server, port configured via `terminal.wsPort` |
+
+### API Routes
+
+| Route | Method | Description |
+|-------|--------|-------------|
+| `/api/internal/terminal/[taskId]/start` | POST | Start a PTY session |
+| `/api/internal/terminal/[taskId]/buffer` | GET | Get terminal output buffer |
+| `/api/internal/terminal/[taskId]/input` | POST | Send input to terminal |
+
+### Server Actions (`src/actions/agent-actions.ts`)
+
+| Function | Description |
+|----------|-------------|
+| `startPtyExecution(taskId, prompt)` | Start Claude CLI PTY |
+| `resumePtyExecution(taskId, sessionId)` | Resume session |
+| `stopPtyExecution(taskId)` | Stop session |
+
+### Components
+
+- `src/components/task/task-terminal.tsx` -- xterm.js terminal UI
+
+### MCP Tools (`src/mcp/tools/terminal-tools.ts`)
+
+- `get_task_terminal_output` / `send_task_terminal_input` / `get_task_execution_status`
+
+## Constraints
+
+- Only one active session per taskId
+- Concurrency limit configured via `system.maxConcurrentExecutions` (default 20)
+- Disconnect keepalive: 2h while running / 5min after exit
+- All sessions automatically cleaned up on SIGTERM
+- `AI_MANAGER_TASK_ID` and `CALLBACK_URL` are injected into PTY environment variables
+- Do not modify `process.env`; use `envOverrides` instead

package/.next/standalone/tower/docs/en/modules/workspace.md

@@ -0,0 +1,61 @@
+---
+title: Workspace
+description: Top-level container for managing projects and labels
+---
+
+# Workspace Module
+
+**Slug:** `workspace`
+
+## Overview
+
+Workspaces are the top-level containers in Tower for organizing teams or project groups. Each workspace has its own label pool that is shared across all projects within it. You can rename workspaces, edit their descriptions, and delete them — deletion cascades to all projects and tasks inside.
+
+## Details
+
+- **Label pool**: Every workspace maintains a set of custom labels. These labels are available to all tasks across every project in that workspace. Built-in labels (global) are also accessible but cannot be deleted.
+- **Cascade delete**: Removing a workspace permanently deletes all of its projects, tasks, executions, and messages. This operation is irreversible.
+- **Project grouping**: Use workspaces to separate concerns — for example, one workspace per team, per client, or per product line.
+
+## Data Model
+
+```
+Workspace (id, name, description?)
+  ├── Project[]
+  └── Label[]
+```
+
+- `id`: cuid
+- `name`: required
+- `description`: optional
+- Cascade delete: Deleting a Workspace removes all its Projects and Labels
+
+## File Reference
+
+### Server Actions (`src/actions/workspace-actions.ts`)
+
+| Function | Description |
+|----------|-------------|
+| `getWorkspaces()` | List all workspaces |
+| `getWorkspaceById(id)` | Get by ID |
+| `createWorkspace({ name, description? })` | Create |
+| `updateWorkspace(id, data)` | Update |
+| `deleteWorkspace(id)` | Delete (cascade) |
+| `getWorkspacesWithProjects()` | With project list |
+| `getWorkspacesWithRecentTasks(limit?)` | With recent tasks |
+
+### Pages
+
+| Route | File | Description |
+|-------|------|-------------|
+| `/workspaces` | `src/app/workspaces/page.tsx` | Workspace list |
+| `/workspaces/[id]` | `src/app/workspaces/[workspaceId]/` | Workspace detail (board) |
+
+### MCP Tools (`src/mcp/tools/workspace-tools.ts`)
+
+- `list_workspaces` / `create_workspace` / `update_workspace` / `delete_workspace`
+
+## Constraints
+
+- Labels under a Workspace are split into builtin (global) and workspace-scoped
+- Builtin labels cannot be deleted

package/.next/standalone/tower/docs/git/README.md

@@ -0,0 +1,42 @@
+# Git 模块
+
+**Slug:** `git`
+
+## 概述
+
+Git 操作集成，包括仓库克隆、Worktree 隔离、Diff 解析、Merge 操作。
+
+## 文件清单
+
+### Server Actions (`src/actions/git-actions.ts`)
+
+Git 克隆、分支管理等操作。
+
+### API Routes
+
+| 路由 | 说明 |
+|------|------|
+| `/api/git/route.ts` | Git 操作 API |
+| `/api/tasks/[taskId]/diff/route.ts` | 获取任务 diff |
+| `/api/tasks/[taskId]/merge/route.ts` | 执行 merge |
+
+### 核心库
+
+| 文件 | 说明 |
+|------|------|
+| `lib/git-url.ts` | Git URL 解析和规范化 |
+| `lib/worktree.ts` | Git worktree 创建和管理 |
+| `lib/diff-parser.ts` | Git diff 解析器 |
+
+### 组件
+
+| 组件 | 说明 |
+|------|------|
+| `task-diff-view.tsx` | Diff 可视化 |
+| `task-merge-confirm-dialog.tsx` | Merge 确认对话框 |
+
+## Worktree 机制
+
+- 每个 Task 执行可在独立 worktree 中进行
+- `TaskExecution.worktreePath` / `worktreeBranch` 记录隔离信息
+- 创建任务时通过 `useWorktree` / `baseBranch` 参数控制

package/.next/standalone/tower/docs/guide/architecture.md

@@ -0,0 +1,29 @@
+---
+title: 架构概览
+description: Tower 系统的分层架构设计
+---
+
+## 分层架构
+
+Tower 采用分层架构设计，从上到下分为：
+
+- **UI 层** — Next.js App Router 页面和 React 组件，使用 shadcn 组件库和 TailwindCSS
+- **状态管理层** — Zustand store 管理客户端状态（看板、执行等）
+- **Server Actions 层** — Next.js Server Actions 处理业务逻辑和数据操作
+- **数据访问层** — Prisma ORM 操作 SQLite 数据库
+- **PTY 层** — node-pty 管理终端会话，WebSocket 实时传输 I/O
+- **MCP 层** — MCP Server 通过 stdio 向外部 AI Agent 暴露工具
+
+## 核心数据流
+
+```
+Workspace → Project → Task → TaskExecution
+                                    ↓
+                              PTY Session (Claude CLI)
+                                    ↓
+                              WebSocket → xterm.js
+```
+
+## 架构图
+
+详细架构图请参见 [架构图](./diagrams) 页面，包括系统架构、数据模型、任务生命周期、AI 架构和模块依赖关系图。

package/.next/standalone/tower/docs/guide/diagrams.md

@@ -0,0 +1,24 @@
+---
+title: 架构图
+description: Tower 系统架构、数据模型、任务生命周期等可视化图表
+---
+
+## 系统架构
+
+<iframe src="/tower/diagrams/tower-system-architecture.html" width="100%" height="600" style="border: 1px solid #333; border-radius: 8px;" />
+
+## 数据模型
+
+<iframe src="/tower/diagrams/tower-data-model.html" width="100%" height="600" style="border: 1px solid #333; border-radius: 8px;" />
+
+## 任务生命周期
+
+<iframe src="/tower/diagrams/tower-task-lifecycle.html" width="100%" height="600" style="border: 1px solid #333; border-radius: 8px;" />
+
+## AI 架构
+
+<iframe src="/tower/diagrams/tower-ai-architecture.html" width="100%" height="600" style="border: 1px solid #333; border-radius: 8px;" />
+
+## 模块依赖
+
+<iframe src="/tower/diagrams/tower-module-map.html" width="100%" height="600" style="border: 1px solid #333; border-radius: 8px;" />

package/.next/standalone/tower/docs/guide/getting-started.md

@@ -0,0 +1,80 @@
+---
+title: 快速开始
+description: 安装和运行 Tower 项目的步骤
+---
+
+## 前置条件
+
+- **Node.js** >= 22
+- **pnpm**（包管理器）
+
+## 安装步骤
+
+### 1. 克隆仓库
+
+```bash
+git clone <repo-url> tower
+cd tower
+```
+
+### 2. 安装依赖
+
+```bash
+pnpm install
+```
+
+### 3. 配置环境变量
+
+```bash
+cp .env.example .env
+```
+
+根据需要编辑 `.env` 文件，主要配置 `DATABASE_URL`（SQLite 数据库路径）。
+
+### 4. 初始化数据库
+
+```bash
+# 同步 Prisma schema 到数据库
+pnpm db:push
+
+# 导入种子数据
+pnpm db:seed
+
+# 创建全文搜索索引
+pnpm db:init-fts
+```
+
+### 5. 启动开发服务器
+
+```bash
+pnpm dev
+```
+
+打开浏览器访问 [http://localhost:3000](http://localhost:3000)。
+
+## MCP 集成
+
+如需将 Tower 的工具能力暴露给外部 AI Agent，在 MCP 客户端配置中添加：
+
+```json
+{
+  "mcpServers": {
+    "tower": {
+      "command": "npx",
+      "args": ["tsx", "<project-root>/src/mcp/index.ts"]
+    }
+  }
+}
+```
+
+将 `<project-root>` 替换为项目的绝对路径。
+
+## 常用命令
+
+| 命令 | 说明 |
+|------|------|
+| `pnpm dev` | 启动开发服务器（Webpack 模式，node-pty 需要） |
+| `pnpm db:push` | 同步 Prisma schema |
+| `pnpm db:seed` | 导入种子数据 |
+| `pnpm db:init-fts` | 创建全文搜索索引 |
+| `pnpm test:run` | 运行测试 |

package/.next/standalone/tower/docs/guide/introduction.md

@@ -0,0 +1,84 @@
+---
+title: 介绍
+description: Tower 是什么，核心概念与技术栈总览
+---
+
+## 什么是 Tower
+
+Tower 是一个面向个人开发者的 AI 任务调度平台，将看板管理、终端交互、代码编辑和 MCP 工具链整合在一起，提供统一的任务管理和 AI Agent 协作环境。
+
+## 为什么做 Tower
+
+AI 改变了开发者的工作方式。以前做项目，你一步步写代码，遇到问题改需求，同步更新代码，节奏是自己掌控的。
+
+现在不一样了。AI 接管了大部分编码工作，人的角色从「写代码」变成了「审代码」。项目数量也多了——同时推进几个项目成了常态。
+
+问题随之而来：
+
+- **频繁打断** — 随时可能插进来一个新任务或修改，打断你当前的思路。刚看完一个 PR，转头去处理另一个项目的 bug，回来已经忘了刚才看到哪了。
+- **上下文丢失** — 一会儿做这个一会儿做那个，某些改动、决策、踩过的坑，没有地方记录，等回过头来已经想不起来了。
+- **无法复盘** — 任务执行过程中产生的对话、代码变更、终端日志散落各处，后续想要回顾、总结、沉淀经验，无从下手。
+
+Tower 要解决的就是这件事：**给每个任务一个完整的记录空间**。
+
+任务的对话记录、终端日志、代码变更、文件资产、执行摘要——全部自动沉淀在一个地方。你可以随时切换任务而不怕丢失上下文，也可以在任务完成后借助 AI 做复盘分析（Dreaming），把遇到的问题和经验提炼成结构化的知识。
+
+后续还会接入个人知识库，让这些沉淀真正可查询、可复用。
+
+## 核心概念
+
+Tower 的数据模型采用三层层级结构：
+
+```
+Workspace → Project → Task
+```
+
+- **Workspace（工作区）**：顶层容器，管理项目和标签的命名空间
+- **Project（项目）**：属于某个 Workspace，承载任务和代码仓库，支持普通项目和 Git 项目
+- **Task（任务）**：核心工作单元，通过状态（TODO / IN_PROGRESS / IN_REVIEW / DONE / CANCELLED）在看板列间流转
+
+每个 Task 可以关联标签、执行记录和消息，支持 AI Agent 自动执行。
+
+## 技术栈
+
+| 技术 | 说明 |
+|------|------|
+| **Next.js 16** | App Router，全栈框架 |
+| **TypeScript** | 类型安全 |
+| **SQLite + Prisma** | 轻量数据库 + ORM |
+| **TailwindCSS 4** | 原子化 CSS |
+| **shadcn (base-nova)** | UI 组件库 |
+| **xterm.js + node-pty** | 终端模拟 |
+| **Monaco Editor** | 代码编辑器 |
+| **MCP Protocol** | AI 工具协议 |
+
+## 功能总览
+
+- **看板管理** — 拖拽排序、标签筛选、优先级管理
+- **AI 终端** — 每个任务独立的 Claude CLI 终端会话
+- **代码编辑** — Monaco Editor 多标签编辑、Git Diff 视图
+- **MCP 工具链** — 24+ 工具供外部 AI Agent 调用
+- **多任务监控** — Missions 面板实时监控多个执行
+- **全局搜索** — 任务、项目、仓库全文搜索
+- **国际化** — 中英文双语支持
+
+## 模块文档
+
+Tower 由以下 14 个模块组成：
+
+| 模块 | 说明 |
+|------|------|
+| [Workspace](../modules/workspace) | 工作区管理 |
+| [Project](../modules/project) | 项目管理 |
+| [Task](../modules/task) | 任务管理 |
+| [Board](../modules/board) | 看板 UI |
+| [Terminal](../modules/terminal) | PTY 终端系统 |
+| [Assistant](../modules/assistant) | AI 助手聊天 |
+| [Missions](../modules/missions) | 多任务监控 |
+| [Search](../modules/search) | 全局搜索 |
+| [Settings](../modules/settings) | 系统配置 |
+| [MCP](../modules/mcp) | MCP Server |
+| [Git](../modules/git) | Git 集成 |
+| [Assets & Notes](../modules/assets-notes) | 资产和笔记 |
+| [AI](../modules/ai) | AI 能力层 |
+| [I18n](../modules/i18n) | 国际化 |

package/.next/standalone/tower/docs/i18n/README.md

@@ -0,0 +1,23 @@
+# I18n 模块
+
+**Slug:** `i18n`
+
+## 概述
+
+国际化系统，支持中文和英文双语。所有用户可见文本使用 `t("key")` 函数。
+
+## 文件清单
+
+### 核心库 (`src/lib/i18n/`)
+
+i18n 配置和资源管理。
+
+### 使用
+
+- `src/lib/i18n.tsx` — i18n Provider 和 hook
+
+## 规范
+
+- 所有用户可见文本必须用 `t("key")` 包裹
+- 同时维护 zh/en 两套翻译
+- Key 命名格式：`模块.功能.描述`

package/.next/standalone/tower/docs/index.md

@@ -0,0 +1,36 @@
+---
+layout: home
+hero:
+  name: Tower
+  text: AI 任务调度平台
+  tagline: 看板 + 终端 + 代码编辑器 + MCP 工具链
+  image:
+    src: /logo.png
+    alt: Tower Logo
+  actions:
+    - theme: brand
+      text: 快速开始
+      link: /guide/getting-started
+    - theme: alt
+      text: 模块文档
+      link: /modules/workspace
+features:
+  - icon: 📋
+    title: 看板管理
+    details: 拖拽任务卡片，支持置顶、标签、优先级筛选，右键快捷操作
+  - icon: 🤖
+    title: AI 终端
+    details: xterm.js + Claude CLI，实时交互执行任务，自动生成总结与洞察
+  - icon: 🔧
+    title: MCP 工具链
+    details: 24 个 MCP 工具，7 大类别，支持外部 AI Agent 无缝调用
+  - icon: ✏️
+    title: 代码编辑器
+    details: Monaco Editor，多标签编辑，语法高亮，Ctrl+S 保存
+  - icon: 📡
+    title: Mission Control
+    details: 多任务并行监控面板，网格布局，实时终端输出
+  - icon: 🔍
+    title: 全局搜索
+    details: FTS5 全文搜索，覆盖任务、项目、笔记、资产
+---

package/.next/standalone/tower/docs/mcp/README.md

@@ -0,0 +1,50 @@
+# MCP 模块
+
+**Slug:** `mcp`
+
+## 概述
+
+Model Context Protocol Server，向外部 AI Agent 暴露 Tower 的工具能力。通过 stdio 传输协议运行。
+
+## 启动方式
+
+```json
+{
+  "mcpServers": {
+    "tower": {
+      "command": "npx",
+      "args": ["tsx", "<project-root>/src/mcp/index.ts"]
+    }
+  }
+}
+```
+
+## 文件清单
+
+### 核心 (`src/mcp/`)
+
+| 文件 | 说明 |
+|------|------|
+| `server.ts` | MCP Server 初始化和配置 |
+| `db.ts` | MCP 专用数据库连接 |
+| `index.ts` | 入口和导出 |
+
+### 工具模块 (`src/mcp/tools/`)
+
+| 文件 | 工具数 | 说明 |
+|------|--------|------|
+| `workspace-tools.ts` | 4 | Workspace CRUD |
+| `project-tools.ts` | 5 | Project CRUD + identify |
+| `task-tools.ts` | 5 | Task CRUD + move |
+| `label-tools.ts` | 4 | Label CRUD + set_task_labels |
+| `terminal-tools.ts` | 3 | 终端输出/输入/状态 |
+| `search-tools.ts` | 1 | 全局搜索 |
+| `report-tools.ts` | 2 | daily_summary / daily_todo |
+| `note-asset-tools.ts` | — | 笔记和资产管理 |
+
+## 内部 HTTP 桥接
+
+MCP stdio 进程无法访问内存中的 PTY 会话，通过内部 HTTP 路由桥接：
+- `GET /api/internal/terminal/[taskId]/buffer`
+- `POST /api/internal/terminal/[taskId]/input`
+- localhost 限定

package/.next/standalone/tower/docs/missions/README.md

@@ -0,0 +1,40 @@
+# Missions 模块
+
+**Slug:** `missions`
+
+## 概述
+
+多任务监控面板，跨工作区展示所有运行中的 Task 执行，嵌入 xterm.js 终端实时查看。
+
+## 功能
+
+- 网格布局预设（1×1, 2×1, 3×2, 2×2, 4×2, 3×3），持久化到 localStorage
+- Workspace 过滤下拉框
+- 启动新执行 / 恢复历史会话（Task Picker）
+- 停止执行（卡片移除）/ 自然完成自动移除
+- 拖拽排序（dnd-kit）
+- 4 秒轮询实时更新
+
+## 文件清单
+
+### 页面
+
+| 路由 | 文件 | 说明 |
+|------|------|------|
+| `/missions` | `missions-client.tsx` | Missions 主页面 |
+
+### 组件 (`src/components/missions/`)
+
+| 组件 | 说明 |
+|------|------|
+| `mission-card.tsx` | 任务执行卡片（含终端） |
+| `grid-preset-picker.tsx` | 网格布局选择器 |
+| `task-picker-dialog.tsx` | 任务选择对话框 |
+
+### Server Actions
+
+- `getActiveExecutionsAcrossWorkspaces()` — 获取所有 RUNNING 执行
+
+### 状态管理 (`src/stores/task-execution-store.ts`)
+
+Zustand store，管理活跃执行状态。