Skip to content

Brand: integrate the approved WVO monogram - #35

Merged
Artsen merged 2 commits into
mainfrom
brand/integrate-wvo-monogram
Jul 22, 2026
Merged

Brand: integrate the approved WVO monogram#35
Artsen merged 2 commits into
mainfrom
brand/integrate-wvo-monogram

Conversation

@Artsen

@Artsen Artsen commented Jul 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds the approved WVO monogram under apps/web/public/brand/ using optimized transparent WebP assets.
  • Replaces the temporary inline compression-frame app mark with theme-aware image variants.
  • Uses the dark-letter transparent variant on light surfaces and the white-letter transparent variant on dark surfaces.
  • Adds a derived PNG favicon from the approved monogram for browser chrome.
  • Removes obsolete SVG brand assets and the oversized PNG logo files so the repo has one canonical lightweight logo family.
  • Updates the README, brand-system documentation, and curated README screenshots.
  • Stabilizes one existing startup-warning unit test by waiting for the async status panel before asserting on it.

Asset Validation

  • Original supplied WVO-logo-transparent.png: 2,008,932 bytes, PNG, 1536x1024, transparent corners.
  • Original supplied WVO-logo-white-transparent.png: 2,115,578 bytes, PNG, 1536x1024, transparent corners.
  • Optimized WVO-logo-transparent.webp: 26,718 bytes, WebP, 768x512, argb alpha.
  • Optimized WVO-logo-white-transparent.webp: 43,058 bytes, WebP, 768x512, argb alpha.
  • WVO-favicon.png: 7,701 bytes, PNG, 256x256, derived from the approved white monogram on the app slate background.

The app logo pair went from 4,124,510 bytes to 69,776 bytes, about a 98.3% reduction. The supplied logo artwork was not redrawn or recolored; the app-facing assets are lossless WebP conversions scaled to a practical 768px source width for UI and README use. Only the favicon was derived as a small browser-chrome crop/scale.

Scope Boundaries

  • No workflow changes.
  • No API changes.
  • No media processing changes.
  • No dependency changes.
  • No Docker changes.
  • No UI redesign beyond replacing the temporary mark with the approved brand asset.
  • No .tmp/, data/, coverage output, build output, personal files, or private media committed.

Visual Review

  • Regenerated deterministic review screenshots with npm run review:ui-screens after both the branding change and the WebP optimization.
  • Refreshed the six curated README WebP screenshots.
  • Verified representative dark, light, and mobile screenshots show the correct logo variant without clipping, distortion, checkerboard background, or excessive visual weight.

Verification

  • npm ci: passed, added 548 packages.
  • npm run format: passed.
  • npm run format:check: passed.
  • npm run lint: passed.
  • npm run typecheck: passed.
  • npm run test:run: passed, 388 tests passed, 1 skipped.
  • npm run build: passed.
  • npm run check: passed after WebP optimization.
  • npm run test:coverage: passed.
  • Coverage headline: API 87.27% lines, Web 83.88% lines.
  • npm audit --omit=dev: passed, 0 vulnerabilities.
  • npm run test:e2e: passed, 10 Chromium tests.
  • npm run test:integration:media: passed, 5 real-media integration tests.
  • npm run review:ui-screens: passed, 1 screenshot review test.
  • git diff --check: passed.
  • Follow-up targeted verification after CI failure: npm run test:run --workspace apps/web -- src/app/App.test.tsx passed, 21 tests; npm run test:run passed, 388 tests, 1 skipped.

Notes

A stale ignored local .tmp/dev-smoke scratch folder caused one initial lint attempt to inspect an old generated script; it was removed. .tmp/ui-review/ and local application data were preserved.

@Artsen
Artsen marked this pull request as ready for review July 22, 2026 02:35
@Artsen
Artsen merged commit d57ff28 into main Jul 22, 2026
4 checks passed
@Artsen
Artsen deleted the brand/integrate-wvo-monogram branch July 22, 2026 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant