Repository navigation
Refresh Mneme branding: README hero and plugin-list icon - #675
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What
dsh-mneme/andmcp/READMEs now open withimages/mneme-banner-hero.webp(1672×941, 282 KiB). The 2.1 MiB source PNG would have doubled theimages/directory. The root README uses a relative path; the two sub-READMEs use the raw absolute URL because npm does not resolve relative image paths (../images/...breaks on npmjs.com).package.json'siconnow points atassets/icon.png(256×256 RGBA, rounded corners genuinely transparent, 120,715 B — under the host's 256 KiB cap). The retiredassets/icon.svgis removed;docs/DIRECTORIES.mdandCHANGELOG.mdfollow.Tests
test/client.test.jsno longer compares the SVG against the inlinedMNEME_MARK_D(the list icon and the sidebar mark are intentionally different marks now). It validates the PNG itself: magic bytes, 256×256 IHDR, 8-bit, colour type 6 (RGBA) — the host falls back to a generic glyph on a bad file without reporting an error.Summary by CodeRabbit