Repository navigation
F121 — a kept session is owned by the conversation that started the run - #126
Merged
Merged
Conversation
- The ownership key of a HarnessSession is the id of the conversation that started the workflow run where there is one, carried onto the step's context by the orchestrator so the executor reads it as data and never infers it; a run started from no conversation keeps the run id as owner, so a workflow's own tasks still share a session - ownedSession and the retry path by logicalExecutionId read that key; the refusal states the conversation rule and keeps the sentence listing how a kept session ends, including the failed re-preparation of the checkout - Tests: a second run by the same conversation continues the session; a run from another conversation is refused with the same text a missing session gets; a run with no conversation falls back to run ownership; the existing retry-continues test still holds - The Commission Change skill text and the plan's F121 row match what is built
…, the retry and poll stamping sites are tested, and the stale ownerRunId literal goes
…one, so a recovered run keeps its sessions
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.
F121 (Plan 315 §6): a fix round commissioned from the same Helmsman conversation continues the coding agent's session instead of starting cold on a branch it has already analysed. The HarnessSession ownership key becomes the starting conversation's id, carried onto the step's context by the orchestrator as data; runs with no conversation keep run-id ownership so a workflow's own tasks still share a session. ownedSession and the logicalExecutionId retry path read the key; the refusal states the conversation rule with the endings sentence intact. Four tests pin the behaviour; the Commission Change skill text and the plan's F121 row match what is built. 20 files, applies clean against e154e5a.