hpd-pipeline
Follow the stage contract in {baseDir}/references/project-pipeline.md.
Preferred mode
- - If the
lobster CLI is available on PATH, prefer a Lobster workflow. - If
lobster is unavailable, run the same stages sequentially in one turn and mark lobster_ready: false.
Required output sections
- - INLINECODE5
- INLINECODE6
- INLINECODE7
- INLINECODE8
- INLINECODE9
- INLINECODE10 when needed
- INLINECODE11
- INLINECODE12
- INLINECODE13
Optional artifact fields
Use these when real outputs exist. If they do not exist, say so explicitly instead of implying they were produced.
- - INLINECODE14
- INLINECODE15
- INLINECODE16
- INLINECODE17
- INLINECODE18
- INLINECODE19
Rules
- - Keep outputs Notion-first.
- Do not claim STEP/STL or validated firmware unless it was actually produced.
hpd-pipeline
遵循 {baseDir}/references/project-pipeline.md 中的阶段合约。
首选模式
- - 如果 PATH 中可用的 lobster CLI，优先使用 Lobster 工作流。
- 如果 lobster 不可用，则在一个轮次中顺序运行相同阶段，并标记 lobster_ready: false。
必需输出部分
- - brief
- costestimate
- bom
- assemblyplan
- renderprompt
- softwarespec（需要时）
- testerreport
- artifactmanifest
- completion_summary
可选工件字段
当实际输出存在时使用这些字段。如果不存在，请明确说明，而不是暗示已生成。
- - renderimage
- cadsteppath
- cadstlpaths
- assemblydocpath
- sourcecodepath
- firmwarebuild_path
规则
- - 保持输出以 Notion 为先。
- 除非实际生成了 STEP/STL 或经过验证的固件，否则不要声称已生成。
