feat(consul): add Consul full-stack workbench

docs/content/docs/databases.cn.mdx

@@ -34,7 +34,7 @@ Desktop 的文件路径属于本机。Docker/Web 的文件路径属于服务器
 - Qdrant、Milvus、Weaviate、ChromaDB
 - HBase
 - Pulsar、Kafka、RocketMQ、RabbitMQ
-- etcd、ZooKeeper、Nacos
+- etcd、ZooKeeper、Nacos、Consul KV
 - InfluxDB、IoTDB、TDengine 和其它时序/IoT profile
 
 这些连接使用键值、文档、搜索、向量、消息或配置中心工作区，不应套用关系型表格和 SQL 的全部概念。入口详见 [专用工作区](/cn/docs/specialized-workspaces)。

docs/content/docs/databases.mdx

@@ -34,7 +34,7 @@ Desktop file paths belong to the local computer. Docker/Web paths belong to the
 - Qdrant, Milvus, Weaviate, and ChromaDB
 - HBase
 - Pulsar, Kafka, RocketMQ, and RabbitMQ
-- etcd, ZooKeeper, and Nacos
+- etcd, ZooKeeper, Nacos, and Consul KV
 - InfluxDB, IoTDB, TDengine, and other time-series or IoT profiles
 
 These connections use key-value, document, search, vector, messaging, or configuration-center workspaces. They do not inherit every relational grid or SQL concept. See [Specialized Workspaces](/en/docs/specialized-workspaces).

docs/content/docs/specialized-workspaces.cn.mdx

@@ -1,9 +1,9 @@
 ---
 title: 专项工作台
-description: 使用 DBX 管理 Redis、MongoDB、搜索与向量数据库、HBase、消息队列、etcd、ZooKeeper 和 Nacos。
+description: 使用 DBX 管理 Redis、MongoDB、搜索与向量数据库、HBase、消息队列、etcd、ZooKeeper、Nacos 和 Consul KV。
 ---
 
-除了 SQL 编辑器和数据表格，DBX 还会根据连接类型打开专项工作台。它们直接使用对应系统的对象模型和管理 API，例如 Redis Key、MongoDB 文档、向量集合、消息队列 Topic、etcd Key、ZooKeeper ZNode 和 Nacos 配置。
+除了 SQL 编辑器和数据表格，DBX 还会根据连接类型打开专项工作台。它们直接使用对应系统的对象模型和管理 API，例如 Redis Key、MongoDB 文档、向量集合、消息队列 Topic、etcd Key、ZooKeeper ZNode、Nacos 配置和 Consul KV。
 
 <Callout type="info">专项能力按数据库类型、服务端版本、驱动和当前账号权限动态开放。界面没有显示某个入口时，先查看 [数据库支持](/cn/docs/databases)、连接测试结果和账号权限。</Callout>
 
@@ -16,7 +16,7 @@ description: 使用 DBX 管理 Redis、MongoDB、搜索与向量数据库、HBas
 | 向量数据库 | Qdrant、Milvus、Weaviate、ChromaDB | Collection 浏览、向量检索、Upsert、删除和请求预览 |
 | 宽表与列族 | HBase | Namespace、表结构、Column Family 和行数据浏览 |
 | 消息队列 | Pulsar、Kafka、RocketMQ、RabbitMQ | Topic、订阅/消费者、消息、监控、权限、策略和管理 API |
-| 注册与配置中心 | etcd、ZooKeeper、Nacos | Key/ZNode、集群状态、访问控制、配置、服务和实例 |
+| 注册与配置中心 | etcd、ZooKeeper、Nacos、Consul | Key/ZNode、集群状态、访问控制、配置、服务和实例 |
 | 运行状态 | MySQL、PostgreSQL、Redis、etcd、Nacos 等 | Dashboard、进程/会话、指标和数据库专属管理视图 |
 
 ## Redis 与 MongoDB
@@ -81,7 +81,7 @@ Pulsar、Kafka、RocketMQ 和 RabbitMQ 共用消息队列控制台框架，但
 
 <Callout type="info">消息队列面板根据 Agent 返回的 capability 动态显示。服务端版本、管理 API、账号权限或未配置的管理端口都可能让某些标签页不可用。</Callout>
 
-## etcd、ZooKeeper 与 Nacos
+## etcd、ZooKeeper、Nacos 与 Consul
 
 ### etcd
 
@@ -103,6 +103,20 @@ Nacos 工作台覆盖配置和服务两个主要视图，并可管理 Namespace
 
 Nacos 的配置历史可能依赖额外的控制台地址和凭据。连接成功但历史入口不可用时，检查连接表单中的控制台设置。
 
+### Consul
+
+Consul 工作台按需加载概览、KV、服务、健康检查、Session、ACL、作用域、Service Mesh、工具和 Operator 领域。能力探测会区分 supported、unsupported、forbidden 和 unknown，因此单个领域权限不足不会清空其他已经加载的数据。
+
+连接项支持 HTTP/HTTPS API 地址、ACL Token、Datacenter、Namespace、Admin Partition、读取一致性、CA 证书、mTLS 客户端身份、跳过证书校验、超时和 DBX Transport Layer。Agent Service/Check 写入还必须配置并验证明确的 Agent target；经过负载均衡而目标不明确时，DBX 会硬性拒绝写入。
+
+KV 已支持递归搜索、版本化前缀导出、不可变导入预览、CAS 冲突处理、事务、原子重命名/复制、受限事务前缀删除和可取消的 Blocking Query Watch。Consul 单事务最多 64 个操作；更大的导入和删除会按确定顺序分批，并明确标记跨批次不具备整体原子性。跨连接或跨 Datacenter 迁移是 DBX 客户端读写流程，不是 Consul 原生复制。
+
+Catalog 与 Health 保持只读浏览。Agent Service/Check、Session/Lock、ACL Token/Policy/Role、Enterprise Namespace/Partition 和 Service Mesh 使用各自领域 DTO 与确认流程。ACL Secret 和 Peering Token 作为一次性敏感值处理，不进入 Consul 前端缓存或普通导出格式。
+
+Prepared Query、Event 和 Coordinate 位于工具区。Operator 读取和 Snapshot 下载为实验性能力。Snapshot 恢复、Autopilot 修改、Raft 修改、Keyring 修改和 License 修改分别由默认关闭的独立开关控制，启用一个不会连带启用其他能力。
+
+<Callout type="warn">Consul 不提供单 Key 历史 API，也不提供原生跨 Datacenter KV 复制 API。`ModifyIndex`、Blocking Index 和 Snapshot 都不会被包装成 Key 历史。Enterprise 与 Operator 能力取决于 Consul 版本、Edition、Agent 角色、ACL 权限和显式启用的 DBX 安全设置。</Callout>
+
 ## Dashboard 与管理视图
 
 部分连接会在对象树或标签页中提供运行状态页面，例如：

docs/content/docs/specialized-workspaces.mdx

@@ -1,9 +1,9 @@
 ---
 title: Specialized Workspaces
-description: Manage Redis, MongoDB, search and vector databases, HBase, message queues, etcd, ZooKeeper, and Nacos in DBX.
+description: Manage Redis, MongoDB, search and vector databases, HBase, message queues, etcd, ZooKeeper, Nacos, and Consul KV in DBX.
 ---
 
-In addition to the SQL editor and data grid, DBX opens specialized workspaces for specific connection types. These interfaces use each system's native object model and management APIs, including Redis keys, MongoDB documents, vector collections, message queue topics, etcd keys, ZooKeeper ZNodes, and Nacos configurations.
+In addition to the SQL editor and data grid, DBX opens specialized workspaces for specific connection types. These interfaces use each system's native object model and management APIs, including Redis keys, MongoDB documents, vector collections, message queue topics, etcd keys, ZooKeeper ZNodes, Nacos configurations, and Consul KV entries.
 
 <Callout type="info">Specialized capabilities are enabled dynamically based on database type, server version, driver, and account privileges. If an entry point is missing, check [Database Support](/en/docs/databases), the connection test result, and server permissions.</Callout>
 
@@ -16,7 +16,7 @@ In addition to the SQL editor and data grid, DBX opens specialized workspaces fo
 | Vector databases | Qdrant, Milvus, Weaviate, ChromaDB | Collection browsing, vector search, upsert, delete, and request preview |
 | Wide-column and column family | HBase | Namespaces, table structure, column families, and row data |
 | Message queues | Pulsar, Kafka, RocketMQ, RabbitMQ | Topics, subscriptions or consumers, messages, monitoring, permissions, policies, and admin APIs |
-| Registry and configuration | etcd, ZooKeeper, Nacos | Keys/ZNodes, cluster status, access control, configuration, services, and instances |
+| Registry and configuration | etcd, ZooKeeper, Nacos, Consul | Keys/ZNodes, cluster status, access control, configuration, services, and instances |
 | Runtime status | MySQL, PostgreSQL, Redis, etcd, Nacos, and others | Dashboards, processes or sessions, metrics, and database-specific administration views |
 
 ## Redis and MongoDB
@@ -81,7 +81,7 @@ Pulsar emphasizes tenants, namespaces, and subscriptions; Kafka uses topics, con
 
 <Callout type="info">Message queue panels are capability-driven. Server versions, management APIs, account privileges, or a missing management port can make individual tabs unavailable.</Callout>
 
-## etcd, ZooKeeper, and Nacos
+## etcd, ZooKeeper, Nacos, and Consul
 
 ### etcd
 
@@ -103,6 +103,20 @@ The Nacos workspace covers configuration and services and can also manage namesp
 
 Configuration history can require an additional console URL and credentials. If the connection works but history is unavailable, check the console settings in the connection form.
 
+### Consul
+
+The Consul workspace is split into independently loaded Overview, KV, Services, Health, Sessions, ACL, Scope, Service Mesh, Tools, and Operator domains. Capability probes distinguish supported, unsupported, forbidden, and unknown endpoints, so a permission failure in one domain does not clear data loaded by another.
+
+Connections accept an HTTP or HTTPS API address, ACL Token, Datacenter, Namespace, Admin Partition, read consistency, CA certificate, mTLS identity, certificate-verification override, timeout, and DBX Transport Layer. Agent Service and Check writes additionally require a verified, explicit Agent target; DBX refuses those writes when a load balancer makes the target ambiguous.
+
+KV supports recursive search, versioned prefix export, immutable import preview, CAS conflict handling, transactions, atomic rename/copy, bounded transactional prefix deletion, and cancellable blocking-query Watch. Consul transactions are limited to 64 operations; larger imports and deletes are deterministically split and explicitly reported as non-atomic across batches. Cross-connection or cross-Datacenter migration is a DBX client read/write workflow, not native Consul replication.
+
+Catalog and Health remain read-only discovery views. Agent Service/Check, Session/Lock, ACL Token/Policy/Role, Enterprise Namespace/Partition, and Service Mesh resources use domain-specific DTOs and confirmations. ACL secrets and peering tokens are treated as one-time sensitive values and are not stored in the Consul frontend cache or normal export formats.
+
+Prepared Query, Event, and Coordinate are available under Tools. Operator reads and snapshot download are experimental. Snapshot restore, Autopilot updates, Raft changes, Keyring changes, and License updates are disabled by default with separate feature switches; enabling one does not enable another.
+
+<Callout type="warn">Consul has no per-Key history API and no native cross-Datacenter KV replication API. `ModifyIndex`, blocking indexes, and snapshots are not presented as Key history. Enterprise and Operator availability depends on Consul edition, version, Agent role, ACL policy, and explicitly enabled DBX safety settings.</Callout>
+
 ## Dashboards and Administration Views
 
 Some connections expose runtime status pages from the object tree or a tab, including: