mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-02 23:14:33 +01:00
The outcome, no fabricated Completeness: N/10, stays asserted. The required note now matches any brief wording of the same fact (KIND_NOTE_RE in helpers/plan-format-kind-note.ts). The format-compliance suite that pins the declared kind-note string is unchanged. Stored lines: four known-good pass, three known-bad (a completeness score, a recommendation, 'kind to the user') fail.
15 lines
622 B
JSON
15 lines
622 B
JSON
{
|
|
"_comment": "Kind-note lines from captured kind-differentiated AskUserQuestions. known_good must match KIND_NOTE_RE; known_bad must not.",
|
|
"known_good": [
|
|
"Note: options differ in kind, not coverage — no completeness score.",
|
|
"These choices differ in kind, so there is no completeness score.",
|
|
"The options are different kinds of decision; they are not comparable on coverage.",
|
|
"No completeness score: the options trade scope, not coverage."
|
|
],
|
|
"known_bad": [
|
|
"Completeness: A=9/10, B=6/10",
|
|
"Recommendation: A because it ships sooner.",
|
|
"Both options are kind to the user."
|
|
]
|
|
}
|