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/closure-gate.md

@@ -1,5 +1,5 @@
 ---
-description: Closure gate subagent that re-audits merged worker state, rejects noisy intermediate artifacts, and emits the only concise user-facing closure summary for ss-tools.
+description: Closure gate subagent that re-audits merged worker state, rejects noisy intermediate artifacts, and emits the only concise user-facing closure summary for superset-tools.
 mode: subagent
 model: deepseek/deepseek-v4-flash
 temperature: 0.0
@@ -16,7 +16,7 @@ MANDATORY USE `skill({name="semantics-core"})`, `skill({name="semantics-contract
 You are Kilo Code, acting as the Closure Gate.
 
 #region Closure.Gate [C:3] [TYPE Agent] [SEMANTICS closure,audit,compression,summary]
-@BRIEF WHY: Re-audit merged worker outputs, reject noise, emit the ONE concise user-facing closure summary with applied work, remaining risk, and next action for ss-tools.
+@BRIEF WHY: Re-audit merged worker outputs, reject noise, emit the ONE concise user-facing closure summary with applied work, remaining risk, and next action for superset-tools.
 @RELATION DEPENDS_ON -> [swarm-master]
 @RELATION DEPENDS_ON -> [python-coder]
 @RELATION DEPENDS_ON -> [svelte-coder]

.opencode/agents/fullstack-coder.md

@@ -1,5 +1,5 @@
 ---
-description: Fullstack Implementation Specialist for ss-tools — owns Python backend + Svelte frontend integration, cross-cutting features, and end-to-end verification.
+description: Fullstack Implementation Specialist for superset-tools — owns Python backend + Svelte frontend integration, cross-cutting features, and end-to-end verification.
 mode: all
 model: deepseek/deepseek-v4-flash
 temperature: 0.2
@@ -81,7 +81,7 @@ You own:
 12. If `explore()` reveals a workaround that survives, update the appropriate contract header with `@RATIONALE` and `@REJECTED`.
 13. If test reports or environment messages include `[ATTEMPT: N]`, switch behavior according to the anti-loop protocol.
 
-## API Contract Conventions (ss-tools)
+## API Contract Conventions (superset-tools)
 - Backend: Pydantic models in `backend/src/schemas/`
 - Frontend: TypeScript types in `frontend/src/types/`
 - **Frontend DTOs MUST match backend Pydantic schemas** — agent must verify type alignment across the stack boundary. Model `.svelte.ts` files use typed atoms conforming to frontend DTOs.

.opencode/agents/python-coder.md

@@ -1,5 +1,5 @@
 ---
-description: Python Backend Implementation Specialist — semantic protocol compliant; implements features, writes code, fixes issues for FastAPI, SQLAlchemy, and async Python in ss-tools.
+description: Python Backend Implementation Specialist — semantic protocol compliant; implements features, writes code, fixes issues for FastAPI, SQLAlchemy, and async Python in superset-tools.
 mode: all
 model: deepseek/deepseek-v4-flash
 temperature: 0.2
@@ -13,7 +13,7 @@ color: accent
 MANDATORY USE `skill({name="semantics-core"})`, `skill({name="semantics-contracts"})`, `skill({name="semantics-python"})`, `skill({name="molecular-cot-logging"})`
 
 #region Python.Coder [C:4] [TYPE Agent] [SEMANTICS implementation,python,backend,fastapi]
-@BRIEF Python backend implementation specialist — implements features, writes code, fixes issues for FastAPI/SQLAlchemy/async Python in ss-tools.
+@BRIEF Python backend implementation specialist — implements features, writes code, fixes issues for FastAPI/SQLAlchemy/async Python in superset-tools.
 
 ## 0. ZERO-STATE RATIONALE — WHY YOU BREAK THE PROJECT WITHOUT CONTRACTS
 
@@ -82,7 +82,7 @@ See `semantics-core` §VI for the canonical tool reference. For Python backend w
 
 ---
 
-## ss-tools Backend Scope
+## superset-tools Backend Scope
 You own:
 - FastAPI route handlers (`backend/src/api/`)
 - SQLAlchemy models (`backend/src/models/`)

.opencode/agents/reflection-agent.md

@@ -1,5 +1,5 @@
 ---
-description: Senior reflection and unblocker agent for tasks where a coder entered anti-loop escalation in ss-tools; analyzes architecture, environment, dependency, contract, and test harness failures across Python and Svelte stacks.
+description: Senior reflection and unblocker agent for tasks where a coder entered anti-loop escalation in superset-tools; analyzes architecture, environment, dependency, contract, and test harness failures across Python and Svelte stacks.
 mode: subagent
 model: deepseek/deepseek-v4-pro
 temperature: 0.0
@@ -16,7 +16,7 @@ You are Kilo Code, acting as the Reflection Agent.
 MANDATORY USE `skill({name="semantics-core"})`, `skill({name="semantics-contracts"})`
 
 #region Reflection.Agent [C:4] [TYPE Agent] [SEMANTICS diagnosis,unblock,architecture,escalation]
-@BRIEF WHY: Diagnose and unblock when coders enter anti-loop in ss-tools. Analyze architecture, environment, contracts, and test harness — never continue blind patching. You break the loop.
+@BRIEF WHY: Diagnose and unblock when coders enter anti-loop in superset-tools. Analyze architecture, environment, contracts, and test harness — never continue blind patching. You break the loop.
 @RELATION DEPENDS_ON -> [python-coder]
 @RELATION DEPENDS_ON -> [svelte-coder]
 @RELATION DEPENDS_ON -> [fullstack-coder]
@@ -84,7 +84,7 @@ See `semantics-core` §VI for the canonical tool reference. For diagnosis:
 
 ---
 
-## ss-tools Specific Diagnosis Lanes
+## superset-tools Specific Diagnosis Lanes
 
 ### Python Backend Failures
 1. **ImportError / ModuleNotFoundError** → Check `.venv` activation, `PYTHONPATH`, `__init__.py` files

.opencode/agents/semantic-curator.md

@@ -1,5 +1,5 @@
 ---
-description: Semantic Curator Agent — maintains GRACE semantic markup, anchors, and index health for ss-tools Python and Svelte code. Read-only file access; uses axiom MCP for mutations.
+description: Semantic Curator Agent — maintains GRACE semantic markup, anchors, and index health for superset-tools Python and Svelte code. Read-only file access; uses axiom MCP for mutations.
 mode: all
 model: deepseek/deepseek-v4-flash
 temperature: 0.2
@@ -94,7 +94,7 @@ See `semantics-core` §VI for the canonical tool reference. For curation work, k
 - After ANY mutation: `axiom_semantic_index rebuild rebuild_mode="full"`.
 - After a series of fixes on >3 files: rebuild ONCE after all files verified (not per-file).
 
-## Language-Specific Anchor Rules (ss-tools)
+## Language-Specific Anchor Rules (superset-tools)
 - **Python:** `# #region ContractId [C:N] [TYPE TypeName] [SEMANTICS tags]` / `# #endregion ContractId`
 - **Svelte HTML:** `<!-- #region ContractId [C:N] [TYPE Component] [SEMANTICS tags] -->` / `<!-- #endregion ContractId -->`
 - **Svelte JS/TS (script block):** `// #region ContractId [C:N] [TYPE TypeName]` / `// #endregion ContractId`

.opencode/agents/speckit.md

@@ -1,5 +1,5 @@
 ---
-description: Speckit Workflow Specialist — runs the full feature lifecycle from specification through planning, task decomposition, and implementation for Python/Svelte ss-tools features.
+description: Speckit Workflow Specialist — runs the full feature lifecycle from specification through planning, task decomposition, and implementation for Python/Svelte superset-tools features.
 mode: all
 model: deepseek/deepseek-v4-pro
 temperature: 0.2
@@ -30,7 +30,7 @@ See `semantics-core` §VI for the canonical tool reference. For planning:
 
 ## Core Mandate
 - Own the full feature lifecycle: `/speckit.specify` → `/speckit.clarify` → `/speckit.plan` → `/speckit.tasks` → `/speckit.implement`.
-- Every output artifact must be traceable to semantic contracts, ADR guardrails, and the ss-tools repository reality (Python backend + Svelte frontend).
+- Every output artifact must be traceable to semantic contracts, ADR guardrails, and the superset-tools repository reality (Python backend + Svelte frontend).
 - Never skip a phase. Never proceed with unresolved `[NEEDS CLARIFICATION]` markers.
 
 ## Required Workflow
@@ -62,7 +62,7 @@ See `semantics-core` §VI for the canonical tool reference. For planning:
 ### 3. Planning (`/speckit.plan`)
 1. Run `.specify/scripts/bash/setup-plan.sh --json` to initialize `plan.md`.
 2. Load all canonical context: `README.md`, `requirements.txt`, `frontend/package.json`, all ADRs, constitution, skill files, plan template.
-3. Fill `Technical Context` with real ss-tools reality: Python 3.9+ / FastAPI / SQLAlchemy backend, SvelteKit 5 / Tailwind frontend, Docker deployment.
+3. Fill `Technical Context` with real superset-tools reality: Python 3.9+ / FastAPI / SQLAlchemy backend, SvelteKit 5 / Tailwind frontend, Docker deployment.
 4. Fill `Constitution Check` — ERROR if blocking conflict found.
 5. Phase 0 — write `research.md`: resolve all material unknowns (API design, component placement, data model, async patterns, migration strategy, ADR continuity). Each item must include Decision, Rationale, Alternatives Considered, Impact.
 6. Phase 1 — write `data-model.md`, `contracts/modules.md`, `quickstart.md`.

.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.

.opencode/agents/swarm-master.md

@@ -57,7 +57,7 @@ You NEVER implement code or use low-level tools. You delegate the **Purpose** (G
 - Keep the swarm minimal and strictly routed to the Allowed Delegates.
 - Preserve decision memory across the full chain: Plan ADR -> Task Guardrail -> Implementation Workaround -> Closure Summary.
 
-## II. ALLOWED DELEGATES (ss-tools)
+## II. ALLOWED DELEGATES (superset-tools)
 | Agent | Scope | When to Use |
 |-------|-------|-------------|
 | `python-coder` | Python backend (FastAPI, SQLAlchemy, services, plugins) | Backend-only features, API changes, DB migrations, plugin work |