create-yss-spec 1.1.3 → 2.0.0

package/template/.agents/skills/to-prd/SKILL.md

@@ -1,75 +0,0 @@
----
-name: to-prd
-description: Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
-disable-model-invocation: true
----
-
-This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
-
-2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
-
-Check with the user that these seams match their expectations.
-
-3. Write the PRD using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.
-
-<prd-template>
-
-## Problem Statement
-
-The problem that the user is facing, from the user's perspective.
-
-## Solution
-
-The solution to the problem, from the user's perspective.
-
-## User Stories
-
-A LONG, numbered list of user stories. Each user story should be in the format of:
-
-1. As an <actor>, I want a <feature>, so that <benefit>
-
-<user-story-example>
-1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
-</user-story-example>
-
-This list of user stories should be extremely extensive and cover all aspects of the feature.
-
-## Implementation Decisions
-
-A list of implementation decisions that were made. This can include:
-
-- The modules that will be built/modified
-- The interfaces of those modules that will be modified
-- Technical clarifications from the developer
-- Architectural decisions
-- Schema changes
-- API contracts
-- Specific interactions
-
-Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
-
-Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Testing Decisions
-
-A list of testing decisions that were made. Include:
-
-- A description of what makes a good test (only test external behavior, not implementation details)
-- Which modules will be tested
-- Prior art for the tests (i.e. similar types of tests in the codebase)
-
-## Out of Scope
-
-A description of the things that are out of scope for this PRD.
-
-## Further Notes
-
-Any further notes about the feature.
-
-</prd-template>

package/template/.claude/skills/to-issues/SKILL.md

@@ -1,84 +0,0 @@
----
-name: to-issues
-description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
-disable-model-invocation: true
----
-
-# To Issues
-
-Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-### 1. Gather context
-
-Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
-
-### 2. Explore the codebase (optional)
-
-If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
-
-Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."
-
-### 3. Draft vertical slices
-
-Break the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
-
-<vertical-slice-rules>
-
-- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
-- A completed slice is demoable or verifiable on its own
-- Any prefactoring should be done first
-
-</vertical-slice-rules>
-
-### 4. Quiz the user
-
-Present the proposed breakdown as a numbered list. For each slice, show:
-
-- **Title**: short descriptive name
-- **Blocked by**: which other slices (if any) must complete first
-- **User stories covered**: which user stories this addresses (if the source material has them)
-
-Ask the user:
-
-- Does the granularity feel right? (too coarse / too fine)
-- Are the dependency relationships correct?
-- Should any slices be merged or split further?
-
-Iterate until the user approves the breakdown.
-
-### 5. Publish the issues to the issue tracker
-
-For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
-
-Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
-
-<issue-template>
-## Parent
-
-A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
-
-## What to build
-
-A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
-
-Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Acceptance criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2
-- [ ] Criterion 3
-
-## Blocked by
-
-- A reference to the blocking ticket (if any)
-
-Or "None - can start immediately" if no blockers.
-
-</issue-template>
-
-Do NOT close or modify any parent issue.

package/template/.claude/skills/to-prd/SKILL.md

@@ -1,75 +0,0 @@
----
-name: to-prd
-description: Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
-disable-model-invocation: true
----
-
-This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
-
-2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
-
-Check with the user that these seams match their expectations.
-
-3. Write the PRD using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.
-
-<prd-template>
-
-## Problem Statement
-
-The problem that the user is facing, from the user's perspective.
-
-## Solution
-
-The solution to the problem, from the user's perspective.
-
-## User Stories
-
-A LONG, numbered list of user stories. Each user story should be in the format of:
-
-1. As an <actor>, I want a <feature>, so that <benefit>
-
-<user-story-example>
-1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
-</user-story-example>
-
-This list of user stories should be extremely extensive and cover all aspects of the feature.
-
-## Implementation Decisions
-
-A list of implementation decisions that were made. This can include:
-
-- The modules that will be built/modified
-- The interfaces of those modules that will be modified
-- Technical clarifications from the developer
-- Architectural decisions
-- Schema changes
-- API contracts
-- Specific interactions
-
-Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
-
-Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Testing Decisions
-
-A list of testing decisions that were made. Include:
-
-- A description of what makes a good test (only test external behavior, not implementation details)
-- Which modules will be tested
-- Prior art for the tests (i.e. similar types of tests in the codebase)
-
-## Out of Scope
-
-A description of the things that are out of scope for this PRD.
-
-## Further Notes
-
-Any further notes about the feature.
-
-</prd-template>

package/template/.codex/skills/to-issues/SKILL.md

@@ -1,84 +0,0 @@
----
-name: to-issues
-description: Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
-disable-model-invocation: true
----
-
-# To Issues
-
-Break a plan into independently-grabbable issues using vertical slices (tracer bullets).
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-### 1. Gather context
-
-Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
-
-### 2. Explore the codebase (optional)
-
-If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
-
-Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."
-
-### 3. Draft vertical slices
-
-Break the plan into **tracer bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
-
-<vertical-slice-rules>
-
-- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
-- A completed slice is demoable or verifiable on its own
-- Any prefactoring should be done first
-
-</vertical-slice-rules>
-
-### 4. Quiz the user
-
-Present the proposed breakdown as a numbered list. For each slice, show:
-
-- **Title**: short descriptive name
-- **Blocked by**: which other slices (if any) must complete first
-- **User stories covered**: which user stories this addresses (if the source material has them)
-
-Ask the user:
-
-- Does the granularity feel right? (too coarse / too fine)
-- Are the dependency relationships correct?
-- Should any slices be merged or split further?
-
-Iterate until the user approves the breakdown.
-
-### 5. Publish the issues to the issue tracker
-
-For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.
-
-Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
-
-<issue-template>
-## Parent
-
-A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
-
-## What to build
-
-A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.
-
-Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Acceptance criteria
-
-- [ ] Criterion 1
-- [ ] Criterion 2
-- [ ] Criterion 3
-
-## Blocked by
-
-- A reference to the blocking ticket (if any)
-
-Or "None - can start immediately" if no blockers.
-
-</issue-template>
-
-Do NOT close or modify any parent issue.

package/template/.codex/skills/to-prd/SKILL.md

@@ -1,75 +0,0 @@
----
-name: to-prd
-description: Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
-disable-model-invocation: true
----
-
-This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
-
-The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
-
-## Process
-
-1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.
-
-2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
-
-Check with the user that these seams match their expectations.
-
-3. Write the PRD using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.
-
-<prd-template>
-
-## Problem Statement
-
-The problem that the user is facing, from the user's perspective.
-
-## Solution
-
-The solution to the problem, from the user's perspective.
-
-## User Stories
-
-A LONG, numbered list of user stories. Each user story should be in the format of:
-
-1. As an <actor>, I want a <feature>, so that <benefit>
-
-<user-story-example>
-1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
-</user-story-example>
-
-This list of user stories should be extremely extensive and cover all aspects of the feature.
-
-## Implementation Decisions
-
-A list of implementation decisions that were made. This can include:
-
-- The modules that will be built/modified
-- The interfaces of those modules that will be modified
-- Technical clarifications from the developer
-- Architectural decisions
-- Schema changes
-- API contracts
-- Specific interactions
-
-Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
-
-Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
-
-## Testing Decisions
-
-A list of testing decisions that were made. Include:
-
-- A description of what makes a good test (only test external behavior, not implementation details)
-- Which modules will be tested
-- Prior art for the tests (i.e. similar types of tests in the codebase)
-
-## Out of Scope
-
-A description of the things that are out of scope for this PRD.
-
-## Further Notes
-
-Any further notes about the feature.
-
-</prd-template>

package/template/.codex/skills/yss-anti-scheduler/SKILL.md

@@ -1,53 +0,0 @@
----
-name: yss-anti-scheduler
-description: 用于 YSS anti-corrosion anti-scheduler、DolphinScheduler SDK、调度器 API client、工作流/任务/租户/资源中心客户端接入和排障。
----
-
-# yss-anti-scheduler
-
-Use this skill for YSS 调度器防腐层组件. Keep implementation grounded in the local project and resolvable YSS backend component source.
-
-中文说明：本技能用于 YSS 调度器防腐层组件，覆盖统一 Scheduler API 以及 DolphinScheduler、DM Scheduler、XXL-JOB、ElasticJob 等后端适配。执行时优先读取源码索引，避免凭记忆猜类名、配置项或接入方式。
-
-## Source Index First
-
-- Backend source location is environment-specific; resolve it with `yss-source-index/references/source-location.md`.
-- Generated index: `references/source-index.md`
-- Component path hints: `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler`
-
-Read `references/source-index.md` as a path-hint index whenever the task depends on exact modules, annotations, auto configuration, properties, controllers, clients, repositories, DTOs, handlers, or troubleshooting.
-
-## Workflow
-
-1. Identify whether the task targets the unified scheduler API, a concrete scheduler backend, generated SDK client calls, workflow/task/resource APIs, cron/schedule behavior, or execution/log troubleshooting.
-2. Read `references/source-index.md`, then start from the unified API module before touching a backend adapter.
-3. Prefer `SchedulerFacadeApi` as the application-facing entry point; it combines execution commands, cron commands, executor operations, and query operations.
-4. For execution behavior, inspect `SchedulerExecutor`; for query/log/history behavior, inspect `SchedulerQuery`; for schedule expression behavior, inspect `SchedulerCronCommand` and `SchedulerCron`.
-5. Choose the concrete backend adapter only after the target scheduler is known: DM Scheduler, DolphinScheduler, XXL-JOB, or ElasticJob.
-6. For raw REST/API interactions, inspect the generated SDK module matching the backend (`dm-scheduler-sdk`, `dolphinscheduler-sdk`, `xxljob-sdk`) and its `ApiClient`/server configuration.
-7. Keep backend-specific models isolated behind the anti-corrosion API unless the task is explicitly adapter development.
-
-## Capability Split
-
-- Unified API: `yss-component-anti-scheduler-api`, especially `SchedulerFacadeApi`, `SchedulerExecutor`, `SchedulerQuery`, `SchedulerCronCommand`, and `SchedulerFactory`.
-- DM Scheduler adapter: `yss-component-anti-scheduler-dmscheduler` plus `dm-scheduler-sdk`.
-- DolphinScheduler adapter: `yss-component-anti-scheduler-dolphin` plus `dolphinscheduler-sdk`.
-- XXL-JOB adapter: `yss-component-anti-scheduler-xxljob` plus `xxljob-sdk`.
-- ElasticJob adapter: `yss-component-anti-scheduler-elasticjob`.
-- Cross-domain APIs: task flow, task definition/instance, workflow execution, resource/file, tenant/user, datasource, quality, tag, variable, and log APIs in generated clients.
-
-## Checklist
-
-- Required dependency or scheduler adapter module is present.
-- Target scheduler backend is identified before using backend-specific APIs.
-- Scheduler host/token/auth/server configuration is externalized.
-- Task group, task instance, cron, and log identifiers use the component domain model consistently.
-- `stop`, `taskInstance`, subtask, and other default methods may be unsupported by some backends; check implementation before relying on them.
-- Backend-specific DTOs do not leak into business modules unless the adapter boundary is the task.
-- Execution/log/retry operations are checked against scheduler permissions and environment.
-
-## Do Not
-
-- Do not invent class names or configuration keys without checking the source index.
-- Do not replace component extension points with business-local framework code.
-- Do not broaden the task into unrelated YSS components unless the user asks.

package/template/.codex/skills/yss-anti-scheduler/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "yss-anti-scheduler"
-  short_description: "YSS component skill for yss-anti-scheduler"
-  default_prompt: "Use yss-anti-scheduler for this YSS backend component task."

package/template/.codex/skills/yss-anti-scheduler/references/source-index.md

@@ -1,157 +0,0 @@
-# yss-anti-scheduler Source Index
-
-Generated: 2026-06-29T16:11:14+00:00
-Indexed source root: resolved at refresh time; set `YSS_SOURCE_ROOT` to reproduce or refresh.
-
-This file is generated by `yss-source-index/scripts/refresh-yss-skill-index.py`. Do not hand-edit generated sections.
-
-Paths below are source path hints captured at refresh time. If they do not exist in the current workspace, locate sources using `YSS_SOURCE_ROOT`, CodeGraph, package/class names, Maven artifact names, or repository search before assuming the source is unavailable.
-
-## Component Path Hints
-
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler` (existed when indexed)
-
-## Documentation Files
-
-- No component documentation files found.
-
-## Maven Modules
-
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dolphinscheduler-sdk`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/xxljob-sdk`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/yss-component-anti-scheduler-api`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/yss-component-anti-scheduler-dmscheduler`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/yss-component-anti-scheduler-dolphin`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/yss-component-anti-scheduler-elasticjob`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/yss-component-anti-scheduler-xxljob`
-
-## Key Java Entry Points
-
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/AnalysisRelatedOperationOfTaskStateApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/AuditLogRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/CloudTagApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/ConfigControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/DataQualityServiceApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/DataSourceRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/DynamicTaskTypeApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/ExecutorOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/FileConfigControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/FileControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/FileGroupControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/GroupControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/LogRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/NameSpaceControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/ProcessTaskRelationRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/SchedulerTagApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/TagControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/TaskControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/TaskDefinitionRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/TaskFlowControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/TaskGroupRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/TaskInstanceRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/UserLoginRelatedOperationsApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/UsersRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/VarNameSpaceControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/VariableControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/WorkFlowLineageRelatedOperationApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/WorkFlowLineageRelatedOperationV2Api.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/WorkflowExecuteControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/WorkflowInstanceTagV2Api.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/YssDataAnalysisControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/YssExecutorControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/api/YssSchedulerControllerApi.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/client/SchedulerHostProvider.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/CommandTypeEnum.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/ExecuteType.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/ReleaseStateEnum.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/TaskDependTypeEnum.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/TaskExecutionStatus.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/WarningTypeEnum.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/enums/WorkflowExecutionStatus.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/invoker/ApiClient.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/invoker/ServerConfiguration.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/invoker/ServerVariable.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ApiResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/AuditDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/BaseDataSourceParamDTO.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/CommandStateCount.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/CreateResourceRequest.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/CreateTaskFlowParamDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/CreateTokenRequest.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DagData.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DataSource.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DataSourceParameters.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DatabaseMetrics.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DefineUserDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DeleteDataTransferResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DependentTaskModel.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DqExecuteResult.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DqRule.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/DynamicSubWorkflowDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/Edit400Response.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/EditFileReq.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/Excel.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/FileCopyOrMoveReq.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/FileCopyOrMoveResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/FileFindPageReq.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/FileReq.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/FileResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/FileType.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/GroupPageReq.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ImportProcessDefinitionRequest.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/IntegrateTaskFlowDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/OAuth2ClientProperties.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageFileResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageGroupResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoAccessToken.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoAlertGroup.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoAlertPluginInstanceVO.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoAuditDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoClusterDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoDqExecuteResult.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoDqRule.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoGroup.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoProcessDefinition.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoProcessInstance.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoProject.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoQueue.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoSchedule.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoStorageEntity.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoTaskDefinition.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoTaskInstance.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageInfoTenant.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageNameSpaceReq.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageNameSpaceResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageTagResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/PageVariableResp.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProcessTaskRelation.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectCreateRequest.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectCreateResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectDeleteResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectListResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectQueryResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectUpdateRequest.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ProjectUpdateResponse.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResponseTaskLog.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/Result.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultAccessToken.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultAlertGroup.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultAlertPluginInstance.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultBoolean.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultCluster.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultClusterDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultDataSource.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultDefineUserDto.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultEnvironment.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultGroup.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultGroupVoObject.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultLinkedListGroup.java`
-- `yss-microservice-components/yss-component-anti-corrosion/yss-component-anti-scheduler/dm-scheduler-sdk/src/main/java/com/yss/datamiddle/client/scheduler/model/ResultListAccessToken.java`
-
-## Recommended Next Reads
-
-- Start with the documentation files above when learning component usage.
-- Search the key Java entry points for annotations, auto configuration, properties, aspects, interceptors, handlers, and result objects before changing application code.
-- Prefer existing component extension points over rewriting framework logic in business modules.