soktri3 · soktri3 · Jul 11, 2026 · gemini-code-assist · Jul 11, 2026
diff --git a/.jules/bolt.md b/.jules/bolt.md
@@ -21,3 +21,7 @@
 **Learning:** Standard SVGO optimizations might not always catch all structural redundancies, such as adjacent path elements with identical attributes. Merging these manually or via targeted scripts can further reduce DOM complexity and file size without visual regression.
 
 **Action:** After running SVGO, inspect SVG structure for mergeable paths with identical stroke or fill attributes. Always verify with visual regression tests using Playwright.
+
+## 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 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.
-## 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.
diff --git a/profile/assets/logo-dark.svg b/profile/assets/logo-dark.svg
diff --git a/profile/assets/logo.svg b/profile/assets/logo.svg