create-yss-spec 3.0.0 → 3.1.0

package/template/.hermes/skills/yss-web-controller/scripts/generate_controller.test.mjs

@@ -1,156 +0,0 @@
-import assert from "node:assert/strict";
-import { createHash } from "node:crypto";
-import { mkdir, mkdtemp, readFile, writeFile } from "node:fs/promises";
-import { tmpdir } from "node:os";
-import path from "node:path";
-import test from "node:test";
-import { fileURLToPath } from "node:url";
-import { generate, parseArgs } from "./generate_controller.mjs";
-
-const scripts = path.dirname(fileURLToPath(import.meta.url));
-const dtoWireProfileFile = path.resolve(scripts, "../../yss-dto/references/openapi-wire-profile.yaml");
-const dtoWireProfileDigest = createHash("sha256").update(await readFile(dtoWireProfileFile)).digest("hex");
-
-const metadataValue = {
-  tables: [{
-    table_name: "quality_rule",
-    table_comment: "质量规则",
-    columns: [
-      { name: "id", sql_type: "bigint", primary: true, nullable: false },
-      { name: "rule_name", sql_type: "varchar(64)", nullable: false }
-    ]
-  }]
-};
-
-function webContract(root, overrides = {}) {
-  return {
-    schema_version: 2,
-    contract_id: "slice-quality-web-1",
-    contract_version: 1,
-    current_version: 1,
-    slice_id: "quality-rule-create",
-    status: "approved",
-    integration_mode: "existing-project",
-    implementation_project_root: root,
-    base_package: "com.yss.demo",
-    module_name: "demo",
-    domain_segment: "quality",
-    application_service_package: "com.yss.demo.application.service",
-    architecture_profile: "target-domain-model",
-    platform_profile: "spring-boot-3-jdk17",
-    validation_namespace: "jakarta",
-    dto_placement: "web",
-    dto_wire_profile_ref: dtoWireProfileFile,
-    dto_wire_profile_digest: dtoWireProfileDigest,
-    openapi_freeze_ref: "openapi://quality-rule@1",
-    allowed_write_paths: [root],
-    expected_evidence_files: ["evidence/web-generation.json"],
-    verification_commands: ["./mvnw test", "./mvnw package"],
-    fields: {
-      quality_rule: {
-        create: ["rule_name"],
-        update: ["id", "rule_name"],
-        query: ["rule_name"],
-        pagination: ["pageIndex", "pageSize"],
-        response: ["id", "rule_name"]
-      }
-    },
-    ...overrides
-  };
-}
-
-async function fixture(overrides = {}) {
-  const root = await mkdtemp(path.join(tmpdir(), "yss-controller-"));
-  const metadata = path.join(root, "metadata.json");
-  const contract = path.join(root, "web-contract.json");
-  const output = path.join(root, "out");
-  await writeFile(metadata, JSON.stringify(metadataValue));
-  await writeFile(contract, JSON.stringify(webContract(root, overrides)));
-  const args = ["--metadata-file", metadata, "--contract-file", contract, "--dto-wire-profile-file", dtoWireProfileFile, "--base-package", "com.yss.demo", "--module-name", "demo", "--domain-segment", "quality", "--output-dir", output, "--application-service-package", "com.yss.demo.application.service", "--validation-namespace", overrides.validation_namespace ?? "jakarta"];
-  return { root, metadata, contract, output, args };
-}
-
-test("generates approved standalone Web code and exposes only approved pagination fields", async () => {
-  const data = await fixture();
-  await generate(parseArgs(data.args), { log() {}, warn() {} });
-  const rest = path.join(data.output, "com", "yss", "demo", "rest");
-  const controller = await readFile(path.join(rest, "QualityRuleController.java"), "utf8");
-  const convertor = await readFile(path.join(rest, "convertor", "QualityRuleWebConvertor.java"), "utf8");
-  const createRequest = await readFile(path.join(rest, "dto", "request", "QualityRuleCreateRequest.java"), "utf8");
-  const pageRequest = await readFile(path.join(rest, "dto", "request", "QualityRulePageRequest.java"), "utf8");
-  assert.match(controller, /import com\.yss\.demo\.application\.service\.QualityRuleService;/);
-  assert.match(controller, /SingleResult\.of\(/);
-  assert.match(controller, /import jakarta\.validation\.Valid;/);
-  assert.match(convertor, /@Mapper\(componentModel = "spring"\)/);
-  assert.match(convertor, /PageResult\.of\(\s*toResponses\(source\.getData\(\)\),\s*source\.getTotalCount\(\),\s*source\.getPageSize\(\),\s*source\.getPageIndex\(\)/s);
-  assert.doesNotMatch(`${controller}\n${convertor}`, /Gateway|\.domain\.|Mappers\.getMapper|INSTANCE/);
-  assert.match(createRequest, /private String ruleName;/);
-  assert.doesNotMatch(createRequest, /private Long id;|@Data/);
-  assert.match(pageRequest, /private int pageIndex = 1;/);
-  assert.match(pageRequest, /private int pageSize = 10;/);
-  assert.doesNotMatch(pageRequest, /orderBy|orderDirection|groupBy|offset|needTotalCount|tempTotalCount|extends PageQuery/);
-});
-
-test("rejects a yss-dto wire profile whose digest differs from the approved contract", async () => {
-  const data = await fixture({ dto_wire_profile_digest: "0".repeat(64) });
-  await assert.rejects(() => generate(parseArgs(data.args), { log() {}, warn() {} }), /yss-dto wire profile digest/);
-});
-
-test("rejects missing CLI arguments, schema v1, draft contracts, and inconsistent platform profiles", async () => {
-  assert.throws(() => parseArgs(["--module-name", "demo"]), /required/);
-  const v1 = await fixture({ schema_version: 1 });
-  await assert.rejects(() => generate(parseArgs(v1.args), { log() {}, warn() {} }), /schema_version=1.*unsupported/);
-  const draft = await fixture({ status: "draft" });
-  await assert.rejects(() => generate(parseArgs(draft.args), { log() {}, warn() {} }), /approved/);
-  const mismatch = await fixture({ platform_profile: "spring-boot-3-jdk17", validation_namespace: "javax" });
-  await assert.rejects(() => generate(parseArgs(mismatch.args), { log() {}, warn() {} }), /platform_profile and validation_namespace/);
-  assert.throws(() => parseArgs([...draft.args, "--force"]), /initialize-only/);
-});
-
-test("binds identity and every target to the approved write scope before writing", async () => {
-  const data = await fixture();
-  await assert.rejects(() => generate(parseArgs(data.args.map((value) => value === "demo" ? "other" : value)), { log() {}, warn() {} }), /approved web generation contract/);
-  await writeFile(data.contract, JSON.stringify(webContract(data.root, { allowed_write_paths: [path.join(data.root, "different-root")] })));
-  await assert.rejects(() => generate(parseArgs(data.args), { log() {}, warn() {} }), /allowed_write_paths/);
-  await writeFile(data.contract, JSON.stringify(webContract(data.root)));
-  const existing = path.join(data.output, "com/yss/demo/rest/QualityRuleController.java");
-  await mkdir(path.dirname(existing), { recursive: true });
-  await writeFile(existing, "user-owned\n");
-  await assert.rejects(() => generate(parseArgs(data.args), { log() {}, warn() {} }), /initialize-only/);
-  assert.equal(await readFile(existing, "utf8"), "user-owned\n");
-  await assert.rejects(() => readFile(path.join(data.output, "com/yss/demo/rest/convertor/QualityRuleWebConvertor.java"), "utf8"), /ENOENT/);
-});
-
-test("scaffold-v2 mode requires an empty-scaffold-verified manifest with matching profile and project layout", async () => {
-  const data = await fixture({ platform_profile: "spring-boot-2.7-jdk8", validation_namespace: "javax" });
-  const projectRoot = path.join(data.root, "demo-service");
-  const webProject = path.join(projectRoot, "demo-service-adapter", "demo-service-web");
-  const manifest = path.join(projectRoot, ".yss", "scaffold-generation.json");
-  await mkdir(path.dirname(manifest), { recursive: true });
-  await writeFile(manifest, JSON.stringify({ schema_version: 2, project_name: "demo-service", base_package: "com.yss.demo", completion_level: "empty-scaffold-verified", profiles: { architecture: "target-domain-model", platform: "spring-boot-2.7-jdk8", validation_namespace: "javax", dto_placement: "web" } }));
-  const contractValue = webContract(projectRoot, {
-    integration_mode: "scaffold-v2",
-    implementation_project_root: projectRoot,
-    scaffold_manifest_ref: manifest,
-    platform_profile: "spring-boot-3-jdk17",
-    validation_namespace: "jakarta",
-    allowed_write_paths: [path.join(webProject, "src/main/java/com/yss/demo/rest")]
-  });
-  await writeFile(data.contract, JSON.stringify(contractValue));
-  const args = ["--metadata-file", data.metadata, "--contract-file", data.contract, "--dto-wire-profile-file", dtoWireProfileFile, "--scaffold-manifest-file", manifest, "--base-package", "com.yss.demo", "--module-name", "demo", "--domain-segment", "quality", "--web-project-dir", webProject, "--application-service-package", "com.yss.demo.application.service", "--validation-namespace", "jakarta"];
-  await assert.rejects(() => generate(parseArgs(args), { log() {}, warn() {} }), /scaffold manifest.*platform/i);
-  contractValue.platform_profile = "spring-boot-2.7-jdk8";
-  contractValue.validation_namespace = "javax";
-  await writeFile(data.contract, JSON.stringify(contractValue));
-  await generate(parseArgs(args.map((value) => value === "jakarta" ? "javax" : value)), { log() {}, warn() {} });
-});
-
-test("rolls back files written before a filesystem failure", async () => {
-  const data = await fixture();
-  const rest = path.join(data.output, "com/yss/demo/rest");
-  await mkdir(rest, { recursive: true });
-  await writeFile(path.join(rest, "convertor"), "blocking-file\n");
-  await assert.rejects(() => generate(parseArgs(data.args), { log() {}, warn() {} }));
-  await assert.rejects(() => readFile(path.join(rest, "QualityRuleController.java"), "utf8"), /ENOENT/);
-  assert.equal(await readFile(path.join(rest, "convertor"), "utf8"), "blocking-file\n");
-});

package/template/.hermes/skills/ytable-usage/SKILL.md

@@ -1,251 +0,0 @@
----
-name: ytable-usage
-description: 指导 YSS UI 业务列表页、CRUD 表格、远程分页、操作列、气泡确认、列筛选、字典翻译、行拖拽、工具栏和自定义插槽正确使用 @yss-ui/components 的 YTable；当需要配置 YTableColumn、YTableActionConfig、pagination、filter-change 或表格实例方法时使用。
----
-
-# YTable 使用
-
-## 触发条件
-
-- 生成或修改业务列表、CRUD 表格、远程分页、操作列、列筛选、工具栏或行拖拽。
-- 需要配置 `YTableColumn`、`YTableActionConfig`、分页状态或表格实例方法。
-
-## 不适用场景
-
-- 可编辑表格是核心需求：使用 `../yedit-table-usage/SKILL.md`。
-- 页面只有短小静态数据且不需要表格交互。
-
-## 实施流程
-
-1. 当前会话可用 yss-ui MCP 时，先用 `get_component_docs` 查询 `YTable` 的 Props、Events、Slots、Types 与实例方法；需要远程分页、筛选、操作列、拖拽或工具栏时，再用 `get_demo` 获取对应官方 Demo。
-2. MCP 工具不可用、调用失败或用 `search_docs/list_components` 校正后仍无结果时，才读取最新 `llms-full.txt`；若文档与当前项目依赖版本不一致，用当前源码和导出核验。
-3. 把远程数据、`loading`、分页映射、API 调用和事件处理放入 Hook；把列定义和纯配置放入 `constant.ts`。
-4. 在模板中组合 `data/columns/loading/pagination`，并根据真实开启的工具栏和分页配置高度 Hook。
-5. 完成后核对删除确认、远程筛选、分页字段映射和 API 错误处理边界。
-
-## 硬约束（禁止/必须）
-
-- 必须从 `@yss-ui/components` 导入 `YTable`、`YTableColumn`、`YTableActionConfig` 等真实导出，不使用 `a-table` 实现业务主表格。
-- 远程分页状态使用 `current/pageSize/total/remote`，显式设置 `remote: true`；后端 `pageIndex/pageSize/totalCount` 只在 Hook 中映射。
-- 开启内置分页时传 `pageable`，受控更新使用 `v-model:pagination`，请求时机使用 `@page-change="handlePageChange"`。
-- `page-change` 事件参数固定为 `{ current: number, pageSize: number }`；回调必须读取 `current`，禁止写成组件不会派发的 `currentPage`。
-- YTable 没有 `request` 或 `searchParams` Props；远程查询由业务 Hook 管理。`refresh()` 是真实实例方法，内部调用 vxe-table `updateData()` 刷新当前表格数据，不等于重新调用后端接口。
-- 行键使用 `:row-config="{ keyField: 'id', useKey: true }"`，不臆造 `row-key` Prop。
-- 新增、导入、批量操作等主按钮直接放入 `#toolbar-right` 或 `#toolbar-left` 插槽即可自动渲染工具栏；**无需配置 `:toolbar-config="{ custom: true }"`**，避免无端展示列设置图标；**仅在业务明确需要列设置时才传入 `:toolbar-config="{ custom: true }"`**。
-- 删除、启停、发布等危险操作使用 `actionConfig.buttons[].isConfirm = true`，不默认使用 `Modal.confirm`。
-- 列配置超过 10 行时放入 `constant.ts`；需要调用组件 Hook 的操作配置使用工厂函数注入回调，禁止在 `constant.ts` 直接引用组件局部的 `openEdit/deleteItem`。
-- 远程筛选必须提供稳定 `filters`，设置 `filterMethod: () => true` 禁用本地二次过滤，并监听 `filter-change`。
-- 自适应滚动列表绑定 `:height="tableHeight"`；`pageable`、工具栏分别对应 `withPagination: true`、`withToolbar: true`。纯短表不强制引入高度 Hook。
-- `mutator.ts` 已对网络错误和 `success === false` 统一 `message.error` 并 reject。API Hook 不再检查 `success === false`，不在 `else/catch` 重复 `message.error`；用 `finally` 恢复 loading，让异常继续中断流程。
-
-## 标准代码骨架
-
-```typescript
-import type { YTableActionConfig, YTableColumn } from '@yss-ui/components';
-
-/** 列表行数据。 */
-export interface ItemRow {
-  id: string;
-  name: string;
-  status: string;
-}
-
-/** 状态字典。 */
-export const STATUS_OPTIONS = [
-  { label: '启用', value: '1' },
-  { label: '停用', value: '0' },
-];
-
-/** 列表固定列配置。 */
-export const TABLE_COLUMNS: YTableColumn[] = [
-  { type: 'seq', title: '序号', width: 70 },
-  { field: 'name', title: '名称', minWidth: 180 },
-  { field: 'status', title: '状态', width: 120, isTransform: true },
-  { type: 'action', title: '操作', width: 180 },
-];
-
-/** 按组件 Hook 提供的回调创建操作列配置。 */
-export const createActionConfig = (handlers: {
-  onEdit: (row: ItemRow) => void;
-  onDelete: (row: ItemRow) => Promise<void>;
-}): YTableActionConfig => ({
-  width: 180,
-  fixed: 'right',
-  buttons: [
-    { value: 'edit', label: '编辑', type: 'link', click: ({ row }) => handlers.onEdit(row) },
-    {
-      value: 'delete',
-      label: '删除',
-      type: 'link',
-      isConfirm: true,
-      confirmProps: { title: '确认删除该数据吗？', okText: '确定', cancelText: '取消' },
-      click: ({ row }) => handlers.onDelete(row),
-    },
-  ],
-});
-```
-
-## 远程分页 Hook 关键模式
-
-```typescript
-import { ref } from 'vue';
-import type { YTablePagination } from '@yss-ui/components';
-import type { ItemRow } from '../constant';
-
-/** 列表 API 依赖，由当前项目的 Orval 函数适配。 */
-export interface ItemListApi {
-  queryPage: (params: { pageIndex: number; pageSize: number }) => Promise<{
-    list?: ItemRow[];
-    totalCount?: number;
-  }>;
-  deleteItem: (params: { id: string }) => Promise<unknown>;
-}
-
-/** 管理 YTable 远程分页和删除刷新。 */
-export const useItemList = (api: ItemListApi) => {
-  const dataList = ref<ItemRow[]>([]);
-  const loading = ref(false);
-  const pagination = ref<YTablePagination>({ current: 1, pageSize: 20, total: 0, remote: true });
-
-  /** 查询当前页；错误提示由 mutator 统一处理。 */
-  const loadList = async () => {
-    loading.value = true;
-    try {
-      const result = await api.queryPage({
-        pageIndex: pagination.value.current,
-        pageSize: pagination.value.pageSize,
-      });
-      dataList.value = result.list ?? [];
-      pagination.value = { ...pagination.value, total: result.totalCount ?? 0 };
-    } finally {
-      loading.value = false;
-    }
-  };
-
-  /** 同步 YTable 分页状态并重新查询。 */
-  const handlePageChange = async ({ current, pageSize }: { current: number; pageSize: number }) => {
-    pagination.value = { ...pagination.value, current, pageSize };
-    await loadList();
-  };
-
-  /** 删除后刷新列表；不重复弹出 API 错误。 */
-  const handleDelete = async (row: ItemRow) => {
-    await api.deleteItem({ id: row.id });
-    await loadList();
-  };
-
-  return { dataList, loading, pagination, loadList, handlePageChange, handleDelete };
-};
-```
-
-```vue
-<script setup lang="ts">
-import { onMounted, ref } from 'vue';
-import { YButton, YTable } from '@yss-ui/components';
-import { useTableHeight } from '@yss-ui/hooks';
-import { createActionConfig, STATUS_OPTIONS, TABLE_COLUMNS, type ItemRow } from './constant';
-import { useItemList, type ItemListApi } from './hooks/useItemList';
-
-/** 列表实例的 API 依赖。 */
-interface Props {
-  api: ItemListApi;
-}
-
-const props = defineProps<Props>();
-const emit = defineEmits<{
-  create: [];
-  edit: [row: ItemRow];
-}>();
-const tableAreaRef = ref<HTMLDivElement>();
-const { tableHeight } = useTableHeight(tableAreaRef, { withPagination: true, withToolbar: true });
-const { dataList, loading, pagination, loadList, handlePageChange, handleDelete } = useItemList(props.api);
-const actionConfig = createActionConfig({
-  onEdit: row => emit('edit', row),
-  onDelete: handleDelete,
-});
-
-onMounted(loadList);
-</script>
-
-<template>
-  <div ref="tableAreaRef" class="table-area">
-    <YTable
-      :data="dataList"
-      :columns="TABLE_COLUMNS"
-      :action-config="actionConfig"
-      :loading="loading"
-      :options-map="{ status: STATUS_OPTIONS }"
-      :row-config="{ keyField: 'id', useKey: true }"
-      :height="tableHeight"
-      pageable
-      v-model:pagination="pagination"
-      @page-change="handlePageChange"
-    >
-      <template #toolbar-right>
-        <YButton type="primary" @click="emit('create')">新增</YButton>
-      </template>
-    </YTable>
-  </div>
-</template>
-
-<style scoped lang="less">
-@import './style.less';
-</style>
-```
-
-```less
-/* style.less */
-.table-area {
-  height: 100%;
-  min-height: 0;
-  overflow: hidden;
-}
-```
-
-## 表格多选与批量操作标准模式
-
-当业务需要 Checkbox 多选与批量操作（如批量删除、批量导出、批量启用）时，遵循以下规范：
-
-1. **列配置**：首列必须声明 `{ type: 'checkbox', width: 50, fixed: 'left', align: 'center' }`。
-2. **行唯一键**：必须显式指定 `:row-config="{ keyField: 'id', useKey: true }"`（`keyField` 与业务主键如 `userCode` 对齐）。
-3. **受控双向绑定**：推荐优先使用 `v-model:selected-row-keys="selectedRowKeys"` 或 `v-model:selected-rows="selectedRows"`，或者统一监听 `@selection-change`。
-4. **批量操作按钮**：放在 `#toolbar-right`，并配置 `:disabled="selectedRowKeys.length === 0"`。
-5. **清空选中态**：批量操作成功后，直接重置 `selectedRowKeys.value = []` 或调用 `tableRef.value.clearSelection()`。
-
-```vue
-<YTable
-  ref="tableRef"
-  v-model:selected-row-keys="selectedRowKeys"
-  :row-config="{ keyField: 'id', useKey: true }"
-  :data="dataList"
-  :columns="TABLE_COLUMNS"
-  pageable
-  v-model:pagination="pagination"
-  @page-change="handlePageChange"
->
-  <template #toolbar-right>
-    <YButton :disabled="selectedRowKeys.length === 0" @click="handleBatchDelete">批量删除</YButton>
-  </template>
-</YTable>
-```
-
-## 插槽与实例边界
-
-- 优先使用 kebab-case：单元格 `#<field>`、表头 `#<field>-header`、筛选 `#<field>-filter`、工具栏 `#toolbar-left/#toolbar-right`、展开行 `#expand-row`、分组表头 `#group-header`、更多图标 `#action-more-icon`。
-- `getTableInstance()`、`refresh()`、`recalculate()`、`clearSelection()`、`getSelectedRows()`、`getSelectedRowKeys()`、`setSelection()`、`getPaginationInstance()` 是真实暴露方法；只在对应语义下使用。
-
-## 交付检查清单
-
-- [ ] 分页状态和 `page-change` 参数均使用 `current/pageSize`，未使用 `currentPage`；`filter-change` 与 YTable 真实 API 一致。
-- [ ] 多选列已配置 `type: 'checkbox'`，已设置 `:row-config="{ keyField: 'xxx', useKey: true }"`，批量按钮绑定了 `selectedRowKeys.length === 0` 禁用。
-- [ ] 批量操作成功后已重置 `selectedRowKeys` 并调用 `tableRef.clearSelection()`。
-- [ ] 未使用虚构 `request/searchParams/row-key` Props，也未把 `refresh()` 当成远程请求。
-- [ ] 工具栏、字典翻译、操作确认与高度偏移均与实际开关一致。
-- [ ] API Hook 没有 `success === false` 分支或重复 `message.error`。
-
-## 失败兜底策略
-
-- 分页字段混乱时，在 Hook 中分离 YTable 状态和后端参数，不直接把 `pageIndex/totalCount` 绑到组件。
-- 操作过多时使用 `displayLimit` 和更多菜单；远程刷新失效时回到业务 `loadList()`，不把实例 `refresh()` 当成接口请求。
-- API 失败后只在 `finally` 恢复本地 loading，让 mutator 的 reject 继续中断删除后刷新等后续流程。
-

package/template/.hermes/skills/ytree-usage/SKILL.md

@@ -1,132 +0,0 @@
----
-name: ytree-usage
-description: 指导 YSS UI 左树右表、组织树、分类树、目录树和节点管理页使用 @yss-ui/components 的 YTree，覆盖 fieldNames 字段映射、搜索过滤、受控选中、节点动作、删除确认、虚拟滚动和自适应高度；当生成或修改树形筛选、左树右表、树搜索或树节点操作时使用。
----
-
-# YTree 使用
-
-## 触发条件
-
-- 生成或修改左树右表、组织树、分类树、目录树、树搜索或树节点操作。
-- 需要配置 `fieldNames`、受控选中、`YTreeActionItem` 或树区域自适应高度。
-
-## 不适用场景
-
-- 树数据只用于表单 TreeSelect 字段：使用 `YFormily` 或对应表单规范。
-- 页面只有普通列表而没有层级筛选：使用 `../ytable-usage/SKILL.md`。
-
-## 实施流程
-
-1. 当前会话可用 yss-ui MCP 时，先用 `get_component_docs` 查询 `YTree` 的 Props、Slots、Events 和 `YTreeActionItem`；需要搜索、节点动作、受控选中或左树右表时，再用 `get_demo` 获取对应官方 Demo。
-2. MCP 工具不可用、调用失败或用 `search_docs/list_components` 校正后仍无结果时，才读取最新 `llms-full.txt`；若文档与当前项目依赖版本不一致，用当前源码和导出核验。
-3. 确定树数据的 title/key/children 字段、受控状态和选中后的业务联动。
-4. 按容器布局配置 `useTreeHeight`，再添加搜索和节点动作。
-5. 若包含删除，单独完成气泡确认链路；不把 `danger` 颜色当成二次确认。
-
-## 硬约束（禁止/必须）
-
-- 从 `@yss-ui/components` 导入 `YTree`、`YTreeActionItem` 等真实导出；高度使用 `@yss-ui/hooks` 的 `useTreeHeight`。
-- 数据字段不一致时配置 `fieldNames`，不为了改名重复递归复制树数据。
-- 搜索使用 `filterable + v-model:searchValue`；受控选中使用 `v-model:selectedKeys`。
-- 普通节点菜单使用 `showActions + getNodeActions`，并监听 `@action`。`YTreeActionItem` 只支持 `key/label/icon/disabled/danger`，禁止臆造 `isConfirm/click` 等字段。
-- `danger: true` 只改变危险项视觉，不会弹出确认框。删除必须放在节点附近的 `#node-suffix` 或当前选中节点操作区，用 Ant Design Vue `Popconfirm` 的 `@confirm` 调用接口；不使用居中 `Modal.confirm`。
-- 树区域需要滚动时绑定 `:height="treeHeight"`，不默认添加 `:virtual="true"`。只有展开后可见扁平节点数 `* itemHeight > height` 时才会实际裁剪 DOM。
-- 使用 YTree 内置搜索时，高度 Hook 通过 `extraOffset: YTREE_SEARCH_HEIGHT` 扣除 48px；不再叠加无依据的魔法数。
-- 左树右表优先组合 `YSplitPane + YCard + YTree + YTable`；切换节点时同步查询条件并把右表分页重置为第 1 页。
-- 节点删除 API 的错误由 `mutator.ts` 统一提示并 reject；不在 `else/catch` 重复 `message.error`。
-
-## 标准代码骨架
-
-```vue
-<script setup lang="ts">
-import { ref } from 'vue';
-import { YTree, type YTreeActionItem } from '@yss-ui/components';
-import { useTreeHeight, YTREE_SEARCH_HEIGHT } from '@yss-ui/hooks';
-
-/** 树节点数据。 */
-interface TreeNode {
-  id: string;
-  name: string;
-  children?: TreeNode[];
-}
-
-const emit = defineEmits<{
-  create: [node: TreeNode];
-  edit: [node: TreeNode];
-}>();
-const treeAreaRef = ref<HTMLDivElement>();
-const treeData = ref<TreeNode[]>([]);
-const searchValue = ref('');
-const selectedKeys = ref<Array<string | number>>([]);
-const { treeHeight } = useTreeHeight(treeAreaRef, {
-  extraOffset: YTREE_SEARCH_HEIGHT,
-});
-
-/** 生成当前节点的非危险操作。 */
-const getNodeActions = (): YTreeActionItem[] => [
-  { key: 'add', label: '新增子节点' },
-  { key: 'edit', label: '编辑' },
-];
-
-/** 处理 YTree 动作事件。 */
-const handleTreeAction = ({ key, node }: { key: string; node: TreeNode }) => {
-  if (key === 'add') emit('create', node);
-  if (key === 'edit') emit('edit', node);
-};
-</script>
-
-<template>
-  <div ref="treeAreaRef" class="tree-area">
-    <YTree
-      :height="treeHeight"
-      :tree-data="treeData"
-      :field-names="{ title: 'name', key: 'id', children: 'children' }"
-      filterable
-      show-actions
-      v-model:searchValue="searchValue"
-      v-model:selectedKeys="selectedKeys"
-      :get-node-actions="getNodeActions"
-      @action="handleTreeAction"
-    />
-  </div>
-</template>
-
-<style scoped lang="less">
-@import './style.less';
-</style>
-```
-
-```less
-/* style.less */
-.tree-area {
-  flex: 1;
-  min-height: 0;
-  overflow: hidden;
-}
-```
-
-## 删除确认边界
-
-```vue
-<template #node-suffix="{ node }">
-  <Popconfirm title="确认删除该节点吗？" ok-text="确定" cancel-text="取消" @confirm="handleDelete(node)">
-    <YButton type="link" @click.stop>删除</YButton>
-  </Popconfirm>
-</template>
-```
-
-`Popconfirm` 从 `ant-design-vue` 导入，`YButton` 从 `@yss-ui/components` 导入。如果每个节点都展示删除会过密，把同样的 `Popconfirm` 放到选中节点的页面工具栏。
-
-## 交付检查清单
-
-- [ ] `fieldNames`、`searchValue`、`selectedKeys`、`action` 与真实 API 一致。
-- [ ] 节点动作项未出现虚构字段，删除不会点菜单后立即执行。
-- [ ] 高度偏移与内置搜索实际开关一致，没有多扣魔法数。
-- [ ] 左树选中后，右表查询条件和分页重置闭环清晰。
-
-## 失败兜底策略
-
-- 节点字段不统一时先修正 `fieldNames`，不复制整棵树换键。
-- 点击删除立即调用 API 时，移出节点动作菜单，改为节点附近或页面操作区 `Popconfirm`。
-- 传入 `height` 但节点未裁剪时，先核对展开后可见节点数、`itemHeight` 和阈值，不盲目强制 `virtual=true`。
-- 节点 API 失败后让 mutator reject 中断右表刷新等后续流程，不重复错误提示。

package/template/.kiro/settings/mcp.json

@@ -1,8 +0,0 @@
-{
-  "mcpServers": {
-    "yss-ui": {
-      "command": "npx",
-      "args": ["-y", "@yss-ui/mcp"]
-    }
-  }
-}

package/template/.pi/skills/ask-matt/PHASE-BOUNDARIES.md

@@ -1,55 +0,0 @@
-# Phase boundaries
-
-A **phase** is a chunk of work inside a session — the grilling, the implementation, the QA. The definition is fuzzy on purpose: a phase ends when you think *"ok, we're done with that"*.
-
-The **phase boundary** is the gap between two phases, and it is the only place this decision belongs. Mid-phase there is no decision to make — continue, or split the work that's left into subagents. Compacting mid-phase makes the agent lose the thread.
-
-## The five options
-
-| Option       | What it does                                                    |
-| ------------ | --------------------------------------------------------------- |
-| **Continue** | Stay in the session. No context switch at all.                    |
-| **`/clear`** | Empty the context window and start from nothing.                  |
-| **`/handoff`** | Write a portable markdown file and seed a session anywhere with it. |
-| **Subagent** | Send the task to its own context window and get a report back.     |
-| **`/compact`** | Compress this context and seed a fresh session with the summary.  |
-
-## The tree
-
-Work top to bottom at the boundary. The first **yes** wins.
-
-**1. Can you continue in this session?** Two things make the answer yes: the next phase needs this phase as a **primary source**, or you have enough [smart zone](https://www.aihero.dev/ai-coding-dictionary/smart-zone) left (~150k tokens) for the next phase to fit. Grilling → implementation is the standard yes: the implementation wants the reasoning verbatim, not a summary of it. Continue costs nothing and loses nothing, so rule it out before anything else.
-
-**2. Is the context irrelevant to what comes next?** Is everything in this session — the exploration, the decisions, the dead ends — disposable? If so, **`/clear`**. It is the cheapest move on the board: it takes no time and hands back the whole window. `/clear` also isn't terminal — the old session stays resumable.
-
-The cost of getting this wrong is one-way. Clear a *relevant* context and you lose the **why** behind what you built, and no amount of reading the diff back gets it returned.
-
-**3. Do you need to hand off?** `/handoff` is narrow. You need it only when you are:
-
-- swapping to a **new harness** (Claude → Codex),
-- moving to a **new directory** or repo,
-- sending the work to a **colleague**,
-- or forking a side task you found **mid-phase** without derailing what you're doing.
-
-That list is the whole clause. What `/handoff` buys is **portability** — a file that travels. If nothing is travelling, you don't need it.
-
-**4. Can the task be done AFK?** Is it scoped tightly enough to run with you away from the keyboard, no steering? Then send it to a **subagent** and leave this session untouched. Automated review is the standard case: the agent reads the diff and reports, and you aren't needed while it does.
-
-**5. Otherwise, `/compact`.** Relevant context, same harness, same directory, and you need to stay in the loop — this is where the tree lands, and it lands here often. Pass it an instruction (`/compact we're going to QA this area`) so the summary keeps what the next phase needs.
-
-`/compact` is the **default, not the first reach**. It sits at the bottom because the four questions above it are all cheaper or more precise. The failure mode when people start here is a fresh session that is confidently wrong about a decision the summary flattened.
-
-## Primary and secondary sources
-
-Every move except **Continue** turns a **primary source** into a **secondary source** — the session as it happened, replaced by a summary of it. The trade is always the same shape:
-
-| Source                            | Information | Noise | Room to move |
-| --------------------------------- | ----------- | ----- | ------------ |
-| Primary (Continue)                | Full        | Lots  | Little       |
-| Secondary (`/compact`, `/handoff`) | Lossy       | Less  | Lots         |
-
-This is why question 1 comes first. You only pay the lossiness when staying costs more than it saves.
-
-## These are judgement calls
-
-The questions are not objective — each has taste in it, and the same boundary can go two ways on two days. The value is in asking them **in order**, at the boundary rather than in the middle of the work.