+```
+
+---
+
+**🤖 AI FIXABILITY: HIGH (Automatic)**
+
+**PROMPT FOR AI:**
+
+```
+Read the file src/lib/components/lines-and-dots/svg/timeline-graph-row.svelte and find line 213.
+Look for any mustache interpolations like {"..."} or {`...`} that contain only string literals.
+Remove the curly braces and quotes, leaving just the plain text.
+Example: {"text"} becomes text, {`string`} becomes string
+```
+
+**REQUIRED CONTEXT:**
+
+- File: `src/lib/components/lines-and-dots/svg/timeline-graph-row.svelte`
+- Pattern to find: `{"string"}` or `{` ` string` `}`
+- Pattern to replace: Just the inner string content
+
+---
+
+### 2. svelte/require-store-reactive-access (1 instance) ⭐ QUICK WIN
+
+**Severity:** High - Reactivity Bugs
+**Effort:** Low
+**Rule Docs:** https://sveltejs.github.io/eslint-plugin-svelte/rules/require-store-reactive-access/
+
+**Description:**
+Requires using the `$` prefix or `get()` function to access reactive store values instead of accessing the raw store object.
+
+**Why This Matters:**
+
+- Accessing raw store won't create reactive subscriptions
+- UI won't update when store changes
+- Common source of reactivity bugs
+
+**Affected Files:**
+
+- `src/lib/holocene/menu/menu-container.svelte` (line 52)
+
+**Fix:**
+Use `$` prefix for auto-subscription.
+
+```svelte
+
+
+
+
+
+```
+
+---
+
+**🤖 AI FIXABILITY: HIGH (Automatic)**
+
+**PROMPT FOR AI:**
+
+```
+Read src/lib/holocene/menu/menu-container.svelte and locate line 52.
+Find any store variable being accessed without the $ prefix (e.g., myStore instead of $myStore).
+Add the $ prefix to access the reactive value.
+Be careful not to add $ to the store in import statements or where the store itself needs to be passed as a reference.
+```
+
+**REQUIRED CONTEXT:**
+
+- File: `src/lib/holocene/menu/menu-container.svelte` around line 52
+- Look for: Store variables accessed without `$` prefix
+- Pattern: `storeName` → `$storeName` (but not in imports or function parameters)
+
+---
+
+### 3. import/order (1 instance) ⭐ QUICK WIN
+
+**Severity:** Low - Code Quality
+**Effort:** Low
+
+**Description:**
+Enforces configured import ordering rules (empty lines within import groups).
+
+**Why This Matters:**
+
+- Consistency across codebase
+- Minor code quality issue
+
+**Affected Files:**
+
+- `.storybook/preview.ts` (line 2)
+
+**Fix:**
+Remove empty lines within import groups or adjust grouping.
+
+---
+
+**🤖 AI FIXABILITY: HIGH (Automatic)**
+
+**PROMPT FOR AI:**
+
+```
+Read .storybook/preview.ts and examine the imports at the top of the file around line 2.
+According to the import/order rule, there should be no empty lines within the same import group.
+Remove any empty lines that appear between imports of the same group (all external imports should be together, all internal imports should be together).
+Keep empty lines between different groups (e.g., between external and internal imports).
+```
+
+**REQUIRED CONTEXT:**
+
+- File: `.storybook/preview.ts` lines 1-10
+- Look for: Empty lines within import groups
+- Fix: Remove empty line at line 2
+
+---
+
+### 4. no-undef (1 instance) ⭐ QUICK WIN
+
+**Severity:** Medium - Type Safety
+**Effort:** Low
+
+**Description:**
+ESLint core rule detecting undefined variables.
+
+**Why This Matters:**
+
+- May indicate missing type definitions
+- Could cause runtime errors
+
+**Affected Files:**
+
+- `src/lib/holocene/lazy-visibility/lazy-visibility.svelte` (line 8: 'IntersectionObserverInit')
+
+**Fix:**
+Add proper TypeScript definitions or import types.
+
+```typescript
+// Fix: Ensure DOM types are available
+///
+```
+
+---
+
+**🤖 AI FIXABILITY: MEDIUM (Semi-automatic)**
+
+**PROMPT FOR AI:**
+
+```
+Read src/lib/holocene/lazy-visibility/lazy-visibility.svelte around line 8.
+Find where IntersectionObserverInit is used. This is a built-in DOM API type.
+Check if there's a TypeScript reference comment at the top of the file.
+If missing, add /// at the very top of the script tag.
+Alternatively, if the file uses TypeScript, ensure it's typed as a .ts or has lang="ts" on the script tag.
+```
+
+**REQUIRED CONTEXT:**
+
+- File: `src/lib/holocene/lazy-visibility/lazy-visibility.svelte`
+- Look for: Usage of `IntersectionObserverInit` around line 8
+- Check: TypeScript configuration and DOM lib references
+- Fix: Add `/// ` or ensure proper TypeScript setup
+
+---
+
+### 5. @typescript-eslint/ban-types (2 instances) ⭐ QUICK WIN
+
+**Severity:** Low - Configuration
+**Effort:** Low
+
+**Description:**
+Shows "Definition for rule was not found" error because the rule was disabled but inline comments in code reference it.
+
+**Why This Matters:**
+
+- Inline rule disables don't work if rule doesn't exist
+- Minor configuration cleanup
+
+**Affected Files:**
+
+- `src/lib/stores/configurable-table-columns.ts` (line 33)
+- `src/lib/utilities/omit.ts` (line 2)
+
+**Fix:**
+Remove inline `eslint-disable` comments for this rule since it's disabled globally.
+
+```typescript
+// Bad (if rule is disabled)
+// eslint-disable-next-line @typescript-eslint/ban-types
+type Foo = {};
+
+// Good (just remove the comment)
+type Foo = {};
+```
+
+---
+
+**🤖 AI FIXABILITY: HIGH (Automatic)**
+
+**PROMPT FOR AI:**
+
+```
+Read these two files:
+1. src/lib/stores/configurable-table-columns.ts (line 33)
+2. src/lib/utilities/omit.ts (line 2)
+
+Find any ESLint comment directives that mention @typescript-eslint/ban-types:
+- // eslint-disable-next-line @typescript-eslint/ban-types
+- // eslint-disable @typescript-eslint/ban-types
+- /* eslint-disable @typescript-eslint/ban-types */
+
+Remove these comment lines entirely since the rule is disabled globally in the config.
+```
+
+**REQUIRED CONTEXT:**
+
+- Files:
+ - `src/lib/stores/configurable-table-columns.ts` around line 33
+ - `src/lib/utilities/omit.ts` around line 2
+- Look for: ESLint disable comments containing `@typescript-eslint/ban-types`
+- Fix: Delete the entire comment line
+
+---
+
+### 6. svelte/no-reactive-literals (2 instances) ⭐ QUICK WIN
+
+**Severity:** Low - Code Quality
+**Effort:** Low
+**Rule Docs:** https://sveltejs.github.io/eslint-plugin-svelte/rules/no-reactive-literals/
+
+**Description:**
+Reports assignment of static, unchanging values within reactive statements because they're unnecessary.
+
+**Why This Matters:**
+
+- Wastes runtime cycles checking for changes
+- Makes code confusing (appears reactive when it's not)
+- Simple code quality issue
+
+**Affected Files:**
+
+- `src/lib/components/data-encoder-settings.svelte` (line 40)
+- `src/lib/holocene/combobox/async-test.svelte` (line 13)
+
+**Fix:**
+Move static assignments outside of reactive statements.
+
+```svelte
+
+
+
+
+
+```
+
+---
+
+**🤖 AI FIXABILITY: HIGH (Automatic)**
+
+**PROMPT FOR AI:**
+
+```
+Read these files:
+1. src/lib/components/data-encoder-settings.svelte (line 40)
+2. src/lib/holocene/combobox/async-test.svelte (line 13)
+
+Find reactive statements ($:) that assign literal values (strings, numbers, booleans, arrays, objects) that never change.
+Example patterns to find:
+- $: foo = 'string';
+- $: bar = 123;
+- $: baz = true;
+
+Convert these to regular const declarations:
+- const foo = 'string';
+- const bar = 123;
+- const baz = true;
+
+Do NOT change reactive statements that depend on other variables or have complex logic.
+```
+
+**REQUIRED CONTEXT:**
+
+- Files:
+ - `src/lib/components/data-encoder-settings.svelte` around line 40
+ - `src/lib/holocene/combobox/async-test.svelte` around line 13
+- Pattern to find: `$: variableName = literalValue;`
+- Pattern to replace: `const variableName = literalValue;`
+
+---
+
+### 7. svelte/infinite-reactive-loop (2 instances) ⚠️ COMPLEX
+
+**Severity:** Critical - Application Stability
+**Effort:** Medium-High per instance
+**Rule Docs:** https://sveltejs.github.io/eslint-plugin-svelte/rules/infinite-reactive-loop/
+
+**Description:**
+Detects situations where updating state in reactive statements could cause infinite loops, especially with async operations across different microtasks.
+
+**Why This Matters:**
+
+- Can freeze the application
+- Causes performance degradation
+- May lead to browser crashes in severe cases
+- Critical stability issue
+
+**Affected Files:**
+
+- `src/lib/components/event/metadata-decoder.svelte` (2 instances at lines 53, 60)
+
+**Fix:**
+Review reactive logic to prevent circular dependencies. Add guards or restructure code.
+
+```svelte
+
+
+
+
+
+```
+
+---
+
+**🤖 AI FIXABILITY: LOW (Manual Review Required)**
+
+**PROMPT FOR AI:**
+
+```
+Read src/lib/components/event/metadata-decoder.svelte completely, paying special attention to lines 53 and 60.
+
+Analyze the reactive logic and identify:
+1. What variables are being read in the reactive statement
+2. What variables are being written in the reactive statement
+3. If any written variables are also being read (circular dependency)
+4. If there's async code that updates reactive state
+
+For each infinite loop:
+- Explain what's causing the loop
+- Suggest one of these fixes:
+ a) Add a guard condition to prevent re-execution
+ b) Use a different reactivity pattern (derived state instead of effect)
+ c) Move the update outside the reactive context
+ d) Use untrack() to break the reactive dependency
+
+Provide the full refactored code with clear comments explaining the fix.
+```
+
+**REQUIRED CONTEXT:**
+
+- File: `src/lib/components/event/metadata-decoder.svelte` (FULL FILE)
+- Understanding of: Component's purpose, data flow, when effects should run
+- Need: Business logic context to determine correct fix
+- Warning: Cannot be fixed without understanding the intended behavior
+
+---
+
+### 8. svelte/no-at-html-tags (2 instances) ⚠️ SECURITY CRITICAL
+
+**Severity:** Critical - Security (XSS)
+**Effort:** Medium per instance
+**Rule Docs:** https://sveltejs.github.io/eslint-plugin-svelte/rules/no-at-html-tags/
+
+**Description:**
+Warns about `{@html}` usage which can lead to XSS (Cross-Site Scripting) attacks if used with unsanitized user input.
+
+**Why This Matters:**
+
+- Major security vulnerability
+- Can allow attackers to execute arbitrary JavaScript
+- Critical for production applications
+- May violate security compliance requirements
+
+**Affected Files:**
+
+- `src/lib/components/schedule/schedule-frequency.svelte` (line 28)
+- `src/lib/components/schedule/schedules-table-row.svelte` (line 94)
+
+**Fix:**
+Ensure HTML is sanitized or use safer alternatives.
+
+```svelte
+
+
+
+
+{@html userContent}
+{@html safeContent}
+
+
+