create-yss-spec 1.0.0

package/template/.codex/skills/yss-domain-modeling/references/modeling-workflow.md

@@ -0,0 +1,90 @@
+# Modeling Workflow
+
+Use this reference to turn PRD/RDD/OpenAPI/page flow/DDL/current code into a YSS domain model brief.
+
+## 1. Read Inputs
+
+Collect only the inputs needed for the current task:
+
+- PRD, user stories, acceptance criteria, and non-scope.
+- RDD Spec, OpenAPI, state machine, error codes, and business rules.
+- Page flow, form fields, table columns, actions, permissions, and visible states.
+- Existing `CONTEXT.md`, `CONTEXT-MAP.md`, ADRs, and related code.
+- DDL or metadata as supporting evidence, not as the source of truth.
+
+If inputs conflict, surface the conflict instead of silently choosing one.
+
+## 2. Extract Ubiquitous Language
+
+Identify:
+
+- Canonical business terms.
+- Synonyms and words to avoid.
+- Overloaded terms that need disambiguation.
+- Terms already defined in `CONTEXT.md`.
+- Terms that should be added or changed in `CONTEXT.md`.
+
+Keep definitions business-focused. Do not add generic technical terms.
+
+## 3. Identify Context Boundaries
+
+For each candidate bounded context, define:
+
+- What it owns.
+- What it explicitly does not own.
+- Which other contexts or systems it depends on.
+- Which data or concepts are referenced by ID only.
+- Whether the boundary is uncertain and needs human confirmation.
+
+Prefer a clear boundary over a large all-purpose domain.
+
+## 4. Model Aggregates
+
+For each aggregate, identify:
+
+- Aggregate root.
+- Entities contained by the aggregate.
+- Value objects.
+- Invariants that must always hold.
+- Commands or domain behaviors that change state.
+- Queries that should stay outside the aggregate when they do not express behavior.
+
+Reject models that only expose CRUD and have no business behavior.
+
+## 5. Model Behavior And State
+
+For each important behavior:
+
+- Name it in business language.
+- Define preconditions.
+- Define resulting state or output.
+- Define failure paths and business errors.
+- Define permissions if the behavior is user-initiated.
+
+For stateful objects, record allowed transitions and forbidden transitions.
+
+## 6. Identify Domain Gateways
+
+Define gateways from the domain's point of view:
+
+- What capability the domain needs.
+- Input and output concepts.
+- Whether the capability is a query, command, integration, or policy lookup.
+
+Do not expose Repository, Mapper, SQL, HTTP client, cache, or implementation details in the gateway name or method intent.
+
+## 7. Identify Events And Decisions
+
+Suggest domain events only when another boundary needs to react to a meaningful business fact.
+
+Suggest ADRs when a decision is hard to reverse, surprising without context, and caused by a real trade-off.
+
+## 8. Produce Handoff
+
+End with a handoff that tells the implementer:
+
+- Which skill to call next.
+- Which packages or modules are likely involved.
+- Which model decisions are stable.
+- Which questions must be confirmed before coding.
+- Which safety or human-review gates apply.

package/template/.codex/skills/yss-domain-modeling/references/yss-ddd-rules.md

@@ -0,0 +1,36 @@
+# YSS DDD Rules
+
+Use these rules as gates while modeling YSS backend domains.
+
+## Core Gates
+
+- Do not derive the whole domain model directly from database tables. DDL and metadata are supporting evidence only.
+- Do not create a CRUD-only model. Identify business behavior, invariants, and state transitions.
+- Do not leak Controller, Repository, Mapper, SQL, HTTP client, cache, or persistence details into Domain concepts.
+- Do not let Domain depend on Web, Infrastructure, Repository implementation, Mapper, or Controller.
+- Put business language before technical naming. Avoid table abbreviations when they hide meaning.
+- Write uncertain rules as assumptions or questions. Do not present guesses as confirmed business facts.
+- Suggest ADR for major boundary decisions, irreversible choices, or non-obvious trade-offs.
+- Suggest `CONTEXT.md` updates for new or sharpened domain terms.
+
+## Modeling Heuristics
+
+- Treat user actions, page buttons, API commands, and state changes as clues for domain behavior.
+- Treat validation rules that protect business truth as candidate invariants.
+- Treat fields that only support display, search, sorting, or pagination as query/view concerns unless they affect behavior.
+- Prefer small cohesive aggregates over a large aggregate that owns unrelated lifecycle rules.
+- Use a Domain Service when behavior coordinates multiple aggregates or external policies and does not naturally belong to one aggregate.
+- Use a Value Object for identity-free concepts with validation or equality semantics, such as ranges, labels, rule parameters, or composite codes.
+- Use a Domain Event for meaningful facts another boundary should react to, not for every method call.
+
+## Gateway Rules
+
+- Name gateways after domain capability, not storage mechanism.
+- Gateway methods should describe what the domain needs, not how data is fetched.
+- Query-oriented gateways may return VO/DTO shapes only when that is the established YSS convention; keep domain behavior independent of view concerns.
+- Do not expose SQL condition builders, Mapper names, table names, or pagination plugins in the gateway contract.
+
+## Safety Gates
+
+- Raw SQL, database migration scripts, auth/permission rules, encryption/security algorithms, payment-like resource operations, and public base-library API changes require human review.
+- If security or data impact cannot be confirmed, mark the item as requiring human confirmation before implementation.

package/template/.codex/skills/yss-dto/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: yss-dto
+description: 用于 YSS DTO 规范相关的实现与排障。当用户提到 Result、PageQuery、CommandDTO、QueryDTO、统一响应格式、分页入参基类或 DTO 继承约定时调用。
+---
+
+# yss-dto
+
+用于处理 `yss-component-dto` 的使用规范和代码接入。
+
+## 何时使用
+
+- 用户要定义新的分页查询对象。
+- 用户要统一接口返回结构。
+- 用户提到 `Result`、`PageQuery`、`CommandDTO`、`QueryDTO`。
+- 用户在排查分页参数、返回结构或 DTO 继承不一致问题。
+
+## 工作方式
+
+1. 优先沿用项目现有 DTO 体系，不重复造返回包装类。
+2. 涉及真实类名、返回结构、分页字段或排障时，先读 `references/source-index.md`，再定位源码或文档。
+3. 先确认当前项目用的是哪一套结果封装，再给出改法。
+4. 只围绕当前 DTO 结构回答，不泛化到整个微服务理论。
+
+## 源码索引
+
+- 源码位置不要假设固定目录；先按 `yss-source-index/references/source-location.md` 定位。
+- 当前技能索引：`references/source-index.md`
+- 重点源码入口通常包括 `CommandDTO`、`QueryDTO`、`PageQuery`、`PageRequestFactory`、`Result`、`SingleResult`、`MultiResult`、`PageResult`。
+
+当组件源码变化后，用 `yss-source-index` 刷新索引；刷新或读取前先按源码定位策略确认真实位置。
+
+## 使用规则
+
+- 写操作参数优先继承 `CommandDTO`。
+- 读操作参数优先继承 `QueryDTO` 或 `PageQuery`。
+- 分页查询优先继承 `PageQuery`，不要自行发明分页字段名。
+- Controller 返回优先使用项目既有的 `Result` 或派生结果对象。
+- 单对象返回优先 `SingleResult`，列表返回优先 `MultiResult`，分页返回优先 `PageResult`，前提是当前项目已采用这套体系。
+- DTO 只表达接口契约，不承载 Repository PO 或领域对象的持久化细节。
+
+## 检查清单
+
+- 分页字段名是否和框架约定一致。
+- Service / Repository 是否真的接收到了 `PageQuery`。
+- 新增 DTO 是否与现有序列化和校验方式兼容。
+- 返回结构是否和前端或上游调用方契约一致。
+- Controller、Application Service、Domain、Repository 之间是否存在 DTO/VO/DO/PO 混穿。
+- 前端 Orval 或调用方是否依赖当前返回包装结构。
+
+## 修改约束
+
+- 不要在一个项目里混用多套返回包装类。
+- 不要新建与 `PageQuery` 含义重叠的分页基类。
+- 若项目已有 `SingleResult`、`PageResult`、`MultiResult` 体系，优先保持一致。
+
+## 按需读取
+
+- 源码索引：`references/source-index.md`
+- DTO 基类示例：`assets/CommandDTO.java`、`assets/QueryDTO.java`
+- 分页基类：`assets/PageQuery.java`
+- 返回结构：`assets/Result.java`

package/template/.codex/skills/yss-dto/agents/openai.yaml

@@ -0,0 +1,5 @@
+version: 1
+interface:
+  display_name: "YSS DTO"
+  short_description: "统一响应、分页查询、Command 与 DTO 设计规范"
+  default_prompt: "Use $yss-dto to define YSS-style DTOs, page queries, commands, and unified response models."

package/template/.codex/skills/yss-dto/assets/CommandDTO.java

@@ -0,0 +1,8 @@
+package com.yss.cloud.dto;
+
+import java.io.Serializable;
+
+public abstract class CommandDTO implements Serializable {
+
+  private static final long serialVersionUID = 1L;
+}

package/template/.codex/skills/yss-dto/assets/PageQuery.java

@@ -0,0 +1,133 @@
+package com.yss.cloud.dto.page;
+
+import com.fasterxml.jackson.annotation.JsonIgnore;
+import com.yss.cloud.dto.QueryDTO;
+
+public class PageQuery extends QueryDTO {
+
+  private static final long serialVersionUID = 1L;
+
+  public static final String ASC = "ASC";
+
+  public static final String DESC = "DESC";
+
+  private static final int DEFAULT_PAGE_SIZE = 10;
+  /**
+   * 每页显示
+   * @mock 10
+   */
+  private int pageSize = DEFAULT_PAGE_SIZE;
+
+  /**
+   * 当前页
+   * @mock 1
+   */
+  private int pageIndex = 1;
+
+  /**
+   * 排序字段
+   * @mock id
+   */
+  private String orderBy;
+
+  /**
+   * 默认倒序
+   * @mock DESC
+   */
+  private String orderDirection = DESC;
+
+  /** 分组字段 */
+  private String groupBy;
+
+  /**
+   * 是否需要总数
+   * @apiNote 暂时未实现
+   * @mock true
+   */
+  @JsonIgnore
+  private boolean needTotalCount = true;
+
+  /**
+   * 总数dto临时字段，忽略即可
+   * @mock 0
+   */
+  @JsonIgnore
+  private long tempTotalCount = 0;
+
+  public int getPageIndex() {
+    return Math.max(pageIndex, 1);
+  }
+
+  public PageQuery setPageIndex(int pageIndex) {
+    this.pageIndex = pageIndex;
+    return this;
+  }
+
+  public int getPageSize() {
+    if (pageSize < 1) {
+      pageSize = DEFAULT_PAGE_SIZE;
+    }
+    return pageSize;
+  }
+
+  public PageQuery setPageSize(int pageSize) {
+    if (pageSize < 1) {
+      pageSize = DEFAULT_PAGE_SIZE;
+    }
+    this.pageSize = pageSize;
+    return this;
+  }
+
+  public int getOffset() {
+    return (getPageIndex() - 1) * getPageSize();
+  }
+
+  public String getOrderBy() {
+    return orderBy;
+  }
+
+  public PageQuery setOrderBy(String orderBy) {
+    this.orderBy = orderBy;
+    return this;
+  }
+
+  public String getOrderDirection() {
+    return orderDirection;
+  }
+
+  public PageQuery setOrderDirection(String orderDirection) {
+    if (ASC.equalsIgnoreCase(orderDirection) || DESC.equalsIgnoreCase(orderDirection)) {
+      this.orderDirection = orderDirection;
+    }
+    return this;
+  }
+
+  public long getTempTotalCount() {
+    return tempTotalCount;
+  }
+
+  public void setTempTotalCount(long tempTotalCount) {
+    this.tempTotalCount = tempTotalCount;
+  }
+
+  public String getGroupBy() {
+    return groupBy;
+  }
+
+  public void setGroupBy(String groupBy) {
+    this.groupBy = groupBy;
+  }
+
+  public boolean isNeedTotalCount() {
+    return needTotalCount;
+  }
+
+  public void setNeedTotalCount(boolean needTotalCount) {
+    this.needTotalCount = needTotalCount;
+  }
+
+  @Override
+  public String toString() {
+    return "PageQuery(" + "pageSize=" + pageSize + ", pageIndex=" + pageIndex + ')';
+  }
+}

package/template/.codex/skills/yss-dto/assets/QueryDTO.java

@@ -0,0 +1,6 @@
+package com.yss.cloud.dto;
+
+public abstract class QueryDTO extends CommandDTO {
+
+  private static final long serialVersionUID = 1L;
+}

package/template/.codex/skills/yss-dto/assets/Result.java

@@ -0,0 +1,105 @@
+package com.yss.cloud.dto.result;
+
+import java.io.Serializable;
+
+/**
+ * @author zhudaoming
+ */
+public class Result implements Serializable {
+
+  private static final long serialVersionUID = 2405172041950251807L;
+
+  private static final String DEFAULT_MESSAGE = "数据返回正常";
+  private static final String DEFAULT_TIPS = "信息返回正常";
+
+  /** 状态 */
+  private boolean success;
+  /** 返回数据格式 */
+  private String dataType;
+  /** 返回状态码 */
+  private Object code;
+  /** 返回消息 */
+  private String message = DEFAULT_MESSAGE;
+  /** 返回提示消息 */
+  private String tips = DEFAULT_TIPS;
+  public Object getCode() {
+    return code;
+  }
+
+  public Result setCode(Object code) {
+    this.code = code;
+    return this;
+  }
+
+  public String getMessage() {
+    return message;
+  }
+
+  public Result setMessage(String message) {
+    this.message = message;
+    return this;
+  }
+
+  public String getTips() {
+    return tips;
+  }
+
+  public void setTips(String tips) {
+    this.tips = tips;
+  }
+
+  public boolean isSuccess() {
+    return success;
+  }
+
+  public void setSuccess(boolean success) {
+    this.success = success;
+  }
+
+  public String getDataType() {
+    return dataType;
+  }
+
+  public void setDataType(String dataType) {
+    this.dataType = dataType;
+  }
+
+  public static Result buildSuccess() {
+    Result response = new Result();
+    response.setSuccess(true);
+    response.setCode("DM-A0001");
+    return response;
+  }
+
+  public static Result buildSuccess(String message) {
+    Result response = new Result();
+    response.setSuccess(true);
+    response.setMessage(message);
+    return response;
+  }
+  public static Result buildSuccess(String code,String message) {
+    Result response = new Result();
+    response.setSuccess(true);
+    response.setCode(code);
+    response.setMessage(message);
+    return response;
+  }
+  public static Result buildFailure(String message) {
+    Result response = new Result();
+    response.setSuccess(false);
+    response.setMessage(message);
+    return response;
+  }
+  public static Result buildFailure(String errCode,String message) {
+    Result response = new Result();
+    response.setSuccess(false);
+    response.setCode(errCode);
+    response.setMessage(message);
+    return response;
+  }
+  @Override
+  public String toString() {
+    return "Response [success=" + success + "]";
+  }
+
+}

package/template/.codex/skills/yss-dto/references/README.md

@@ -0,0 +1,60 @@
+# 参考资料
+
+本文档详细介绍了 `yss-component-dto` 组件的核心数据传输对象（DTO）。这些 DTO 类被广泛应用于各个服务项目，用于规范数据交互格式。
+
+## 核心类 (Core Classes)
+
+### 1. Result.java
+
+**位置**: `../assets/Result.java`
+
+通用响应包装类，用于统一 API 接口的返回格式。
+
+**核心字段**:
+
+- `success`: 操作是否成功 (boolean)
+- `code`: 状态码 (Object, 默认 "DM-A0001")
+- `message`: 消息描述 (String, 默认 "数据返回正常")
+- `dataType`: 返回数据格式
+- `tips`: 提示消息
+
+**常用静态方法**:
+
+- `buildSuccess()`: 构建成功响应
+- `buildSuccess(String message)`: 构建带消息的成功响应
+- `buildFailure(String message)`: 构建失败响应
+- `buildFailure(String errCode, String message)`: 构建带错误码的失败响应
+
+### 2. PageQuery.java
+
+**位置**: `../assets/PageQuery.java`
+
+分页查询基础类，所有需要分页的查询参数都应继承此类。
+
+**核心字段**:
+
+- `pageIndex`: 当前页码 (默认 1)
+- `pageSize`: 每页条数 (默认 10)
+- `orderBy`: 排序字段
+- `orderDirection`: 排序方向 (ASC/DESC, 默认 DESC)
+- `tempTotalCount`: 临时总数字段（由分页插件回填）
+
+**功能**:
+
+- 提供了链式调用的 Setter 方法 (`setPageIndex`, `setPageSize` 等)。
+- 自动计算偏移量 `getOffset()`。
+
+### 3. CommandDTO.java & QueryDTO.java
+
+**位置**: `../assets/CommandDTO.java`, `../assets/QueryDTO.java`
+
+基础 DTO 抽象类，用于区分命令（写操作）和查询（读操作）对象。
+
+- **CommandDTO**: 实现 `Serializable` 接口，所有命令参数应继承此类。
+- **QueryDTO**: 继承自 `CommandDTO`，所有查询参数应继承此类。
+
+## 使用场景
+
+1. **API 响应**: 所有 Controller 方法应返回 `Result` 或其子类（如 `PageResult`, `SingleResult`）。
+2. **分页查询**: Controller 接收分页请求时，参数类应继承 `PageQuery`。MyBatis 分页插件会自动识别并处理。
+3. **参数封装**: 使用 `CommandDTO` 封装增删改参数，使用 `QueryDTO` 封装查询参数，保持代码语义清晰。

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

@@ -0,0 +1,50 @@
+# yss-dto 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-dto` (existed when indexed)
+
+## Documentation Files
+
+- `yss-microservice-components/yss-component-dto/readme.md`
+
+## Maven Modules
+
+- `yss-microservice-components/yss-component-dto`
+
+## Key Java Entry Points
+
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/SystemIdEnum.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/cache/CacheKey.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/cache/CacheKeyCode.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/cache/CacheType.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/CommandDTO.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/QueryDTO.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/audit/message/AuditMessage.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/audit/message/AuditOperationType.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/audit/message/AuditResourceType.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/audit/message/EventMessage.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/camel/RouteInfo.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/page/PageQuery.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/page/PageRequestFactory.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/result/MultiResult.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/result/PageResult.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/result/Result.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/result/SingleResult.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/support/DicMapUtil.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/upload/FileInfo.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/dto/user/UserInfo.java`
+- `yss-microservice-components/yss-component-dto/src/main/java/com/yss/cloud/sankuai/GenerationTypeSeq.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.

package/template/.codex/skills/yss-duckdb/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: yss-duckdb
+description: 用于 YSS DuckDB 组件接入、DuckDB 查询、嵌入式分析和相关配置排障。
+---
+
+# yss-duckdb
+
+Use this skill for YSS DuckDB 组件. Keep implementation grounded in the local project and resolvable YSS backend component source.
+
+中文说明：本技能用于 YSS DuckDB 组件。执行时优先读取源码索引，避免凭记忆猜类名、配置项或接入方式。
+
+## 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-duckdb`
+
+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 is DuckDB datasource setup, report table query, column data modeling, or quality/report data analysis.
+2. Read `references/source-index.md`, then inspect `DefaultDuckDataSource`, `ReportTable`, `ReportTableQuery`, `ReportData`, and `ColumnDataModel`.
+3. Use this skill for the standalone DuckDB quality/report-table component; load `yss-report` when the task is report template/export integration.
+4. Keep embedded/temporary database lifecycle explicit: connection creation, table creation, file cleanup, and query scope.
+5. Validate SQL and data shape before running large local analytical queries.
+
+## Checklist
+
+- Required dependency or starter module is present.
+- DuckDB datasource lifecycle is clear.
+- Column metadata matches incoming report data.
+- Large datasets consider memory/temp-file behavior.
+- SQL is controlled by the application or validated before execution.
+- Result shape is mapped through existing report/quality models.
+
+## 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-duckdb/agents/openai.yaml

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

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

@@ -0,0 +1,34 @@
+# yss-duckdb 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-duckdb` (existed when indexed)
+
+## Documentation Files
+
+- No component documentation files found.
+
+## Maven Modules
+
+- `yss-microservice-components/yss-component-duckdb`
+
+## Key Java Entry Points
+
+- `yss-microservice-components/yss-component-duckdb/src/main/java/com/yss/cloud/quality/ColumnDataModel.java`
+- `yss-microservice-components/yss-component-duckdb/src/main/java/com/yss/cloud/quality/ReportData.java`
+- `yss-microservice-components/yss-component-duckdb/src/main/java/com/yss/cloud/quality/config/DefaultDuckDataSource.java`
+- `yss-microservice-components/yss-component-duckdb/src/main/java/com/yss/cloud/quality/duck/ReportTable.java`
+- `yss-microservice-components/yss-component-duckdb/src/main/java/com/yss/cloud/quality/duck/ReportTableQuery.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.