Draft
RESUME_MSG: don't claim environmental facts in history remain valid#4
Conversation
…story may be stale
Contributor
|
I'm not sure if this is the solution. A better solution would be to have stuff like list_pyskills templatized so the current output is always shown. Applies to doc() results and list_pyskills results. WDYT? |
jph00
marked this pull request as draft
July 27, 2026 21:57
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
2 participants
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.
The resume hook told a resumed session that "everything you can still see remains valid". A session bootstrapped from a baked dojo template took that at face value, treated the replayed round's
list_pyskills()catalog as current, and missed a skill registered since the capture.RESUME_MSG now scopes the validity claim to doc() output and the dojo completion id, and adds that environmental facts in visible history (cwd, file paths, the catalog) may come from another machine or an earlier date, so they need re-checking in the live session. COMPACT_MSG and SYNTH_MSG are unchanged: they already treat context as stale wholesale.
Verified by launching
claude -r $(claudedojo)and asking for git status: the fresh session re-ranlist_pyskills(), noticed the catalog differed from the replayed transcript, and picked the newly-registered fastgit skill.Companion PR AnswerDotAI/llmdojo#8 makes the
dojo_start(id)already-complete message carry the same warning.