Repository navigation
Add protected typed tool media and fenced native task continuation - #120
Merged
Merged
Conversation
added 30 commits
October 13, 2026 11:25
added 21 commits
October 13, 2026 18:07
first-assist
marked this pull request as ready for review
October 13, 2026 13:42
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.
Summary
Registered tool results can deliver owner-verified protected JPEG/PNG bytes as real provider image content. The SDK retains completed effects and original/effect/current provenance, checks current source authorization on every disclosure, and reserves image capacity atomically. Unsupported or unguarded adapters refuse before protected effects.
Retained native runs can change only their original fingerprint-bound static tool subset after confirmed old-thread deletion and a fenced fresh-thread transition. The same original task/event/status context is freshly priced and authorized. One proved unstarted image reduction can finish through tool-free withholding without renewing consent, repeating effects, or redisclosing unavailable history.
AI 0.107.0, profiles 0.16.0, AI schema 0.72.0. These are documented pre-1.0 source-breaking package releases. Consumer integration: GEMA PR450.
Reviewed PR head
2255dab3c29f5fe2e8233b53a42edc1bf79733e4merged as2e8cb79941a41ce1a1ae2a6138b18f2fdb08562b. Its Rust/manifests/lock are byte-identical to qualified runtime source881cb8a6144d43d377e099fdc4c2e9f18b9a6403; final intervening changes affect six Markdown files.Verification
3dcb51231a69ad40158af74f250be133747eacd5: AI 196 checks / 192 passed / 4 failed / 49 skipped; profiles 196 / 195 / 1 / 49. The failures identify documented pre-1.0 source-breaking changes: request-context unwind auto traits, generated session input/aggregate-enum changes, and the descriptor media field. These negative compatibility results remain visible. Selected default release-version classification passed for both packages, detecting a major compatibility boundary (0 checks / 245 skipped). That validates version policy, not backward compatibility. Initial implicit SemVer commands made no API comparison and are not compatibility evidence.Publication
Published immutable workspace-2026.10.13.1 at merged source
2e8cb79941a41ce1a1ae2a6138b18f2fdb08562b. The protected canonical Workspace release run completed all 20 jobs successfully after the required Dastari human review. Independent readback verified all nine annotated package tag/tree bindings and the three exact source-only assets, SHA256SUMS/API digests and cryptographic attestations bound to this workflow, main and source commit. Published manifest SHA-256:c26fdb21aa37661c7b98e3fd1cf30605e998d20b50e32fdcd6b522c0ba5241af. The release contains source metadata; GEMA adoption and physical model/endpoint acceptance remain separate.Documentation impact
Owning README, migration guide, dated changelog and indexed media reference document source custody, original/effect/current fencing, budgets, final transport guards, schema/restore, static offerings, cleanup and original-task continuation. Migration notes enumerate every reported source-breaking change and consumer remediation. Historical release entries are preserved.