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

package/bin/skills/lakehouse-doc-en/references/task_development.md

@@ -4,11 +4,11 @@ The task development module is a visual development page provided by Singdata La
 
 ## Development Concepts
 
-| **Concept** | **Definition** |
-| ------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| Task | Simple node: a single, concrete task type, such as SQL or Python. |
-| | Complex workflow node: a group of nodes composed of multiple individual nodes, such as a composite node. Parameters and scheduling configuration for complex workflow nodes are managed centrally. |
-| Task Group | A task group is a virtual management concept provided by Singdata Lakehouse. You can add tasks to a task group for centralized management, including visual drag-and-drop dependency orchestration, task group parameter configuration, batch scheduling setup, and batch submission. **Note**: If you need to manage a group of tasks using a DAG-style drag interface, or copy and refactor a batch of task pipelines, the task group feature is recommended. |
+| **Concept** | **Definition**                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Task        | Simple node: a single, concrete task type, such as SQL or Python.                                                                                                                                                                                                                                                                                                                                                                                               |
+|             | Complex workflow node: a group of nodes composed of multiple individual nodes, such as a composite node. Parameters and scheduling configuration for complex workflow nodes are managed centrally.                                                                                                                                                                                                                                                              |
+| Task Group  | A task group is a virtual management concept provided by Singdata Lakehouse. You can add tasks to a task group for centralized management, including visual drag-and-drop dependency orchestration, task group parameter configuration, batch scheduling setup, and batch submission. **Note**: If you need to manage a group of tasks using a DAG-style drag interface, or copy and refactor a batch of task pipelines, the task group feature is recommended. |
 
 ## Dependencies: Node-level Dependencies
 
@@ -20,13 +20,13 @@ Dependencies are attached to nodes. Whether a node is a simple node or a complex
 
 ## Scenario Overview
 
-- You can create various task nodes directly under "Tasks" and establish dependencies between nodes through the scheduling dependency settings in the scheduling configuration.
-- You can also create new nodes or add existing nodes under a "Task Group" to organize and orchestrate a batch of tasks, including configuring task group-level parameters and visually dragging to set dependencies between tasks.
+* You can create various task nodes directly under "Tasks" and establish dependencies between nodes through the scheduling dependency settings in the scheduling configuration.
+* You can also create new nodes or add existing nodes under a "Task Group" to organize and orchestrate a batch of tasks, including configuring task group-level parameters and visually dragging to set dependencies between tasks.
 
-| **Development approach** | **Target users** | **Scenario advantages** | **Limitations and differences** |
-| -------- | ---------------------- | ---------------------------------------- | --------------------------------------------------------------- |
-| Create tasks directly | Teams with relatively innovative business needs or those who prefer a fast, lightweight pace. | No need to build complex business relationships — just set up node dependencies and get the pipeline running quickly. Ideal for fast-moving scenarios. | Does not support batch operations, such as bulk modification of task scheduling times or compute clusters. |
-| Manage tasks within a task group | Mature, standardized data warehouse teams that organize work around business domains. | Manage a related batch of task nodes by business scenario, with support for visual drag-and-drop dependency configuration. | Real-time tasks are not currently supported in task groups. A task node can only belong to one task group. Task group parameters only take effect after the task group is submitted. |
+| **Development approach**         | **Target users**                                                                              | **Scenario advantages**                                                                                                                                | **Limitations and differences**                                                                                                                                                      |
+| -------------------------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Create tasks directly            | Teams with relatively innovative business needs or those who prefer a fast, lightweight pace. | No need to build complex business relationships — just set up node dependencies and get the pipeline running quickly. Ideal for fast-moving scenarios. | Does not support batch operations, such as bulk modification of task scheduling times or compute clusters.                                                                           |
+| Manage tasks within a task group | Mature, standardized data warehouse teams that organize work around business domains.         | Manage a related batch of task nodes by business scenario, with support for visual drag-and-drop dependency configuration.                             | Real-time tasks are not currently supported in task groups. A task node can only belong to one task group. Task group parameters only take effect after the task group is submitted. |
 
 ^
 
@@ -36,7 +36,7 @@ Dependencies are attached to nodes. Whether a node is a simple node or a complex
 
 A task group is a virtual management concept provided by Singdata Lakehouse. You can add tasks to a task group for centralized management, including visual drag-and-drop dependency orchestration, task group parameter configuration, batch scheduling setup, and batch submission.
 
-- **Note**: If you need to manage a group of tasks using a DAG-style drag interface, or copy and refactor a batch of task pipelines, the task group feature is recommended. For more details, see [Task Group](task_group.md).
+* **Note**: If you need to manage a group of tasks using a DAG-style drag interface, or copy and refactor a batch of task pipelines, the task group feature is recommended. For more details, see [Task Group](task_group.md).
 
 #### Task
 
@@ -44,11 +44,13 @@ Singdata Lakehouse provides several types of task nodes, including real-time mul
 
 #### Parameters
 
-- **Task group parameters**: Parameters created within a task group, used for global management of tasks inside that group.
-- **Scheduling parameters**: Parameters used during scheduled task execution.
-- **Temporary parameters**: Parameters used during ad-hoc task execution.
+* **Task group parameters**: Parameters created within a task group, used for global management of tasks inside that group.
+* **Scheduling parameters**: Parameters used during scheduled task execution.
+* **Temporary parameters**: Parameters used during ad-hoc task execution.
 
 #### Scheduling Configuration
 
-- Currently, only periodic scheduling is supported.
-- **Dependency method**: Interval dependency — the system determines whether upstream and downstream task instances overlap by comparing their start and end time ranges. For more on dependency relationships, see [Task Scheduling Dependencies](task_scheduling_dependency.md).
+* Currently, only periodic scheduling is supported.
+* **Dependency method**: Interval dependency — the system determines whether upstream and downstream task instances overlap by comparing their start and end time ranges. For more on dependency relationships, see [Task Scheduling Dependencies](task_scheduling_dependency.md).
+
+^

package/bin/skills/lakehouse-doc-en/references/task_group.md

@@ -24,7 +24,7 @@ This article covers how to create, edit, and submit task groups, as well as how
 
 When you need to batch-copy a group of tasks that have dependencies and recreate those dependencies in the new tasks, you can use the task group copy feature.
 
-![](.topwrite/assets/91c6efc6cd/3c6fcb545a6b507a072943955259ae593b4f1892.jpeg =700)
+^
 
 Add the tasks you want to copy (along with their dependencies) to Task Group 1. After copying Task Group 1, the resulting Task Group 2 will contain:
 
@@ -36,7 +36,7 @@ Add the tasks you want to copy (along with their dependencies) to Task Group 1.
 
 When you need to refactor a branch in the current task pipeline and batch-update custom variables across tasks, you can combine the downstream link copy feature with task groups.
 
-![](.topwrite/assets/91c6efc6cd/f8dfd42b7ace23593c3f7d3d79bff8eb46d2a1f9.jpeg =751)
+^
 
 On any node (whether it belongs to a task group or is standalone), clicking "Copy Downstream Link" will batch-copy that node and all its downstream nodes.
 
@@ -54,7 +54,7 @@ Before creating a task group, plan and design a business process that fits your
 
 3. Click OK.
 
-![](.topwrite/assets/image_1722251763584.png =434)
+^
 
 After creation:
 
@@ -65,7 +65,7 @@ After creation:
 
 You can design and manage task nodes and dependencies within a task group in either list mode or DAG mode.
 
-![](.topwrite/assets/image_1722251928404.png)
+^
 
 1. **Create/Add nodes**: Both modes support creating new task nodes or adding existing tasks to the task group.
 
@@ -92,7 +92,7 @@ After successfully creating or adding a node, enter the node's editing interface
 * Click the "Parameters" tab in the task group operation area to open the parameter configuration interface.
 * Click the New button and enter the parameter name and value in the dialog. For details on built-in parameter values, see [Task Parameters](task_param.md). For the full syntax, see [Task Parameter Syntax Reference](task_param_reference.md).
 
-  ![](.topwrite/assets/image_1722252018555.png =497)
+  ^
 
 After creating task group parameters, use them as follows:
 
@@ -102,7 +102,7 @@ After creating task group parameters, use them as follows:
 
 * In the "Value Source" dropdown, select the task group parameter.
 
-  ![](.topwrite/assets/image_1722252102342.png =472)
+  ^
 
 After creating and referencing a task group parameter:
 
@@ -116,12 +116,12 @@ You can use the batch edit scheduling time feature to update the scheduling time
 1. Click "Batch Edit Scheduling Time."
 
 * In DAG editing mode: Hover over the batch button and select "Edit Scheduling Time."
-  ![](.topwrite/assets/image_1736303777548.png =498)
+
 * In list mode: Select the target tasks you want to update, then click "Edit Scheduling Time."
 
 2. Batch edit the scheduling time.
    Select the scheduling time for the batch update. The operation is the same as the scheduling configuration in task scheduling. For details, see [Task Development and Scheduling](task-develop.md).
-   ![](.topwrite/assets/image_1736303843406.png =499)
+
 
 3. Confirm and submit the batch operation.
 
@@ -135,7 +135,7 @@ After editing and creating the task group, you need to submit it to the producti
 
 ## FAQ
 
-**Q1: Why can't I click the Submit button again after the task group has been submitted?**
+**Q1: Why can't I click the Submit button again after the task group has been submitted**?
 
 After a task group is submitted, if no changes have been made (i.e., the status has not changed to "Submitted with modifications"), it cannot be submitted again. To batch-submit task information within the task group, use one of these two approaches:
 
@@ -148,11 +148,13 @@ Task group status changes when:
 * Tasks are added to or removed from the task group.
 * Task group parameters are added, deleted, modified, or queried.
 
----
+***
 
 ## Related Documentation
 
-- [Task Parameters](task_param.md) — Task-level parameter concepts and configuration, and how they differ from task group parameters
-- [Task Parameter Syntax Reference](task_param_reference.md) — Full syntax for built-in parameters and time expressions
-- [Composite Task](composite_task.md) — How composite task parameters and task group parameters work together
-- [Task Development and Scheduling](task-develop.md) — Referencing task group parameters in individual tasks
+* [Task Parameters](task_param.md) — Task-level parameter concepts and configuration, and how they differ from task group parameters
+* [Task Parameter Syntax Reference](task_param_reference.md) — Full syntax for built-in parameters and time expressions
+* [Composite Task](composite_task.md) — How composite task parameters and task group parameters work together
+* [Task Development and Scheduling](task-develop.md) — Referencing task group parameters in individual tasks
+
+^

package/bin/skills/lakehouse-doc-en/references/task_instance.md

@@ -38,44 +38,44 @@ The system calculates the difference between the **actual time the instance ente
 
 ### Scenario 1: Run Timeout Duration
 
-|              |                         |
-| ------------ | ----------------------- |
-| Time         | Event                   |
-| 14:00        | T1 starts running       |
-| 14:10        | Run time reaches the 10-minute limit; T1 is set to Failed |
+|                                        |                                                                                  |
+| -------------------------------------- | -------------------------------------------------------------------------------- |
+| Time                                   | Event                                                                            |
+| 14:00                                  | T1 starts running                                                                |
+| 14:10                                  | Run time reaches the 10-minute limit; T1 is set to Failed                        |
 | Subsequent instances from 14:05 onward | All self-dependent subsequent instances are suspended because upstream T1 failed |
 
-![](/.topwrite/assets/image_1780067288681.png)
+^
 
 ### Scenario 2: Schedule Wait Duration
 
-|       |                                       |
-| ----- | ------------------------------------- |
-| Time  | Event                                 |
-| 14:00 | T1 starts running normally (not affected by this setting) |
-| 14:05 | T2 reaches its trigger time and enters the waiting-for-upstream (T1) state |
-| 14:15 | T2's wait time reaches the 10-minute limit; T2 is set to Failed. T1 can continue running normally |
+|       |                                                                                                                |
+| ----- | -------------------------------------------------------------------------------------------------------------- |
+| Time  | Event                                                                                                          |
+| 14:00 | T1 starts running normally (not affected by this setting)                                                      |
+| 14:05 | T2 reaches its trigger time and enters the waiting-for-upstream (T1) state                                     |
+| 14:15 | T2's wait time reaches the 10-minute limit; T2 is set to Failed. T1 can continue running normally              |
 | 14:10 | T3 reaches its trigger time and enters the waiting state; its downstream tasks are suspended because T2 failed |
-| 14:20 | T3's wait time reaches the 10-minute limit; T3 is set to Failed. T1 completes normally |
+| 14:20 | T3's wait time reaches the 10-minute limit; T3 is set to Failed. T1 completes normally                         |
 
 > The schedule wait duration triggers independently for each instance; T1's normal execution is not affected.
-> ![](/.topwrite/assets/image_1780067342320.png)
+>
 
 ### Scenario 3: Delayed Run Skip Duration
 
-|       |                                                    |
-| ----- | -------------------------------------------------- |
-| Time  | Event                                              |
-| 14:00 | T1 starts running normally                         |
-| 14:05 | T2 reaches its trigger time and waits for T1 to complete |
+|       |                                                                                            |
+| ----- | ------------------------------------------------------------------------------------------ |
+| Time  | Event                                                                                      |
+| 14:00 | T1 starts running normally                                                                 |
+| 14:05 | T2 reaches its trigger time and waits for T1 to complete                                   |
 | 14:20 | T1 completes; T2 enters the running state. Delay = 14:20 − 14:05 = 15 minutes > 10 minutes |
-| 14:20 | T2 is dry-run skipped and set to Succeeded, triggering T3's scheduling |
+| 14:20 | T2 is dry-run skipped and set to Succeeded, triggering T3's scheduling                     |
 
 > A dry-run skip does not execute any actual business logic; it only marks the instance as Succeeded to keep the scheduling chain moving.
 
 ***
 
-![](/.topwrite/assets/image_1780067317383.png)
+^
 
 ***
 

package/bin/skills/lakehouse-doc-en/references/task_param.md

@@ -6,9 +6,9 @@
 
 In day-to-day data development, you often encounter situations like these:
 
-- Processing the previous day's data: `WHERE dt = '2023-09-21'`
-- Aggregating last month's data: `WHERE month = '2023-08'`
-- Querying data for a specific city: `WHERE city = 'Shanghai'`
+* Processing the previous day's data: `WHERE dt = '2023-09-21'`
+* Aggregating last month's data: `WHERE month = '2023-08'`
+* Querying data for a specific city: `WHERE city = 'Shanghai'`
 
 If you hard-code dates, cities, and other values directly in your code, the task cannot adapt dynamically at runtime. **Task parameters** are designed to solve this — use `${parameter_name}` as a placeholder in your code, and the system automatically substitutes the actual value at runtime.
 
@@ -16,15 +16,15 @@ If you hard-code dates, cities, and other values directly in your code, the task
 
 ### Basic Concepts
 
-| Category | Concept | Meaning | Example |
-| ---- | ---- | ---- | ---- |
-| Parameter definition | Custom parameter | Referenced in code using `${parameter_name}` | `${yesterday}` |
-| Parameter value | Constant | A fixed string or number | `Shanghai`, `1234` |
-| Parameter value | System built-in parameter | System-provided dynamic values, such as the scheduled time | `sys_plan_datetime` |
-| Parameter value | Time expression | Format and offset calculations based on the scheduled time | `$[yyyy-MM-dd, -1d]` |
-| Parameter value | Built-in time function | Handles complex time calculations like first day of month, Monday, etc. | `first_day_of_month()` |
+| Category             | Concept                   | Meaning                                                                 | Example                |
+| -------------------- | ------------------------- | ----------------------------------------------------------------------- | ---------------------- |
+| Parameter definition | Custom parameter          | Referenced in code using `${parameter_name}`                            | `${yesterday}`         |
+| Parameter value      | Constant                  | A fixed string or number                                                | `Shanghai`, `1234`     |
+| Parameter value      | System built-in parameter | System-provided dynamic values, such as the scheduled time              | `sys_plan_datetime`    |
+| Parameter value      | Time expression           | Format and offset calculations based on the scheduled time              | `$[yyyy-MM-dd, -1d]`   |
+| Parameter value      | Built-in time function    | Handles complex time calculations like first day of month, Monday, etc. | `first_day_of_month()` |
 
----
+***
 
 ## Quick Start
 
@@ -38,8 +38,8 @@ SELECT * FROM sales_table WHERE city = '${city}' AND dt = '${yesterday}';
 
 Click the "Parameters" button. The system automatically detects the `city` and `yesterday` parameters. Assign values to them:
 
-- `city` = `Shanghai`
-- `yesterday` = `$[yyyy-MM-dd, -1d]`
+* `city` = `Shanghai`
+* `yesterday` = `$[yyyy-MM-dd, -1d]`
 
 **Step 3: Run and verify**
 
@@ -50,11 +50,12 @@ SELECT * FROM sales_table WHERE city = 'Shanghai' AND dt = '2023-09-21';
 ```
 
 **Key points**:
-- The parameter format is always `${parameter_name}`. Parameter names may only contain letters, digits, and underscores.
-- You cannot reference built-in parameters (such as `sys_biz_day`) directly in code — you must first assign them to a custom parameter, then reference the custom parameter.
-- Add quotes in SQL yourself when needed: `'${city}'`
 
----
+* The parameter format is always `${parameter_name}`. Parameter names may only contain letters, digits, and underscores.
+* You cannot reference built-in parameters (such as `sys_biz_day`) directly in code — you must first assign them to a custom parameter, then reference the custom parameter.
+* Add quotes in SQL yourself when needed: `'${city}'`
+
+***
 
 ## Parameter Types and Scope
 
@@ -66,13 +67,13 @@ Scoped to the current task only. Use these for configuration that is unique to a
 
 ![](.topwrite/assets/image_1740658949338.png =700)
 
-| Field | Description | Example |
-| ---- | ---- | ---- |
-| Parameter name | Unique identifier for the parameter | `city`, `yesterday` |
-| Value source | Select "Task" or "Task Group" | Task |
-| Parameter value | The actual value or expression | `Shanghai`, `$[yyyy-MM-dd, -1d]` |
-| Encrypt value | When checked, the value is masked | Use for passwords and other sensitive data |
-| Ignore | When checked, no substitution is performed | Treats `${var}` as literal text |
+| Field           | Description                                | Example                                    |
+| --------------- | ------------------------------------------ | ------------------------------------------ |
+| Parameter name  | Unique identifier for the parameter        | `city`, `yesterday`                        |
+| Value source    | Select "Task" or "Task Group"              | Task                                       |
+| Parameter value | The actual value or expression             | `Shanghai`, `$[yyyy-MM-dd, -1d]`           |
+| Encrypt value   | When checked, the value is masked          | Use for passwords and other sensitive data |
+| Ignore          | When checked, no substitution is performed | Treats `${var}` as literal text            |
 
 ### Task Group Parameters
 
@@ -89,7 +90,7 @@ SELECT * FROM ${db_name}.table_a;
 SELECT * FROM ${db_name}.table_b;
 ```
 
----
+***
 
 ## Parameter Behavior by Run Mode
 
@@ -97,13 +98,13 @@ SELECT * FROM ${db_name}.table_b;
 
 A dialog prompts you to enter parameter values. The values apply to this run only and do not affect the saved parameter configuration. Useful for debugging and validation.
 
-![](/.topwrite/assets/image_1761284431760.png =680)
+![](/.topwrite/assets/image_1780887030206.png =668)
 
 ### Scheduled run
 
 Uses the saved parameter configuration and dynamically calculates parameter values based on the scheduled time. Use this in production.
 
----
+***
 
 ## Appendix: How to verify full parameter support
 
@@ -117,14 +118,16 @@ Parameter configuration: `lastDay` = `add_days('yyyy-MM-dd', -1)`
 
 If the result is yesterday's date (e.g., `2023-11-11`), your account is in the rollout scope and full parameter functionality is supported. If `${lastDay}` is not substituted, it is not yet supported.
 
----
+***
 
 ## Related Documentation
 
-| Document | Description |
-| ---- | ---- |
-| [Task Parameter Syntax Reference](task_param_reference.md) | Complete syntax and quick-reference for system built-in parameters, time expressions, and built-in time functions |
-| [Task Parameter Examples](task_param_examples.md) | Complete business scenario examples for daily reports, monthly reports, weekly reports, timestamp queries, and FAQ |
-| [Task Development and Scheduling](task-develop.md) | Creating, scheduling, and operating SQL tasks in Studio |
-| [Workflow (Composite Task)](composite_task.md) | Orchestrate multiple parameterized tasks into a DAG with unified scheduling |
-| [Python Task](python-task.md) | Using parameters in Python tasks |
+| Document                                                   | Description                                                                                                        |
+| ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| [Task Parameter Syntax Reference](task_param_reference.md) | Complete syntax and quick-reference for system built-in parameters, time expressions, and built-in time functions  |
+| [Task Parameter Examples](task_param_examples.md)          | Complete business scenario examples for daily reports, monthly reports, weekly reports, timestamp queries, and FAQ |
+| [Task Development and Scheduling](task-develop.md)         | Creating, scheduling, and operating SQL tasks in Studio                                                            |
+| [Workflow (Composite Task)](composite_task.md)             | Orchestrate multiple parameterized tasks into a DAG with unified scheduling                                        |
+| [Python Task](python-task.md)                              | Using parameters in Python tasks                                                                                   |
+
+^

package/bin/skills/lakehouse-doc-en/references/task_param_reference.md

@@ -12,22 +12,22 @@ The system provides a set of commonly used parameters that you can use directly
 
 ### Date and Time Parameters
 
-| Parameter name | Format | Description | Example (reference time: 2023-09-22 18:00:00) |
-| ---- | ---- | ---- | ---- |
-| `bizdate` | yyyyMMdd | Business date (scheduled time minus 1 day) | 20230921 |
-| `sys_biz_day` | yyyy-MM-dd | Business date | 2023-09-21 |
-| `sys_biz_datetime` | yyyy-MM-dd HH:mm:ss | Business datetime | 2023-09-21 18:00:00 |
-| `sys_plan_day` | yyyy-MM-dd | Scheduled date | 2023-09-22 |
-| `sys_plan_datetime` | yyyy-MM-dd HH:mm:ss | Scheduled datetime | 2023-09-22 18:00:00 |
-| `sys_plan_timestamp` | 13-digit timestamp | Scheduled timestamp (milliseconds) | 1695463200000 |
+| Parameter name       | Format               | Description                                | Example (reference time: 2023-09-22 18:00:00) |
+| -------------------- | -------------------- | ------------------------------------------ | --------------------------------------------- |
+| `bizdate`            | yyyyMMdd             | Business date (scheduled time minus 1 day) | 20230921                                      |
+| `sys_biz_day`        | yyyy-MM-dd           | Business date                              | 2023-09-21                                    |
+| `sys_biz_datetime`   | yyyy-MM-dd HH\:mm:ss | Business datetime                          | 2023-09-21 18:00:00                           |
+| `sys_plan_day`       | yyyy-MM-dd           | Scheduled date                             | 2023-09-22                                    |
+| `sys_plan_datetime`  | yyyy-MM-dd HH\:mm:ss | Scheduled datetime                         | 2023-09-22 18:00:00                           |
+| `sys_plan_timestamp` | 13-digit timestamp   | Scheduled timestamp (milliseconds)         | 1695463200000                                 |
 
 ### Task Information Parameters
 
-| Parameter name | Description | Example | Notes |
-| ---- | ---- | ---- | ---- |
-| `sys_task_id` | Task ID | 1002 | Scheduled run only |
-| `sys_task_name` | Task name | demo_task | Scheduled run only |
-| `sys_task_owner` | Task owner | UAT_TEST | Scheduled run only |
+| Parameter name   | Description | Example    | Notes              |
+| ---------------- | ----------- | ---------- | ------------------ |
+| `sys_task_id`    | Task ID     | 1002       | Scheduled run only |
+| `sys_task_name`  | Task name   | demo\_task | Scheduled run only |
+| `sys_task_owner` | Task owner  | UAT\_TEST  | Scheduled run only |
 
 ### Usage Examples
 
@@ -45,12 +45,12 @@ SELECT * FROM table WHERE create_time >= ${start_ts};
 
 ### Usage Recommendations
 
-- **Business date scenarios**: prefer `bizdate` or `sys_biz_day`
-- **When hours, minutes, and seconds are needed**: use `sys_biz_datetime` or `sys_plan_datetime`
-- **Timestamp calculations**: use `sys_plan_timestamp`
-- **Audit logging**: use the `sys_task_*` parameters to record task information
+* **Business date scenarios**: prefer `bizdate` or `sys_biz_day`
+* **When hours, minutes, and seconds are needed**: use `sys_biz_datetime` or `sys_plan_datetime`
+* **Timestamp calculations**: use `sys_plan_timestamp`
+* **Audit logging**: use the `sys_task_*` parameters to record task information
 
----
+***
 
 ## Time Expressions
 
@@ -68,17 +68,17 @@ $[time_format, offset1, offset2, ...]  # Multiple offsets (applied in sequence)
 
 Time expressions follow the **ISO-8601 standard** and are strictly case-sensitive.
 
-| Element | Meaning | Example |
-| ---- | ---- | ---- |
-| `yyyy` | Four-digit year | 2023 |
-| `yy` | Two-digit year | 23 |
-| `MM` | Two-digit month (01-12) | 09 |
-| `dd` | Two-digit day (01-31) | 22 |
-| `HH` | 24-hour hour (00-23) | 18 |
-| `mm` | Minute (00-59) | 59 |
-| `ss` | Second (00-59) | 49 |
-| `.SSS` | Millisecond | 0.377 |
-| `ZZ` | Time zone | +08:00 |
+| Element | Meaning                 | Example |
+| ------- | ----------------------- | ------- |
+| `yyyy`  | Four-digit year         | 2023    |
+| `yy`    | Two-digit year          | 23      |
+| `MM`    | Two-digit month (01-12) | 09      |
+| `dd`    | Two-digit day (01-31)   | 22      |
+| `HH`    | 24-hour hour (00-23)    | 18      |
+| `mm`    | Minute (00-59)          | 59      |
+| `ss`    | Second (00-59)          | 49      |
+| `.SSS`  | Millisecond             | 0.377   |
+| `ZZ`    | Time zone               | +08:00  |
 
 > ⚠️ Common mistakes: `YYYY` (uppercase Y is not supported), `yyyy-mm-dd` (lowercase m is minute, not month), `hh` (lowercase h is 12-hour format). Correct form: `yyyy-MM-dd HH:mm:ss`.
 
@@ -96,16 +96,16 @@ $[yyyy-MM-dd HH:mm:ss.SSSZZ] → 2023-09-22 18:00:00.377+08:00
 
 ### Time Offsets
 
-| Unit | Abbreviation | Full name | Example |
-| ---- | ---- | ---- | ---- |
-| Millisecond | ms | milli/millisecond | 400ms |
-| Second | s | sec/second | 30s |
-| Minute | m | min/minute | 15m |
-| Hour | h | hour | 2h |
-| Day | d | day | -1d |
-| Week | w | week | -1w |
-| Month | mon | month | -1mon |
-| Year | y | year | -1y |
+| Unit        | Abbreviation | Full name         | Example |
+| ----------- | ------------ | ----------------- | ------- |
+| Millisecond | ms           | milli/millisecond | 400ms   |
+| Second      | s            | sec/second        | 30s     |
+| Minute      | m            | min/minute        | 15m     |
+| Hour        | h            | hour              | 2h      |
+| Day         | d            | day               | -1d     |
+| Week        | w            | week              | -1w     |
+| Month       | mon          | month             | -1mon   |
+| Year        | y            | year              | -1y     |
 
 ### Offset Examples
 
@@ -121,7 +121,7 @@ $[yyyy-MM-dd, -1y, -1mon, -1d]  → Last year, last month, yesterday
 $[yyyyMMdd, 1mon, -7d]          → Next month minus 7 days
 ```
 
----
+***
 
 ## Built-in Time Functions
 
@@ -270,53 +270,55 @@ today_start     = biz_timestamp()    → 1695312000000 (2023-09-22 00:00:00)
 yesterday_start = biz_timestamp(-1d) → 1695225600000
 ```
 
----
+***
 
 ## Quick Reference
 
 ### Common Time Requirements
 
-| Requirement | Parameter configuration | Example result (reference: 2023-09-22) |
-| ---- | ---- | ---- |
-| Today | `$[yyyy-MM-dd]` or `sys_plan_day` | 2023-09-22 |
-| Yesterday | `$[yyyy-MM-dd, -1d]` or `sys_biz_day` | 2023-09-21 |
-| Same day last week | `$[yyyy-MM-dd, -7d]` | 2023-09-15 |
-| Same day last month | `$[yyyy-MM-dd, -1mon]` | 2023-08-22 |
-| First day of this month | `first_day_of_month()` | 2023-09-01 |
-| Last day of this month | `last_day_of_month()` | 2023-09-30 |
-| First day of last month | `first_day_of_month('yyyy-MM-dd', '-1mon')` | 2023-08-01 |
-| Last day of last month | `last_day_of_month('yyyy-MM-dd', '-1mon')` | 2023-08-31 |
-| This Monday | `first_day_of_week()` | 2023-09-18 |
-| This Sunday | `last_day_of_week()` | 2023-09-24 |
-| Last Monday | `first_day_of_week('yyyy-MM-dd', '-1w')` | 2023-09-11 |
-| Last Sunday | `last_day_of_week('yyyy-MM-dd', '-1w')` | 2023-09-17 |
-| This Tuesday | `get_day_of_week('yyyy-MM-dd', 2)` | 2023-09-19 |
-| Last year yesterday | `$[yyyy-MM-dd, -1y, -1d]` | 2022-09-21 |
-| Today at 00:00 timestamp | `biz_timestamp()` | 1695312000000 |
-| Current timestamp | `timestamp()` | 1695463200000 |
+| Requirement              | Parameter configuration                     | Example result (reference: 2023-09-22) |
+| ------------------------ | ------------------------------------------- | -------------------------------------- |
+| Today                    | `$[yyyy-MM-dd]` or `sys_plan_day`           | 2023-09-22                             |
+| Yesterday                | `$[yyyy-MM-dd, -1d]` or `sys_biz_day`       | 2023-09-21                             |
+| Same day last week       | `$[yyyy-MM-dd, -7d]`                        | 2023-09-15                             |
+| Same day last month      | `$[yyyy-MM-dd, -1mon]`                      | 2023-08-22                             |
+| First day of this month  | `first_day_of_month()`                      | 2023-09-01                             |
+| Last day of this month   | `last_day_of_month()`                       | 2023-09-30                             |
+| First day of last month  | `first_day_of_month('yyyy-MM-dd', '-1mon')` | 2023-08-01                             |
+| Last day of last month   | `last_day_of_month('yyyy-MM-dd', '-1mon')`  | 2023-08-31                             |
+| This Monday              | `first_day_of_week()`                       | 2023-09-18                             |
+| This Sunday              | `last_day_of_week()`                        | 2023-09-24                             |
+| Last Monday              | `first_day_of_week('yyyy-MM-dd', '-1w')`    | 2023-09-11                             |
+| Last Sunday              | `last_day_of_week('yyyy-MM-dd', '-1w')`     | 2023-09-17                             |
+| This Tuesday             | `get_day_of_week('yyyy-MM-dd', 2)`          | 2023-09-19                             |
+| Last year yesterday      | `$[yyyy-MM-dd, -1y, -1d]`                   | 2022-09-21                             |
+| Today at 00:00 timestamp | `biz_timestamp()`                           | 1695312000000                          |
+| Current timestamp        | `timestamp()`                               | 1695463200000                          |
 
 ### Time Function Quick Reference
 
-| Function | Purpose | Return type |
-| ---- | ---- | ---- |
-| `first_day_of_month()` | First day of the current month | Date string |
-| `last_day_of_month()` | Last day of the current month | Date string |
-| `first_day_of_week()` | First day of the current week (Monday) | Date string |
-| `last_day_of_week()` | Last day of the current week (Sunday) | Date string |
-| `day_of_week()` | Day of the week (1-7) | Integer |
-| `week_of_month()` | Week number within the current month | Integer |
-| `week_of_year()` | Week number within the current year | Integer |
-| `get_day_of_week()` | Date of a specific day of the week | Date string |
-| `timestamp()` | Millisecond timestamp (based on scheduled time) | 13-digit integer |
-| `biz_timestamp()` | Millisecond timestamp (based on 00:00:00) | 13-digit integer |
-| `unix_timestamp()` | Second timestamp | 10-digit integer |
-| `biz_unix_timestamp()` | Business second timestamp | 10-digit integer |
-| `biz_format()` | Business time formatting | String |
-
----
+| Function               | Purpose                                         | Return type      |
+| ---------------------- | ----------------------------------------------- | ---------------- |
+| `first_day_of_month()` | First day of the current month                  | Date string      |
+| `last_day_of_month()`  | Last day of the current month                   | Date string      |
+| `first_day_of_week()`  | First day of the current week (Monday)          | Date string      |
+| `last_day_of_week()`   | Last day of the current week (Sunday)           | Date string      |
+| `day_of_week()`        | Day of the week (1-7)                           | Integer          |
+| `week_of_month()`      | Week number within the current month            | Integer          |
+| `week_of_year()`       | Week number within the current year             | Integer          |
+| `get_day_of_week()`    | Date of a specific day of the week              | Date string      |
+| `timestamp()`          | Millisecond timestamp (based on scheduled time) | 13-digit integer |
+| `biz_timestamp()`      | Millisecond timestamp (based on 00:00:00)       | 13-digit integer |
+| `unix_timestamp()`     | Second timestamp                                | 10-digit integer |
+| `biz_unix_timestamp()` | Business second timestamp                       | 10-digit integer |
+| `biz_format()`         | Business time formatting                        | String           |
+
+***
 
 ## Related Documentation
 
-- [Task Parameters](task_param.md) — concepts, quick start, parameter types
-- [Task Parameter Examples](task_param_examples.md) — complete business scenarios for daily, monthly, and weekly reports
-- [Task Development and Scheduling](task-develop.md) — creating and scheduling SQL tasks in Studio
+* [Task Parameters](task_param.md) — concepts, quick start, parameter types
+* [Task Parameter Examples](task_param_examples.md) — complete business scenarios for daily, monthly, and weekly reports
+* [Task Development and Scheduling](task-develop.md) — creating and scheduling SQL tasks in Studio
+
+^