Make things 'betterer' across the board (#23)

* Make things 'betterer' across the board

* fix: reorganize struct fields and config parameters for consistency

- [x] Reorder Config struct fields alphabetically and by related functionality
- [x] Reorganize Observation model fields with archival fields grouped together
- [x] Reorder ObservationStore fields to group related members
- [x] Reorder Store struct fields with health check caching grouped
- [x] Reorganize HealthInfo and PoolMetrics struct field order
- [x] Reorder maintenance Service struct fields logically
- [x] Reorganize MCP server handler parameter structs alphabetically
- [x] Reorder pattern detector candidate tracking fields
- [x] Reorganize search Manager struct fields by functionality
- [x] Reorder vector Client struct fields with mutex protections grouped
- [x] Reorganize handler request/response struct fields
- [x] Update handlers_test.go to expect wrapped response format
- [x] Reorder middleware TokenAuth and rate limiter fields
- [x] Reorganize Service struct fields with grouped functionality
- [x] Fix RateLimiter field ordering for clarity
- [x] Reorder CircuitBreaker metrics fields

* fix(security): improve JSON output safety and path traversal protection

- [x] Replace unsafe JSON string formatting with proper json.Marshal in export handler
- [x] Remove escapeJSONString helper function in favor of standard JSON marshaling
- [x] Add safeResolvePath function to validate paths and prevent directory traversal
- [x] Apply path traversal validation in captureFileMtimes operations
- [x] Cap result slice capacity in getRecentSearchQueries to prevent DoS via excessive allocation

* fix(sdk): improve path traversal protection and allocation safety

- [x] Enhance safeResolvePath with stricter validation using filepath.Rel
- [x] Reject paths containing ".." after cleaning to prevent traversal
- [x] Validate absolute paths are within cwd when cwd is specified
- [x] Apply safeResolvePath validation to GetFileContent for consistency
- [x] Add comprehensive test coverage for path traversal protection
- [x] Fix allocation safety in getRecentSearchQueries by using constant capacity

ui/src/components/ObservationCard.vue

@@ -8,6 +8,7 @@ import Card from './Card.vue'
 import IconBox from './IconBox.vue'
 import Badge from './Badge.vue'
 import RelationGraph from './RelationGraph.vue'
+import ScoreBreakdown from './ScoreBreakdown.vue'
 import { computed, ref, onMounted } from 'vue'
 
 const props = defineProps<{
@@ -95,6 +96,9 @@ const relationsLoading = ref(false)
 const relationsExpanded = ref(false)
 const showGraph = ref(false)
 
+// Score breakdown state
+const showScoreBreakdown = ref(false)
+
 const hasRelations = computed(() => relations.value.length > 0)
 const relationCount = computed(() => relations.value.length)
 
@@ -350,14 +354,15 @@ const splitPath = (path: string, components = 3) => {
           <i class="fas fa-thumbs-up text-sm" />
         </button>
 
-        <span
-          class="text-[10px] font-mono px-1.5 py-0.5 rounded bg-slate-800/50 text-slate-400 flex items-center gap-1 transition-all duration-300"
+        <button
+          @click="showScoreBreakdown = true"
+          class="text-[10px] font-mono px-1.5 py-0.5 rounded bg-slate-800/50 text-slate-400 flex items-center gap-1 transition-all duration-300 hover:bg-purple-500/20 hover:text-purple-300 cursor-pointer"
           :class="{ 'text-green-400': localScore !== null && localScore > (observation.importance_score || 1), 'text-red-400': localScore !== null && localScore < (observation.importance_score || 1) }"
-          :title="`Importance Score: ${currentScore.toFixed(3)}\nRetrieval Count: ${observation.retrieval_count || 0}`"
+          :title="`Importance Score: ${currentScore.toFixed(3)}\nRetrieval Count: ${observation.retrieval_count || 0}\nClick for details`"
         >
-          <i class="fas fa-scale-balanced text-amber-500/60" />
+          <i class="fas fa-chart-bar text-purple-500/60" />
           {{ currentScore.toFixed(2) }}
-        </span>
+        </button>
 
         <button
           @click="submitFeedback(-1)"
@@ -383,5 +388,12 @@ const splitPath = (path: string, components = 3) => {
       @close="showGraph = false"
       @navigate-to="handleNavigateTo"
     />
+
+    <!-- Score Breakdown Modal -->
+    <ScoreBreakdown
+      :observation-id="observation.id"
+      :show="showScoreBreakdown"
+      @close="showScoreBreakdown = false"
+    />
   </Card>
 </template>