release-skill 0.9.16 → 0.9.18

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.16",
+  "version": "0.9.18",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codebuddy-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.16",
+  "version": "0.9.18",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.16",
+  "version": "0.9.18",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"
@@ -19,7 +19,7 @@
     ],
     "defaultPrompt": [
       "Assess this project for release readiness.",
-      "Prepare a release plan for version 0.9.16.",
+      "Prepare a release plan for version 0.9.18.",
       "Help me understand the release workflow."
     ]
   }

package/.cursor-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "release-skill",
+  "version": "0.9.18",
+  "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
+  "author": {
+    "name": "广州市风荷科技有限公司"
+  },
+  "license": "Apache-2.0",
+  "skills": "./adapters/cursor/skills/"
+}

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "release-skill",
-  "version": "0.9.16",
+  "version": "0.9.18",
   "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
   "author": {
     "name": "广州市风荷科技有限公司"

package/.qoder-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "release-skill",
+  "version": "0.9.18",
+  "description": "Safe preparation and frozen GitHub/npm production publishing with full happy end verification",
+  "author": {
+    "name": "广州市风荷科技有限公司"
+  },
+  "license": "Apache-2.0",
+  "skills": "./adapters/qoder/skills/"
+}

package/CHANGELOG.md

@@ -1,5 +1,69 @@
 # Changelog
 
+<!-- release-skill:changelog:start version=0.9.18 locale=en baseline=sha256:486d52ac38ecb11f043c79661728004fb1c1593089915741867cdc0f449be275 -->
+## [0.9.18] - 2026-09-11
+
+0.9.18 is a local source candidate that adds first-class Cursor packaging, Foundation-backed host verification, and a final local distribution path for Claude, Codex, Kimi, CodeBuddy, WorkBuddy, Qoder, and Cursor. The three Foundation dependencies remain pinned to the exact 0.21.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance.
+
+### Security
+
+- Cursor must be closed before its plugin tree is scanned or replaced. Failed upgrades preserve or restore a complete old or new directory instead of publishing a mixed tree.
+- Host verification receives only caller-declared roots and records mechanism observations separately from release-domain publication and verification state.
+- Hub publication remains a compare-and-swap operation. A partial Hub publication is never rolled back or force-pushed automatically.
+
+### Added
+
+- The npm package now includes `.cursor-plugin/plugin.json` and a self-contained `adapters/cursor/` projection with all release-skill Skills and runtime resources.
+- Release verification can invoke Foundation 0.21.0 host verification with explicit executable and user-state roots, including Cursor project-level plugin verification.
+- The final local updater can distribute the verified release to the declared Claude, Codex, Kimi, CodeBuddy, WorkBuddy, Qoder, and Cursor installations.
+- Skill Family Hub remains the central marketplace. Its release entry is published through the existing Git Data API after release verification.
+
+### Changed
+
+- Local host updates verify the frozen snapshot and manifest identity before installation, and Cursor updates use Foundation fixed-set publication for first install and atomic full-directory replacement for upgrades.
+- Platform generation, public-file projection, package allowlists, schemas, and release-finish guidance now treat Cursor as a declared host and adapter.
+
+### Fixed
+
+- Cursor plugin names reject underscores so generated local plugin directories remain compatible with Cursor's manifest requirements.
+- The package's native prebuild allowlist and fixed resource-closure checks now include every generated adapter, including Cursor.
+
+### Upgrade Notes
+
+Upgrade from 0.9.17 to obtain Cursor packaging and local installation, the Foundation-backed host verification bridge, and the unified seven-host local finish path. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. Reload each host after updating; an `UPDATED` filesystem result alone does not prove that the running host loaded the new version.
+<!-- release-skill:changelog:end version=0.9.18 locale=en -->
+
+
+<!-- release-skill:changelog:start version=0.9.17 locale=en baseline=sha256:b7b382ee18c66d75612df7c83aa80439100237bf7d1ce3e36dc0cf1a038ed051 -->
+## [0.9.17] - 2026-09-09
+
+0.9.17 is a local source candidate that adds explicit offline verification of historical release records and a self-contained Qoder projection, while preserving the setup-root and Kimi initial-directory trust fixes. The three Foundation dependencies are pinned to the exact 0.21.0 release. This note is not evidence of publication, real-host acceptance, consumer installation verification, or independent acceptance; it also does not establish Hub acceptance.
+
+### Security
+
+- Offline verification reads only paths explicitly supplied on the command line and redacts local path details from its JSON result. Historical consistency does not prove that records are globally latest or that remote objects still exist.
+- Qoder remains outside release distributions and publication checkpoints. The updater does not add a marketplace, perform a first install, uninstall, or reload the current session; `UPDATED` does not mean the new plugin has been loaded.
+- Any later central Skill Family Hub publication uses the existing Git Data API with compare-and-swap. A partial Hub publication remains recoverable and is never rolled back or force-pushed automatically.
+
+### Added
+
+- The public `release-skill verify-records` CLI checks caller-supplied plan, approval, target-run, and predecessor-run bytes. It reports `CONSISTENT`, `CONTRADICTED`, or `INSUFFICIENT` without scanning `.release-skill`, following paths from records, contacting remotes, writing files, or changing release state.
+- The npm package now includes `.qoder-plugin/plugin.json` and a self-contained `adapters/qoder/` projection. The existing post-release updater can update an already installed user-scope Qoder plugin only after the selected Hub source and frozen payload match.
+
+### Changed
+
+- The release-finish setup continuation uses the current `--root` release project directly. It no longer asks for a second project path, while project-level readiness and host-specific loading checks remain distinct.
+
+### Fixed
+
+- An authorized Kimi update can confirm the standard initial `Trust this folder?` dialog for the current release project before continuing. Unknown rows, selections, repeated trust dialogs, timeout, or early exit still stop that host.
+
+### Upgrade Notes
+
+Upgrade from 0.9.16 to use `release-skill verify-records`, the Qoder package projection, and the setup/Kimi fixes. Remove the old release-skill standalone marketplace; use the ifoohoo/skill-family-hub repository and Hub-qualified plugin id release-skill@skill-family-hub. The central Skill Family Hub must accept the Qoder entry before marketplace installation can begin. Real Qoder and Kimi installation, reload, and business invocation remain separate authorized follow-up work.
+<!-- release-skill:changelog:end version=0.9.17 locale=en -->
+
+
 <!-- release-skill:changelog:start version=0.9.16 locale=en baseline=sha256:ea8288d2ffcedf02008eb0bc10280d52bc6ddd2e383f072913340eb64cb7ca63 -->
 ## [0.9.16] - 2026-09-09
 

package/INSTALL.md

@@ -2,7 +2,7 @@
 
 [简体中文](INSTALL.zh-CN.md)
 
-<!-- release-skill:release-version: 0.9.16 -->
+<!-- release-skill:release-version: 0.9.18 -->
 ## Prerequisites
 
 - Node.js 22.0.0 or later
@@ -41,7 +41,9 @@ Claude Code, CodeBuddy, WorkBuddy, and Codex install release-skill from the
 central [Skill Family Hub](https://github.com/ifoohoo/skill-family-hub).
 The release-skill repository carries plugin manifests but no marketplace index.
 release-skill currently invokes no scriptable install API for Kimi Code — see the
-[Kimi Code section](#install-as-a-kimi-code-plugin). Add the marketplace once,
+[Kimi Code section](#install-as-a-kimi-code-plugin). Qoder uses the same Hub only
+after its root `marketplace.json` has accepted the release-skill entry; see the
+[Qoder section](#install-as-a-qoder-plugin). Add the marketplace once,
 then install the plugin:
 
 > **Prerequisite: GitHub access.** The `owner/repo` shorthand makes Claude Code
@@ -81,6 +83,16 @@ release-skill currently uses the version-pinned interactive TUI path for Kimi
 Code. The release state machine reports installation as a post-release manual
 task and does not verify its completion.
 
+**Qoder:** after the central Hub has accepted the release-skill Qoder entry and
+that marketplace is configured locally:
+
+```bash
+qoder plugins install release-skill@skill-family-hub --scope user --json
+```
+
+Do not treat the local adapter or a successful validation alone as proof of a
+Hub marketplace install.
+
 ### Alternative: direct repository install (advanced)
 
 The Hub marketplace above is the supported primary path. Direct installation
@@ -91,6 +103,9 @@ remains available only where the host supports a repository URL:
 - CodeBuddy: single-session use from a source checkout via
   `--plugin-dir <path>/adapters/workbuddy` (see the
   [CodeBuddy/WorkBuddy section](#install-as-a-codebuddyworkbuddy-plugin)).
+- Qoder: validate the generated candidate with
+  `qoder plugins validate <path>/adapters/qoder --json --strict`; validation is
+  not marketplace installation or a real Skill call.
 
 ## Install as a Kimi Code plugin
 
@@ -110,7 +125,7 @@ tag pinned to the exact version (never the bare repository URL, which installs
 the latest release or default branch), confirm the trust prompt, then reload:
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.16
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.18
    /plugins reload
    ```
 
@@ -129,12 +144,26 @@ same TUI session before accepting the plugin trust prompt and reloading.
 
 The effective configuration root is explicit `kimiHome`, then
 `KIMI_CODE_HOME`, then `~/.kimi-code`. The TUI process and post-operation
-observation use that same root. release-finish strips ANSI/OSC control sequences
-and soft wrapping before it checks the frozen repository, tag, and selected
-`Trust and install` action inside the plugin trust dialog. A `Trust this folder?`
-prompt, unknown interface, timeout, early exit, or identity mismatch stops the
-flow without confirming folder trust or continuing installation. This local
-check is not part of `verify` and does not alter the `VERIFIED` release state.
+observation use that same root. The TUI working directory is the resolved release
+project root passed through `--root`. After explicit confirmation of the frozen
+plan and selection of Kimi for update, release-finish reads the complete initial
+`Trust this folder?` dialog and requires exactly one positive
+`Trust this folder` action and exactly one selected action. If the positive action
+is already selected, it confirms without sending a direction key. If a known
+rejection action is selected, it moves once according to the action's position,
+reads the complete dialog again, and verifies the positive selection before
+confirming. Unknown or duplicate actions, a missing or duplicate positive action,
+an unverifiable selection, a failed move, timeout, early exit, or a folder-trust
+dialog after the plugin command fails closed. When a later Kimi version presents
+a new reproducible blocking layout, capture the Kimi version, visible actions,
+selected action, and their relationship first. Add the nearest regression and
+continue compatibility work when those facts uniquely identify the current
+directory, positive trust action, and selection result; stop and escalate when
+directory identity or action semantics remain ambiguous. release-finish still
+strips ANSI/OSC control sequences and soft wrapping before it checks the frozen
+repository, tag, and selected
+`Trust and install` action inside the plugin trust dialog. This local check is
+not part of `verify` and does not alter the `VERIFIED` release state.
 
 No receipt or attestation is required. The `attest` command remains available
 only for frozen plans created by older versions that lack the
@@ -178,6 +207,72 @@ For a single session from a source checkout you can also point CodeBuddy at the
 generated plugin directory with `--plugin-dir <path>/adapters/workbuddy`; the
 adapter never references files outside its own directory.
 
+## Install as a Cursor Local plugin
+
+`adapters/cursor/` contains `.cursor-plugin/plugin.json`, all public Skills and a
+self-contained runtime. Skills resolve the plugin from the absolute `SKILL.md`
+path supplied by Cursor and validate the root manifest; no plugin-root environment
+variable is required.
+
+Declare `cursor` in `postPublish.localHostUpdate.hosts` and set
+`cursor.sourcePath: adapters/cursor`. The directory and manifest identity are
+frozen with the public snapshot. Optional `cursor.dependencyInstall:
+npm-ci-ignore-scripts` installs lockfile dependencies in a candidate outside the
+scanner root.
+
+On macOS, quit Cursor and run the installed finishing entry. Supply the real
+absolute plugins root, commonly `.cursor/plugins` inside the user directory:
+
+```bash
+node <installed-plugin-root>/bin/release-skill-local-finish.mjs \
+  --root <release-project-root> --plan <frozen-plan-path> --run <completed-run-path> \
+  --update-local-hosts --hosts cursor --confirm-plan <planDigest> \
+  --cursor-plugins-root <absolute-cursor-plugins-root> --json
+```
+
+The command verifies the plan, run lineage and frozen snapshot before installing
+the complete plugin at `<cursor-plugins-root>/local/<plugin>`. First installation
+never overwrites an existing directory. Upgrades atomically exchange whole
+directories and retain the old version at `backups/<plugin>/release-*/plugin`.
+An identical version and full closure returns `ALREADY_CURRENT`; a completed
+write returns `UPDATED` with restart instructions. Indeterminate exchanges retain
+both sides for manual inspection; do not retry blindly. If backup relocation
+fails while the exchanged mapping remains provable, the script restores the old
+directory and reports failure.
+
+Restart Cursor or run Reload Window, then verify the Local source, version,
+public Skills and a real business invocation separately. Installation does not
+prove loading and never changes `VERIFIED`. Other operating systems, a running
+Cursor process or unavailable process observation return `MANUAL_REQUIRED`.
+
+## Install as a Qoder plugin
+
+The npm package ships `.qoder-plugin/plugin.json` and a generated,
+self-contained `adapters/qoder/` tree. Qoder is a build-only projection: it does
+not add a `qoder-plugin` distribution type or a publish/reconcile/verify install
+checkpoint.
+
+The central Hub root `marketplace.json` must first contain an accepted
+release-skill entry whose source resolves to this Qoder projection. Once that
+entry is present and `skill-family-hub` is configured, install at user scope:
+
+```bash
+qoder plugins install release-skill@skill-family-hub --scope user --json
+```
+
+The optional `release-finish` path updates only an existing user-scope Qoder
+installation selected by the user and declared in the frozen plan. Before any
+write it matches the Hub name and repository, then rechecks the refreshed source
+and frozen payload. It may run the named marketplace update followed by
+`qoder plugins update release-skill@skill-family-hub --scope user`; it never
+adds a marketplace, first-installs the plugin, removes a marketplace, or
+uninstalls and reinstalls the plugin.
+
+An `UPDATED` result proves installed bytes, not what the current Qoder session
+has loaded. Reload the plugin or start a new session, then use the discovered
+release-skill to complete one read-only release task before claiming the new
+version is active. These local results do not change `VERIFIED`.
+
 ## Consumer verification boundaries
 
 **When verification runs.** Consumer-side install verification executes only

package/INSTALL.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](INSTALL.md)
 
-<!-- release-skill:release-version: 0.9.16 -->
+<!-- release-skill:release-version: 0.9.18 -->
 ## 前置条件
 
 - Node.js 22.0.0 或更高版本
@@ -37,7 +37,9 @@ release-skill help
 Claude Code、CodeBuddy、WorkBuddy 和 Codex 从统一的
 [Skill Family Hub](https://github.com/ifoohoo/skill-family-hub)
 安装 release-skill。release-skill 仓库只携带插件清单，不再携带市场索引。当前没有接入
-Kimi Code 的可脚本化安装接口，见 [Kimi Code 小节](#安装为-kimi-code-插件)。先添加一次市场，再安装
+Kimi Code 的可脚本化安装接口，见 [Kimi Code 小节](#安装为-kimi-code-插件)。Qoder
+只有在 Hub 根 `marketplace.json` 已接纳 release-skill 条目后才使用同一市场，见
+[Qoder 小节](#安装为-qoder-插件)。先添加一次市场，再安装
 插件：
 
 > **前置条件：GitHub 访问。** `owner/repo` 简写会让 Claude Code 通过
@@ -75,6 +77,14 @@ codex plugin marketplace add ifoohoo/skill-family-hub
 release-skill 当前对 Kimi Code 采用钉死版本的交互式 TUI 路径。发布状态机会把安装
 列为发布后人工待办，不核验其完成结果。
 
+**Qoder：** 中央 Hub 已接纳 release-skill 的 Qoder 条目，且本机已配置该市场后执行：
+
+```bash
+qoder plugins install release-skill@skill-family-hub --scope user --json
+```
+
+本地适配器存在或候选校验成功，都不能单独证明 Hub 市场安装成立。
+
 ### 备选：直接从仓库安装（进阶）
 
 上面的 Hub 市场是受支持的主路径。只有宿主支持仓库 URL 时，才能直接安装：
@@ -84,6 +94,8 @@ release-skill 当前对 Kimi Code 采用钉死版本的交互式 TUI 路径。
 - CodeBuddy：源码检出后通过 `--plugin-dir <path>/adapters/workbuddy`
   单会话使用（见
   [CodeBuddy/WorkBuddy 小节](#安装为-codebuddyworkbuddy-插件)）。
+- Qoder：执行 `qoder plugins validate <path>/adapters/qoder --json --strict`
+  校验生成候选；该结果不等于市场安装，也不等于真实 Skill 调用。
 
 ## 安装为 Kimi Code 插件
 
@@ -101,7 +113,7 @@ release-skill 当前只采用并验证 Kimi Code 的交互式 TUI 路径，**无
 （切勿使用裸仓库地址，它会安装最新 release 或默认分支），确认信任提示后重新加载：
 
    ```
-   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.16
+   /plugins install https://github.com/ifoohoo/release-skill/releases/tag/release-skill-v0.9.18
    /plugins reload
    ```
 
@@ -114,10 +126,18 @@ release-finish 会重新读取 Kimi 的受管安装根，不复用操作前的
 移除，再按发布标签安装、确认插件信任并重新加载。
 
 有效配置根依次取显式 `kimiHome`、`KIMI_CODE_HOME`、`~/.kimi-code`，TUI 进程和
-操作后观察使用同一根。release-finish 会先清理 ANSI/OSC 控制序列和软换行，再在插件
-信任对话框内核对冻结仓库、标签和当前选中的 `Trust and install`。出现
-`Trust this folder?`、未知界面、超时、提前退出或身份不一致时，流程停止，不确认目录
-信任，也不继续安装。这个本机检查不属于 `verify`，也不会改变
+操作后观察使用同一根，TUI 工作目录固定为 `--root` 指定的当前发布项目。用户确认冻结
+计划并显式选择更新 Kimi 后，release-finish 会读取完整的初始 `Trust this folder?`
+对话框，并要求其中只有一个正向项 `Trust this folder` 和一个选中项。正向项已经选中时，
+流程不发送方向键，直接确认；已知拒绝项选中时，流程按它与正向项的相对位置移动一次，
+重新读取完整对话框并确认正向项已选中，然后才提交。出现未知或重复选项、正向项缺失或
+重复、选中状态无法核验、移动后无法确认、超时、提前退出，或者插件命令发出后再次出现
+目录信任时，该宿主失败并停止。若后续 Kimi 版本出现新的可复现阻断界面，先记录 Kimi
+版本、可见选项、选中项及其相对关系；这些事实足以唯一确认当前目录、正向信任项和选择
+结果时，在最近测试补回归与兼容并继续，目录身份或选项语义仍有歧义时停止并交回主会话。
+release-finish 仍会先清理 ANSI/OSC 控制序列和软换行，再在插件信任对话框内核对冻结
+仓库、标签和当前选中的
+`Trust and install`。这个本机检查不属于 `verify`，也不会改变
 已经完成的 `VERIFIED` 发布状态。
 
 新计划无需收据或人工证明。`attest` 命令仅兼容缺少
@@ -152,6 +172,57 @@ codebuddy CLI 可以添加市场并安装插件，但 **`plugin marketplace add`
 源码检出后也可以用 `--plugin-dir <path>/adapters/workbuddy` 把 CodeBuddy 指向
 生成的插件目录做单会话使用；适配器不引用自身目录之外的任何文件。
 
+## 安装为 Qoder 插件
+
+npm 包内提供 `.qoder-plugin/plugin.json` 和生成的自包含 `adapters/qoder/` 目录。
+Qoder 只是 build-only 投影，不新增 `qoder-plugin` 分发类型，也不新增 publish、
+reconcile 或 verify 安装检查点。
+
+中央 Hub 根 `marketplace.json` 必须先接纳 release-skill 条目，且该条目的来源要解析到
+本插件的 Qoder 投影。条目存在并已配置 `skill-family-hub` 后，执行用户范围安装：
+
+```bash
+qoder plugins install release-skill@skill-family-hub --scope user --json
+```
+
+可选的 `release-finish` 只更新用户已选择、冻结计划已声明且已经存在的用户范围 Qoder
+安装。写入前先核对 Hub 名称和仓库；刷新市场后，再核对来源与冻结载荷。流程可以更新
+指定市场，再执行 `qoder plugins update release-skill@skill-family-hub --scope user`；
+不会添加市场、首次安装插件、删除市场，也不会卸载后重装。
+
+`UPDATED` 只证明安装载荷已更新，不代表当前 Qoder 会话已经加载新版。必须重新加载插件
+或新开会话，再由真实发现的 release-skill 完成一次只读发布业务调用，才能宣称新版已
+生效。这些本机结果不会改变 `VERIFIED`。
+
+## 安装为 Cursor 本地插件
+
+包内 `adapters/cursor/` 包含 `.cursor-plugin/plugin.json`、全部公开 Skill 和自足运行资源。
+Skill 根据宿主实际加载的 `SKILL.md` 绝对路径定位插件根，并检查根清单；不依赖插件根环境变量。
+
+发布项目在 `postPublish.localHostUpdate.hosts` 中声明 `cursor`，并设置
+`cursor.sourcePath: adapters/cursor`。该相对目录与清单身份随公开快照冻结；需要锁文件依赖时，
+可设置 `cursor.dependencyInstall: npm-ci-ignore-scripts`，脚本只在扫描根外的候选中安装依赖。
+
+macOS 上先退出 Cursor，再运行已安装版本的收尾入口。插件根必须使用真实绝对路径；
+常见位置是用户目录下的 `.cursor/plugins`，命令不会自动推断它。
+
+```bash
+node <installed-plugin-root>/bin/release-skill-local-finish.mjs \
+  --root <release-project-root> --plan <frozen-plan-path> --run <completed-run-path> \
+  --update-local-hosts --hosts cursor --confirm-plan <planDigest> \
+  --cursor-plugins-root <absolute-cursor-plugins-root> --json
+```
+
+命令先复验计划、运行谱系和冻结快照，再把完整插件放到 `<cursor-plugins-root>/local/<plugin>`。
+首次安装不覆盖已有目录；升级整体交换目录，并把旧版保存到 `backups/<plugin>/release-*/plugin`。
+相同版本和完整闭包一致时返回 `ALREADY_CURRENT`；写入成功返回 `UPDATED` 和重启提示。
+交换结果不确定时保留现场并要求人工检查，禁止原样重试。备份迁移失败且交换映射可确认时，
+脚本恢复原目录并报告失败。
+
+重启 Cursor 或执行 Reload Window 后，分别核对 Local 来源、版本、公开 Skill 和一次实际业务调用。
+安装成功不等于新版已加载；本机结果不改变 `VERIFIED`。其他操作系统、Cursor 仍运行或进程状态
+无法判断时，自动安装返回 `MANUAL_REQUIRED`。
+
 ## 消费端安装验证边界
 
 **何时执行验证。** 消费端安装验证仅在安装契约关键文件相对已确认公开基线发生变化时执行；