perf(remote-config): specialize WASM for agentless use - #254
Draft
BridgeAR wants to merge 1 commit into
Draft
Conversation
The dedicated remote-config entry point is consumed only in agentless mode, but optional credentials kept the generic transport dispatch reachable. Require the agentless inputs and call the explicit upstream constructor so the contract is static at the binding boundary. With the final dependency cohort, the raw remote-config artifact drops from 893,017 to 892,798 bytes. The dependency stays pinned to the reviewed upstream commit until its release is available.
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.
Requires agentless credentials at the dedicated WASM binding boundary and calls the explicit upstream constructor. The capabilities, pipeline, and remote-config dependency cohort is pinned to the reviewed upstream commit.
The raw remote-config artifact drops from 893,017 to 892,798 bytes.
Tested with both WASM Cargo checks, dependency validation, a rebuilt artifact, and the complete 47-test package and type suite.