feat: adopt selected CLI Proxy brand icon - #6
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
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.
Replace the old CLIProxy image with the selected plugin-owned 256×256 brand PNG. The existing public plugin
iconexport and model-providerBrandIconV1presentation share the exact image bytes; the provider dimensions now match the square asset. Trackassets/icon.pngand include it in the package allowlist so Marketplace can reference an immutable source URL.Validation: selected PNG SHA256
15295b1c1634e631b5e1d11a4b17838778c3d4cba03cca95b8bf5d13c13ff0d4, dimensions, inline byte equality andgit diff --checkpass. Added checks for built-module byte equality and tarball inclusion. Fullnpm run checkand packing are delegated to CI per shared-machine resource constraints; local dependency setup was stopped, so local check/pack attempts could not find tsc/vite.Version remains 0.1.0, private, explicit-local-v1 source distribution. No npm release, new release mechanism, Host behavior, or operation icons change. Native UI acceptance is not claimed by these package checks.