Repository navigation
Guide v2.8: the opening states what the recommended build needs (fixed lines) - #91
Merged
Merged
Conversation
…ixed lines v2.7's opening clause kept "which needs no key", so every spec opened with "They need no key" although each recommended build needs a key. A described clause still produced it in 20 of 24 runs; the opening now carries two fixed lines (what the build needs to run, then the fastest path), copied word for word like the section 8 gate. Register row 39 (corrects row 36). Version v2.8 in guide, generation prompt and skill. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrects v2.7's item A. The opening is the part of a spec learners are expected to read.
Problem. v2.7's 10.1 clause kept "the build is finished when the offline tests pass, which needs no key". Every v2.7 spec (#88, #89, #90 and all 24 test runs) opened with "They need no key", although each course's recommended build needs an OpenAI key. Owner: the opening must state the truth for the course's recommended build.
Change (10.1 item 1, in place). The opening carries two fixed lines, filled in per course and otherwise copied word for word, like the section 8 gate:
Plus: never write that the build, the app or its tests need no key unless the recommended build uses none. The 2026-09-09 completion rule (finished offline; skipped live tests are not failures) stays, as the owner chose.
Checklist
Not tested: a course whose recommended build uses no key (none of the benchmark courses has one).
🤖 Generated with Claude Code