⚡ Bolt: optimize organization logo SVGs

[soktri3]

This PR implements a small but effective performance optimization by minifying the organization's logo SVGs.

💡 What

I have optimized profile/assets/logo.svg and profile/assets/logo-dark.svg using svgo. The optimization involves rounding path coordinates to integers and removing unnecessary metadata. I also added a performance comment to each file to document the optimization.

🎯 Why

Large asset files increase the bandwidth required to load the organization's profile page and can delay the rendering of the primary branding elements. Minifying these SVGs provides a measurable reduction in asset size without sacrificing visual quality.

📊 Impact

• Total Asset Size Reduction: ~47% (from ~10.1KB to ~5.3KB).
• Per File Savings: ~2.4KB per SVG.

🔬 Measurement

• Size: Verified using ls -lh.
• Visuals: Verified using a Playwright script that rendered the original and optimized versions side-by-side in a high-contrast environment. No visual differences were detectable.
• Linting: Confirmed no new regressions using npx markdownlint-cli ..

---

PR created automatically by Jules for task 17850838849565367474 started by @soktri3

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Code Review

This pull request documents an SVGO 4.x precision quirk and applies SVGO optimization with --precision 0 to logo-dark.svg and logo.svg. The reviewer noted that using --precision 0 on paths with round linecaps introduces zero-length path segments (m0 0, h0) which can render as unwanted circular artifacts on some SVG renderers and add redundant bytes. Additionally, the reviewer advised removing the manually added comment <!-- ⚡ Bolt: optimized with svgo --> to achieve better minification, and suggested updating the documentation in .jules/bolt.md to warn against using --precision 0 in such cases.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Using --precision 0 has introduced zero-length path segments like m0 0 (from m.7-.7) and h0 (from l.3.4). Because this path has stroke-linecap="round" and stroke-width="12", these zero-length segments can render as visible circular dots (artifacts) on some SVG renderers. Additionally, these redundant commands (m0 0, h0) waste bytes, defeating the purpose of minification.

Furthermore, the manually added comment <!-- ⚡ Bolt: optimized with svgo --> adds unnecessary bytes to the file. For production-ready assets, all comments should be stripped to achieve maximum minification.

Please re-optimize the SVG using --precision 1 or --precision 2 and ensure all comments are removed.

[gemini-code-assist]

Using --precision 0 has introduced zero-length path segments like m0 0 (from m.7-.7) and h0 (from l.3.4). Because this path has stroke-linecap="round" and stroke-width="12", these zero-length segments can render as visible circular dots (artifacts) on some SVG renderers. Additionally, these redundant commands (m0 0, h0) waste bytes, defeating the purpose of minification.

Furthermore, the manually added comment <!-- ⚡ Bolt: optimized with svgo --> adds unnecessary bytes to the file. For production-ready assets, all comments should be stripped to achieve maximum minification.

Please re-optimize the SVG using --precision 1 or --precision 2 and ensure all comments are removed.

[gemini-code-assist]

Using --precision 0 is highly discouraged for SVGs with round linecaps (stroke-linecap="round"). Coordinate rounding converts small relative movements/lines (like m.7-.7 and l.3.4) into zero-length commands (m0 0 and h0). In SVG, zero-length path segments with round linecaps can render as visible circular dots (artifacts) on some renderers, and they add redundant bytes to the file.

Instead, we should use at least --precision 1 or --precision 2 to preserve path integrity, and rely on other SVGO plugins to strip metadata and comments.

Suggested change

	## 2026-06-17 - Precision Quirk in SVGO 4.x
	**Learning:** In SVGO version 4.0.1, the default precision or even `--precision 1` can result in 0% file size reduction for certain path-heavy logos. Specifically, organization assets in this repo required `--precision 0` to trigger any meaningful optimization.
	**Action:** If `svgo` reports 0% reduction, retry with `--precision 0` and perform visual verification to ensure coordinate rounding hasn't introduced artifacts.
	## 2026-06-17 - Precision and Artifacts in SVGO 4.x
	**Learning:** Using `--precision 0` in SVGO can round small coordinate values to zero, creating redundant zero-length path commands (like `m0 0` and `h0`). When paths use `stroke-linecap="round"`, these zero-length segments can render as unwanted circular artifacts (dots) depending on the SVG renderer.
	**Action:** Avoid using `--precision 0` for paths with round linecaps. Use at least `--precision 1` or `--precision 2` to preserve path integrity, and ensure all comments and metadata are stripped for optimal minification.