Teach the skills the resume_session join path - #166
Draft
Cammisuli wants to merge 2 commits into
Draft
Conversation
- Add resume_session to the tool table beside start_session/show_session - Join flow: ask whether an existing session covers the work before ad-hoc clones or untracked reads; resume_session to work, show_session to read - Explore section: keep the no-changes-until-asked rule; the join is recorded in the session's history (who picked it up, when) - Qualify the current-repo principle: resume's full reconstruct may switch branches inside session-materialized repositories, refusing dirty trees
…on path When a session already exists and the intent is to continue work in it, join via resume_session (tracked adoption; restored context returned in the tool result); show_session stays the read-only alternative.
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.
Teaches the Polygraph skills that resuming a session is a tracked join, not an untracked read or an ad-hoc clone.
polygraph skill
resume_session— join an existing session from this conversation: full reconstruct, tracked (CLI:polygraph session resume --session <id> --json).resume_session;show_sessionremains the read-only path.resume_session, and the resume itself is recorded in the session's history (who picked it up, when). Recording the adoption is not making changes to the work.session-start skill
resume_session(the primer comes back in the tool result); read-only exploration stays onshow_session.All three platform dists rebuilt; tests pass.
View Polygraph session ↗