CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-09-16 18:05:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge origin/main (v1.67.2.0) — v1.68.0.0 stays on top

Browse Source 
CHANGELOG keeps both entries in release order (1.68.0.0 above 1.67.2.0);
VERSION and package.json keep the branch's higher claim. Generated
SKILL.md files verified byte-exact against a fresh regen from the merged
templates.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-08-18 17:09:29 -07:00
co-authored by Claude Fable 5
parent c4907640a3 60e51342b5
commit a57095e4ae
37 changed files with 1193 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/resolvers/preamble/generate-completeness-section.ts
+7
View File
@@ -2,6 +2,13 @@ import type { TemplateContext } from '../types';
export function generateCompletenessSection(ctx?: TemplateContext): string {
if (ctx?.explainLevel === 'terse') return '';
if (ctx?.model === 'gpt-5.6-sol') {
return `## Completeness Principle — Boil the Ocean Within Scope
AI makes completeness cheap, so do the complete thing **inside the user's explicit task boundary**. The requested target, allowed files or systems, and acceptance criteria define the lake. Within that lake, cover the relevant tests, edge cases, and error paths. Related but unnecessary refactors, speculative hardening, cleanup, and migrations are separate scope: report them, do not implement them.
When options differ in in-scope coverage, include \`Completeness: X/10\` (10 = all relevant in-scope 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 or expand the lake to raise one.`;
}
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.
scripts/resolvers/preamble/generate-lake-intro.ts
+12 -1
View File
@@ -1,6 +1,17 @@
import type { TemplateContext } from '../types';
export function generateLakeIntro(): string {
export function generateLakeIntro(ctx: TemplateContext): string {
if (ctx.model === 'gpt-5.6-sol') {
return `If \`LAKE_INTRO\` is \`no\`: say "gstack follows the **Boil the Ocean** principle — do the complete thing within the user's explicit task boundary when AI makes marginal cost near-zero. Do not widen that boundary to adjacent cleanup or speculative hardening. Read more: https://garryslist.org/posts/boil-the-ocean" Offer to open:
\`\`\`bash
open https://garryslist.org/posts/boil-the-ocean
touch ~/.gstack/.completeness-intro-seen
\`\`\`
Only run \`open\` if yes. Always run \`touch\`.`;
}
return `If \`LAKE_INTRO\` is \`no\`: say "gstack follows the **Boil the Ocean** principle — do the complete thing when AI makes marginal cost near-zero. Read more: https://garryslist.org/posts/boil-the-ocean" Offer to open:
\`\`\`bash