Why: Layout rules alone do not produce conclusion-first documents, extra views, or infographics, and nothing scored a deliverable before it was returned. Evidence: go test ./internal/prompts/ ./internal/quality/ ./internal/tools/ ./internal/squadadapter/ ./eval/ -count=1 and the house-style unittest passed in the previous session. Impact: Every task inherits content rules. Meetings, reports, and comparisons can name a view family. Long documents without a visual summary warn. quality_review and the squad checker share one scorecard. Refs: deliverable-quality-system A1-A5 Co-authored-by: Cursor <cursoragent@cursor.com>
406 B
406 B
交付物评测
仓内 testdata/ 是脱敏短样例,用来确认评分卡能区分“结论先行”和“栏目式笔记”。
真实会议材料不要放进仓库。放到 ~/.agent-system/eval/,或设置 EVAL_DIR。其中的 .md 会在 go test ./eval/ 里被打分并打印,缺失该目录时测试跳过。
cd modules/backend && go test ./eval/ ./internal/quality/ -count=1