Skip to content

feat(pipeline): structure failure reasons and recovery paths in step conclusions - #195

Open
ruanzhengxin-zhuxing wants to merge 1 commit into
mainfrom
harness/e12eec71
Open

feat(pipeline): structure failure reasons and recovery paths in step conclusions#195
ruanzhengxin-zhuxing wants to merge 1 commit into
mainfrom
harness/e12eec71

Conversation

@ruanzhengxin-zhuxing

Copy link
Copy Markdown
Collaborator

背景

Aone 需求 #84518490:Pipeline 步骤结论未结构化记录失败原因与恢复路径(Session 43b8f91f 部署步骤 7-9 结论字节级相同仅有 status=failed;Session 69f59a80 preview 在 cost_estimating 期间 body_file invalid 后隐式恢复未体现)。

变更

  • iac-aliyun-deploying conclusion_schema:新增 error_code / error_message / failed_stack_status / recovery_attempts[]status=failed 时必填 error_message,使每次重试结论可区分、根因可追溯。
  • iac-aliyun-cost preview_validation:新增 recovered / failure_history[],预览失败-重试-恢复路径在 cost 结论中可见。
  • 同步更新 prompts/deploying.mdprompts/cost_estimating.md 与两个技能正文指引,禁止跨重试复用同一失败文案。
  • 补充两个技能测试的 schema/正文断言。

测试

  • tests/pipeline/selling/skills 154 passed;全量 pytest 13280 passed(2 个失败为父提交同样失败的既有环境相关问题);ruff 全过。

…conclusions

- iac-aliyun-deploying conclusion_schema: add error_code/error_message/
  failed_stack_status and recovery_attempts; failed conclusions now require
  error_message so each retry is distinguishable and root-cause traceable
- iac-aliyun-cost preview_validation: add recovered/failure_history so
  implicit preview failure-retry-recovery paths are visible in cost conclusions
- update deploying/cost prompts and skill guidance; forbid reusing identical
  failure text across retries
- add schema and content tests for both skills

Refs: Aone #84518490 (sessions 43b8f91f/69f59a80)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant