@fitlab-ai/agent-infra 0.8.5 → 0.9.0

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

@@ -1,155 +1,20 @@
 # Issue 字段
 
-写入或校验 Issue Type pinned custom fields 前先读取本文件。
+Issue Type 与 pinned fields 统一由 `platform-issue` intent 动态读取组织 schema 并同步：
 
-## 边界
-
-- 仅在已知 `upstream_repo`、`has_push` 和 Issue 编号后使用本规则。
-- 如果 `has_push=false`，跳过直接字段写入并继续流程。
-- 每次写入前都读取组织当前 Issue Type schema；不要硬编码字段集合。
-- 缺失、空值或无法解析的值直接跳过。字段写入是 best-effort，不应阻断工作流。
-
-## 支持的 task.md frontmatter
+```bash
+agent-infra-internal platform-issue sync {task-id} --agent {agent} --issue-type --fields
+```
 
-所有字段均可选：
+## 支持字段
 
 | task.md 字段 | Issue 字段 | 值格式 |
 |---|---|---|
-| `priority` | `Priority` | `Urgent`、`High`、`Medium` 或 `Low` |
-| `effort` | `Effort` | `High`、`Medium` 或 `Low` |
+| `priority` | `Priority` | `Urgent`、`High`、`Medium`、`Low`，支持紧急/高/中/低本地化输入 |
+| `effort` | `Effort` | `High`、`Medium`、`Low`，支持高/中/低本地化输入 |
 | `start_date` | `Start date` | `YYYY-MM-DD` |
 | `target_date` | `Target date` | `YYYY-MM-DD` |
 
-写入前可规范化本地化选项：
-
-| 输入 | 写入选项 |
-|---|---|
-| `紧急` | `Urgent` |
-| `高` | `High` |
-| `中` | `Medium` |
-| `低` | `Low` |
-
-AI agent 在创建或修订任务时可根据标题与描述推断 `priority` 和 `effort`。日期字段为事实值、不估算：`start_date` 由 analyze 阶段写入（= 分析开始日），`target_date` 由 complete 阶段写入（= 完成日）。`task.md` 中人工填写的值优先。
-
-## GraphQL 参考
-
-读取 Issue Type pinned fields：
-
-```graphql
-query($owner:String!){
-  organization(login:$owner){ issueTypes(first:20){ nodes{
-    id name
-    pinnedFields{
-      __typename
-      ... on IssueFieldSingleSelect{ id name options{ id name } }
-      ... on IssueFieldDate{ id name }
-      ... on IssueFieldText{ id name }
-      ... on IssueFieldNumber{ id name }
-    }
-  } } }
-}
-```
-
-读取单个 Issue 的当前 type 与字段值：
-
-```graphql
-query($owner:String!,$name:String!,$number:Int!){
-  repository(owner:$owner,name:$name){ issue(number:$number){
-    id
-    issueType{ name pinnedFields{
-      __typename
-      ... on IssueFieldSingleSelect{ id name options{ id name } }
-      ... on IssueFieldDate{ id name }
-      ... on IssueFieldText{ id name }
-      ... on IssueFieldNumber{ id name }
-    } }
-    issueFieldValues(first:50){ nodes{
-      __typename
-      ... on IssueFieldSingleSelectValue{ name optionId field{ ... on IssueFieldSingleSelect{ name } } }
-      ... on IssueFieldDateValue{ value field{ ... on IssueFieldDate{ name } } }
-      ... on IssueFieldTextValue{ value field{ ... on IssueFieldText{ name } } }
-      ... on IssueFieldNumberValue{ value field{ ... on IssueFieldNumber{ name } } }
-    } }
-  } }
-}
-```
-
-写入或清空字段，以及更新 Issue Type：
-
-```graphql
-mutation($issueId:ID!,$issueFields:[IssueFieldCreateOrUpdateInput!]!){
-  setIssueFieldValue(input:{issueId:$issueId,issueFields:$issueFields}){ issue{ id } }
-}
-
-mutation($issueId:ID!,$issueTypeId:ID){
-  updateIssueIssueType(input:{issueId:$issueId,issueTypeId:$issueTypeId}){ issue{ id } }
-}
-```
-
-`IssueFieldCreateOrUpdateInput` 支持 `fieldId`、`singleSelectOptionId`、`dateValue`、`textValue`、`numberValue` 和 `delete`。
-
-最小命令壳：
-
-```bash
-gh api graphql \
-  -f query='query($owner:String!){organization(login:$owner){issueTypes(first:20){nodes{id name pinnedFields{__typename ... on IssueFieldSingleSelect{id name options{id name}} ... on IssueFieldDate{id name} ... on IssueFieldText{id name} ... on IssueFieldNumber{id name}}}}}}' \
-  -F owner="{owner}"
-
-gh api graphql \
-  -f query='query($owner:String!,$name:String!,$number:Int!){repository(owner:$owner,name:$name){issue(number:$number){id issueType{name pinnedFields{__typename ... on IssueFieldSingleSelect{id name options{id name}} ... on IssueFieldDate{id name} ... on IssueFieldText{id name} ... on IssueFieldNumber{id name}}} issueFieldValues(first:50){nodes{__typename ... on IssueFieldSingleSelectValue{name optionId field{... on IssueFieldSingleSelect{name}}} ... on IssueFieldDateValue{value field{... on IssueFieldDate{name}}} ... on IssueFieldTextValue{value field{... on IssueFieldText{name}}} ... on IssueFieldNumberValue{value field{... on IssueFieldNumber{name}}}}}}}}' \
-  -F owner="{owner}" -F name="{repo}" -F number="{issue-number}"
-
-gh api graphql --input - <<'JSON'
-{
-  "query": "mutation($issueId:ID!,$issueFields:[IssueFieldCreateOrUpdateInput!]!){setIssueFieldValue(input:{issueId:$issueId,issueFields:$issueFields}){issue{id}}}",
-  "variables": {
-    "issueId": "{issue-id}",
-    "issueFields": [
-      { "fieldId": "{field-id}", "singleSelectOptionId": "{option-id}" },
-      { "fieldId": "{date-field-id}", "dateValue": "YYYY-MM-DD" },
-      { "fieldId": "{old-field-id}", "delete": true }
-    ]
-  }
-}
-JSON
-
-gh api graphql --input - <<'JSON'
-{
-  "query": "mutation($issueId:ID!,$issueTypeId:ID){updateIssueIssueType(input:{issueId:$issueId,issueTypeId:$issueTypeId}){issue{id}}}",
-  "variables": {
-    "issueId": "{issue-id}",
-    "issueTypeId": "{issue-type-id}"
-  }
-}
-JSON
-```
-
-未列入本地化映射表的值会按字面量 option name 处理；这是为了支持规范英文输入。
-
-## 流程 A：创建 Issue 后写入字段
-
-1. 如果 `has_push` 不是 `true`，停止本流程。
-2. 从 `$upstream_repo` 解析 `{owner}`，查询 `organization.issueTypes`。
-3. 选择目标 Issue Type 的 `pinnedFields`。
-4. 从 `task.md` 读取非空的 `priority`、`effort`、`start_date` 和 `target_date`。
-5. 对每个值：
-   - 目标 type 未 pin 同名字段时跳过。
-   - single-select 字段先规范化本地化输入，再按 option name 匹配。
-   - date 字段只写入 `YYYY-MM-DD` 值。
-6. 用所有已解析 input 一次性提交 `setIssueFieldValue` mutation。没有 input 时跳过。
-
-## 流程 B：设置 Type 并迁移字段
-
-现有 Issue Type 发生变更时使用本流程。
-
-1. 如果 `has_push` 不是 `true`，停止本流程。
-2. 读取 Issue id、当前 Issue Type、pinned fields 和当前字段值。
-3. 查询组织 Issue Type 列表，解析目标 Issue Type id。
-4. 用目标 Issue Type id 执行 `updateIssueIssueType`。
-5. 解析目标 type 的 pinned fields。
-6. 对每个旧字段值：
-   - 目标 type 有同名字段时重新写入该值。single-select 值按 option name 在目标 type 中重新解析 option id。
-   - 目标 type 没有同名字段时，对旧字段发送 `{ fieldId, delete: true }`。
-7. 用所有迁移 input 一次性提交 `setIssueFieldValue` mutation。迁移 input 为空时跳过。
+适配层每次从组织读取当前 Issue Type schema，不硬编码 Type、field 或 option ID。Type 变化时按字段名迁移仍受支持的值，并清理目标 Type 不再支持的旧字段。个人仓库或 `push=false` 时只跳过 Type/fields operations，其他同步继续。
 
-两个流程均应保持幂等。重复写入未变化的值或删除已为空字段都是可接受的。
+调用方只声明业务时机，不直接拼 GraphQL；结果和错误处理遵循 `.agents/rules/issue-sync.md`。

package/templates/.agents/rules/issue-pr-commands.en.md

@@ -1,5 +1,45 @@
-# Issue and PR Commands
+# PR Platform Intents
 
-This code platform does not provide built-in issue or pull request commands.
+PR lookup, creation, binding, and metadata synchronization go through typed internal intents. Skills decide branches and write titles/bodies; they do not assemble platform commands.
 
-Platform-specific automation is skipped for custom platforms unless you provide matching `.{platform}.en.md` rule templates. Keep local task artifacts as the source of truth, or install a platform-specific template pack before running the workflow.
+## Inspect
+
+```bash
+agent-infra-internal platform-pr inspect {task-id}
+```
+
+## Create or recover
+
+Write the title and body to files, then run:
+
+```bash
+agent-infra-internal platform-pr create {task-id} \
+  --agent {agent} --base {target-branch} --head {current-branch} \
+  --title-file {title-file} --body-file {body-file}
+```
+
+The core performs exact upstream/head/base lookup first. One match is reused, zero creates, and multiple matches fail closed. Unknown create outcomes are reconciled by the same exact identity rather than retried blindly. `--dry-run` returns only the plan.
+
+## Bind
+
+```bash
+agent-infra-internal platform-pr bind {task-id} --pr {pr-number} --agent {agent}
+```
+
+Conflicting bindings fail without changing `task.md`.
+
+## Synchronize metadata
+
+```bash
+agent-infra-internal platform-pr sync {task-id} \
+  --agent {agent} --metadata --closing-issue
+```
+
+The core copies type / `in:` labels, assignee, a specific milestone, and the closing association from the linked Issue. Permission-bound operations report `skipped` under top-level `degraded`; the Issue is never updated in reverse.
+
+## Status contract
+
+- `planned|applied|no-op|degraded`: exit 0.
+- `failed`: exit 1.
+- `blocked`: exit 2 for authentication, network, or unknown outcome.
+- Metadata or summary failures never roll back an already-created PR.

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

@@ -1,237 +1,32 @@
-# Issue / PR Platform Commands
+# PR Platform Intents
 
-Read this file before verifying platform authentication, reading Issues / PRs, or creating and updating Issues / PRs.
+PR lookup, creation, binding, and metadata synchronization go through typed internal intents. Skills decide branches and write titles/bodies; they do not assemble platform commands.
 
-## Authentication and Repository Info
-
-Verify that GitHub CLI is available and authenticated:
-
-```bash
-gh auth status
-gh repo view --json nameWithOwner
-```
-
-If either command fails, stop or degrade according to the calling skill.
-
-## Upstream Repository and Permission Detection
-
-Before any later `gh issue` or `gh api "repos/..."` call, follow `.agents/rules/issue-sync.md` to resolve `upstream_repo`, `has_triage`, and `has_push`.
-
-- every later `gh issue` command must use `-R "$upstream_repo"`
-- every later repository-scoped `gh api` command must use `"repos/$upstream_repo/..."`
-- keep `gh pr *` commands on the current repository without adding `-R`
-- keep organization-scoped commands such as `gh api "orgs/{owner}/..."` unchanged
-
-## Issue Template Detection
-
-Detect GitHub Issue Forms with:
-
-```bash
-rg --files .github/ISSUE_TEMPLATE -g '*.yml' -g '!config.yml'
-```
-
-Read matching form files locally before creating the Issue. If the directory is missing or no form matches the task, use the caller's fallback body format.
-
-Typical candidate templates:
-- `bug_report.yml` for bug work
-- `question.yml` for question or investigation work
-- `feature_request.yml` for feature work
-- `documentation.yml` for documentation work
-- `other.yml` as the general fallback
-
-For GitHub Issue Forms, inspect the matched form's:
-- `name`
-- `type:`
-- `labels:`
-- `body:`
-
-Field handling rules:
-- `textarea` and `input`: use `attributes.label` as the markdown heading and fill values from task.md
-- `markdown`: skip template explanation prose
-- `dropdown` and `checkboxes`: skip
-- when task.md lacks a suitable value, write `N/A`
-
-Suggested field mapping:
-
-| Template field hint | task.md source |
-|---|---|
-| `summary`, `title` | task title |
-| `description`, `problem`, `what happened`, `issue-description`, `current-content` | task description |
-| `solution`, `requirements`, `steps`, `suggested-content`, `impact`, `context`, `alternatives`, `expected` | requirements list |
-| other `textarea` / `input` fields | task description, otherwise `N/A` |
-
-## Read and Create Issues
-
-Read an Issue:
-
-```bash
-gh issue view {issue-number} -R "$upstream_repo" --json number,title,body,labels,state,milestone,url
-```
-
-Create an Issue:
-
-```bash
-gh issue create -R "$upstream_repo" --title "{title}" --body "{body}" --assignee @me {label-args} {milestone-arg}
-```
-
-- expand `{label-args}` into repeated `--label` flags from the validated label list
-- pass `{label-args}` only when `has_triage=true`; otherwise omit it and continue
-- omit all `--label` flags when nothing valid remains
-- pass `{milestone-arg}` only when `has_triage=true`; otherwise omit it and continue
-- omit `{milestone-arg}` entirely when no milestone should be set
-
-Set the Issue Type:
-
-```bash
-owner_type=$(gh api "repos/$upstream_repo" --jq '.owner.type // empty' 2>/dev/null || true)
-if [ "$owner_type" = "Organization" ]; then
-  owner=${upstream_repo%%/*}
-  gh api "orgs/$owner/issue-types" --jq '.[].name'
-  gh api "repos/$upstream_repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent
-fi
-```
-
-- set the Issue Type only when `has_push=true`; otherwise skip and continue
-- query and set Issue Type only when the owner type is `Organization`; skip and continue for user repositories or failed owner type probes
-- when changing an existing Issue Type, read `.agents/rules/issue-fields.md` and use Flow B so same-name pinned fields are migrated and fields absent from the new type are cleared
-
-## Update Issues
-
-Use this shape when updating titles, labels, assignees, or milestones:
+## Inspect
 
 ```bash
-gh issue edit {issue-number} -R "$upstream_repo" {edit-args}
+agent-infra-internal platform-pr inspect {task-id}
 ```
 
-Common arguments:
-- `--title "{title}"`
-- `--add-label "{label}"` (only when `has_triage=true`)
-- `--remove-label "{label}"` (only when `has_triage=true`)
-- `--add-assignee @me`
-- `--milestone "{milestone}"` (only when `has_triage=true`)
-
-Do not pre-check assignee permissions. If the assignee command fails, silently skip it per the caller's contract.
-
-Close an Issue:
+## Create or recover
 
 ```bash
-gh issue close {issue-number} -R "$upstream_repo" --reason "{reason}"
+agent-infra-internal platform-pr create {task-id} \
+  --agent {agent} --base {target-branch} --head {current-branch} \
+  --title-file {title-file} --body-file {body-file}
 ```
 
-## Read Issue Comments
+The core performs exact upstream/head/base lookup. One match is reused, zero creates, and multiple matches fail closed. Unknown create outcomes are reconciled by exact identity. `--dry-run` returns only the plan.
 
-Read Issue comments or search for existing hidden markers:
+## Bind and synchronize
 
 ```bash
-gh api "repos/$upstream_repo/issues/{issue-number}/comments" --paginate
-```
+agent-infra-internal platform-pr bind {task-id} --pr {pr-number} --agent {agent}
 
-## Historical Task Comment Scan
-
-`find-existing-task.js` only consumes stdin and does not call `gh` directly. The AI selects the pipeline command for the host OS.
-
-POSIX (bash / zsh):
-
-```bash
-set -o pipefail
-gh api "repos/$upstream_repo/issues/{issue-number}/comments" \
-  --paginate --jq '.[] | @json' \
-  | node .agents/scripts/find-existing-task.js
+agent-infra-internal platform-pr sync {task-id} \
+  --agent {agent} --metadata --closing-issue
 ```
 
-Windows (PowerShell 7+ / pwsh):
-
-```powershell
-$ErrorActionPreference = 'Stop'
-gh api "repos/$upstream_repo/issues/{issue-number}/comments" `
-  --paginate --jq '.[] | @json' |
-  node .agents/scripts/find-existing-task.js
-if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }
-```
-
-On PowerShell 5.1, explicitly enable UTF-8 stdio first; otherwise the pipe may corrupt multibyte characters:
-
-```powershell
-[Console]::OutputEncoding = $OutputEncoding = [System.Text.UTF8Encoding]::new()
-```
-
-## PR Template and Metadata Helpers
-
-Read a repository PR template when present:
-
-```bash
-cat .github/PULL_REQUEST_TEMPLATE.md
-```
-
-Review recent merged PRs for style:
-
-```bash
-gh pr list --limit 3 --state merged --json number,title,body
-```
-
-Verify that standard type labels exist before PR metadata sync:
-
-```bash
-gh label list --search "type:" --limit 1 --json name --jq 'length'
-```
-
-If the result is `0`, run `init-labels` before retrying PR metadata sync.
-
-## Read and Create PRs
-
-Read a PR:
-
-```bash
-gh pr view {pr-number} --json number,title,body,labels,state,milestone,url,files
-```
-
-List PRs:
-
-```bash
-gh pr list --state {state} --base {base-branch} --json number,title,url,headRefName,baseRefName
-```
-
-Find the open PR whose head is the current branch (used by the `commit` push wrap-up):
-
-```bash
-gh pr list --head "{branch}" --state open --json number,url --jq '.[0].url // empty'
-```
-
-Create a PR:
-
-```bash
-gh pr create --base "{target-branch}" --title "{title}" --assignee @me \
-  {label-args} {milestone-arg} \
-  --body "$(cat <<'EOF'
-{pr-body}
-EOF
-)"
-```
-
-- expand `{label-args}` into repeated `--label "{label}"` flags from the validated label list
-- pass `{label-args}` only when `has_triage=true`; otherwise omit it and continue
-- omit all `--label` flags when nothing valid remains
-- expand `{milestone-arg}` into `--milestone "{milestone}"`
-- pass `{milestone-arg}` only when `has_triage=true`; otherwise omit it and continue
-- omit `{milestone-arg}` entirely when no milestone should be set
-
-## Update PRs
-
-Update PR titles, labels, or milestones with:
-
-```bash
-gh pr edit {pr-number} {edit-args}
-```
-
-Common arguments:
-- `--title "{title}"`
-- `--add-label "{label}"`
-- `--remove-label "{label}"`
-- `--milestone "{milestone}"`
-
-## Error Handling
+Conflicting bindings do not change `task.md`. Metadata comes from the linked Issue, permission-bound items degrade independently, and an already-created PR is never rolled back.
 
-- read failures: stop or skip based on the calling skill
-- update failures: warn and continue when the caller marks the action as best-effort
-- insufficient permission: skip direct writes according to the `has_triage` / `has_push` branch and continue
-- `@me` is resolved by `gh` CLI to the authenticated user
+Statuses `planned|applied|no-op|degraded` exit 0, `failed` exits 1, and `blocked` exits 2.