@fitlab-ai/agent-infra 0.9.11 → 0.9.13

package/templates/.agents/rules/issue-pr-commands.github.zh-CN.md

@@ -1,49 +0,0 @@
-# PR 平台意图命令
-
-> `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
-
-PR 资源的定位、创建、绑定和元数据同步统一通过 typed internal intent；SKILL 只负责决定分支、标题、正文和调用时机，不直接拼装平台命令。
-
-## 定位
-
-```bash
-agent-infra-internal platform-pr inspect {task-id}
-```
-
-返回已绑定 PR 的规范身份；未绑定时返回 `PR_NOT_LINKED`。调用方不得按标题模糊匹配。
-
-## 创建或恢复
-
-调用方把标题和正文分别写入临时文件，然后执行：
-
-```bash
-agent-infra-internal platform-pr create {task-id} \
-  --agent {standard-agent-token} --base {target-branch} --head {current-branch} \
-  --title-file {title-file} --body-file {body-file}
-```
-
-core 会先按 upstream、head 和 base 精确定位；唯一既有 PR 会复用并绑定，零个才创建，多个稳定失败。远端结果未知时重新精确定位，不盲重建。`--dry-run` 只返回计划。
-
-## 显式绑定
-
-```bash
-agent-infra-internal platform-pr bind {task-id} --pr {pr-number} --agent {standard-agent-token}
-```
-
-冲突绑定稳定失败且不修改 `task.md`。
-
-## 元数据同步
-
-```bash
-agent-infra-internal platform-pr sync {task-id} \
-  --agent {standard-agent-token} --metadata --closing-issue
-```
-
-core 从关联 Issue 复制 type / `in:` labels、assignee、具体 milestone，并确保 closing association。权限不足返回逐项 `skipped` 和顶层 `degraded`；不得反向修改 Issue。
-
-## 状态语义
-
-- `planned|applied|no-op|degraded`：退出码 0。
-- `failed`：退出码 1，确定性输入或远端错误。
-- `blocked`：退出码 2，网络、认证或结果未知，需要人工介入或安全重跑。
-- 创建后摘要或元数据同步失败不得回滚 PR；调用方按所属 SKILL 记录 warning。

package/templates/.agents/rules/issue-sync.github.en.md

@@ -1,40 +0,0 @@
-# Issue Sync
-
-> `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
-
-## Marker Registry
-
-| Key | Marker |
-|---|---|
-| `task` | `<!-- sync-issue:{task-id}:task -->` |
-| `artifact` | `<!-- sync-issue:{task-id}:{artifact-stem} -->` |
-| `artifactChunk` | `<!-- sync-issue:{task-id}:{artifact-stem}:{part}/{total} -->` |
-| `summary` | `<!-- sync-issue:{task-id}:summary -->` |
-| `cancel` | `<!-- sync-issue:{task-id}:cancel -->` |
-
-`pr-review` content is synced only as an Issue artifact comment (via the `artifact` / `artifactChunk` markers) and is never a `restore-task` recovery source; restore still accepts only an Issue number and reads only registered Issue markers, with no PR source.
-
-Comments use `platform-comment`; Issue resources use `platform-issue`:
-
-```bash
-agent-infra-internal platform-issue inspect {task-id}
-agent-infra-internal platform-issue create {task-id} --agent {standard-agent-token}
-agent-infra-internal platform-issue bind {task-id} --issue {number} --agent {standard-agent-token}
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} {desired-state-flags}
-```
-
-The core owns status/in labels, assignees, milestones, Issue Type, pinned fields, requirements, state, capabilities, dry-run, retries, errors, and idempotency. Omitted flags preserve values; `none` explicitly clears them. Status labels converge to at most one, and ambiguous requirement identity fails closed.
-
-`planned|applied|no-op|degraded` exit 0; `failed` exits 1; `blocked` exits 2.
-
-Map material degraded/failed/blocked results to workflow warnings through the structured intent; callers must not edit warning rows directly:
-
-```bash
-agent-infra-internal task-warning {task-id} add \
-  --step issue-sync --severity {severity} --code {code} \
-  --target {target} --message {message} --action {action}
-```
-
-## Backfill
-
-During completion, artifact comments are replayed with `--kind artifact --artifact <file> --backfill`. If the remote Issue has no matching marker, the core creates a comment with a historical-backfill notice. If a valid base or chunk marker set already exists, the core returns `no-op` and preserves the existing bodies and chunks. Marker conflicts still fail without writes.

package/templates/.agents/rules/issue-sync.github.zh-CN.md

@@ -1,76 +0,0 @@
-# Issue 同步规则
-
-> `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
-
-## Marker 注册表
-
-以下 key 及格式是 Issue 评论身份的兼容契约；调用方只传 key/资源，不自行拼 marker。
-
-| Key | Marker |
-|---|---|
-| `task` | `<!-- sync-issue:{task-id}:task -->` |
-| `artifact` | `<!-- sync-issue:{task-id}:{artifact-stem} -->` |
-| `artifactChunk` | `<!-- sync-issue:{task-id}:{artifact-stem}:{part}/{total} -->` |
-| `summary` | `<!-- sync-issue:{task-id}:summary -->` |
-| `cancel` | `<!-- sync-issue:{task-id}:cancel -->` |
-
-`prSummary` 属于 `.agents/rules/pr-sync.md`，本规则不实现 PR 聚合。
-
-`pr-review` 原文只通过 `artifact` / `artifactChunk` marker 同步为 Issue artifact 评论，不作为 `restore-task` 恢复来源；恢复仍只接受 Issue 编号并只读注册的 Issue marker，不新增 PR 来源。
-
-## 平台 intent
-
-GitHub upstream、认证、capability、分页、marker 查找、幂等 create/update、分片、重试与错误分类由 typed platform core 统一处理：
-
-```bash
-agent-infra-internal platform-context resolve [--cwd <path>]
-agent-infra-internal platform-comment list --issue <N> [--cwd <path>]
-agent-infra-internal platform-comment owner <task-ref>
-agent-infra-internal platform-comment sync <task-ref> \
-  --kind task|artifact|summary|cancel --agent {standard-agent-token} \
-  [--artifact <canonical.md>] [--body-file <path|->] [--backfill]
-```
-
-- `applied|no-op|degraded` → exit 0；`failed` → exit 1；`blocked` → exit 2。
-- task 评论保持 `<details>` frontmatter 可逆格式；artifact 原文内联并在超过 profile 上限时使用 `artifactChunk`。
-- 相同 intent 重放必须收敛为 `no-op`；重复 marker 返回 `COMMENT_MARKER_CONFLICT` 且不写入。
-- 外部贡献者锁定统一使用 `platform-comment owner`；不同作者且无 triage 时返回 `COMMENT_OWNER_CONFLICT`。
-
-## 降级与告警
-
-平台结果不直接写 task.md。调用方在有关联任务时把关键失败映射为 workflow warning：
-
-- capability 不足：`IMPORTANT / PERMISSION_DEGRADED`
-- 评论同步永久失败：`ACTION_REQUIRED / COMMENT_SYNC_FAILED`
-- 网络重试耗尽：`ACTION_REQUIRED / NETWORK_RETRY_EXHAUSTED`
-
-使用 `agent-infra-internal task-warning {task-id} add ...` 登记；不得手写 warning 表。
-
-```bash
-agent-infra-internal task-warning {task-id} add \
-  --step issue-sync --severity {severity} --code {code} \
-  --target {target} --message {message} --action {action}
-```
-
-## Issue 元数据 intent
-
-所有 Issue 元数据写入统一使用：
-
-```bash
-agent-infra-internal platform-issue inspect {task-id}
-agent-infra-internal platform-issue create {task-id} --agent {standard-agent-token}
-agent-infra-internal platform-issue bind {task-id} --issue {number} --agent {standard-agent-token}
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} {desired-state-flags}
-```
-
-`sync` 支持 status/in labels、assignee、milestone、Issue Type、pinned fields、需求复选框与 Issue state。省略 flag 表示 preserve，`none` 表示显式清空。适配层统一处理集合差集、动态 schema、权限降级、dry-run、重试、错误分类与幂等重放；SKILL 不得拼装 `gh issue`、GraphQL 或权限分支。
-
-- `planned|applied|no-op|degraded` → exit 0
-- `failed` → exit 1
-- `blocked` → exit 2
-
-status labels 始终至多一个；关闭后不保留 status label。`in:` labels 只从项目允许映射与仓库实际 labels 交集产生。需求复选框以 task.md 原文为身份，歧义时 fail closed。
-
-## 补发
-
-complete-task 按 artifact catalog 时间线遍历本地已有产物：task 使用 `--kind task`，其余使用 `--kind artifact --artifact <file> --backfill`；最后用 `--kind summary --body-file <path>` 原地同步交付摘要。artifact backfill 在远端缺少 marker 时创建带“历史产物补发”提示的评论；已存在合法 marker 集合时保持原评论和分片不变并返回 `no-op`；marker 冲突仍失败。该判定由 core 完成，不由 Skill 扫描评论或拼标题。

package/templates/.agents/rules/label-milestone-setup.github.en.md

@@ -1,60 +0,0 @@
-# Label / Milestone Platform Commands
-
-Read this file before initializing labels, initializing milestones, or adjusting milestones during release work.
-
-## Authentication and Repository Info
-
-```bash
-gh auth token
-gh repo view --json nameWithOwner --jq '.nameWithOwner'
-```
-
-## Label Operations
-
-List existing labels:
-
-```bash
-gh label list --limit 200 --json name --jq '.[].name'
-```
-
-Create or update a label:
-
-```bash
-gh label create "{name}" --color "{color}" --description "{description}" --force
-```
-
-## Milestone Operations
-
-List milestones:
-
-```bash
-gh api "repos/$repo/milestones?state=all" --paginate
-```
-
-Create a milestone:
-
-```bash
-gh api "repos/$repo/milestones" -f title="{title}" -f description="{description}" -f state="{state}"
-```
-
-Update a milestone:
-
-```bash
-gh api "repos/$repo/milestones/{number}" -X PATCH -f state="{state}" -f description="{description}"
-```
-
-## Error Prompt Templates
-
-Use these normalized prompts when the GitHub setup scripts fail:
-
-| Condition | Prompt |
-|---|---|
-| CLI missing | GitHub CLI (`gh`) is not installed |
-| Authentication failed | `GitHub CLI is not authenticated` |
-| API rate limit | `GitHub API rate limit reached, please retry later` |
-
-## Constraints
-
-- use label names as the idempotency key
-- use milestone titles as the idempotency key, then milestone numbers when patching state
-- stop or skip according to the calling skill when commands fail

package/templates/.agents/rules/label-milestone-setup.github.zh-CN.md

@@ -1,60 +0,0 @@
-# Label / Milestone 平台命令
-
-在初始化 label、初始化 milestone，或发布流程需要调整 milestone 前先读取本文件。
-
-## 认证与仓库信息
-
-```bash
-gh auth token
-gh repo view --json nameWithOwner --jq '.nameWithOwner'
-```
-
-## Label 操作
-
-列出现有 label：
-
-```bash
-gh label list --limit 200 --json name --jq '.[].name'
-```
-
-创建或更新 label：
-
-```bash
-gh label create "{name}" --color "{color}" --description "{description}" --force
-```
-
-## Milestone 操作
-
-列出 milestone：
-
-```bash
-gh api "repos/$repo/milestones?state=all" --paginate
-```
-
-创建 milestone：
-
-```bash
-gh api "repos/$repo/milestones" -f title="{title}" -f description="{description}" -f state="{state}"
-```
-
-更新 milestone：
-
-```bash
-gh api "repos/$repo/milestones/{number}" -X PATCH -f state="{state}" -f description="{description}"
-```
-
-## 错误提示模板
-
-GitHub 初始化脚本失败时使用以下标准提示：
-
-| 条件 | 提示 |
-|---|---|
-| CLI 缺失 | GitHub CLI (`gh`) is not installed |
-| 认证失败 | `GitHub CLI is not authenticated` |
-| API 限流 | `GitHub API rate limit reached, please retry later` |
-
-## 约束
-
-- label 以名称作为幂等键
-- milestone 以标题作为幂等键，必要时再结合编号更新状态
-- 失败时按调用方规则决定停止或跳过

package/templates/.agents/rules/milestone-inference.github.en.md

@@ -1,15 +0,0 @@
-# Milestone Inference
-
-> `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
-
-Milestones narrow through declarative Issue intents:
-
-```bash
-# create/import phase
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --milestone initial
-
-# code phase
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --milestone specific
-```
-
-`initial` prefers a valid task milestone, otherwise the lowest open `X.Y.x`, then `General Backlog`. `specific` narrows a release line to the highest open patch version using main/release-line ancestry. Missing facts or triage permission preserve the remote value and return skipped/degraded. `create-pr` reuses the Issue milestone in the 09/10 PR adapter.

package/templates/.agents/rules/milestone-inference.github.zh-CN.md

@@ -1,27 +0,0 @@
-# Milestone 推断规则
-
-> `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
-
-Milestone 继续按生命周期逐步收窄，但候选读取、分支判断、权限降级和写入统一由 `platform-issue` 处理。
-
-## 阶段 1：创建或导入
-
-```bash
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --milestone initial
-```
-
-优先使用 task.md 中存在且有效的显式 milestone；否则从 open milestones 选择最低 `X.Y.x` 版本线，最后回退 `General Backlog`。`triage=false` 或外部事实不足时保持远端值并返回 skipped/degraded。
-
-## 阶段 2：`code-task`
-
-```bash
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --milestone specific
-```
-
-版本线收窄规则保持不变：主干模式在当前版本线取最高 patch；多版本分支模式依据 release-line/main 祖先关系选择版本线。无法可靠判断时保持原值。完成门禁仍拒绝 `X.Y.x`。
-
-## 阶段 3：`create-pr`
-
-PR 只复用关联 Issue 的具体 milestone；该 PR 资源写入属于 09/10，不在 `platform-issue` 中实现。
-
-调用方不得重新实现 milestone 列表、排序、分支祖先或 `gh issue edit` 逻辑。

package/templates/.agents/rules/pr-checks-commands.github.en.md

@@ -1,18 +0,0 @@
-# GitHub PR Readiness Intents
-
-The GitHub adapter requires `gh >= 2.72.0`. Platform context checks this dependency before any GitHub API, PR, or checks operation. Projects that do not select GitHub neither probe nor depend on `gh`.
-
-```bash
-agent-infra-internal platform-checks inspect {task-id}
-
-agent-infra-internal platform-checks watch {task-id} \
-  --interval-seconds 30 --deadline-seconds 1800
-
-agent-infra-internal platform-checks resolve-run {task-id} \
-  --check-name {check-name} [--details-url {details-url}]
-
-agent-infra-internal platform-checks logs {task-id} \
-  --run {run-id} [--job {job-id}]
-```
-
-The adapter normalizes REST `mergeable=false` to `conflicting`, null/missing to `unknown`, and true to `mergeable`; `mergeable=true` plus diagnostic `dirty` is contradictory and becomes `unknown`. Other diagnostics such as `blocked` do not override REST true. Core combines that fact with all checks for one `headSha`: only `ready` exits 0, `conflicting|checks-failed` exit 1, and pending/timeout/cancel/network blocking exit 2. Dependency and deterministic platform errors are preserved without degradation.

package/templates/.agents/rules/pr-checks-commands.github.zh-CN.md

@@ -1,34 +0,0 @@
-# GitHub PR readiness 平台意图
-
-PR 全部 checks 的获取、轮询 deadline、失败 run/job 定位和日志获取统一由 typed internal intent 执行。SKILL/模型只负责失败分类、根因分析、最小修复和授权后的提交推送。
-
-GitHub adapter 要求 `gh >= 2.72.0`。平台上下文会在任何 GitHub API、PR 或 checks 操作前检查该依赖；未选择 GitHub 平台时不探测也不依赖 `gh`。
-
-## 快照与监控
-
-```bash
-agent-infra-internal platform-checks inspect {task-id}
-
-agent-infra-internal platform-checks watch {task-id} \
-  --interval-seconds 30 --deadline-seconds 1800
-```
-
-adapter 把 REST `mergeable=false` 规范化为 `conflicting`，null/缺失为 `unknown`，true 为 `mergeable`；true 与诊断 `dirty` 矛盾时降为 `unknown`。`blocked` 等其他诊断不覆盖 REST true。core 在同一 `headSha` 上与全部 checks 聚合：仅 `ready` 退出 0，`conflicting|checks-failed` 退出 1，pending/timeout/cancel/网络阻塞退出 2。依赖与确定性平台错误不降级。
-
-## 定位失败 run/job
-
-```bash
-agent-infra-internal platform-checks resolve-run {task-id} \
-  --check-name {check-name} [--details-url {details-url}]
-```
-
-core 优先验证详情链接；否则按 PR head SHA 与 exact check name 查询。零个或多个候选均 fail closed，不选择其他 run。
-
-## 获取失败日志
-
-```bash
-agent-infra-internal platform-checks logs {task-id} \
-  --run {run-id} [--job {job-id}]
-```
-
-日志结果保真返回；缺失、权限、网络和资源不存在使用稳定错误码区分。平台 intent 不修改业务代码、不测试、不提交也不推送。

package/templates/.agents/rules/pr-sync.github.en.md

@@ -1,43 +0,0 @@
-# PR Summary Synchronization
-
-> `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
-
-The model writes the semantic reviewer summary. Typed core owns canonical artifact selection, marker/HEAD wrapping, paginated comment lookup, and reconciliation.
-
-## Three-Layer Isolation
-
-- `sync-pr:{task-id}:summary` (`platform-pr summary-sync`) is an updatable reviewer summary; it is neither a process copy nor a formal Review.
-- The full `pr-review*` process copy lives in the Issue artifact comment (`platform-comment sync --kind artifact`) and is restored by `restore-task` under its Issue-only contract.
-- A formal PR Review (`platform-pr-review publish`) is the only formal conclusion carrier published to the PR, bound to the reviewed head SHA, and includes conclusion, findings, receipt, and the Issue artifact link.
-
-The three never cross: a regular PR comment does not carry the full process copy; an Issue artifact comment is not treated as a formal Review; a summary is not presented as a formal Review.
-
-```bash
-agent-infra-internal platform-pr summary-context {task-id}
-
-agent-infra-internal platform-pr summary-sync {task-id} \
-  --agent {standard-agent-token} --body-file {summary-body-file}
-```
-
-Use only canonical inputs returned by the context command. Write the plain body without marker or SHA. The core owns `<!-- sync-pr:{task-id}:summary -->`, current `<!-- last-commit: ... -->`, create/update/no-op behavior, and duplicate-marker conflicts. Summary failure never rolls back a PR or commit.
-
-The canonical comment envelope produced by the core is:
-
-```markdown
-<!-- sync-pr:{task-id}:summary -->
-<!-- last-commit: {git-head-sha} -->
-## Review Summary
-{manual-validation-section}
-### Key Technical Decisions
-### Review History
-### Test Results
-### PR Code Changes
-```
-
-Canonical inputs include `manual-validation.md`. The manual-validation section is one of `### ✅ Manual Validation Passed`, `### ⚠️ Manual Verification Required`, or `### ✅ No Manual Verification Needed`; `complete-manual-validation` refreshes the same summary in place. The PR code-change section uses authoritative base/head facts from `platform-pr inspect` and the complete `git diff --find-renames --numstat base...head`, reconciles runtime, test, skill/rule, template, documentation, and other categories, and explains renames, mechanical mirrors, and potentially unnecessary changes.
-
-```bash
-agent-infra-internal task-warning {task-id} add --step {step} --severity WARNING \
-  --code COMMENT_SYNC_FAILED --target pr-summary --message "{reason}" \
-  --action "Restore comment permission or connectivity and rerun this step"
-```

package/templates/.agents/rules/pr-sync.github.zh-CN.md

@@ -1,69 +0,0 @@
-# PR 摘要同步
-
-> `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
-
-PR 摘要的语义聚合由模型完成；canonical 产物选择、marker、当前 HEAD、分页评论查找和 create/update/no-op 由 typed core 负责。
-
-## 三层隔离
-
-- `sync-pr:{task-id}:summary`（`platform-pr summary-sync`）是可更新的 reviewer 摘要，不是过程原文，也不是正式 Review。
-- `pr-review*` 完整过程原文在 Issue artifact 评论（`platform-comment sync --kind artifact`），由 `restore-task` 按 Issue-only 契约恢复。
-- 正式 PR Review（`platform-pr-review publish`）是唯一发布到 PR 的正式结论载体，绑定被审 head SHA，含结论、finding、receipt 与 Issue artifact 链接。
-
-三者不串用：PR 普通评论不承载完整过程原文；Issue artifact 评论不当作正式 Review；摘要不冒充正式 Review。
-
-## 聚合输入
-
-```bash
-agent-infra-internal platform-pr summary-context {task-id}
-```
-
-只使用返回的 canonical latest `plan*`、`review-plan*`、`code*`、`review-code*`、`manual-validation*`（包括 `manual-validation.md`）。模型据此生成 reviewer 摘要正文，至少包含：
-
-- 变更摘要与实现范围
-- 测试结果
-- 审查历程与当前结论
-- 人工校验三态：`### ⚠️ 需人工校验`、`### ✅ 人工验证已通过` 或 `### ✅ 无需人工校验`
-- `### PR 代码增减`：基于 `platform-pr inspect` 的权威 base/head 和完整 `git diff --find-renames --numstat base...head`，按运行时代码、测试、Skill/规则、模板、文档及其他分类核算，并说明 rename、机械镜像与疑似不必要变化
-
-保留人工校验项时，每条写明校验内容、定位和只能人工完成的原因。
-
-core 最终包装出的 canonical 评论结构为：
-
-```markdown
-<!-- sync-pr:{task-id}:summary -->
-<!-- last-commit: {git-head-sha} -->
-## 审查摘要
-{manual-validation-section}
-### 关键技术决策
-### 审查历程
-### 测试结果
-### PR 代码增减
-```
-
-## 发布
-
-把聚合后的纯正文写入 `{summary-body-file}`，不要自行添加 marker 或 commit SHA：
-
-```bash
-agent-infra-internal platform-pr summary-sync {task-id} \
-  --agent {standard-agent-token} --body-file {summary-body-file}
-```
-
-core 会包装唯一 `<!-- sync-pr:{task-id}:summary -->` 和当前 `<!-- last-commit: ... -->`，分页查找 PR 普通评论：不存在则创建、正文变化则原地更新、无差异则 no-op、重复 marker 则稳定失败。正文通过文件输入，调用方不得拼 shell/heredoc。
-
-## 结果回传
-
-- `applied`：`summary created` 或 `summary updated`
-- `no-op`：`summary skipped (no diff)`
-- `failed|blocked`：`summary failed: {error.code}: {error.message}`
-
-`create-pr` 中摘要失败不回滚已创建 PR；`commit` 中只记 warning，不回滚 commit；`complete-manual-validation` 在 canonical artifact 落盘后调用同一 intent 原地刷新。
-
-关联任务的摘要失败由调用方登记结构化告警：
-
-```bash
-agent-infra-internal task-warning {task-id} add --step {step} --severity WARNING \
-  --code COMMENT_SYNC_FAILED --target pr-summary --message "{reason}" \
-  --action "修复评论权限或平台连接后重跑当前步骤"
-```

package/templates/.agents/rules/release-commands.github.en.md

@@ -1,44 +0,0 @@
-# Release Platform Commands
-
-Release-note platform operations use a typed internal intent. Callers consume structured JSON and do not interpret platform commands, raw fields, identity email rules, or authentication errors.
-
-## Collect Release-note Context
-
-```bash
-agent-infra-internal platform-release-notes context \
-  --from-tag "v{prev-version}" \
-  --to-tag "v{version}" \
-  --branch "{branch}" \
-  --history-limit 3
-```
-
-The result contains `history`, `pullRequests`, `closingIssues`, and commit `authors` with normalized `login` / `resolution` values. `status: no-op` with error code `PLATFORM_RELEASE_NOTES_UNSUPPORTED` means the current platform does not support remote release-note operations.
-
-### Identity Safety Boundary
-
-- Render an identity as `@login` only when `resolution` is `platform-user` or `platform-noreply` and `login` is non-empty.
-- Exclude `resolution: unresolved` identities from the release-note contributor list. Never infer a login from a name, email address, domain, brand, or same-named platform account, and never substitute a guessed personal or organization account.
-- Do not publish unresolved identity emails or identity-verification TODOs in Release notes. Record any required investigation outside the release workflow without creating a platform mention.
-
-## Stage Release Notes
-
-```bash
-agent-infra-internal platform-release-notes stage \
-  --notes-file "{notes-file}"
-```
-
-The command accepts only an external regular file, normalizes it atomically, and returns SHA-256 for its exact bytes.
-
-## Publish Release Notes
-
-Call this only after user confirmation:
-
-```bash
-agent-infra-internal platform-release-notes publish \
-  --tag "v{version}" \
-  --title "v{version}" \
-  --notes-file "{notes-file}" \
-  --expected-sha256 "{preview-sha256}"
-```
-
-The command recomputes the digest before platform access and performs no platform write on mismatch. On a match it updates an existing Release or creates it when missing; `--dry-run` returns only the planned operation. Exit code `0` means success, `1` means a stable failure, and `2` means a network or platform block.

package/templates/.agents/rules/release-commands.github.zh-CN.md

@@ -1,44 +0,0 @@
-# Release 平台命令
-
-发布说明平台操作统一使用 typed internal intent。调用方只解释结构化 JSON，不解析平台命令、原始字段、身份邮箱规则或认证错误。
-
-## 收集发布说明上下文
-
-```bash
-agent-infra-internal platform-release-notes context \
-  --from-tag "v{prev-version}" \
-  --to-tag "v{version}" \
-  --branch "{branch}" \
-  --history-limit 3
-```
-
-结果包含 `history`、`pullRequests`、`closingIssues` 和带规范化 `login` / `resolution` 的 commit `authors`。`status: no-op` 且错误码为 `PLATFORM_RELEASE_NOTES_UNSUPPORTED` 表示当前平台不支持远端发布说明能力。
-
-### 身份安全边界
-
-- 只有 `resolution` 为 `platform-user` 或 `platform-noreply` 且 `login` 非空的身份可以渲染为 `@login`。
-- `resolution: unresolved` 的身份不得进入发布说明的贡献者列表；不得从 Name、邮箱、域名、品牌或同名平台账号推断 login，也不得替换成推测的个人或组织账号。
-- 不得把未解析身份的邮箱或身份确认 TODO 写入可发布的 Release notes。需要调查时仅在发布流程外记录，不得产生平台 mention。
-
-## Stage Release notes
-
-```bash
-agent-infra-internal platform-release-notes stage \
-  --notes-file "{notes-file}"
-```
-
-命令只接受工作树外普通文件，原子规范化并返回精确 bytes 的 SHA-256。
-
-## 发布 Release notes
-
-用户确认后调用：
-
-```bash
-agent-infra-internal platform-release-notes publish \
-  --tag "v{version}" \
-  --title "v{version}" \
-  --notes-file "{notes-file}" \
-  --expected-sha256 "{preview-sha256}"
-```
-
-命令在平台访问前复算摘要，不匹配时零写入；匹配时更新已有 Release，缺失时创建。`--dry-run` 只返回 planned operation。退出码为 `0` 时成功，`1` 表示稳定失败，`2` 表示网络或平台阻塞。

package/templates/.agents/rules/security-alerts.github.en.md

@@ -1,43 +0,0 @@
-# Security Alert Platform Commands
-
-Read this file before importing or dismissing Dependabot or Code Scanning alerts.
-
-## Dependabot Alerts
-
-Read an alert:
-
-```bash
-gh api "repos/{owner}/{repo}/dependabot/alerts/{number}"
-```
-
-Dismiss an alert:
-
-```bash
-gh api --method PATCH "repos/{owner}/{repo}/dependabot/alerts/{number}" \
-  -f state="dismissed" \
-  -f dismissed_reason="{reason}" \
-  -f dismissed_comment="{comment}"
-```
-
-## Code Scanning Alerts
-
-Read an alert:
-
-```bash
-gh api "repos/{owner}/{repo}/code-scanning/alerts/{number}"
-```
-
-Dismiss an alert:
-
-```bash
-gh api --method PATCH "repos/{owner}/{repo}/code-scanning/alerts/{number}" \
-  -f state="dismissed" \
-  -f dismissed_reason="{reason}" \
-  -f dismissed_comment="{comment}"
-```
-
-## Constraints
-
-- read the current alert state before deciding whether to continue
-- validate dismissal reasons in the calling skill before sending them
-- stop or escalate according to the calling skill when API calls fail