1.6.0: grounding research + Track Setup topic shortcut - #4
Merged
Conversation
Custom-track generation now checks its facts. Before writing exercises for a fast-moving library/framework with a versioned API (a game/UI library, a cloud SDK, a build tool), Sage uses WebSearch/WebFetch to pull current docs first, recording what it consulted in a new optional `sources` field. Validated live on Raylib: the research genuinely caught that Raylib is on v6.0 and shaped the generated verify command's real linker flags, not a plausible-sounding guess. Stable fundamentals (a language's own core syntax) still skip this entirely -- no need to burn a research round on what training data already gets right. Also fixes a real redundancy: Track Setup used to ask "what do you want to learn?" even when the learner's trigger message already said so. Now a stated topic matching no bundled curriculum skips Round 0 and Round 1 outright; a topic matching one compresses Round 0 into a direct named confirm instead of the generic list, without removing the custom-track choice. Two new scenarios (09, 10) validate both features live, 10/10 and 10/10 respectively. Scenario 06 gained a no-sources assertion and a staleness fix -- its original "Rust" example collided with the rust-cli curriculum added in 1.5.0, so Round 0 was silently offering three options instead of the two it assumed. Both 06 and 09 had their trigger messages reverted to topic-neutral, since the new shortcut rule would otherwise entangle their own regression targets with Round 0's behavior. All ten Tier 2 scenarios now pass. Pre-release checklist bumped from "all eight" to "all ten." Version bumped to 1.6.0. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hi @luxsolari! 👋
Your private repo does not have access to Sourcery.
Please upgrade to continue using Sourcery ✨
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
1 participant
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.
Summary
sourcesYAML field. Validated live on Raylib: genuinely caught it's currently on v6.0 and shaped the generatedverifycommand's real linker flags.sourcesassertion plus a staleness fix (its "Rust" example collided with therust-clicurriculum from a prior release, silently changing Round 0's option count).All ten Tier 2 scenarios pass. Full detail in
CHANGELOG.md's 1.6.0 entry.Test plan
python tests/test_check_progress_schema.py— 7/7 pass (Tier 1, also runs in CI)🤖 Generated with Claude Code