Configure final output contracts for handoff workflows - #18
Merged
Merged
Conversation
DrDrewCain
changed the base branch from
feature/task-output-contracts
to
main
September 13, 2026 13:13
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.
Handoff workflow authors can now configure a final text or JSON/schema contract while agents exchange ordinary prose notes. The editor preserves authored schemas through save/reload, marks invalid schema drafts unsaved, and keeps each agent's selected model and allowed targets.
Requires the independent agents.handoffs.output_requirements capability; task contract support alone does not enable these controls. Older hosts retain the existing editor. Loaded contracts are preserved and cannot be saved through unsupported capabilities. Result text remains a string and the native host enforces the final contract.
Validation: 479 unit tests passed, followed by 27 focused capability/contract checks including the additional explicit capability case; strict TypeScript, build, and packaged assets passed. Four real packaged-console/native HTTP desktop/mobile journeys passed, covering task and two-hop handoff execution, exact schemas, rejected output, invalid draft/discard behavior, and encrypted journal restart without inference. Both handoff screenshots inspected. Independent review: eight focused tests/types and four additional source-editor browser scenarios passed, including legacy and unsupported hosts. Existing bundle-size advisory remains.
Depends on Web17 and native ProjectScone PR79. Actual Fable exact-head consultation and all CI remain required before merge.