Skip to content

fix(go-tools): blind-validation fixes; v0.3.1 (closes #11) - #13

Merged
chrispezza merged 1 commit into
mainfrom
chore/issue-11-go-tools-validation
Aug 12, 2026
Merged

chrispezza merged 1 commit into
mainfrom
chore/issue-11-go-tools-validation

Conversation

@chrispezza

Copy link
Copy Markdown
Contributor

What

Executes issue #11: blind validation of all five clownware-go-tools skills per house standard 5, and ships the three doc fixes the runs surfaced. Bumps go-tools 0.3.0 → 0.3.1; ROADMAP records the validation under Graduated.

Validation summary

10/10 blind runs met every criterion pinned before launch (hit context: go-performance-starter@50a8fee; miss context: a minimal non-starter Go module per skill):

Skill Hit Miss
templ-component-scaffold typed-props component, generate + full task ci green stopped on fallback, nothing invented
test-scaffold t.Skip table stubs, stdlib, vet+test green generic-Go path, green
sqlc-query-scaffold query + regenerate + repository seam + fake, green stopped on no-sqlc fallback
perf-budget-check per-gate verdicts byte-identical to independently pinned run stopped, pointed at /perf-audit
go-pr-description master base, both commits, honest boxes; caught a real ADR-027 contradiction the probe branch accidentally seeded main base, honest about missing Taskfile/tests

Fixes (found by the runs)

  • templ-component-scaffold no longer asserts IsHTMXRequest exists in render.go (the starter ships only Render/CurrentYear)
  • test-scaffold now checks sibling _test.go files for existing coverage of the target's functions before stubbing duplicates
  • perf-budget-check's attribution diffs are base-branch-aware (main or master) instead of hardcoding main — the starter itself is master-based

Full pinned ground truth and per-run reports are recorded in the release commit body.

Merge as rebase (single commit; keeps the release commit intact for plugin-release delta derivation).

🤖 Generated with Claude Code

Blind validation per house standard 5 (issue #11): all five skills run by
fresh agents against go-performance-starter@50a8fee (hit) and a minimal
non-starter Go module (miss), scored against criteria pinned before any
agent launched. 10/10 runs met every pinned criterion.

Validation record:
- templ-component-scaffold: scaffolded typed-props StatusBadge, templ
  generate + full task ci green; miss context stopped on the pre-fetch
  fallback without inventing a view layer.
- test-scaffold: table-driven t.Skip stubs beside source, stdlib style,
  vet+test green in both contexts (miss context is the generic-Go path).
- sqlc-query-scaffold: CountUsers :one appended, db:generate round-trip,
  repository interface + postgres adapter (RLS inScope pattern) + fake
  updated, build/tests green; miss context stopped on the no-sqlc fallback.
- perf-budget-check: ran task test:performance, per-gate verdicts verbatim
  and byte-identical to the independently pinned run (binary 16341986B,
  JS 32771B gzipped, CSS 7678B gzipped, all green); miss context stopped
  and pointed at /perf-audit without running anything.
- go-pr-description: master base detected, both commits covered, honest
  unchecked boxes with env-failure attribution; its ADR step caught a
  genuine ADR-027 contradiction the probe branch had accidentally seeded
  (unconditional left-most XFF trust) — unplanned true positive.

Doc gaps found by the runs, fixed here (fix the skill, not the test):
- templ-component-scaffold: named IsHTMXRequest as a render.go given; the
  starter ships only Render/CurrentYear — now reads the repo's actual
  helpers and never references an absent one.
- test-scaffold: only checked <source>_test.go for existing coverage;
  sibling test files can already cover the target funcs — now greps the
  package's other _test.go files and reports instead of duplicating.
- perf-budget-check: hardcoded 'git diff main' twice; the starter itself
  is master-based — now base-branch-aware (main or master).

Closes #11

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@chrispezza
chrispezza merged commit dc14b44 into main Aug 12, 2026
2 checks passed
@chrispezza
chrispezza deleted the chore/issue-11-go-tools-validation branch August 12, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant