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/command/read_semantics.md

@@ -1,4 +1,4 @@
 ---
-description: Load semantic protocol context for ss-tools
+description: Load semantic protocol context for superset-tools
 ---
 MANDATORY USE `skill({name="semantics-core"})`, `skill({name="semantics-contracts"})`, `skill({name="molecular-cot-logging"})`, `skill({name="semantics-python"})`, `skill({name="semantics-svelte"})`

.opencode/command/speckit.analyze.md

@@ -1,5 +1,5 @@
 ---
-description: Perform a read-only consistency analysis across spec.md, plan.md, tasks.md, contracts/modules.md, and ADR sources for the active ss-tools feature. Covers UX Contract Traceability, ATTN Rules Compliance, and decision-memory continuity.
+description: Perform a read-only consistency analysis across spec.md, plan.md, tasks.md, contracts/modules.md, and ADR sources for the active superset-tools feature. Covers UX Contract Traceability, ATTN Rules Compliance, and decision-memory continuity.
 ---
 
 ## User Input

.opencode/command/speckit.constitution.md

@@ -1,5 +1,5 @@
 ---
-description: Create or update the local workflow constitution and propagate principle changes into dependent speckit artifacts for ss-tools.
+description: Create or update the local workflow constitution and propagate principle changes into dependent speckit artifacts for superset-tools.
 handoffs:
   - label: Build Specification
     agent: speckit.specify
@@ -30,7 +30,7 @@ You are updating the local constitution at `.specify/memory/constitution.md`. Th
 Execution flow:
 
 1. Load the existing constitution at `.specify/memory/constitution.md`.
-2. Identify placeholders, stale assumptions, or principles that conflict with the current ss-tools repository (Python/Svelte, not Rust/MCP).
+2. Identify placeholders, stale assumptions, or principles that conflict with the current superset-tools repository (Python/Svelte, not Rust/MCP).
 3. Derive concrete constitutional text from user input and repository reality.
 4. Version the constitution using semantic versioning:
    - MAJOR: incompatible governance/principle change

.opencode/command/speckit.implement.md

@@ -1,5 +1,5 @@
 ---
-description: Execute the implementation plan by processing the active tasks.md for the ss-tools repository (Python backend + Svelte frontend).
+description: Execute the implementation plan by processing the active tasks.md for the superset-tools repository (Python backend + Svelte frontend).
 handoffs:
   - label: Audit & Verify (Tester)
     agent: qa-tester

.opencode/command/speckit.plan.md

@@ -1,5 +1,5 @@
 ---
-description: Execute the implementation planning workflow for ss-tools (Python backend + Svelte frontend) and generate research, design, contracts, and quickstart artifacts.
+description: Execute the implementation planning workflow for superset-tools (Python backend + Svelte frontend) and generate research, design, contracts, and quickstart artifacts.
 handoffs:
   - label: Create Tasks
     agent: speckit.tasks
@@ -143,7 +143,7 @@ Every contract in `contracts/modules.md` MUST pass these checks. Contracts that
 
 ### Data Model Output
 
-Generate `data-model.md` for ss-tools domain entities such as:
+Generate `data-model.md` for superset-tools domain entities such as:
 - Pydantic request/response schemas
 - SQLAlchemy models and relationships
 - WebSocket message formats

.opencode/command/speckit.semantics.md

@@ -1,5 +1,5 @@
 ---
-description: Maintain semantic integrity by reindexing, auditing, and reviewing the ss-tools repository through AXIOM MCP tools.
+description: Maintain semantic integrity by reindexing, auditing, and reviewing the superset-tools repository through AXIOM MCP tools.
 ---
 
 ## User Input

.opencode/command/speckit.specify.md

@@ -1,5 +1,5 @@
 ---
-description: Create or update the feature specification from a natural-language feature description for the ss-tools project (Python backend + Svelte frontend).
+description: Create or update the feature specification from a natural-language feature description for the superset-tools project (Python backend + Svelte frontend).
 handoffs:
   - label: Build Technical Plan
     agent: speckit.plan
@@ -63,7 +63,7 @@ The feature description is the text passed to `/speckit.specify`.
 
 Generate `FEATURE_DIR/checklists/requirements.md` and ensure it validates:
 - no implementation leakage into `spec.md`
-- compatibility with the Python/Svelte ss-tools stack
+- compatibility with the Python/Svelte superset-tools stack
 - measurable success criteria
 - explicit edge cases and recovery paths
 - decision-memory readiness for downstream planning

.opencode/command/speckit.tasks.md

@@ -1,5 +1,5 @@
 ---
-description: Generate an actionable, dependency-ordered tasks.md for the active ss-tools feature (Python backend + Svelte frontend).
+description: Generate an actionable, dependency-ordered tasks.md for the active superset-tools feature (Python backend + Svelte frontend).
 handoffs:
   - label: Analyze For Consistency
     agent: speckit.analyze
@@ -73,7 +73,7 @@ Rules:
 4. `[USx]` required only for user-story phases
 5. exact file paths required in the description
 
-### ss-tools Pathing
+### superset-tools Pathing
 
 Prefer real repository paths such as:
 - `backend/src/api/*.py` (FastAPI routes)

.opencode/command/speckit.test.md

@@ -1,5 +1,5 @@
 ---
-description: Execute mocking discipline audit, semantic verification, and native testing for the active ss-tools feature batch (pytest + vitest). Read-only audit first, then auto-fix violations.
+description: Execute mocking discipline audit, semantic verification, and native testing for the active superset-tools feature batch (pytest + vitest). Read-only audit first, then auto-fix violations.
 handoffs:
   - label: Orchestration Control
     agent: swarm-master
@@ -17,7 +17,7 @@ You **MUST** consider the user input before proceeding (if not empty). User may
 
 ## Goal
 
-Run the full verification loop for the touched ss-tools scope:
+Run the full verification loop for the touched superset-tools scope:
 1. **Mocking discipline audit** — scan every test file in scope, classify every mock/spy/stub/patch, flag violations
 2. **Auto-fix violations** — correct SUT mocks and Logic Mirrors (no flag needed; fix by default)
 3. **Semantic audit** — contract density, belief runtime, rejected-path regression