⚡ Bolt: optimize SVG path data

[soktri3]

💡 What:
Optimized SVG path data in profile/assets/logo.svg and profile/assets/logo-dark.svg by removing redundant commands like v0, h0, and simplifying m0 0 sequences.

🎯 Why:
Every byte counts for organization profile assets. Removing no-op path commands reduces the overall weight of the repository and minimizes the effort required for browsers to parse and render the vector graphics.

📊 Impact:

• Reduces file size of both logo.svg and logo-dark.svg from 2702 to 2692 bytes (~0.37% reduction per file).
• Simplifies SVG path complexity by eliminating redundant drawing instructions.

🔬 Measurement:

• Verified via ls -l (2702 -> 2692 bytes).
• Visual regression testing performed using Playwright to ensure zero visual impact.
• Path integrity checked manually via cat and grep.

---

PR created automatically by Jules for task 15579230762284456084 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 optimizes the SVG path data for both the dark and light logos by removing redundant moves and zero-length segments, and documents these path sanitization learnings in .jules/bolt.md. Feedback was provided on the documentation, pointing out that replacing m0 0 with m is unsafe because subsequent coordinate pairs are implicitly treated as lineto commands, which can break path geometry.

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]

Replacing m0 0 with m is actually not a safe general practice and can easily break SVG path geometry.

Why this happens:

In SVG path data, if a relative moveto (m) command is followed by multiple coordinate pairs, the first pair is treated as a move, but all subsequent pairs are implicitly treated as relative lineto (l) commands.

For example, in l-51 51m0 0 51-51:

1. l-51 51 draws a line.
2. m0 0 moves relative by 0,0 (no-op).
3. 51-51 is an implicit relative lineto drawing a line back.

If you replace m0 0 with m, you get m51-51, which is parsed as a relative moveto (moving the pen without drawing). This completely omits the line segment. While this happened to be a redundant line in this specific logo, in other SVGs this will break non-redundant path segments.

To optimize m0 0 safely, either convert subsequent coordinates to explicit l commands or merge them into preceding commands.

Suggested change

	## 2025-07-11 - Artifact Management and Path Sanitization
	**Learning:** Including verification scripts, screenshots, and backup files in a PR is considered "workspace litter" and will be rejected. Additionally, when using `sed` to remove redundant relative moves like `m0 0` in SVGs, it's safer to replace them with `m` to prevent accidental coordinate concatenation.
	**Action:** Always delete all temporary verification artifacts and backups before submission. Ensure SVG path data remains syntactically valid after string replacements.
	## 2025-07-11 - Artifact Management and Path Sanitization
	**Learning:** Including verification scripts, screenshots, and backup files in a PR is considered "workspace litter" and will be rejected. Additionally, when optimizing redundant relative moves like m0 0 in SVGs, note that any coordinate pairs following a moveto (m/M) command are implicitly treated as lineto (l/L) commands. Simply replacing m0 0 with m converts these implicit lines into moves, which can break path geometry.
	**Action:** Always delete all temporary verification artifacts and backups before submission. When optimizing m0 0 sequences, ensure subsequent coordinate pairs are either converted to explicit l commands or safely merged into preceding commands to preserve path geometry.