feat: add mastery-driven Tutor progression - #111
Merged
Merged
Conversation
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.
Summary
Implements the mastery-driven Tutor progression contract from the approved SSOT at
fdd641bbae30ceae8347f9835620c3d1274462d9.Final review fixes
Final review fixes are included through
9315f55d9298873cbdda1e70d70fc32006069aac:planInitial()determines the actual topic/phase before effective strategy resolution, preventing stale EXPAND strategy leakage after topic changes.Validation
36315744897: Clean-room reproducibility, Lint & Unit Tests, Arduino Toolchain Integration, Docker Sandbox Integration, and Playwright E2E all passed.Docker/Capacity load testing was not rerun locally because Capacity and Docker behavior were not changed; the hosted Docker Sandbox Integration job passed.
Scope protections
Capacity implementation/defaults, Tutor Registry SSOT, the external UnoSim-Examples repository, and its pilot worktree were not modified.
Single-backend limitation remains: progression state is attached to the existing process-local opaque Course Content session with its current one-hour TTL; distributed session state is outside this Stage-A scope.