Repository navigation
Use approved plugin-owned Ascension brand icon - #17
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.
Replace Ascension's site-derived icon with the approved plugin-owned 256×256 PNG. The existing public
iconexport embeds exactly those bytes; reasoning controls, portraits, site assets, and package version stay unchanged.The tracked image is
plugin/src/assets/identity/ascension.png, SHA2562a037ea870d249272dc3ff7de69fc178e06fa89dc16dbfe8bebfc5bdc966626c. Build tests verify byte identity, hash and dimensions. Plugin checks passed locally; existing formatting and shared-quality CI remain required.Validation:
npm run check(typecheck, build, 3 tests),npm run dev:dry-run, Host brand-icon projector acceptance,npm pack --dry-runsource asset inclusion, andgit diff --check. Native window interaction is not claimed. This private source-distributed plugin has no npm/tag release workflow; merging updates its source distribution.