CalvinBackup/gstack
1
0 Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-11-02 15:04:37 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix(preamble): completeness means complete coverage with minimal code (GSTA-96)

Browse Source 
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
garrytanandcapy-ai[bot] committed 2026-10-25 23:01:09 +00:00
1 parent c23d7d48fe
commit 8ab9e41e56
52 files changed
+167 -146
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

scripts/resolvers/preamble/generate-completeness-section.ts
+1 -1
View File
@@ -11,7 +11,7 @@ When options differ in in-scope coverage, include \`Completeness: X/10\` (10 = a
}
return `## Completeness Principle — Boil the Ocean
AI makes completeness cheap, so the complete thing is the goal. Recommend full coverage (tests, edge cases, error paths) — boil the ocean one lake at a time. The only thing out of scope is genuinely unrelated work (rewrites, multi-quarter migrations); flag that as separate scope, never as an excuse for a shortcut.
Complete coverage, minimal code. Recommend full coverage of the requirement (tests, edge cases, error paths) and no code beyond it: on equal coverage, prefer the smaller diff; no checks for impossible states. Unrelated work (rewrites, multi-quarter migrations) is separate scope: flag it; it never excuses a gap.
When options differ in coverage, include \`Completeness: X/10\` (10 = all edge cases, 7 = happy path, 3 = shortcut). When options differ in kind, write: \`Note: options differ in kind, not coverage — no completeness score.\` Do not fabricate scores.`;
}