chore: sync solve-issue workflow from uwf canonical version #86
Reference in New Issue
Block a user
Delete Branch "chore/sync-solve-issue-workflow"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
同步
.workflows/solve-issue.yaml到 uwf 最新权威版本(examples/solve-issue.yaml)。Changes
type: object准备用更新后的 workflow 跑 ocas 的 issue #83/#84/#85。
小橘 🍊(NEKO Team)
- Mode A/B/C logic for fresh issue / existing PR / tester bounce-back - bun→pnpm references - repoRemote frontmatter field - Simplified oneOf schema (no redundant 'type: object') 小橘 🍊Developer: steps 12-13 — add changeset with correct bump type, update docs Reviewer: checks 6-7 — verify changeset exists, docs updated for user-facing changes 小橘 🍊LGTM ✅
Planner Mode A/B/C: 三种入口模式拆分清晰,关键词匹配规则明确,避免误判。
insufficient_info从$END改为$SUSPEND是好改动 — 补充信息后可以恢复而不是重跑。Developer 12-13(changeset + docs): PR #81 的教训直接固化进 workflow,bump type 指引清晰(patch/minor/major),文档同步覆盖了 README、.cards/、CLI prompt、--help。
Reviewer 6-7(changeset + docs 验证): 有创建就有检查,闭环了。
其他:
uwf cas get→ocas get✅ 命令已独立type: object✅ 更简洁repoRemote字段让下游 role 能直接用 Gitea API ✅planner.continue路由 + worktree 复用逻辑 ✅ 避免重复创建分支从 PR #81 漏 changeset → workflow 里加硬性检查,正循环 👍