@fitlab-ai/agent-infra 0.8.5 → 0.9.0

package/templates/.agents/skills/post-release/SKILL.en.md

@@ -1,98 +1,28 @@
 ---
 name: post-release
 description: >
-  Run post-release follow-up tasks.
-  Use when a release has shipped and follow-up housekeeping is needed.
+  Run post-release processing.
+  Use after a version has been published and needs finalization.
 ---
 
-# Post-release Tasks
+# Post-release
 
-Run the standard follow-up workflow after a release tag has been pushed.
-
-## Execution Flow
-
-### 1. Detect the Latest Released Version
-
-```bash
-git tag --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1
-```
-
-- Detect the latest `vX.Y.Z` tag, then strip the `v` prefix when you need the version number in later steps
-- If no tag is found, error: "No released version tag found. Please create and push a release tag first."
-
-### 2. Verify Clean Workspace
-
-```bash
-git status --short
-```
-
-- If there are uncommitted changes, error: "Workspace has uncommitted changes. Please commit or stash first."
-
-### 3. Prepare the Next Development Version
-
-<!-- TODO: Replace this step with your project's version bump command -->
-
-```bash
-# TODO: Replace with your project's post-release version bump command
-# npm version prerelease --preid=alpha --no-git-tag-version
-```
-
-- Update lockfiles or generated version metadata if your project needs them
-- Keep all version references in sync after the bump
-
-### 4. Rebuild Generated Artifacts
-
-<!-- TODO: Replace this step with your project's rebuild command -->
+## 1. Inspect Channel Facts
 
 ```bash
-# TODO: Replace with your project's artifact rebuild command
+agent-infra-internal release-workflow inspect {version}
 ```
 
-- Rebuild any generated files, embedded assets, or inline templates affected by the new version
-- If your project has no generated artifacts, remove this step in the project-specific copy
+Pending or unknown is blocked; a definite failure is failed.
 
-### 5. Run Other Post-release Tasks (Optional)
-
-<!-- TODO: Add project-specific follow-up tasks such as demo capture, docs publishing, or downstream notifications -->
-
-- Examples: record a terminal demo, refresh a docs site, notify downstream teams, update release dashboards
-- If a task here displays or captures the just-released version (e.g., recording a CLI demo), move it **before** Step 3 — otherwise it will reflect the next development version, not the release
-- If there are no extra tasks, remove this step in the project-specific copy
-
-### 6. Create the Follow-up Commit
+## 2. Run Post-release
 
 ```bash
-git add -A
-git commit -m "chore: prepare next dev iteration after v{released-version}"
+agent-infra-internal release-workflow post {version}
 ```
 
-### 7. Output Summary
-
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent. If `.agents/.airc.json` configures custom TUIs (via `customTUIs`), read each tool's `name` and `invoke`, then add the matching command line in the same format (`${skillName}` becomes the skill name and `${projectName}` becomes the project name).
-
-```
-Post-release tasks completed.
-
-Summary:
-- Released version: {released-version}
-- Next development version: {new-version}
-- Extra tasks completed: {summary}
-
-Next step (manual):
-- Push branch: git push origin {current-branch}
-```
-
-## Notes
-
-1. **No arguments**: Detect the released version from the latest tag instead of asking the user to repeat it
-2. **Clean workspace required**: Avoid mixing unrelated edits into the post-release commit
-3. **Project-specific customization**: Replace the TODO steps with the commands your project actually needs
-4. **Local-only workflow**: This skill prepares local changes and does not push automatically
+The core owns build, next development version, inline artifacts, explicit-path commit, normal push, and post-write inspection.
 
-## Error Handling
+## 3. Report the Snapshot
 
-- No release tag found: Prompt the user to finish the release first
-- Dirty workspace: Prompt the user to commit or stash changes
-- Version bump failed: Display the command error and stop
-- Artifact rebuild failed: Display the build error and stop
-- Git commit failed: Display the error and leave the workspace intact for manual recovery
+Report channel, smoke, commit, and push facts without presenting degraded or blocked as complete.

package/templates/.agents/skills/post-release/SKILL.zh-CN.md

@@ -7,92 +7,22 @@ description: >
 
 # 发布后处理
 
-在版本标签推送完成后，执行标准化的发布后收尾流程。
-
-## 执行流程
-
-### 1. 检测最新发布版本
-
-```bash
-git tag --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -n 1
-```
-
-- 检测最新 `vX.Y.Z` 标签，并在后续步骤中去除 `v` 前缀得到版本号
-- 如果没有找到标签，报错："No released version tag found. Please create and push a release tag first."
-
-### 2. 验证工作区干净
-
-```bash
-git status --short
-```
-
-- 如果存在未提交变更，报错："Workspace has uncommitted changes. Please commit or stash first."
-
-### 3. 准备下一个开发版本
-
-<!-- TODO: 将此步骤替换为你的项目版本 bump 命令 -->
-
-```bash
-# TODO: 替换为你的项目发布后版本 bump 命令
-# npm version prerelease --preid=alpha --no-git-tag-version
-```
-
-- 如果项目需要，记得同步锁文件或其他版本元数据
-- 版本 bump 后保持所有版本引用一致
-
-### 4. 重新生成构建产物
-
-<!-- TODO: 将此步骤替换为你的项目产物重建命令 -->
+## 1. 检查渠道事实
 
 ```bash
-# TODO: 替换为你的项目产物重建命令
+agent-infra-internal release-workflow inspect {version}
 ```
 
-- 重建所有受新版本号影响的生成文件、内嵌产物或内联模板
-- 如果项目没有生成产物，请在项目特化版本中删除此步骤
+pending/unknown 必须 blocked，确定失败必须 failed。
 
-### 5. 执行其他发布后任务（可选）
-
-<!-- TODO: 添加项目特定的发布后任务，例如录制演示、发布文档站或通知下游 -->
-
-- 示例：录制终端演示、刷新文档站、通知下游团队、更新发布面板
-- 如果这一步里的任务需要显示或捕获刚发布的版本号（例如录制 CLI 演示），把它挪到**第 3 步「准备下一个开发版本」之前**——否则会反映下一个开发版本号，而不是 released 版本号
-- 如果没有额外任务，请在项目特化版本中删除此步骤
-
-### 6. 创建后处理提交
+## 2. 执行后处理
 
 ```bash
-git add -A
-git commit -m "chore: prepare next dev iteration after v{released-version}"
+agent-infra-internal release-workflow post {version}
 ```
 
-### 7. 输出摘要
-
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
-
-```
-发布后处理已完成。
-
-结果摘要：
-- 已发布版本：{released-version}
-- 新开发版本：{new-version}
-- 额外任务完成情况：{summary}
-
-下一步（手动执行）：
-- 推送分支：git push origin {current-branch}
-```
-
-## 注意事项
-
-1. **无参数设计**：从最新标签自动检测已发布版本，不要求用户重复输入
-2. **需要干净工作区**：避免把无关改动带入发布后提交
-3. **项目定制**：将带 TODO 的步骤替换为你的项目实际命令
-4. **仅本地执行**：本技能只准备本地变更，不自动推送
+core 负责 build、下一开发版本、内联产物、显式路径 commit 与普通 push，并在写后复核。
 
-## 错误处理
+## 3. 输出摘要
 
-- 未找到发布标签：提示用户先完成发布
-- 工作区不干净：提示先提交或暂存
-- 版本 bump 失败：显示命令错误并停止
-- 产物重建失败：显示构建错误并停止
-- Git 提交失败：显示错误并保留当前工作区供人工处理
+报告全部渠道、smoke、commit 与 push 事实，不把 degraded/blocked 表述为完成。

package/templates/.agents/skills/refine-title/SKILL.en.md

@@ -60,7 +60,7 @@ If the user confirms:
 - for an Issue, update the title by following the "Update Issues" command in `.agents/rules/issue-pr-commands.md`
 - for a PR, update the title by following the "Update PRs" command in `.agents/rules/issue-pr-commands.md`
 
-Title changes require write permission. Follow the permission-degradation rules in `.agents/rules/issue-pr-commands.md` and `.agents/rules/issue-sync.md`; if permission is unavailable, skip the change and inform the user.
+Before changing a title, run `agent-infra-internal platform-context resolve` for upstream and capabilities, then follow the Issue metadata intent contract in `.agents/rules/issue-pr-commands.md`; if permission is unavailable, skip the change and inform the user.
 
 ### 5. Inform User
 

package/templates/.agents/skills/refine-title/SKILL.zh-CN.md

@@ -60,7 +60,7 @@ Issue/PR #{id} 分析结果：
 - 对于 Issue：按 `.agents/rules/issue-pr-commands.md` 中的 “Issue 更新” 命令设置标题
 - 对于 PR：按 `.agents/rules/issue-pr-commands.md` 中的 “PR 更新” 命令设置标题
 
-标题修改需要写权限，按 `.agents/rules/issue-pr-commands.md` 与 `.agents/rules/issue-sync.md` 中的权限降级规则执行；无权限时跳过修改操作并告知用户。
+标题修改前调用 `agent-infra-internal platform-context resolve` 取得 upstream 与 capabilities，再按 `.agents/rules/issue-pr-commands.md` 的 Issue metadata intent 契约执行；无权限时跳过修改操作并告知用户。
 
 ### 5. 告知用户
 

package/templates/.agents/skills/release/SKILL.en.md

@@ -2,188 +2,41 @@
 name: release
 description: >
   Run the version release workflow.
-  Use when you are ready to cut and publish a new version.
+  Use when preparing and publishing a version. Parameter: X.Y.Z.
 ---
 
-# Version Release
+# Release
 
-Execute the version release workflow for the specified version.
+Release state is derived from external facts and prepare/publish require separate authorization.
 
-<!-- TODO: Adapt the steps below to your project's release process -->
+## 1. Validate Input and Entropy Report
 
-## Execution Flow
+Confirm SemVer and the human release checkpoint.
 
-### 1. Parse and Validate Version
-
-Extract version from arguments. Must match `X.Y.Z` format.
-
-Parse components:
-- MAJOR = X, MINOR = Y, PATCH = Z
-- Release version = `X.Y.Z`
-
-If format is invalid, error: "Version format incorrect, expected X.Y.Z (e.g. 1.2.3)"
-
-### 2. Verify Clean Workspace
+## 2. Inspect Facts
 
 ```bash
-git status --short
+agent-infra-internal release-workflow inspect {version}
 ```
 
-If there are uncommitted changes, error: "Workspace has uncommitted changes. Please commit or stash first."
-
-### 3. Pre-release Verification
-
-<!-- TODO: Replace with your project's pre-release verification steps -->
-
-Run any checks that must pass before preparing a release:
+## 3. Prepare
 
 ```bash
-git branch --show-current
-# TODO: Replace with your project's test/build verification commands
+agent-infra-internal release-workflow prepare {version} --entropy-report {path}
 ```
 
-Verification guidance:
-- Confirm the release is being prepared from the correct branch for your project
-- Run the full validation commands required by your release process
-
-Handling rules:
-- If the current branch is unexpected, print a warning or exit based on your policy
-- If any verification command fails, stop the release process and fix the issue first
-
-### 4. Update Version References
-
-<!-- TODO: Replace with your project's version update steps -->
-
-Search for version references in project files and update them:
-
-```bash
-# Find files with version references
-# Search for current version pattern
-# Update version strings
-```
+Stop after prepare; never publish implicitly.
 
-**Common files to update**:
-- `package.json` (Node.js)
-- `package-lock.json` (Node.js; run `npm install --package-lock-only` after updating `package.json`)
-- `pom.xml` (Maven)
-- `setup.py` / `pyproject.toml` (Python)
-- `version.go` (Go)
-- `README.md` (documentation)
-- `SECURITY.md` / `SECURITY.zh-CN.md` (supported version table)
-
-**Exclude from version replacement**:
-- `.agents/`, `.agents/workspace/`, `.claude/`, `.codex/`, `.gemini/`, `.opencode/` (AI tool configs)
-
-If the project uses `package-lock.json`, run `npm install --package-lock-only` after updating `package.json` so the lockfile version stays in sync.
-
-### 5. Rebuild Artifacts
-
-<!-- TODO: Replace with your project's artifact rebuild steps -->
-
-If version updates affect generated files, embedded metadata, or bundled assets, rebuild them now:
-
-```bash
-# TODO: Replace with your project's rebuild command(s)
-```
-
-Execution guidance:
-- Run this after updating version references so generated artifacts pick up the new version
-- If your project has no generated artifacts, document that explicitly in the project-specific skill
-- If the rebuild fails, stop the release process and fix the build first
-
-### 6. Create Release Commit
-
-```bash
-git add -A
-git commit -m "chore: release v{version}"
-```
+## 4. Publish Separately
 
-### 7. Create Git Tag
+Only after explicit user authorization:
 
 ```bash
-git tag v{version}
+agent-infra-internal release-workflow publish {version}
 ```
 
-### 8. Manage Milestones
-
-Close the milestone for the released version when it exists, and create the missing planning milestones for the next cycle.
-
-Run:
-
-```bash
-bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PATCH"
-```
-
-The script is responsible for:
-- Read `.agents/rules/label-milestone-setup.md` before this step
-- Use its milestone list and update commands to load and adjust current milestones
-- Closing `{MAJOR}.{MINOR}.{PATCH}` when it exists and is still open
-- Ensuring `{MAJOR}.{MINOR}.{PATCH+1}` and `{MAJOR}.{MINOR}.x` exist
-- When `PATCH=0`, also ensuring `{MAJOR}.{MINOR+1}.0` and `{MAJOR}.{MINOR+1}.x`
-- Printing a milestone summary with the released milestone action and new milestone count
-
-### 9. Output Summary
-
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent. If `.agents/.airc.json` configures custom TUIs (via `customTUIs`), read each tool's `name` and `invoke`, then add the matching command line in the same format (`${skillName}` becomes the skill name and `${projectName}` becomes the project name).
-
-```
-Release v{version} prepared.
-
-Release info:
-- Version: {version}
-- Release commit: {commit-hash}
-- Tag: v{version}
-
-Files updated: {count}
-
-Next steps (manual):
-
-1. Push branch:
-   git push origin {current-branch}
-
-2. Push tag:
-   git push origin v{version}
-
-3. (Optional) Generate release notes:
-   - Claude Code / OpenCode: /create-release-note {version}
-   - Gemini CLI: /{{project}}:create-release-note {version}
-   - Codex CLI: $create-release-note {version}
-
-4. (Optional) Run post-release follow-up tasks:
-   - Claude Code / OpenCode: /post-release
-   - Gemini CLI: /{{project}}:post-release
-   - Codex CLI: $post-release
-```
-
-### Rollback Instructions
-
-If something went wrong:
-```bash
-# Delete tag
-git tag -d v{version}
-
-# Reset commit
-git reset --soft HEAD~1
-
-# Restore files
-git checkout -- .
-```
-
-## Notes
-
-1. **Clean workspace required**: Must have no uncommitted changes
-2. **No auto-push**: All operations are local only; user pushes manually
-3. **Pre-release verification**: Replace the Step 3 TODOs with the branch, test, and validation commands your release process requires
-4. **Generated artifacts**: Replace the Step 5 TODOs when version changes affect generated files, bundled assets, or embedded metadata
-5. **Release automation**: If pushing a tag triggers CI/CD or package publishing, confirm the required credentials and pipeline settings first
-6. **Version replacement scope**: Search determines which files to update; exclude AI tool directories
-7. **Adapt to your project**: The version update and rebuild steps above are generic; customize them for your project's versioning scheme
-8. **Milestone coordination**: Releases should create the next planning milestones automatically; initialize the taxonomy first with `init-milestones` when needed
+Push refs normally, preserve partial success for replay, and never force push.
 
-## Error Handling
+## 5. Report Facts
 
-- Invalid version format: Prompt correct format and exit
-- Dirty workspace: Prompt to commit or stash
-- Verification failure: Display the failing check and stop the release
-- Artifact rebuild failure: Display the build error and stop the release
-- Git operation failure: Display error and provide rollback instructions
+Show the snapshot and every TUI command. Treat unknown external state as blocked.

package/templates/.agents/skills/release/SKILL.zh-CN.md

@@ -2,188 +2,41 @@
 name: release
 description: >
   执行版本发布流程。
-  当准备切出并发布新版本时使用。
+  当准备切出并发布新版本时使用。参数：版本号（X.Y.Z）。
 ---
 
 # 版本发布
 
-执行指定版本的版本发布流程。
+发布由事实驱动，并拆为独立授权的 prepare 与 publish。
 
-<!-- TODO: 根据你的项目发布流程调整以下步骤 -->
+## 1. 检查输入与 entropy 报告
 
-## 执行流程
+确认 SemVer 和人工发布检查点已满足。
 
-### 1. 解析并验证版本号
-
-从参数中提取版本。必须匹配 `X.Y.Z` 格式。
-
-解析组件：
-- MAJOR = X，MINOR = Y，PATCH = Z
-- 发布版本 = `X.Y.Z`
-
-如果格式无效，报错："Version format incorrect, expected X.Y.Z (e.g. 1.2.3)"
-
-### 2. 验证工作区干净
+## 2. 检查事实
 
 ```bash
-git status --short
+agent-infra-internal release-workflow inspect {version}
 ```
 
-如果有未提交的变更，报错："Workspace has uncommitted changes. Please commit or stash first."
-
-### 3. 发布前验证
-
-<!-- TODO: 替换为你的项目发布前验证步骤 -->
-
-运行所有在准备发布前必须通过的检查：
+## 3. 准备发布
 
 ```bash
-git branch --show-current
-# TODO: 替换为你的项目测试/构建验证命令
+agent-infra-internal release-workflow prepare {version} --entropy-report {path}
 ```
 
-验证要求：
-- 确认发布使用的是项目规定的分支
-- 运行你的发布流程要求的完整校验命令
-
-处理规则：
-- 如果当前分支不符合预期，按项目策略输出警告或直接退出
-- 如果任何验证命令失败，停止发布流程并先修复问题
-
-### 4. 更新版本引用
-
-<!-- TODO: 替换为你的项目版本更新步骤 -->
-
-搜索项目文件中的版本引用并更新：
-
-```bash
-# 查找包含版本引用的文件
-# 搜索当前版本模式
-# 更新版本字符串
-```
+prepare 后停止，不得隐式 publish。
 
-**常见需要更新的文件**：
-- `package.json`（Node.js）
-- `package-lock.json`（Node.js；更新 `package.json` 后运行 `npm install --package-lock-only` 同步锁文件）
-- `pom.xml`（Maven）
-- `setup.py` / `pyproject.toml`（Python）
-- `version.go`（Go）
-- `README.md`（文档）
-- `SECURITY.md` / `SECURITY.zh-CN.md`（支持版本表格）
-
-**排除以下目录的版本替换**：
-- `.agents/`、`.agents/workspace/`、`.claude/`、`.codex/`、`.gemini/`、`.opencode/`（AI 工具配置）
-
-如果项目使用 `package-lock.json`，在更新 `package.json` 后运行 `npm install --package-lock-only`，确保锁文件中的版本号保持同步。
-
-### 5. 重新生成构建产物
-
-<!-- TODO: 替换为你的项目产物重建步骤 -->
-
-如果版本更新会影响生成文件、内嵌元数据或打包产物，现在重新生成它们：
-
-```bash
-# TODO: 替换为你的项目构建/重建命令
-```
-
-执行要求：
-- 在更新版本引用后运行，确保生成产物使用最新版本号
-- 如果项目没有生成产物，请在项目特化版本中明确说明
-- 如果重建失败，停止发布流程并先修复构建问题
-
-### 6. 创建发布提交
-
-```bash
-git add -A
-git commit -m "chore: release v{version}"
-```
+## 4. 独立发布
 
-### 7. 创建 Git 标签
+仅在用户明确授权后执行：
 
 ```bash
-git tag v{version}
+agent-infra-internal release-workflow publish {version}
 ```
 
-### 8. 管理里程碑
-
-为已发布版本关闭对应版本里程碑，并为下一轮创建缺失的规划里程碑。
-
-执行：
-
-```bash
-bash .agents/skills/release/scripts/manage-milestones.sh "$MAJOR" "$MINOR" "$PATCH"
-```
-
-脚本负责：
-- 执行前先读取 `.agents/rules/label-milestone-setup.md`
-- 使用其中的 milestone 查询与更新命令读取和调整当前里程碑
-- 在 `{MAJOR}.{MINOR}.{PATCH}` 存在且仍为开启状态时将其关闭
-- 确保 `{MAJOR}.{MINOR}.{PATCH+1}` 与 `{MAJOR}.{MINOR}.x` 存在
-- 当 `PATCH=0` 时，同时确保 `{MAJOR}.{MINOR+1}.0` 与 `{MAJOR}.{MINOR+1}.x`
-- 输出包含已发布里程碑动作和新建数量的汇总
-
-### 9. 输出摘要
-
-> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。如果 `.agents/.airc.json` 中配置了自定义 TUI（`customTUIs`），读取每个工具的 `name` 和 `invoke`，按同样格式补充对应命令行（`${skillName}` 替换为技能名，`${projectName}` 替换为项目名）。
-
-```
-版本 v{version} 已准备好发布。
-
-发布信息：
-- 版本：{version}
-- 发布提交：{commit-hash}
-- 标签：v{version}
-
-已更新文件数：{数量}
-
-下一步（手动执行）：
-
-1. 推送分支：
-   git push origin {current-branch}
-
-2. 推送标签：
-   git push origin v{version}
-
-3.（可选）生成发布说明：
-   - Claude Code / OpenCode：/create-release-note {version}
-   - Gemini CLI：/{{project}}:create-release-note {version}
-   - Codex CLI：$create-release-note {version}
-
-4.（可选）执行发布后处理：
-   - Claude Code / OpenCode：/post-release
-   - Gemini CLI：/{{project}}:post-release
-   - Codex CLI：$post-release
-```
-
-### 回滚说明
-
-如果出了问题：
-```bash
-# 删除标签
-git tag -d v{version}
-
-# 重置提交
-git reset --soft HEAD~1
-
-# 恢复文件
-git checkout -- .
-```
-
-## 注意事项
-
-1. **需要干净的工作区**：必须没有未提交的变更
-2. **不自动推送**：所有操作仅在本地执行；用户手动推送
-3. **发布前验证**：将步骤 3 的 TODO 替换为你的项目所需的分支、测试和验证命令
-4. **生成产物**：如果版本变化会影响生成文件、打包产物或内嵌元数据，需要将步骤 5 的 TODO 替换为实际命令
-5. **发布自动化**：如果推送标签会触发 CI/CD 或包发布，请先确认所需凭据和流水线配置
-6. **版本替换范围**：通过搜索确定需要更新哪些文件；排除 AI 工具目录
-7. **适配你的项目**：以上版本更新和产物重建步骤是通用的；请根据你的项目版本方案进行定制
-8. **里程碑联动**：发布时自动创建下一轮里程碑；如果里程碑体系未初始化，建议先运行 `init-milestones`
+逐 ref 普通 push；部分成功可重放，禁止 force push。
 
-## 错误处理
+## 5. 输出事实摘要
 
-- 版本格式无效：提示正确格式并退出
-- 工作区不干净：提示提交或暂存
-- 验证失败：显示失败的检查并停止发布流程
-- 产物重建失败：显示构建错误并停止发布流程
-- Git 操作失败：显示错误并提供回滚说明
+完整展示 snapshot 和后续 TUI 命令；unknown 必须视为 blocked。