@fitlab-ai/agent-infra 0.9.11 → 0.9.12

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

package/templates/.agents/rules/security-alerts.github.zh-CN.md

@@ -1,43 +0,0 @@
-# 安全告警平台命令
-
-在导入或关闭 Dependabot / Code Scanning 告警前先读取本文件。
-
-## Dependabot 告警
-
-读取告警：
-
-```bash
-gh api "repos/{owner}/{repo}/dependabot/alerts/{number}"
-```
-
-关闭告警：
-
-```bash
-gh api --method PATCH "repos/{owner}/{repo}/dependabot/alerts/{number}" \
-  -f state="dismissed" \
-  -f dismissed_reason="{reason}" \
-  -f dismissed_comment="{comment}"
-```
-
-## Code Scanning 告警
-
-读取告警：
-
-```bash
-gh api "repos/{owner}/{repo}/code-scanning/alerts/{number}"
-```
-
-关闭告警：
-
-```bash
-gh api --method PATCH "repos/{owner}/{repo}/code-scanning/alerts/{number}" \
-  -f state="dismissed" \
-  -f dismissed_reason="{reason}" \
-  -f dismissed_comment="{comment}"
-```
-
-## 约束
-
-- 先读取当前告警状态，再决定是否继续
-- 关闭理由必须由调用方校验后再传入
-- API 失败时按调用方规则停止或提示人工介入