workflow-repair

Version History

• v2.1: Added mandatory repair-task bootstrap, tmp/workflow-issues/ history documents, all-history replay on every run, strict-review completion rules without mandatory re-embed, and expanded write-scope rules for task and issue-history artifacts
• v2.0: Aligned intake with temp-project-only scan reports; removed source-project-root matching and source-location requirements from the shared report contract
• v1.4: Added recurrence-closure, contract-surface coverage, and anti-regression gates to reduce repeated repairs and leftover issues
• v1.3: Aligned frontmatter with the latest public skill spec by making the description explicitly cover both purpose and trigger, and by adding compatibility requirements
• v1.2: Replaced misleading fixed example paths and task-directory placeholders with runtime-sensitive placeholders
• v1.1: Clarified temp-project-first verification, explicit repair authorization, no-agent execution, and same-pattern variant handling
• v1.0: Initial release

Purpose

Consume a WORKFLOW_QUESTIONS.md report produced by workflow-scan, verify each finding against the temp project and the source project, and apply safe repairs to workflow source files — ONLY within docs/workflows/新项目开发工作流/.