@clickzetta/cz-cli-darwin-arm64 0.5.16 → 0.5.17

package/bin/skills/lakehouse-doc-en/references/cz-cli-sql.md

@@ -6,21 +6,16 @@ This page covers cz-cli commands for SQL execution, schema and table management,
 
 ### Basic Usage
 
-```bash
-```
-
 Synchronous execution, returns results directly (default):
 
 ```bash
 cz-cli -p prod sql "SELECT current_timestamp()"
-
 ```
 
 Pass SQL with -e:
 
 ```bash
 cz-cli -p prod sql -e "SELECT * FROM public.orders LIMIT 10"
-
 ```
 
 Read SQL from a file:
@@ -33,21 +28,17 @@ cz-cli -p prod sql -f query.sql
 
 `cz-cli sql` executes synchronously by default (`--sync`), waiting for results before exiting. For long-running queries, you can submit asynchronously, get the job\_id, and then retrieve results:
 
-```bash
-```
 
 Submit asynchronously, returns job\_id immediately:
 
 ```bash
 cz-cli -p prod sql "SELECT * FROM huge_table" --async
-
 ```
 
 Check job status:
 
 ```bash
 cz-cli -p prod sql status <job_id>
-
 ```
 
 Or use the job command:
@@ -110,28 +101,23 @@ cz-cli -p prod sql --dry-run -f deploy.sql
 
 ### Output Control
 
-```bash
-```
 
 Do not truncate long fields:
 
 ```bash
 cz-cli -p prod sql "SELECT * FROM public.orders" --no-truncate
-
 ```
 
 Remove row limit (default 100 rows):
 
 ```bash
 cz-cli -p prod sql "SELECT * FROM public.orders" --no-limit
-
 ```
 
 Do not output column names:
 
 ```bash
 cz-cli -p prod sql "SELECT id, name FROM public.orders" --no-header
-
 ```
 
 Specify output format:
@@ -144,7 +130,7 @@ cz-cli -p prod sql "SELECT * FROM public.orders LIMIT 5" -o csv
 ### Full Parameter Reference
 
 | Parameter | Description | Default |
-|-----------|-------------|---------|
+| --------- | ----------- | ------- |
 | `--sync` / `--no-sync` | Wait synchronously for results | `true` |
 | `--async` | Submit asynchronously, returns job\_id immediately | `false` |
 | `--write` | Allow write operations (DDL/DML) | Off |
@@ -166,28 +152,22 @@ cz-cli -p prod sql "SELECT * FROM public.orders LIMIT 5" -o csv
 
 ## cz-cli schema — Schema Management
 
-```bash
-```
-
 List all schemas:
 
 ```bash
 cz-cli -p prod schema list
-
 ```
 
 View schema details (including table list):
 
 ```bash
 cz-cli -p prod schema describe public
-
 ```
 
 Create a schema:
 
 ```bash
 cz-cli -p prod schema create dwd
-
 ```
 
 Drop a schema (requires confirmation):
@@ -200,56 +180,47 @@ cz-cli -p prod schema drop old_schema
 
 ## cz-cli table — Table Management and Data Exploration
 
-```bash
-```
 
 List all tables in the current schema:
 
 ```bash
 cz-cli -p prod table list
-
 ```
 
 List tables in a specific schema:
 
 ```bash
 cz-cli -p prod -s dwd table list
-
 ```
 
 View table structure (column names, types, comments):
 
 ```bash
 cz-cli -p prod table describe public.orders
-
 ```
 
 Preview table data (default 10 rows):
 
 ```bash
 cz-cli -p prod table preview public.orders
-
 ```
 
 View table row count and recent job statistics:
 
 ```bash
 cz-cli -p prod table stats public.orders
-
 ```
 
 View table version history (Time Travel support):
 
 ```bash
 cz-cli -p prod table history public.orders
-
 ```
 
 Create a table from DDL:
 
 ```bash
 cz-cli -p prod table create --write "CREATE TABLE public.test (id INT, name STRING)"
-
 ```
 
 Drop a table (requires confirmation):
@@ -264,21 +235,17 @@ cz-cli -p prod table drop public.test
 
 Asynchronously submitted queries return a job\_id; use the `job` command to track them:
 
-```bash
-```
 
 View job status and execution summary:
 
 ```bash
 cz-cli -p prod job status <job_id>
-
 ```
 
 Get job query results (waits if still running):
 
 ```bash
 cz-cli -p prod job result <job_id>
-
 ```
 
 View job execution profile (analyze performance bottlenecks):
@@ -291,28 +258,23 @@ cz-cli -p prod sql --job-profile <job_id>
 
 ## cz-cli workspace — Workspace Switching
 
-```bash
-```
 
 View current workspace:
 
 ```bash
 cz-cli -p prod workspace current
-
 ```
 
 List all available workspaces:
 
 ```bash
 cz-cli -p prod workspace list
-
 ```
 
 Temporarily switch workspace (current command only):
 
 ```bash
 cz-cli -p prod workspace use analytics
-
 ```
 
 Persistent switch (saved to profile):
@@ -335,8 +297,6 @@ cz-cli -p prod table stats public.orders
 
 **Scenario 2: Debugging a slow query**
 
-```bash
-```
 
 Submit asynchronously first:
 
@@ -353,14 +313,11 @@ cz-cli -p prod sql --job-profile <job_id>
 
 **Scenario 3: Executing DDL in CI/CD**
 
-```bash
-```
 
 Validate syntax with dry-run first:
 
 ```bash
 cz-cli -p prod sql --dry-run -f migrations/v2.sql
-
 ```
 
 Execute after confirming no issues:
@@ -389,7 +346,7 @@ cz-cli -p prod sql \
 **Lakehouse Related Documentation**
 
 * [Workspace](workspace-introduction.md) — Workspace concepts, user management, permission system
-* [Compute Cluster](virtual-cluster.md) — VCluster type selection, specification configuration
+* [Virtual Cluster](virtual-cluster.md) — Virtual Cluster type selection, specification configuration
 * [Schema](schema.md) — Schema creation and management
 * [Time Travel](timetravel-summary.md) — Historical version queries (the underlying mechanism of the `table history` command)
 

package/bin/skills/lakehouse-doc-en/references/cz-cli.md

@@ -1,36 +1,38 @@
-# Singdata CLI (cz-cli)
+# ClickZetta CLI (cz-cli)
 
-cz-cli is the command-line tool for Singdata Lakehouse. For human users, it lets data developers query tables, run SQL, manage tasks, and view run logs from the terminal — no browser required. For AI Agents, it provides a high-level operation interface tailored to data warehouse scenarios, letting agents complete full operations with minimal context overhead.
+cz-cli is the command-line operations tool for Singdata Lakehouse. For human users, it lets data developers query tables, run SQL, manage tasks, and view run logs from the terminal—no browser required. For AI Agents, it provides a high-level operation interface tailored to data warehouse scenarios, letting agents complete full operations with minimal context overhead.
+
+![](.topwrite/assets/anim-14-cz-cli.svg)
 
 ## Why cz-cli?
 
-Lakehouse already offers Studio Web UI, MCP Server, JDBC, REST API, and other access methods — but each has fundamental limitations for AI Agents. cz-cli provides differentiated value for two core scenarios:
+Lakehouse already offers Studio Web UI, MCP Server, JDBC, REST API, and other access methods—but each has fundamental limitations for AI Agents. cz-cli provides differentiated value for two core scenarios:
 
 ### Scenario 1: Agent Calls Commands Directly (Tool-Call Mode)
 
-The agent uses `cz-cli` commands to perform data warehouse operations — one command per complete business action.
+The agent uses `cz-cli` commands to perform data warehouse operations—one command per complete business action.
 
 **Limitations of other interfaces:**
 
-| Interface | Core limitation |
+| Interface | Core Limitation |
 |------|---------|
 | **JDBC / SQL** | Agent must inject the full schema before writing SQL; large warehouse schemas can cost tens of thousands of tokens. Without schema context, hallucinations are severe (fabricated table and column names). Studio task status, run logs, and other operational actions have no SQL interface at all. |
-| **REST API** | No unified interface discovery mechanism — agents cannot automatically know which endpoints exist. Even with an OpenAPI spec, the full spec is a context bomb. A single business action requires chaining 3–5 API calls; any intermediate failure silently breaks the flow. |
-| **MCP Server** | Each tool description costs ~300–600 tokens; 3 MCP servers can consume 70%+ of the context window. As tool count grows, agent selection accuracy drops significantly — quality degrades noticeably beyond 50 tools. |
+| **REST API** | No unified interface discovery mechanism—agents cannot automatically know which endpoints exist. Even with an OpenAPI spec, the full spec is a context bomb. A single business action requires chaining 3-5 API calls; any intermediate failure silently breaks the flow. |
+| **MCP Server** | Each tool description costs ~300-600 tokens; 3 MCP servers can consume 70%+ of the context window. As tool count grows, agent selection accuracy drops significantly—quality degrades noticeably beyond 50 tools. |
 | **Studio Web UI** | Requires simulating browser interactions; many steps, unstable state, high agent operation cost, low accuracy. |
 
 **cz-cli advantages:**
 
 - **Self-describing and discoverable**: `cz-cli --help` and `cz-cli <subcommand> --help` are self-describing. Agents query on demand without preloading any documentation. `cz-cli ai-guide` generates a more compact task-oriented command reference.
-- **Business-semantic encapsulation**: Each command maps to one complete business action — agents get it done in one step, no multi-step composition, no pagination, authentication, or error code handling.
-- **Covers capabilities beyond SQL**: Studio task management, run inspection, backfill, data source browsing — all unreachable via JDBC.
+- **Business-semantic encapsulation**: Each command maps to one complete business action—agents get it done in one step, no multi-step composition, no pagination, authentication, or error code handling.
+- **Covers capabilities beyond SQL**: Studio task management, run inspection, backfill, data source browsing—all unreachable via JDBC.
 - **Built-in guardrails**: Write operations require `--write`; high-risk operations require `-y` confirmation, reducing agent error risk.
-- **Structured output**: JSON by default — agents parse directly without processing natural language or HTML.
+- **Structured output**: JSON by default—agents parse directly without processing natural language or HTML.
 - **Headless-friendly**: A plain process, no persistent connection needed. Works directly in CI/CD pipelines, scheduled scripts, and enterprise bots.
 
 ### Scenario 2: As a Specialized Sub-Agent (cz-cli agent Mode)
 
-When a primary agent (Claude Code, Cursor, Kiro, etc.) loads too many skills, two problems emerge: **context pollution** — information accumulated from a previous task interferes with reasoning on the next — and **attention dilution** — the more tools available, the higher the probability of choosing the wrong one.
+When a primary agent (Claude Code, Cursor, Kiro, etc.) loads too many skills, two problems emerge: **context pollution**—information accumulated from a previous task interferes with reasoning on the next—and **attention dilution**—the more tools available, the higher the probability of choosing the wrong one.
 
 The solution is Anthropic's recommended **orchestrator-subagent pattern**: the primary agent handles planning and coordination, delegating specialized domain problems wholesale to a specialized sub-agent, which completes the work in an isolated, clean context and returns results to the primary agent.
 
@@ -44,50 +46,45 @@ Primary Agent (Claude Code)
             └─ returns structured results to primary agent
 ```
 
-Anthropic's Research feature uses the same architecture — benchmarks show a 90.2% improvement over single-agent approaches with 90% less research time. Data warehouse operations (checking task status, reading logs, backfilling, diagnosing SQL) are a natural fit for this delegation pattern — tasks are independent, boundaries are clear, and results are verifiable.
+Anthropic's Research feature uses the same architecture—benchmarks show a 90.2% improvement over single-agent approaches with 90% less research time. Data warehouse operations (checking task status, reading logs, backfilling, diagnosing SQL) are a natural fit for this delegation pattern—tasks are independent, boundaries are clear, and results are verifiable.
 
 ## Command Overview
 
-| Command | Description |
-|------|------|
-| `cz-cli profile` | Manage connection profiles (create, switch, update) |
-| `cz-cli status` | Verify the current connection is working |
-| `cz-cli sql` | Execute SQL queries and DDL/DML |
-| `cz-cli schema` | View and manage schemas |
-| `cz-cli table` | View table structure, preview data, count rows |
-| `cz-cli workspace` | View and switch workspaces |
-| `cz-cli task` | Create, configure, deploy, and execute Studio tasks |
-| `cz-cli runs` | View task run records, logs, backfill, rerun |
-| `cz-cli attempts` | View retry records and logs for a single run |
-| `cz-cli job` | SQL job performance diagnostics |
-| `cz-cli datasource` | Manage external data sources, browse source objects |
-| `cz-cli agent` | *(Agent)* Start an AI agent session, configure LLM, operate Lakehouse with natural language |
-| `cz-cli ai-guide` | *(Agent)* Generate a compact command reference for agents to load |
+| Command | Object | Description |
+|------|----------|------|
+| `cz-cli profile` | Local connection configuration | Create, switch, update Lakehouse connections |
+| `cz-cli status` | Current connection | Verify connection is working |
+| `cz-cli sql` | Lakehouse SQL engine | Execute SQL queries, DDL/DML |
+| `cz-cli schema` | Schemas under Workspace | View and manage Schemas |
+| `cz-cli table` | Lakehouse tables | View table structure, preview data, count rows |
+| `cz-cli workspace` | Workspaces under instance | View and switch workspaces |
+| `cz-cli task` | Studio tasks | Create, configure, deploy, execute Studio tasks |
+| `cz-cli runs` | Studio task run records | View run logs, backfill, rerun |
+| `cz-cli attempts` | Retry records for a single run | View retry details and logs |
+| `cz-cli job` | SQL Jobs | SQL Job performance diagnostics |
+| `cz-cli datasource` | Studio external data sources | Browse schemas/tables in data sources, test connectivity |
+| `cz-cli agent` | *(Agent only)* Local AI Agent | Start AI Agent session, operate Lakehouse in natural language |
+| `cz-cli ai-guide` | *(Agent only)* Command documentation | Generate compact command reference for agents to load |
 
 ## Quick Start
 
-```bash
-```
-
 Install:
 
 ```bash
 npm install -g @clickzetta/cz-cli
-
 ```
 
 Configure connection:
 
 ```bash
-cz-cli setup --credential <CLI connection string>
-
+cz-cli setup
 ```
+Follow the prompts to create a new Singdata Lakehouse account connection or enter the credentials for an existing account.
 
 Verify connection:
 
 ```bash
 cz-cli status
-
 ```
 
 Run a query:
@@ -100,31 +97,45 @@ For detailed installation and configuration steps, see the [Installation and Con
 
 ## Use Cases
 
-| Scenario | Recommended approach |
+| Scenario | Recommended Approach |
 |------|---------|
 | Daily data queries, viewing table structure, sample data | `cz-cli sql` / `cz-cli table` |
 | Managing and debugging Studio tasks, viewing run logs | `cz-cli task` / `cz-cli runs` |
 | Automated DDL or task execution in CI/CD pipelines | cz-cli commands + `--write` |
-| AI agent performing data warehouse operations | cz-cli tool-call mode |
-| AI agent handling complex warehouse operations | `cz-cli agent run` sub-agent mode |
+| AI Agent performing data warehouse operations | cz-cli tool-call mode |
+| AI Agent handling complex warehouse operations | `cz-cli agent run` sub-agent mode |
 | Visual configuration of data sync or complex task orchestration | Studio Web UI |
 
-## Related Documentation
+## LLM Source
+
+The LLM model used by `cz-cli agent` is provided uniformly by **[AI Gateway](AIGateway.md)**. New users are recommended to complete configuration in one step via the CLI connection string (Singdata built-in LLM, no separate API Key required). External LLMs can also be integrated via `cz-cli agent llm add`—in this case, enter the AI Gateway Endpoint as an OpenAI-compatible gateway:
+
+```bash
+cz-cli agent llm add my-gateway \
+  --provider openai-compatible \
+  --base-url https://<your-instance>.singdata.com/gateway/v1 \
+  --api-key <AI-Gateway-API-Key> \
+  --use
+```
+
+See [AI Agent Integration → Configure LLM](cz-cli-agent.md) for details.
+
+## Related Documents
 
 **cz-cli Documentation**
 
-- [Installation and Configuration Guide](setup_cz_cli.md) — Installation, profile configuration, output formats, upgrades, FAQ
+- [Installation and Configuration Guide](setup_cz_cli.md) — Installation, Profile configuration, output formats, upgrades, FAQ
 - [SQL Execution and Data Exploration](cz-cli-sql.md) — Full reference for sql, schema, table, job, workspace commands
 - [Studio Task Development and Operations](cz-cli-studio-tasks.md) — Task creation, scheduling, runs operations, backfill, task flow
 - [Studio External Data Source Management](cz-cli-datasource.md) — Data source browsing, connectivity testing, sample data preview
 - [AI Agent Integration](cz-cli-agent.md) — Agent LLM configuration, natural language operations, enterprise bot scenarios
 
-**Lakehouse Documentation**
+**Lakehouse Related Documents**
 
 - [Studio Guide](studio_manual.md) — Complete Studio Web UI operations guide
 - [Workspace](workspace-introduction.md) — Workspace concepts, user management, permission model
-- [Compute Cluster](virtual-cluster.md) — VCluster types, specs, start/stop management
-- [Task Development and Scheduling](task-develop.md) — Studio SQL task development and scheduling configuration
+- [Virtual Cluster](virtual-cluster.md) — Virtual Cluster types, specs, start/stop management
+- [Task Development and Scheduling](task-develop.md) — Studio SQL task development, scheduling configuration
 - [Real-time Sync Tasks](realtime_sync.md) — CDC real-time sync configuration and management
 - [Batch Sync Tasks](batch_sync.md) — Batch offline sync configuration and management
 - [Data Source Management](config-datasource.md) — External data source connection configuration

package/bin/skills/lakehouse-doc-en/references/dashboard-version-management-guide.md

@@ -20,13 +20,13 @@ Now, the system automatically saves a version each time AI modifies a dashboard
 
 Click the **Version History** button in the upper right corner of the dashboard page
 
-![](/.topwrite/assets/image_1779185094088.png =555)
+:-: ![](/.topwrite/assets/image_1780902105757.png =527)
 
 ### 2. View Historical Versions
 
 Each version card in the version panel contains:
 
-![](/.topwrite/assets/image_1779185134029.png =311)
+:-: ![](/.topwrite/assets/image_1780902136018.png =366)
 
 * Version number (V1, V2, V3...)
 
@@ -44,7 +44,7 @@ Click on a version card to view a snapshot of the dashboard at that version (rea
 
 Hover over a version card and click the **Restore** button:
 
-![](/.topwrite/assets/image_1779185185822.png)
+:-: ![](/.topwrite/assets/image_1780902285772.png =558)
 
 * The system will show a confirmation prompt: "The rollback operation will create a new version based on this version"
 
@@ -80,7 +80,7 @@ Hover over a version card and click the **Restore** button:
 
 ### Private to Shared Transition
 
-![](/.topwrite/assets/image_1779185254845.png =393)
+:-: ![](/.topwrite/assets/image_1780902352447.png =704)
 
 * Versions before the sharing time point are visible only to the creator
 
@@ -107,3 +107,11 @@ Hover over a version card and click the **Restore** button:
 2\. Restoring does not delete intermediate versions; instead, it creates a new version based on the target version
 
 3\. The version retention limit is 100; it is recommended to periodically confirm the status of important versions
+
+## Related Documentation
+
+* [Chart Auto-Refresh Settings](chart-auto-refresh-guide.md) — Set automatic data updates for dashboard charts
+* [Table Rendering](table_rendering.md) — Generate complex table layouts through natural language
+* [Conversational Data Analytics (Analytics Agent)](datagpt_introduction.md) — Return to feature overview
+
+^

package/bin/skills/lakehouse-doc-en/references/data-integration-intro.md

@@ -12,7 +12,7 @@ A data synchronization task is a type of task used to collect data from a data s
 
 Lakehouse Studio currently supports two main types of synchronization tasks: offline periodic synchronization and real-time synchronization. In the "Development -> Tasks" section, use the new button to select the appropriate task type as needed.
 
-![](.topwrite/assets/image_1740136964041.png =600)
+:-: ![](.topwrite/assets/image_1740136964041.png =600)
 
 ^
 

package/bin/skills/lakehouse-doc-en/references/data-integration.md

@@ -4,13 +4,13 @@ Singdata Lakehouse Studio includes a full-featured data integration capability t
 
 ## Choosing a Sync Approach
 
-| My scenario | Recommended approach | Documentation |
-|-------------|----------------------|---------------|
-| MySQL / PG / Oracle or similar — single-table real-time CDC | Real-time sync task | [Real-time Sync Task](realtime_sync.md) |
-| Full-database migration, syncing multiple tables together | Multi-table real-time sync | [Multi-table Real-time Sync Complete Guide](multitable_realtime_sync_sop.md) |
-| Scheduled batch sync (T+1 or hourly) | Offline sync task | [Offline Sync Task](batch_sync.md) |
-| Full-database offline migration, multiple tables at once | Multi-table offline sync | [Multi-table Offline Sync Task](multitable_batch_sync.md) |
-| Not sure which to use | Check supported sources | [Data Source Support](data-sources.md) |
+| My scenario                                                 | Recommended approach       | Documentation                                                                |
+| ----------------------------------------------------------- | -------------------------- | ---------------------------------------------------------------------------- |
+| MySQL / PG / Oracle or similar — single-table real-time CDC | Real-time sync task        | [Real-time Sync Task](realtime_sync.md)                                      |
+| Full-database migration, syncing multiple tables together   | Multi-table real-time sync | [Multi-table Real-time Sync Complete Guide](multitable_realtime_sync_sop.md) |
+| Scheduled batch sync (T+1 or hourly)                        | Offline sync task          | [Offline Sync Task](batch_sync.md)                                           |
+| Full-database offline migration, multiple tables at once    | Multi-table offline sync   | [Multi-table Offline Sync Task](multitable_batch_sync.md)                    |
+| Not sure which to use                                       | Check supported sources    | [Data Source Support](data-sources.md)                                       |
 
 ## Quick Start
 
@@ -26,26 +26,28 @@ Singdata Lakehouse Studio includes a full-featured data integration capability t
 
 ## Scheduling, Deployment, and Operations
 
-| Scenario | Documentation |
-|----------|---------------|
-| Configure scheduled runs and task dependencies | [Task Scheduling](task_scheduling.md) · [Task Scheduling Dependencies](task_scheduling_dependency.md) |
-| Publish / unpublish a task | [Task and Instance Operations](task-instance-maintenance.md) |
-| View run history, logs, and failure details | [Task and Instance Operations](task-instance-maintenance.md) |
-| Configure alert notifications (DingTalk / Lark / email) | [Monitoring and Alerting](monitoring_and_alerting.md) |
-| Understand monitoring metric definitions | [Monitoring Metric Specifications](monitoring_item_specification.md) |
-| Backfill historical data | [Data Backfill Tasks](backfilling_data.md) |
+| Scenario                                                | Documentation                                                                                         |
+| ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| Configure scheduled runs and task dependencies          | [Task Scheduling](task_scheduling.md) · [Task Scheduling Dependencies](task_scheduling_dependency.md) |
+| Publish / unpublish a task                              | [Task and Instance Operations](task-instance-maintenance.md)                                          |
+| View run history, logs, and failure details             | [Task and Instance Operations](task-instance-maintenance.md)                                          |
+| Configure alert notifications (DingTalk / Lark / email) | [Monitoring and Alerting](monitoring_and_alerting.md)                                                 |
+| Understand monitoring metric definitions                | [Monitoring Metric Specifications](monitoring_item_specification.md)                                  |
+| Backfill historical data                                | [Data Backfill Tasks](backfilling_data.md)                                                            |
 
 ## Contents of This Section
 
-| Page | Description |
-|------|-------------|
-| [Overview](data-integration-intro.md) | Basic concepts, task types, and core components of data sync |
-| [Data Source Management](config-datasource.md) | Add and manage data source connections |
-| [Supported Data Sources](data-sources.md) | List of 40+ supported data sources |
-| [Data Source Configuration Guide](datasource-config-guide.md) | Detailed setup steps for each database type |
-| [Offline Sync Task](batch_sync.md) | Scheduled batch sync with full and incremental modes |
-| [Multi-table Offline Sync Task](multitable_batch_sync.md) | Full-database offline migration |
-| [Real-time Sync Task](realtime_sync.md) | Single-table real-time CDC sync |
-| [Multi-table Real-time Sync Task](multitable_realtime_sync.md) | Full-database real-time CDC sync |
-| [Multi-table Real-time Sync Complete Guide](multitable_realtime_sync_sop.md) | End-to-end SOP for full-database migration |
-| [Offline Sync FAQ](batch_sync_sop.md) | Common questions and usage guide |
+| Page                                                                         | Description                                                  |
+| ---------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| [Overview](data-integration-intro.md)                                        | Basic concepts, task types, and core components of data sync |
+| [Data Source Management](config-datasource.md)                               | Add and manage data source connections                       |
+| [Supported Data Sources](data-sources.md)                                    | List of 40+ supported data sources                           |
+| [Data Source Configuration Guide](datasource-config-guide.md)                | Detailed setup steps for each database type                  |
+| [Offline Sync Task](batch_sync.md)                                           | Scheduled batch sync with full and incremental modes         |
+| [Multi-table Offline Sync Task](multitable_batch_sync.md)                    | Full-database offline migration                              |
+| [Real-time Sync Task](realtime_sync.md)                                      | Single-table real-time CDC sync                              |
+| [Multi-table Real-time Sync Task](multitable_realtime_sync.md)               | Full-database real-time CDC sync                             |
+| [Multi-table Real-time Sync Complete Guide](multitable_realtime_sync_sop.md) | End-to-end SOP for full-database migration                   |
+| [Offline Sync FAQ](batch_sync_sop.md)                                        | Common questions and usage guide                             |
+
+^

package/bin/skills/lakehouse-doc-en/references/data-load-summary.md

@@ -15,8 +15,8 @@ There are various methods to load data into Lakehouse, depending on the data sou
 |                                                                                                                   | [Use Jdbc client](load-data-local.md) In versions after JDBC 2.0.0, the local COPY command has been deprecated. We recommend using the PUT method to upload data to the volume, and then use the server-side COPY command to import. | 1. Small data volume without a visual interface, suitable for technical users, especially those familiar with command line operations and need to batch process small data volumes. 2. Quickly process CSV files, suitable for scripting and automation operations.                                                          |
 | Batch Import Data from Object Storage                                                                             | [Use Volume to batch load data from object storage](load-data-oss.md)                                                                                                                                                                | 1. Suitable for data stored in object storage, needing to leverage SQL performance advantages to quickly read large amounts of data. 2. Efficiently handle large-scale datasets. 3. Supports direct SQL data conversion, simplifying the data import process. 4. Supports multiple file formats, including CSV, PARQUET, ORC |
 |                                                                                                                   | [Import using Copy command](load-data-oss.md)                                                                                                                                                                                        | 1. Has the advantages of Volume, with the difference being that the Copy command provides more fault tolerance parameters and data export support. It also supports exporting to object storage data.                                                                                                                        |
-| Use JavaSDK to read Kafka and write to Lakehouse in real-time                                                     | [Import data using Java SDK](use-java-sdk-realtime-uploaddata.md)                                                                                                                                                                   | 1. Suitable for business scenarios requiring real-time data stream processing, especially for developers familiar with Java. 2. Real-time data reading and writing ensure the immediate availability of data. 3. Suitable for custom data import, providing high flexibility.                                                |
-| Use custom SDK to read files and write to Lakehouse                                                               | [Import data using Java SDK](use-java-sdk-upload-data-local.md)                                                                                                                                                                       | 1. Suitable for one-time bulk data import with low data frequency (time interval greater than five minutes). 2. Supports custom data sources, providing flexibility in data import.                                                                                                                                          |
+| Use JavaSDK to read Kafka and write to Lakehouse in real-time                                                     | [Import data using Java SDK](use-java-sdk-realtime-uploaddata.md)                                                                                                                                                                    | 1. Suitable for business scenarios requiring real-time data stream processing, especially for developers familiar with Java. 2. Real-time data reading and writing ensure the immediate availability of data. 3. Suitable for custom data import, providing high flexibility.                                                |
+| Use custom SDK to read files and write to Lakehouse                                                               | [Import data using Java SDK](use-java-sdk-upload-data-local.md)                                                                                                                                                                      | 1. Suitable for one-time bulk data import with low data frequency (time interval greater than five minutes). 2. Supports custom data sources, providing flexibility in data import.                                                                                                                                          |
 |                                                                                                                   | [Import data using Python SDK](use-python-sdk-upload-data.md)                                                                                                                                                                        | 1. Suitable for developers familiar with Python who need custom data import, especially when the data is not in object storage or the integration does not support the data source.                                                                                                                                          |
 | Users needing fully managed services and visual operations, especially for synchronizing third-party data sources | Use Lakehouse Studio data integration                                                                                                                                                                                                | 1. Supports a wide range of data sources and various import methods. 2. Provides real-time synchronization, CDC mirroring synchronization, and offline periodic scheduling synchronization. 3. Visual monitoring improves data management transparency.                                                                      |
 
@@ -24,7 +24,7 @@ There are various methods to load data into Lakehouse, depending on the data sou
 
 | Import Method Name                        | Usage                                                                                                                               | Usage Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
 | ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| COPY Command                                   | [COPY INTO Command](copy-into-table.md)                                                                                                  | 1. Currently supported object storage locations are Tencent Cloud COS and Alibaba Cloud OSS. 2. Cross-cloud vendor import is not supported (will be supported later). For example, your Lakehouse is hosted on Alibaba Cloud but the object storage is on Tencent Cloud.                                                                                                                                                                                                 |
+| COPY Command                              | [COPY INTO Command](copy-into-table.md)                                                                                             | 1. Currently supported object storage locations are Tencent Cloud COS and Alibaba Cloud OSS. 2. Cross-cloud vendor import is not supported (will be supported later). For example, your Lakehouse is hosted on Alibaba Cloud but the object storage is on Tencent Cloud.                                                                                                                                                                                                 |
 | Volume                                    | [Use ISNERT INTO... SELECT FORM VOLUME to import](datalake_volume.md)                                                               | 1. Currently supported object storage locations are Tencent Cloud COS and Alibaba Cloud OSS. 2. Cross-cloud vendor import is not supported (will be supported later). For example, your Lakehouse is hosted on Alibaba Cloud but the object storage is on Tencent Cloud.                                                                                                                                                                                                 |
 | Data Integration                          | [Use Data Integration to import](data-integration-intro.md)                                                                         | 1. Supports a wide range of data sources, performance is slightly worse than COPY command and Volume.                                                                                                                                                                                                                                                                                                                                                                    |
 | SDK Realtime Data Stream (RealtimeStream) | [Upload data in real-time](java_reference/realtime-upload.md)                                                                       | 1. Data written in real-time can be queried in seconds. 2. When changing the table structure, you need to stop the real-time writing task first, then restart the task after a period of time (about 90 minutes) after the table structure change. 3. Table stream, materialized view, and dynamic table can only display committed data. Data written by real-time tasks needs to wait 1 minute to be confirmed, so table stream also needs to wait 1 minute to see it. |