Skip to content

v11: prescriptive recipe flips logparse net-positive#67

Merged
dpetrou-continua merged 2 commits into
mainfrom
dpetrou/v11-prescriptive-recipe
Feb 22, 2026
Merged

v11: prescriptive recipe flips logparse net-positive#67
dpetrou-continua merged 2 commits into
mainfrom
dpetrou/v11-prescriptive-recipe

Conversation

@dpetrou-continua
Copy link
Copy Markdown
Contributor

Summary

  • v11: prescriptive recipe wording ("use .venv/bin/pytest, not pytest") prevents model shortcuts
  • ledgerkit: −11% time (was −5%), logparse: −4% time and −0.4 errors (was +7%), webutil: neutral time, −0.2 errors
  • Value: both undocumented-tool repos now net-positive on time; 3 repos show error reduction
  • Vibe-coded (wording change only, no architecture changes)

Testing

  • npm run verify (158 tests passing)
  • v11 benchmark: 72 runs (3 repos × 4 tasks × 2 variants × 3 replicates)

…scripts

Traces show the model skips venv creation (ON: 33% vs OFF: 58% on
logparse) because "python -m pytest" is a shortcut. New wording:
- "Use .venv/bin/pytest (not pytest or python -m pytest)"
- Names concrete setup scripts: ./kit, ./qa, ./dev
- Removes generic "check for executable files" language
ledgerkit: -11% time (was -5% in v10)
logparse: -4% time, -0.4 errors (was +7% in v10)
webutil: +1% time, -0.2 errors, -0.8 calls (new in v11)

Added lesson #4: be prescriptive not advisory.
@dpetrou-continua dpetrou-continua merged commit 81edfeb into main Feb 22, 2026
2 checks passed
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