rename ss-tools to superset-tools across the entire project

- Replace all occurrences of 'ss-tools' with 'superset-tools' in 104 files
- Rename git bundle file ss-tools.bundle → superset-tools.bundle
- Update .gitignore pattern accordingly
- Preserve variable names (hasSsTools etc.) and code identifiers

.opencode/agents/svelte-coder.md

@@ -1,5 +1,5 @@
 ---
-description: Svelte Frontend Implementation Specialist for ss-tools — implements Svelte 5 (Runes) UI with Tailwind CSS, browser-driven validation, and UX state machines.
+description: Svelte Frontend Implementation Specialist for superset-tools — implements Svelte 5 (Runes) UI with Tailwind CSS, browser-driven validation, and UX state machines.
 mode: all
 model: deepseek/deepseek-v4-flash
 temperature: 0.1
@@ -57,7 +57,7 @@ See `semantics-core` §VI for the canonical tool reference. For Svelte frontend
 
 ---
 
-## ss-tools Frontend Scope
+## superset-tools Frontend Scope
 You own:
 - SvelteKit routes (`frontend/src/routes/`)
 - Svelte 5 components (`frontend/src/lib/components/` — **only directory for NEW domain components**)
@@ -113,7 +113,7 @@ You do not own:
 ## UX Contract Reference
 See `semantics-svelte` §II for full UX contract definitions. See `semantics-core` §III for the tag-to-tier permissiveness matrix. All UX tags (@UX_STATE, @UX_FEEDBACK, @UX_RECOVERY, @UX_REACTIVITY, @UX_TEST) are informational and allowed at any tier.
 
-## Frontend Design Practice (ss-tools)
+## Frontend Design Practice (superset-tools)
 For frontend design and implementation tasks, default to these rules unless the existing product design system clearly requires otherwise:
 
 ### Composition and hierarchy
@@ -122,7 +122,7 @@ For frontend design and implementation tasks, default to these rules unless the
 - Prefer whitespace, alignment, scale, and contrast before adding chrome.
 - Default to cardless layouts; use cards only when a card is the actual interaction container for a specific resource.
 
-### Visual system (ss-tools design tokens — source: `tailwind.config.js`)
+### Visual system (superset-tools design tokens — source: `tailwind.config.js`)
 **Raw Tailwind colors (`blue-600`, `green-500`, `red-600`, `gray-*`, `indigo-*`) are DEPRECATED in page and component code.** Use ONLY these semantic tokens:
 
 - Primary action: `bg-primary text-white hover:bg-primary-hover`
@@ -250,7 +250,7 @@ npm run dev           # Development server for browser validation
 
 ## Execution Rules
 - Frontend test path: `cd frontend && npm run test`
-- Docker logs for backend interaction: `docker compose -p ss-tools-current --env-file .env.current logs -f`
+- Docker logs for backend interaction: `docker compose -p superset-tools-current --env-file .env.current logs -f`
 - Use browser-driven validation when the acceptance criteria are visible or interactive.
 - Never bypass semantic or UX debt to make the UI appear working.
 - Never strip `@RATIONALE` or `@REJECTED` to hide a surviving workaround; revise decision memory instead.