Conversation
AgencyZero registered its relaunch handler through `tauri_runtime_blitz::set_agent_control_handler` and named the request types through that crate's `control_protocol` re-export. So the vocabulary an agent drives this application with arrived through a window runtime, and naming an `AgentControlRequest` meant compiling Tauri. A runtime bridges Tauri to Blitz and owns a native window. It does not proxy an inspection service, and it no longer exports one. This takes `blitz-control-protocol` directly, with default features: the vocabulary and the lifecycle handler, no engine and no transport. `tauri-runtime-blitz` stays, at `^0.4`. AgencyZero opens a window, so it wants the runtime for the reason the runtime exists. Not compiled here: its build script needs a frontend install this checkout does not have.
Owner
Author
|
Closing in favor of #211. The lifecycle ownership change is folded there together with the descriptor-by-PID QA correction. |
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
1 participant
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.
Last of five repos in one change: the Blitz control surface is centralised in
blitz-control-protocol.AgencyZero registered its relaunch handler through
tauri_runtime_blitz::set_agent_control_handlerand named the request types through that crate'scontrol_protocolre-export, so the vocabulary an agent drives this application with arrived through a window runtime.tauri-runtime-blitzstays, at^0.4. AgencyZero opens a window, so it wants the runtime for the reason the runtime exists. Only the control symbols move.Merge last, after:
ps-blitz0.4.8 →tauri-runtime-blitz0.4.0 →ps-observability(blitz-control-protocol 0.5.0) →chuzz. Each resolves the previous by caret at build time, so wait for the publish, not the merge.Not verified here: this was not compiled. Its build script needs a frontend install this checkout does not have, so the change is a mechanical swap of two symbol paths plus a manifest entry, unproven by a build.