create-yss-spec 3.5.3 → 3.5.5

package/template/.agents/skills/wayfinder/references/chart-map.md

@@ -0,0 +1,14 @@
+# 建立决策地图
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。仓库脚本与 pnpm 命令从当前登记的项目根目录执行。
+
+### Chart the map
+
+User invokes with a loose idea.
+
+1. **Name the destination.** Run a `/grilling` and `/domain-modeling` session to pin down what this map is finding its way to — the spec, decision, or change. The destination fixes the scope, so it's settled first.
+2. **Map the frontier.** Grill again, **breadth-first** this time: fan out across the whole space rather than deep on any one thread, surfacing the open decisions and the first steps takeable now. **If this surfaces no fog** — the way to the destination is already clear, the whole journey small enough for one session — you don't need a map. Stop and ask the user how they'd like to proceed.
+3. **Create the map** (label `wayfinder:map`): Destination and Notes filled in, Decisions-so-far empty, the fog sketched into **Not yet specified**.
+4. **Create the tickets you can specify now** as child issues of the map — then wire blocking edges in a **second pass** (issues need ids before they can reference each other). Wiring sorts them into the frontier and the blocked; everything you can't yet specify stays in the fog — the **Not yet specified** section.
+5. **Fire the research subagents.** For each `research` ticket you just created, spin up a `/yss-research` subagent to resolve it in parallel, capturing its findings on a throwaway `research/<name>` branch with a context pointer from the ticket. `/research` remains only as a deprecated compatibility alias.
+6. Stop — charting is one session's work; it hand-resolves nothing.

package/template/.agents/skills/wayfinder/references/map-format.md

@@ -0,0 +1,49 @@
+# 决策地图与 Ticket 结构
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。仓库脚本与 pnpm 命令从当前登记的项目根目录执行。
+
+### The map body
+
+The whole map at low resolution, loaded once per session. Open tickets are **not** listed — they are open child issues, found by query.
+
+```markdown
+## Destination
+
+<what reaching the end of this map looks like — the spec, decision, or change this effort is finding its way to. One or two lines; every session orients to it before choosing a ticket.>
+
+## Notes
+
+<domain; skills every session should consult; standing preferences for this effort>
+
+## Decisions so far
+
+<!-- the index — one line per closed ticket: enough to judge relevance, then zoom the link for the detail the ticket holds -->
+
+- [<closed ticket title>](../link) — <one-line gist of the answer>
+
+## Not yet specified
+
+<!-- see "Fog of war": in-scope fog you can't ticket yet; graduates as the frontier advances -->
+
+## Out of scope
+
+<!-- see "Out of scope": work ruled beyond the destination; closed, never graduates -->
+```
+
+### Tickets
+
+Each ticket is a **child issue** of the map; the tracker's issue id is its identity. Its body is the question, bounded by a coherent decision and the current runtime/context capacity:
+
+```markdown
+## Question
+
+<the decision or investigation this ticket resolves>
+```
+
+Each ticket carries a `wayfinder:<type>` label — one of `research`, `prototype`, `grilling`, `task` (see [Ticket Types](ticket-types.md#ticket-types)).
+
+A session **claims** a ticket by assigning it to the dev driving the map, **first**, before any work, so concurrent sessions skip it. That assignee _is_ the claim: an open, unassigned ticket is unclaimed.
+
+Blocking uses the tracker's **native** dependency relationship — essential because it renders the frontier _visually_ in the tracker's own UI, so the human sees what's takeable without opening the map. Only a tracker that lacks native blocking falls back to a body convention. A ticket is **unblocked** when every ticket blocking it is closed; the **frontier** is the open, unblocked, unclaimed children — the edge of the known.
+
+The answer isn't part of the body — it's recorded on resolution (see [Work through the map](work-map.md#work-through-the-map)). Assets created while resolving a ticket are linked from the issue, not pasted in.

package/template/.agents/skills/wayfinder/references/scope-and-frontier.md

@@ -0,0 +1,24 @@
+# 范围与决策前沿
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。仓库脚本与 pnpm 命令从当前登记的项目根目录执行。
+
+## Fog of war
+
+The map is _deliberately_ incomplete: don't chart what you can't yet see. Beyond the live tickets lies the **fog of war** — the dim view of decisions and investigations you can tell are coming but can't yet pin down, because they hang on questions still open. Resolving a ticket clears the fog ahead of it, graduating whatever's now specifiable into fresh tickets — one at a time, until the way to the destination is clear and no tickets remain.
+
+The map's **Not yet specified** section is where that dim view is written down: the suspected question, the area to revisit later. It's the undiscovered frontier _toward_ the destination — everything here is in scope, just not sharp enough to ticket. Write as loosely or as fully as the view allows; it doubles as a signpost for collaborators reading where the effort is headed.
+
+**Fog or ticket?** The test is whether you can state the question precisely now — _not_ whether you can answer it now.
+
+- **Ticket when** the question is already sharp — even if it's blocked and you can't act on it yet.
+- **Not yet specified when** you can't yet phrase it that sharply. Don't pre-slice the fog into ticket-sized pieces: it's coarser than a ticket, and one patch may graduate into several tickets, or none, once the frontier reaches it.
+
+**Not yet specified** excludes what's already decided (Decisions so far), what's already a live ticket, and what's out of scope (the next section).
+
+## Out of scope
+
+Fog only ever gathers _toward_ the destination. The destination fixes the scope, so work beyond it is **out of scope** — it isn't fog, and it doesn't belong in **Not yet specified**. It gets its own **Out of scope** section on the map: work you've consciously ruled out of _this_ effort. Scope, not sharpness, lands it here.
+
+Out-of-scope work never graduates — the frontier stops at the destination — so it returns only if the destination is redrawn, and then as a fresh effort, not a resumption.
+
+Ruling something out of scope is a scoping act, not a step on the route. When a ticket that already exists turns out to sit past the destination — mis-scoped in while charting, or exposed by a resolution — **close it** (a closed ticket is unambiguously off the frontier) and leave one line in the **Out of scope** section: the gist plus why it's out of scope, linking the closed ticket. It stays out of **Decisions so far**, which records the route actually walked — a scope boundary isn't a step on it.

package/template/.agents/skills/wayfinder/references/ticket-types.md

@@ -0,0 +1,12 @@
+# 决策 Ticket 类型
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。仓库脚本与 pnpm 命令从当前登记的项目根目录执行。
+
+## Ticket Types
+
+Every ticket is either **HITL** — human in the loop, worked _with_ a human who speaks for themselves — or **AFK**, driven by the agent alone. A HITL ticket only resolves through that live exchange; the agent never stands in for the human's side of it (a grilling agent that answers its own questions has broken this).
+
+- **Research** (AFK): Reading documentation, third-party APIs, or local resources like knowledge bases to surface a fact a decision waits on. Resolved by a `/yss-research` **subagent** (`/research` is a deprecated alias). Use when knowledge outside the current working directory is required.
+- **Prototype** (HITL): Raise the fidelity of the discussion by making a cheap, rough, concrete artifact to react to — an outline, a rough take, a stub, or UI/logic code via the /prototype skill. Links the prototype as an asset. Use when "how should it look" or "how should it behave" is the key question.
+- **Grilling** (HITL): Conversation. The default case. Always invoke the /grilling and /domain-modeling skills.
+- **Task** (HITL or AFK): Manual work that must happen before a _decision_ can be made — nothing to decide, prototype, or research, but the discussion is blocked until it's done. Signing up for a service so its API can be judged, provisioning access, moving data so its shape can be seen. This is the one type that _does_ rather than decides — and it earns its place by unblocking a decision, not by delivering the destination. The agent drives it alone where it can (AFK); otherwise it hands the human a precise checklist (HITL). Resolved when the work is done; the answer records what was done and any resulting facts (credentials location, new URLs, row counts) later tickets depend on.

package/template/.agents/skills/wayfinder/references/work-map.md

@@ -0,0 +1,15 @@
+# 推进决策地图
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。仓库脚本与 pnpm 命令从当前登记的项目根目录执行。
+
+### Work through the map
+
+User invokes with a map (URL or number). A ticket is **optional** — without one, you pick the next decision, not the user.
+
+1. Load the **map** — the low-res view, not every ticket body.
+2. Choose the ticket. If the user named one, use it. Otherwise take the first frontier ticket in order. **Claim it**: assign it to yourself before any work.
+3. Resolve it — **zoom as needed**: fetch the full body of any related or closed ticket on demand; invoke the skills the `## Notes` block names. If in doubt, use `/grilling` and `/domain-modeling`.
+4. Record the resolution: post the answer as a **resolution comment**, **close** the issue, and **append a context pointer** to the map's Decisions-so-far.
+5. Add newly-surfaced tickets (create-then-wire); graduate any fog the answer has made specifiable, clearing each graduated patch from **Not yet specified** so it lives only as its new ticket. If the answer reveals a ticket — this one or another — sits beyond the destination, **rule it out of scope** rather than resolving it on the route. If the decision invalidates other parts of the map, update or delete those tickets.
+
+The user may run unblocked tickets in parallel, so expect other sessions to be editing the tracker concurrently.

package/template/.agents/skills/writing-for-agents/SKILL-MECHANICS.md

@@ -1,22 +1,31 @@
 # Skill mechanics
 
-The skill-specific branch of [`writing-for-agents`](SKILL.md): what changes when the document is a skill — frontmatter, the invocation choice, and router skills. Everything else about writing it is the universal reference in `SKILL.md`.
+Read this reference when designing a skill's invocation policy or shared dependencies. The host repository owns authorization and lifecycle rules; runtime metadata expresses only the capabilities that the installed host actually supports.
 
-## Invocation
+## Keep the decisions separate
 
-Two choices, trading the two loads:
+- **Discovery** makes an entry available through a catalog, description or explicit command. Keep the required `name` and `description` even when automatic selection is disabled.
+- **Automatic selection** lets the model choose a relevant entry. A precise description helps selection; it does not grant permission to run commands or change files.
+- **Explicit invocation** follows the host's supported user entry. Do not assume that a natural-language mention and a slash command behave identically on every host.
+- **Reading dependencies** loads an authorized reference or shared contract. Disabling automatic selection does not by itself make that file unreadable.
+- **Executing actions** still requires the repository's current scope, prerequisites and user authorization. Reading a commit contract does not authorize a commit.
 
-- A **model-invoked** skill keeps a `description`, so the agent can fire it autonomously — and other skills can reach it. You can still type its name: model-invocation always _includes_ user reach; a description only ever adds agent discovery, never removes the human's. The description is the skill's top-level context pointer, forced to stay loaded at all times — permanent context load in exchange for discoverability. A model-invoked skill whose content is all reference is also one home for shared reference: another skill can invoke it, so reference needed by several skills lives in one place. Mechanics: omit `disable-model-invocation`, and write a model-facing description carrying the trigger branches (the pointer-writing rules in `SKILL.md` apply in full).
-- A **user-invoked** skill strips the description from the agent's reach: only the human typing its name can invoke it, and no other skill can. Zero context load, but it spends cognitive load — you are the index that must remember it exists. Mechanics: set `disable-model-invocation: true`; the `description` becomes human-facing — a one-line summary, trigger lists stripped.
+## Express policy for the target host
 
-Pick model-invocation only when the agent must reach the skill on its own, or another skill must. If it only ever fires by hand, make it user-invoked and pay no context load.
+`description`, `disable-model-invocation` and `agents/openai.yaml` are not interchangeable controls. The frontmatter field is interpreted by hosts that support it; Codex has its own `policy.allow_implicit_invocation` metadata. A generated projection proves that files were distributed, not that another host enforces the same policy.
 
-Shared reference that two user-invoked skills both need can live in neither — with no descriptions, neither can fire the other. Push it to a plain file outside the skill system: external reference any skill can point at.
+For YSS registry and metadata consistency, use [the maintained authoring contract](../maintaining-skills/references/authoring.md). Preserve existing interface and dependency metadata. Verify the actual installed host's catalog and invocation behavior; record unsupported or unknown capabilities instead of treating an ignored field as enforcement.
 
-## Splitting by invocation
+Do not claim that a description is always loaded, that explicit-only skills have zero context cost, or that a policy field is a filesystem sandbox. Measure observable reads and runtime usage for the task being optimized, and leave absent telemetry unknown.
 
-The invocation cut of splitting (the sequence cut lives in `SKILL.md`): split off a model-invoked skill when you have a distinct leading word that should trigger it on its own — a trigger word you actually use in your prompts — or another skill must reach it. You pay context load for the new always-loaded description, so that independent reach has to be worth it.
+## Share references without adding unintended entry points
 
-## Router skills
+An authorized public skill may read an internal contract by its registered path while that internal skill remains excluded from independent automatic selection. The YSS commit skills use this pattern with `git-commit-core`. Retain the public caller's action-authorization boundary and the dependency's ownership and distribution rules.
 
-When user-invoked skills multiply past what you can remember, that piled-up cognitive load is cured by a **router skill**: one user-invoked skill that names the others and when to reach for each, so the human has one skill to remember instead of many. It can only hint, never fire them: user-invoked skills have no description, so nothing but the human can reach them.
+Put shared material in a plain reference file or an internal skill according to its ownership and consumers. Neither location requires a new automatic workflow. Preserve the dependency closure, and do not publish a second copy that can drift independently.
+
+## Split and route by responsibility
+
+Create a separate discoverable skill when it has a distinct task, trigger and useful outcome. Move conditional detail into references when it serves the same task. Avoid mechanical splits based on leading words, length or assumptions about permanent context load.
+
+A router can explain which entry or reference applies. It must preserve host-specific explicit-invocation requirements and the repository's approval boundaries; routing alone cannot grant execution authority. Check a natural-language positive, a nearby non-trigger, explicit invocation and any affected dependency or authorization boundary.

package/template/.agents/skills/yedit-table-usage/SKILL.md

@@ -39,178 +39,11 @@ description: "配置或修复 YSS UI YEditTable 的行内编辑、候选联动
 - 自适应高度使用 `useTableHeight(tableAreaRef, options)` 并绑定 `:height="tableHeight"`；直接父容器必须可计算且设置 `min-height: 0`。若表格内容会反向撑开观察容器，改用稳定 `boundaryRef`；弹层展开后高度仍不准时才调用 `nextTick(recalculateHeight)`。
 - API 失败由 `mutator.ts` 统一提示并 reject。Hook 中不写 `success === false` 分支，不在 `else/catch` 重复 `message.error`；清理状态放在 `finally`。
 
-## 标准代码骨架
-
-```typescript
-import type { YEditTableColumn, YTableActionConfig } from '@yss-ui/components';
-
-/** 扩展属性行。 */
-export interface ExtRow {
-  id?: string;
-  _rowKey: string;
-  extName?: string;
-  extValues?: string[];
-  memo?: string;
-}
-
-/** 可编辑表格列。 */
-export const EDIT_COLUMNS: YEditTableColumn[] = [
-  {
-    field: 'extName',
-    title: '扩展属性',
-    minWidth: 220,
-    component: 'form-item-select',
-    props: { placeholder: '请选择扩展属性' },
-    customRule: (value, _row, _field, all) => {
-      if (!value) return { errMsg: '扩展属性不能为空' };
-      if (all.filter(item => item.extName === value).length > 1) return { errMsg: '扩展属性不能重复' };
-      return {};
-    },
-  },
-  {
-    field: 'extValues',
-    title: '扩展值',
-    minWidth: 240,
-    component: 'form-item-select',
-    props: { multiple: true, placeholder: '请选择扩展值' },
-    customRule: value =>
-      Array.isArray(value) && value.some(item => String(item).length > 100)
-        ? { errMsg: '单个扩展值最多 100 个字符' }
-        : {},
-  },
-  {
-    field: 'memo',
-    title: '备注',
-    minWidth: 240,
-    component: 'form-item-input',
-    props: { placeholder: '请输入备注' },
-    customRule: value => (String(value ?? '').length > 200 ? { errMsg: '最多 200 个字符' } : {}),
-  },
-  { type: 'action', title: '操作', width: 100, fixed: 'right' },
-];
-
-/** 表格字典数据；实际项目可由 Hook 响应式提供。 */
-export const EDIT_OPTIONS_MAP = {
-  extName: [
-    { label: '类型', value: 'type' },
-    { label: '级别', value: 'level' },
-  ],
-  extValues: [
-    { label: '默认', value: 'default' },
-    { label: '扩展', value: 'extended' },
-  ],
-};
-
-/** 创建前端新行。 */
-export const createEmptyRow = (): ExtRow => ({
-  _rowKey: `temp-${Date.now()}-${Math.random().toString(36).slice(2)}`,
-  extValues: [],
-});
-
-/** 创建带删除确认的操作配置。 */
-export const createActionConfig = (onDelete: (row: ExtRow) => void): YTableActionConfig => ({
-  buttons: [
-    {
-      value: 'delete',
-      label: '删除',
-      type: 'link',
-      isConfirm: true,
-      confirmProps: { title: '是否确认删除此条数据？', okText: '确定', cancelText: '取消' },
-      click: ({ row }) => onDelete(row),
-    },
-  ],
-});
-```
-
-```vue
-<script setup lang="ts">
-import { computed, ref } from 'vue';
-import { YEditTable } from '@yss-ui/components';
-import { createActionConfig, createEmptyRow, EDIT_COLUMNS, EDIT_OPTIONS_MAP, type ExtRow } from './constant';
-
-/** 组件模式。0-新增，1-编辑，2-查看。 */
-interface Props {
-  mode: 0 | 1 | 2;
-}
-
-const props = defineProps<Props>();
-const rows = ref<ExtRow[]>([]);
-const tableRef = ref<InstanceType<typeof YEditTable>>();
-const readonly = computed(() => props.mode === 2);
-const columns = computed(() => (readonly.value ? EDIT_COLUMNS.filter(column => column.type !== 'action') : EDIT_COLUMNS));
-const actionConfig = createActionConfig(row => {
-  rows.value = rows.value.filter(item => item._rowKey !== row._rowKey);
-});
-
-/** 处理组件 add 事件，显式更新 v-model:data。 */
-const handleAddRow = () => {
-  rows.value = [...rows.value, createEmptyRow()];
-};
-
-/** 校验全部编辑行。 */
-const validateRows = async (): Promise<boolean> => {
-  if (!tableRef.value) return false;
-  const { valid } = await tableRef.value.validate();
-  return valid;
-};
-</script>
-
-<template>
-  <YEditTable
-    ref="tableRef"
-    v-model:data="rows"
-    :columns="columns"
-    :action-config="actionConfig"
-    :options-map="EDIT_OPTIONS_MAP"
-    :row-config="{ keyField: '_rowKey', useKey: true }"
-    :table-config="{ editConfig: { trigger: 'click', mode: 'row', autoClear: false } }"
-    :disabled="readonly"
-    :addable="!readonly"
-    add-btn-text="添加一行"
-    add-position="bottom"
-    @add="handleAddRow"
-  />
-</template>
-
-<style scoped lang="less">
-@import './style.less';
-</style>
-```
-
-## Select 值类型边界
-
-```typescript
-/** allowCreate 对应 tags 模式，字段按数组存储。 */
-interface CreatableRow {
-  tags?: string[];
-}
-
-const creatableColumn: YEditTableColumn = {
-  field: 'tags',
-  title: '标签',
-  component: 'form-item-select',
-  props: { allowCreate: true, placeholder: '请选择或输入标签' },
-};
-```
-
-## 表头筛选
-
-```typescript
-const textFilterColumn: YEditTableColumn = {
-  field: 'columnName',
-  title: '目标列名称',
-  component: 'form-item-input',
-  filterable: true,
-  filters: [{ data: '' }],
-  filterMethod: ({ option, cellValue }) =>
-    String(cellValue ?? '').toLowerCase().includes(String(option?.data ?? '').trim().toLowerCase()),
-  filterRender: { name: 'VxeInput', props: { clearable: true, placeholder: '请输入关键词' } },
-};
-```
-
-- 远程筛选监听 `@filter-change`，并设置 `filterMethod: () => true` 禁用本地二次筛选。
-- 切换数据源或新增行后，可调用 `tableRef.value?.getTableInstance()?.clearFilter()`。
-- 只在面板高度定制时使用 `#<field>-filter`；修改 `option.data` 后调用 `updateFilterOptionStatus(option, !!option.data)` 同步状态。
+## 按需示例
+
+首次组织可编辑明细行、查看态或提交校验时，读取 [完整组合示例](references/editable-table-example.md)。
+
+需要可创建 Select 或表头筛选时，读取 [Select 与筛选示例](references/select-and-filter-examples.md)；行级候选与表头筛选仍是不同职责。
 
 ## 交付检查清单
 

package/template/.agents/skills/yedit-table-usage/references/editable-table-example.md

@@ -0,0 +1,141 @@
+# YEditTable 组合示例
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。示例代码属于目标工程，模块相对导入按所示文件位置解析。
+
+## 标准代码骨架
+
+```typescript
+import type { YEditTableColumn, YTableActionConfig } from '@yss-ui/components';
+
+/** 扩展属性行。 */
+export interface ExtRow {
+  id?: string;
+  _rowKey: string;
+  extName?: string;
+  extValues?: string[];
+  memo?: string;
+}
+
+/** 可编辑表格列。 */
+export const EDIT_COLUMNS: YEditTableColumn[] = [
+  {
+    field: 'extName',
+    title: '扩展属性',
+    minWidth: 220,
+    component: 'form-item-select',
+    props: { placeholder: '请选择扩展属性' },
+    customRule: (value, _row, _field, all) => {
+      if (!value) return { errMsg: '扩展属性不能为空' };
+      if (all.filter(item => item.extName === value).length > 1) return { errMsg: '扩展属性不能重复' };
+      return {};
+    },
+  },
+  {
+    field: 'extValues',
+    title: '扩展值',
+    minWidth: 240,
+    component: 'form-item-select',
+    props: { multiple: true, placeholder: '请选择扩展值' },
+    customRule: value =>
+      Array.isArray(value) && value.some(item => String(item).length > 100)
+        ? { errMsg: '单个扩展值最多 100 个字符' }
+        : {},
+  },
+  {
+    field: 'memo',
+    title: '备注',
+    minWidth: 240,
+    component: 'form-item-input',
+    props: { placeholder: '请输入备注' },
+    customRule: value => (String(value ?? '').length > 200 ? { errMsg: '最多 200 个字符' } : {}),
+  },
+  { type: 'action', title: '操作', width: 100, fixed: 'right' },
+];
+
+/** 表格字典数据；实际项目可由 Hook 响应式提供。 */
+export const EDIT_OPTIONS_MAP = {
+  extName: [
+    { label: '类型', value: 'type' },
+    { label: '级别', value: 'level' },
+  ],
+  extValues: [
+    { label: '默认', value: 'default' },
+    { label: '扩展', value: 'extended' },
+  ],
+};
+
+/** 创建前端新行。 */
+export const createEmptyRow = (): ExtRow => ({
+  _rowKey: `temp-${Date.now()}-${Math.random().toString(36).slice(2)}`,
+  extValues: [],
+});
+
+/** 创建带删除确认的操作配置。 */
+export const createActionConfig = (onDelete: (row: ExtRow) => void): YTableActionConfig => ({
+  buttons: [
+    {
+      value: 'delete',
+      label: '删除',
+      type: 'link',
+      isConfirm: true,
+      confirmProps: { title: '是否确认删除此条数据？', okText: '确定', cancelText: '取消' },
+      click: ({ row }) => onDelete(row),
+    },
+  ],
+});
+```
+
+```vue
+<script setup lang="ts">
+import { computed, ref } from 'vue';
+import { YEditTable } from '@yss-ui/components';
+import { createActionConfig, createEmptyRow, EDIT_COLUMNS, EDIT_OPTIONS_MAP, type ExtRow } from './constant';
+
+/** 组件模式。0-新增，1-编辑，2-查看。 */
+interface Props {
+  mode: 0 | 1 | 2;
+}
+
+const props = defineProps<Props>();
+const rows = ref<ExtRow[]>([]);
+const tableRef = ref<InstanceType<typeof YEditTable>>();
+const readonly = computed(() => props.mode === 2);
+const columns = computed(() => (readonly.value ? EDIT_COLUMNS.filter(column => column.type !== 'action') : EDIT_COLUMNS));
+const actionConfig = createActionConfig(row => {
+  rows.value = rows.value.filter(item => item._rowKey !== row._rowKey);
+});
+
+/** 处理组件 add 事件，显式更新 v-model:data。 */
+const handleAddRow = () => {
+  rows.value = [...rows.value, createEmptyRow()];
+};
+
+/** 校验全部编辑行。 */
+const validateRows = async (): Promise<boolean> => {
+  if (!tableRef.value) return false;
+  const { valid } = await tableRef.value.validate();
+  return valid;
+};
+</script>
+
+<template>
+  <YEditTable
+    ref="tableRef"
+    v-model:data="rows"
+    :columns="columns"
+    :action-config="actionConfig"
+    :options-map="EDIT_OPTIONS_MAP"
+    :row-config="{ keyField: '_rowKey', useKey: true }"
+    :table-config="{ editConfig: { trigger: 'click', mode: 'row', autoClear: false } }"
+    :disabled="readonly"
+    :addable="!readonly"
+    add-btn-text="添加一行"
+    add-position="bottom"
+    @add="handleAddRow"
+  />
+</template>
+
+<style scoped lang="less">
+@import './style.less';
+</style>
+```

package/template/.agents/skills/yedit-table-usage/references/select-and-filter-examples.md

@@ -0,0 +1,38 @@
+# YEditTable Select 与筛选示例
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。示例代码属于目标工程，模块相对导入按所示文件位置解析。
+
+## Select 值类型边界
+
+```typescript
+/** allowCreate 对应 tags 模式，字段按数组存储。 */
+interface CreatableRow {
+  tags?: string[];
+}
+
+const creatableColumn: YEditTableColumn = {
+  field: 'tags',
+  title: '标签',
+  component: 'form-item-select',
+  props: { allowCreate: true, placeholder: '请选择或输入标签' },
+};
+```
+
+## 表头筛选
+
+```typescript
+const textFilterColumn: YEditTableColumn = {
+  field: 'columnName',
+  title: '目标列名称',
+  component: 'form-item-input',
+  filterable: true,
+  filters: [{ data: '' }],
+  filterMethod: ({ option, cellValue }) =>
+    String(cellValue ?? '').toLowerCase().includes(String(option?.data ?? '').trim().toLowerCase()),
+  filterRender: { name: 'VxeInput', props: { clearable: true, placeholder: '请输入关键词' } },
+};
+```
+
+- 远程筛选监听 `@filter-change`，并设置 `filterMethod: () => true` 禁用本地二次筛选。
+- 切换数据源或新增行后，可调用 `tableRef.value?.getTableInstance()?.clearFilter()`。
+- 只在面板高度定制时使用 `#<field>-filter`；修改 `option.data` 后调用 `updateFilterOptionStatus(option, !!option.data)` 同步状态。

package/template/.agents/skills/yss-ddd-scaffold-generator/SKILL.md

@@ -23,27 +23,11 @@ description: 用于生成完整的 YSS DDD 多模块后端脚手架。当用户
 
 ## Spring Boot / Java 平台选择
 
-调用本技能前由生命周期编排器展示 `scripts/backend-platforms` 的精确版本清单及兼容状态，并通过 `gate.backend-architecture-platform-approved` 把架构、Spring Boot、Java 和 YSS 父 POM/BOM 合并展示、取得真实用户确认；生成器不提问、不猜版本、不使用 `x` 或 `latest`。已有批准且当前的选择展示摘要后复用；既有工程核验并复用登记值，不触发该门禁。
-
-- 精确候选版本与可选状态只读取 `scripts/backend-platforms` 和共享平台清单，不在此复制版本表；候选不等于可生成。
-- 独立子项目可继承主项目组合或覆盖，必须逐项目确认（允许一次确认明确列出的项目）；同一 Maven Reactor 使用一个平台。
-- 只开放共享兼容清单中已有真实 YSS 构建、依赖和启动证据的组合。缺少兼容父 POM、BOM、starter 或相应能力证据即 `blocked`；不替换官方组件、不降级回退。
-- 新生成合同必须有 `platform_configuration` v2，与架构决策、Maven 坐标及兼容条目摘要一致。Boot、Java、YSS 坐标或依赖配方变化时回生命周期重新确认并编译合同；仅追加同配置验证记录不重复确认，仍核验证据有效性。
-- Spring MVC、Servlet、Validation、Jackson 和 starter 坐标消费共享平台清单；Java 下限和允许组合由当前平台条目决定。Jakarta 转换不包括 `javax.sql` 等 Java SE API。
-- 平台候选维护验证产物标记 `platform_verification=candidate`，不能交给业务生成、升级完成等级或进入首切片验证。测试夹具不证明 YSS 兼容。
-
-版本清单、合同字段、候选验证和支持晋级规则见 仓库共享合同 `.template-spec/engineering/backend-platforms.md`。
+核验新工程平台时读取 [平台选择与证据](references/platform-selection.md)。只消费生命周期经 `gate.backend-architecture-platform-approved` 取得的真实用户确认和当前 `platform_configuration` v2；以 `scripts/backend-platforms` 的已验证可选组合为准。生成器不提问、不默认、不降级；缺证据即 `blocked`。
 
 ## 优先流程
 
-1. 确认服务级 `scaffold_request_id`、已通过 `gate.backend-architecture-platform-approved` 的 `domain-driven` 架构与精确 Spring Boot 版本选择及 digest、项目名、基础包名、Maven 项目坐标、父 POM GAV、YSS Components BOM 版本、输出目录和批准 Profile。Java `base_package` 与 Maven `group_id` 是两个独立输入，不得相互推导；脚手架发生在 Ticket 正式化前，不使用 `slice_id` 伪造切片身份。
-   Harness 内输出目录必须是 `apps/backend/` 容器，生成器再以 `project_name` 创建 `apps/backend/<project>/`；禁止使用 `app/backend/`、`app/frontend/` 或把 `apps/backend/` 之外的容器根当作后端项目根。
-2. 优先运行 `node scripts/generate_and_verify_scaffold.mjs`，在同一个受控工作流中生成骨架并执行真实 Maven 验证。`generate_scaffold.mjs` 只是底层生成原语，单独返回 0 不代表脚手架完成。
-3. 检查生成的模块名、POM、机械启动入口、基础配置文件和包路径。
-4. 受控工作流必须在生成项目根目录实际执行 `./mvnw validate`、`./mvnw test` 和 `./mvnw package`；三条命令全部返回 0 后才能报告完成。
-5. 三条 Wrapper 命令通过只得到 `empty-scaffold-verified`。如需声称已满足下游技能的首切片就绪条件，必须使用 `node scripts/run_first_slice_verification.mjs` 校验批准且版本当前的 Slice Implementation Contract、完整分层产物、当前合同 freshness 与根 Wrapper；只有验证器成功更新 Manifest 后才得到 `first-slice-verified`。
-
-受控验证命令由本 skill 的 `node scripts/run_scaffold_verification.mjs` 固定执行；验证器先检查 `.yss/scaffold-generation.json` 的合同元数据和 Wrapper、Java、项目级 Maven settings/profile、仓库凭据是否就绪，再在指定 evidence 目录写入每条命令的 stdout/stderr、`exit_code`、`failure_category`、耗时、执行时间和 `scaffold-verification.json`。仓库或凭据失败归为 `repository-access`，与 `project-model`、`compilation`、`bootstrap-entrypoint`、`test-failure`、`packaging` 分开；任何一条命令失败或未执行都必须阻断。
+合同与输出范围通过后，运行生成器前读取 [受控生成与验证](references/generation-workflow.md)。入口为 `scripts/generate_and_verify_scaffold.mjs`；根 `./mvnw validate/test/package` 必须真实执行并全部成功，仅获得 `empty-scaffold-verified`。首切片等级另由 `run_first_slice_verification.mjs` 核验。
 
 ## 推荐命令
 
@@ -60,6 +44,8 @@ description: 用于生成完整的 YSS DDD 多模块后端脚手架。当用户
 - `*-bootstrap` 下可被 Spring Boot Maven Plugin 发现的机械 `*Application` 启动入口
 - 基础配置、机械模板、构建脚本
 
+生成前预检与生成后内容验收须读取 [工程内容检查](references/engineering-checks.md)，并消费既有 [工程基线](references/engineering-baseline.md)。凭据仅从安全环境注入，日志须脱敏。
+
 ## 使用约束
 
 - 先在生命周期批准的脚手架受控生成合同下生成骨架，再做业务化定制；不要直接把脚手架当最终代码交付。
@@ -67,10 +53,7 @@ description: 用于生成完整的 YSS DDD 多模块后端脚手架。当用户
 - 若目标工程已经存在，直接返回 `unsupported`。旧项目继续按原工程维护；需要现代化时单独立项、先评估再逐切片迁移，不属于本 skill。
 - 输出目录必须显式指定；目标工程目录必须不存在，`--force` 永久拒绝。
 - Harness 内多项目布局必须使用 `apps/backend/<project>/`；`apps/backend/` 只能是生成器的父容器，`app/backend/`、`app/frontend/` 及其子路径一律拒绝。`git-submodule` gitlink、空挂载点、detached HEAD 工作树不得覆盖生成，即使传入 `--force` 也不得当成普通目录，且不得走「请显式传入 `--force`」普通目录覆盖 / rename 路径。`--output-dir` 指向 detached HEAD 子仓时不得 mkdir、staging 或生成工程。先 `git submodule update --init` 并在子仓附加分支工作树内生成。维护生成器时按 [守卫顺序](references/generator-maintenance.md) 检查，不能将 gitlink 当普通目录。
-- 不要在 skill 里硬编码用户业务字段或真实连接信息。
-- 生成后要检查依赖关系是否仍符合分层约束。
 - 生成时的工程基线由本 skill 的 `references/engineering-baseline.md` 持有并绑定摘要；它不是独立 Skill。生成后必须回到 实现合同编译器，并按批准切片加载 `yss-domain`、`yss-application`、`yss-repository`、`yss-mybatis`、`yss-web-controller`、`yss-dto`、`yss-exception`、`yss-validation`、`mapstruct`、`lombok`、`alibaba-java-code-style` 等实际命中的行为 skill。
-- 验证数据库固定 H2，生产数据库 `not-bound`；后续存储接入按批准的切片合同执行。
 - 生成后的后端工程必须使用项目根目录 `./mvnw ...` 执行构建、测试、运行和 CI 验证；不得在 README、实施记录、Ticket、Review 或 Release 中默认写裸 `mvn ...`。既有仓库确实无法使用 wrapper 时，必须记录受控例外。
 - 原型确认后，`scaffold_status=required` 才能进入本 skill；本 skill 的生成边界是工程结构、POM、配置、Wrapper 和机械模板，不是业务实现。
 - 脚手架合同必须携带 `contract_id`、`contract_version`、实现合同编译器 draft 引用、生命周期批准引用、持久化引用、当前版本、允许写路径、预期证据文件和验证命令；字段缺失或版本过期时阻断。
@@ -82,10 +65,6 @@ description: 用于生成完整的 YSS DDD 多模块后端脚手架。当用户
 - 严禁把领域规则、状态机、权限、事务、复杂查询、错误映射、业务字段或用户可见行为塞进脚手架生成步骤。`./mvnw validate`、输出目录存在或“生成成功”都不等于生命周期批准、架构放行或 `ready-for-agent`。
 - 生命周期脚手架生成必须关闭 `--with-example`，不得把 User CRUD 或业务字段当作样板。生成器严格 `initialize-only`：非空目标、`--force`、旧项目迁移和当前模板升级一律 `unsupported`。未来若支持同一 Target Profile 内的模板升级，必须另行设计和批准，当前不预留可执行承诺。
 - 脚手架完成后，所有后续生成的后端代码必须回到 `yss-implementation-contract-compiler`，消费批准且版本当前的 Slice Implementation Contract 和对应 YSS skill；业务行为使用 `behavior-tdd`，机械生成才使用 `controlled-generation`。
-- `.mvn/settings.xml` 只能通过 `${env.MAVEN_REPO_USERNAME}` 和 `${env.MAVEN_REPO_PASSWORD}` 读取 Maven 仓库凭据；内部仓库构建前由 CI 或本地安全环境注入变量，禁止把 Maven 仓库用户名、明文密码或 Maven 加密密码写入 skill、模板或生成工程。
-- `.mvn/maven.config` 必须显式加载项目级 `.mvn/settings.xml` 并激活 `yss-internal`；仓库 URL 来自 `YSS_MAVEN_REPOSITORY_URL`，凭据来自 `MAVEN_REPO_USERNAME` / `MAVEN_REPO_PASSWORD`。预检缺失时先于 Maven 执行阻断，日志必须脱敏。
-- Domain POM 不得依赖 YSS DTO/Exception、Web Validation、Swagger 或 Jackson；DTO/Exception/OpenAPI 注解属于 Web。MapStruct 统一 `componentModel="spring"`，父 POM 负责 processor 与 `lombok-mapstruct-binding`。
-- 生成工程必须携带 ArchUnit、Maven Enforcer 和 Wrapper checksum；DEBUG 与 MyBatis stdout SQL 只能进入 `application-local.yml`。
 - 涉及 API 契约时，先确认 `docs/.scratch/<feature>/api/<feature>.yaml` 中的 OpenAPI Draft / Freeze 状态；不要用脚手架生成结果反向替代产品契约设计。
 
 ## 按需读取

package/template/.agents/skills/yss-ddd-scaffold-generator/references/engineering-checks.md

@@ -0,0 +1,11 @@
+# DDD 生成工程检查
+
+生成后验收工程内容时读取；Maven 执行前先检查凭据、settings 与脱敏要求。
+
+- 不要在 skill 里硬编码用户业务字段或真实连接信息。
+- 生成后要检查依赖关系是否仍符合分层约束。
+- 验证数据库固定 H2，生产数据库 `not-bound`；后续存储接入按批准的切片合同执行。
+- `.mvn/settings.xml` 只能通过 `${env.MAVEN_REPO_USERNAME}` 和 `${env.MAVEN_REPO_PASSWORD}` 读取 Maven 仓库凭据；内部仓库构建前由 CI 或本地安全环境注入变量，禁止把 Maven 仓库用户名、明文密码或 Maven 加密密码写入 skill、模板或生成工程。
+- `.mvn/maven.config` 必须显式加载项目级 `.mvn/settings.xml` 并激活 `yss-internal`；仓库 URL 来自 `YSS_MAVEN_REPOSITORY_URL`，凭据来自 `MAVEN_REPO_USERNAME` / `MAVEN_REPO_PASSWORD`。预检缺失时先于 Maven 执行阻断，日志必须脱敏。
+- Domain POM 不得依赖 YSS DTO/Exception、Web Validation、Swagger 或 Jackson；DTO/Exception/OpenAPI 注解属于 Web。MapStruct 统一 `componentModel="spring"`，父 POM 负责 processor 与 `lombok-mapstruct-binding`。
+- 生成工程必须携带 ArchUnit、Maven Enforcer 和 Wrapper checksum；DEBUG 与 MyBatis stdout SQL 只能进入 `application-local.yml`。

package/template/.agents/skills/yss-ddd-scaffold-generator/references/generation-workflow.md

@@ -0,0 +1,14 @@
+# DDD 受控生成与验证
+
+仅在入口所列条件命中时读取本文件。Markdown 链接相对本文件；行内 references/assets/schemas 路径相对 Skill 根目录。Skill 自带的 bin/scripts 命令从 Skill 根目录执行；明确注明 repository root 的包装命令仍从项目根目录执行。
+
+## 优先流程
+
+1. 确认服务级 `scaffold_request_id`、已通过 `gate.backend-architecture-platform-approved` 的 `domain-driven` 架构与精确 Spring Boot 版本选择及 digest、项目名、基础包名、Maven 项目坐标、父 POM GAV、YSS Components BOM 版本、输出目录和批准 Profile。Java `base_package` 与 Maven `group_id` 是两个独立输入，不得相互推导；脚手架发生在 Ticket 正式化前，不使用 `slice_id` 伪造切片身份。
+   Harness 内输出目录必须是 `apps/backend/` 容器，生成器再以 `project_name` 创建 `apps/backend/<project>/`；禁止使用 `app/backend/`、`app/frontend/` 或把 `apps/backend/` 之外的容器根当作后端项目根。
+2. 优先运行 `node scripts/generate_and_verify_scaffold.mjs`，在同一个受控工作流中生成骨架并执行真实 Maven 验证。`generate_scaffold.mjs` 只是底层生成原语，单独返回 0 不代表脚手架完成。
+3. 检查生成的模块名、POM、机械启动入口、基础配置文件和包路径。
+4. 受控工作流必须在生成项目根目录实际执行 `./mvnw validate`、`./mvnw test` 和 `./mvnw package`；三条命令全部返回 0 后才能报告完成。
+5. 三条 Wrapper 命令通过只得到 `empty-scaffold-verified`。如需声称已满足下游技能的首切片就绪条件，必须使用 `node scripts/run_first_slice_verification.mjs` 校验批准且版本当前的 Slice Implementation Contract、完整分层产物、当前合同 freshness 与根 Wrapper；只有验证器成功更新 Manifest 后才得到 `first-slice-verified`。
+
+受控验证命令由本 skill 的 `node scripts/run_scaffold_verification.mjs` 固定执行；验证器先检查 `.yss/scaffold-generation.json` 的合同元数据和 Wrapper、Java、项目级 Maven settings/profile、仓库凭据是否就绪，再在指定 evidence 目录写入每条命令的 stdout/stderr、`exit_code`、`failure_category`、耗时、执行时间和 `scaffold-verification.json`。仓库或凭据失败归为 `repository-access`，与 `project-model`、`compilation`、`bootstrap-entrypoint`、`test-failure`、`packaging` 分开；任何一条命令失败或未执行都必须阻断。