fix: preserve nested fanout subagent tool history#270
Closed
jamesjwood wants to merge 10 commits into
Closed
Conversation
Explicit acceptance now owns completion through a bounded same-session self-review loop. The runtime derives acceptance provenance internally, uses an explicit CompletionPolicy to avoid competing completion guards, and keeps raw acceptance reports out of normal output while preserving ledger/status details.
Prepare the 0.27.0 release with acceptance finalization notes, goal-style guidance, and version metadata.
Guide agents to use acceptance criteria, evidence, verification, stop rules, and loop caps when delegating implementation from plans or specs.
Remove provider-unfriendly required-only acceptance subschemas while preserving runtime validation for empty acceptance contracts.
Make acceptance prompts map required evidence to acceptance-report JSON fields so visible prose does not satisfy structured evidence by itself.
Prepare the 0.28.0 release with foreground timeouts, per-agent resource limits, and acceptance compatibility fixes.
This was referenced Jun 19, 2026
Owner
|
Thanks for the PR. I verified the nested fanout history issue is real, but this branch also pulls in the broader 0.27/0.28 acceptance-finalization work plus unrelated nested activity timestamp UI, so it is too wide to merge as this bugfix. I split the narrow history preservation fix into #291 and left the separate fanout child registration conflict to #281. |
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.
Summary
Tests