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>
15 lines
360 B
Go
15 lines
360 B
Go
package eval
|
|
|
|
import "strings"
|
|
|
|
// MissingThemes 报告候选文本没有覆盖的参考主题。主题是短词,不是整句照抄。
|
|
func MissingThemes(candidate string, themes []string) []string {
|
|
var missing []string
|
|
for _, theme := range themes {
|
|
if !strings.Contains(candidate, theme) {
|
|
missing = append(missing, theme)
|
|
}
|
|
}
|
|
return missing
|
|
}
|