Repository navigation
Add shared ongoing-agent controls across client contracts - #14
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
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.
Add shared ongoing-agent forms and controls for reviewing standing instructions, sources, tools and resource limits; explicit unattended consent; retained activity and work; and pause, resume, revise, run-now, revoke and stop actions. Full clients expose the shared controls, while the wrist contract provides status and chat handoff. Sensitive actions continue through Deep's attended authorization flow.
The renderer preserves every selected tool and unchecked consent through the actual web transport. Protocol and client drift guards change together. At current head
07e5c90cb310c48c2315997f74dc8dd6f5fa22ea, stopped and completed assignments retain status, history and safe failure information while wrist guidance removes pause/resume/stop commands that cannot apply to terminal work. The companion Deep adapter applies the same terminal-state guidance to its rendered views. Build-only setuptools is hash-locked to 83.0.0. No runtime dependency, primitive or verification threshold changed.Validation of this repair: 177 shared-view/protocol/provenance tests passed with one existing native-platform skip, and the shipped-client browser fixture passed 5/5. Both new executable Projection lines are covered. Deep's related rendered-view, personalization and native-surface integration tests passed 159/159 with all three new Deep lines covered. These are source-bound local tests, not authenticated all-client acceptance.
The earlier unchanged feature implementation retains its measured evidence: the 1,190-test Python owner suite, Windows 1,080 passed / nine skipped, C# 37 passed, Node 28 passed, the shipped-client browser fixture, and Android lint/unit/coverage/assemble gates. Earlier changed Python coverage was 203/204 lines (99.51%). Reports preserve their actual source identities rather than claiming those earlier full runs tested this later terminal-guidance repair.
All required hosted owner CI checks passed for exact
07e5c90cb310c48c2315997f74dc8dd6f5fa22ea: Python/package, web, Windows, Android build/emulator/aggregate, strict Swift formatting, AstralCore, iOS/macOS app continuity, iOS/macOS first-login and voice UI, watchOS continuity, and both final core/Apple aggregates. The optional next-major Android readiness job was skipped under its existing conditions. Provider run/job identities and native Android/Apple archives are retained with verified SHA256 digests. The complete strict owner coverage diagnostic passes 206/207 changed executable lines (99.52%) across all nine required producer slots, using those hosted reports plus exact-source-bound local Python/Windows/JavaScript observations. This required a reviewed collector ownership correction so overlapping folders do not demand coverage from the wrong language; all producer requirements and the 90% threshold remain intact. These are owner CI and diagnostic coverage checks, not evidence of authenticated persistent-agent behavior on every live client against Deep.Keep this PR draft until required owner checks, independent review and affected live-client qualification are complete. No approving review is present. No signing, store submission, production promotion or activation of historical release workflows is included. Deep's companion implementation pins this component and owns scheduling, permissions, durable execution and approvals.