soktri3 · soktri3 · Jun 21, 2026 · gemini-code-assist · Jun 21, 2026
diff --git a/.jules/bolt.md b/.jules/bolt.md
@@ -15,3 +15,7 @@
 **Learning:** Using non-canonical URLs (e.g., those missing trailing slashes or using old repository names) triggers HTTP redirects (301, 302, 308). This adds at least one extra network round-trip (RTT), which can significantly delay page load or navigation on slower connections.
 
 **Action:** Always use the final, canonical destination URLs for documentation and external links. Verify these URLs with `curl` to ensure they return a 200 OK status without further redirects.
+
+## 2026-06-21 - Precision Matters in SVG Optimization
+**Learning:** With SVGO 4.0.1, the default precision or precision >= 1 may result in zero file size reduction for certain assets. Using `--precision 0` was necessary to achieve a ~47% reduction for the organization logos without visual degradation. Overwriting the source files directly is preferred over creating `.min.svg` variants to avoid technical debt.
+**Action:** Experiment with precision levels (starting at 0) if default SVGO passes yield no gains. Always optimize in-place for referenced assets.
-## 2026-06-21 - Precision Matters in SVG Optimization
-**Learning:** With SVGO 4.0.1, the default precision or precision >= 1 may result in zero file size reduction for certain assets. Using `--precision 0` was necessary to achieve a ~47% reduction for the organization logos without visual degradation. Overwriting the source files directly is preferred over creating `.min.svg` variants to avoid technical debt.
-**Action:** Experiment with precision levels (starting at 0) if default SVGO passes yield no gains. Always optimize in-place for referenced assets.
+## 2026-06-21 - Precision Matters in SVG Optimization
+**Learning:** With SVGO 4.0.1, using an appropriate precision level (typically precision 1 or 2) is crucial to balance file size reduction with visual fidelity. While precision 0 yields the smallest file size, it can introduce geometric distortion (e.g., breaking 45-degree diagonal symmetry) and lumpy curves on text paths when scaled. Overwriting the source files directly is preferred over creating minified variants to avoid technical debt.
+**Action:** Use precision 1 or 2 as the default for logo assets to preserve geometric symmetry and smooth curves. Always optimize in-place for referenced assets.
-## 2026-06-21 - Precision Matters in SVG Optimization
-**Learning:** With SVGO 4.0.1, the default precision or precision >= 1 may result in zero file size reduction for certain assets. Using `--precision 0` was necessary to achieve a ~47% reduction for the organization logos without visual degradation. Overwriting the source files directly is preferred over creating `.min.svg` variants to avoid technical debt.
-**Action:** Experiment with precision levels (starting at 0) if default SVGO passes yield no gains. Always optimize in-place for referenced assets.
+## 2026-06-21 - Precision Matters in SVG Optimization
+**Learning:** With SVGO 4.0.1, using an appropriate precision level (typically precision 1 or 2) is crucial to balance file size reduction with visual fidelity. While precision 0 yields the smallest file size, it can introduce geometric distortion (e.g., breaking 45-degree diagonal symmetry) and lumpy curves on text paths when scaled. Overwriting the source files directly is preferred over creating minified variants to avoid technical debt.
+**Action:** Use precision 1 or 2 as the default for logo assets to preserve geometric symmetry and smooth curves. Always optimize in-place for referenced assets.
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