Repository navigation
fix(context): clear previous results when starting a new task - #40
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
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.
Starting a new task cleared inherited slots and the public result reference but still copied the previous task's artifact, query fingerprint and data hash into taskState.result. Execution-contract and prompt serialization consequently referenced the old result even when inheritance was disallowed.
Retain the previous result only when the existing canInherit policy allows it. Explicit new questions, forced resets and expired inheritance budgets now clear old result metadata. Eligible continuations, result operations and direct result references retain their behavior.
Validation: four reset/expiry regressions reproduced before the fix; seven new cases use actual completed task history and verify the externally consumed prompt/contract. Full npm test: 581 tests, 569 passed, 12 optional skips, 0 failures. Lint: 0 errors / 7 existing warnings; eval: 14/14 fixtures with 2 L3 judgments pending. Independent review approved and ran 25 new/existing context/router tests, all passed. No external model was used.
Depends on #37 for the shared PostgreSQL HTTP acceptance path; merge #37 first. Its prerequisite changes are included to keep this branch verifiable.