@softspark/ai-toolkit 1.9.0 → 2.0.1

package/app/skills/mem-search/SKILL.md

@@ -15,7 +15,7 @@ $ARGUMENTS
 
 ## How It Works
 
-This skill queries the SQLite FTS5 full-text search index at `~/.ai-toolkit/memory.db` to find relevant observations from past sessions.
+This skill queries the SQLite FTS5 full-text search index at `~/.softspark/ai-toolkit/memory.db` to find relevant observations from past sessions.
 
 ## Instructions
 
@@ -23,12 +23,12 @@ This skill queries the SQLite FTS5 full-text search index at `~/.ai-toolkit/memo
 
 2. **Initialize the database** if it does not exist:
    ```bash
-   python3 "$HOME/.ai-toolkit/hooks/../plugins/memory-pack/scripts/init_db.py" 2>/dev/null || true
+   python3 "$HOME/.softspark/ai-toolkit/hooks/../plugins/memory-pack/scripts/init_db.py" 2>/dev/null || true
    ```
 
 3. **Run the FTS5 search** against the observations table:
    ```bash
-   sqlite3 ~/.ai-toolkit/memory.db "
+   sqlite3 ~/.softspark/ai-toolkit/memory.db "
      SELECT o.id, o.session_id, o.tool_name, o.content, o.created_at,
             s.project_dir, s.summary
      FROM observations_fts fts

package/app/skills/repeat/SKILL.md

@@ -77,7 +77,7 @@ After loop ends:
 
 ## Stats Logging
 
-Each iteration MUST be logged to `~/.ai-toolkit/stats.json`:
+Each iteration MUST be logged to `~/.softspark/ai-toolkit/stats.json`:
 
 ```json
 {

package/bin/ai-toolkit.js

@@ -62,8 +62,8 @@ const COMMANDS = {
   status: 'Show installed modules, version, and profile from state.json',
   reset: 'Wipe and recreate project-local configs from scratch (requires --local)',
   uninstall: 'Remove ai-toolkit from ~/.claude/',
-  'add-rule': 'Register a rule file in ~/.ai-toolkit/rules/ (applied on every install/update)',
-  'remove-rule': 'Unregister a rule from ~/.ai-toolkit/rules/ and remove its block from CLAUDE.md',
+  'add-rule': 'Register a rule file in ~/.softspark/ai-toolkit/rules/ (applied on every install/update)',
+  'remove-rule': 'Unregister a rule from ~/.softspark/ai-toolkit/rules/ and remove its block from CLAUDE.md',
   'inject-hook': 'Inject external hooks into ~/.claude/settings.json (tagged with _source for idempotent updates)',
   'remove-hook': 'Remove injected hooks by source name from ~/.claude/settings.json',
   validate: 'Verify toolkit integrity',
@@ -427,7 +427,12 @@ function handleStatus(_args) {
  */
 function handleUpdate(args) {
   const isLocal = args.includes('--local');
-  const statePath = path.join(process.env.HOME, '.ai-toolkit', 'state.json');
+  let statePath = path.join(process.env.HOME, '.softspark', 'ai-toolkit', 'state.json');
+  // Fallback to legacy path for first run after upgrade (before migration runs)
+  if (!fs.existsSync(statePath)) {
+    const legacyState = path.join(process.env.HOME, '.ai-toolkit', 'state.json');
+    if (fs.existsSync(legacyState)) statePath = legacyState;
+  }
   let stateArgs = [];
 
   if (fs.existsSync(statePath)) {
@@ -452,7 +457,7 @@ function handleUpdate(args) {
 
   // After global update (not --local), propagate to all registered projects
   if (!isLocal) {
-    const registryPath = path.join(process.env.HOME, '.ai-toolkit', 'projects.json');
+    const registryPath = path.join(process.env.HOME, '.softspark', 'ai-toolkit', 'projects.json');
     if (fs.existsSync(registryPath)) {
       try {
         const registry = JSON.parse(fs.readFileSync(registryPath, 'utf8'));

package/kb/history/completed/enterprise-config-inheritance-plan-20260412.md

@@ -53,10 +53,10 @@ Create a configuration inheritance system where projects can extend a shared bas
 | FR3 | Constitution immutability — Articles I-V cannot be modified | Must | 100% block rate on modification attempts |
 | FR4 | Override validation with `override: true` + `justification` | Must | Missing justification → error |
 | FR5 | `enforce` block constraints (minHookProfile, requiredPlugins, forbidOverride, requiredAgents) | Must | All 4 constraint types enforced |
-| FR6 | Install/update integration — resolve extends during install | Must | `install --local` detects `.ai-toolkit.json` |
+| FR6 | Install/update integration — resolve extends during install | Must | `install --local` detects `.softspark-toolkit.json` |
 | FR7 | `config diff` command — show project vs base differences | Must | All merge layers visible |
 | FR8 | `config validate` command — schema + enforcement validation | Must | Exit 0/1 for pass/fail |
-| FR9 | `config init` — interactive project config setup | Should | Guided flow produces valid `.ai-toolkit.json` |
+| FR9 | `config init` — interactive project config setup | Should | Guided flow produces valid `.softspark-toolkit.json` |
 | FR10 | `config create-base` — scaffold npm base config package | Should | Ready-to-publish package with `package.json` |
 | FR11 | Lock file for reproducible installs | Should | Identical resolved config across team members |
 | FR12 | Audit trail in `state.json` | Should | Resolved version + overrides recorded |
@@ -84,7 +84,7 @@ Project Level (per-repository):
 ══════════════════════════════
 
   my-service/
-  ├── .ai-toolkit.json             ← project config with "extends"
+  ├── .softspark-toolkit.json             ← project config with "extends"
   ├── .claude/
   │   ├── CLAUDE.md                ← generated (base + project merged)
   │   └── settings.json            ← generated (base hooks + project hooks merged)
@@ -99,7 +99,7 @@ Merge Pipeline:
   ai-toolkit defaults (manifest.json) ← Layer 1: toolkit defaults
           │
           ▼
-  .ai-toolkit.json                  ← Layer 2: project overrides
+  .softspark-toolkit.json                  ← Layer 2: project overrides
           │
           ▼
   Resolved Configuration             ← Final: CLAUDE.md, settings.json, etc.
@@ -110,7 +110,7 @@ Merge Pipeline:
 ```
 1. Load base config from "extends" (npm package, git URL, or local path)
 2. Merge with ai-toolkit defaults (manifest.json profiles)
-3. Apply project-level overrides from .ai-toolkit.json
+3. Apply project-level overrides from .softspark-toolkit.json
 4. Validate merged config (constitution immutability, schema validation)
 5. Generate output files (CLAUDE.md, settings.json, agent symlinks, etc.)
 ```
@@ -121,7 +121,7 @@ Merge Pipeline:
 
 | # | Feature | Priority | Status | Est. Time | Notes |
 |---|---------|----------|--------|-----------|-------|
-| 1.1 | `.ai-toolkit.json` schema definition | P0 | **Done** | 1d | `scripts/schemas/ai-toolkit-config.schema.json` |
+| 1.1 | `.softspark-toolkit.json` schema definition | P0 | **Done** | 1d | `scripts/schemas/ai-toolkit-config.schema.json` |
 | 1.2 | Config resolver (npm, git, local path) | P0 | **Done** | 3d | `scripts/config_resolver.py` (~330 LOC) |
 | 1.3 | Merge engine (layered merge with override semantics) | P0 | **Done** | 3d | `scripts/config_merger.py` (~340 LOC) |
 | 1.4 | Constitution immutability guard | P0 | **Done** | 1d | In config_merger.py `_merge_constitution()` |
@@ -130,8 +130,8 @@ Merge Pipeline:
 | 2.3 | `ai-toolkit config validate` command | P0 | **Done** | 1d | `scripts/config_cli.py` `cmd_validate()` |
 | 2.4 | `ai-toolkit config init` command | P1 | **Done** | 1.5d | Interactive + flag-driven, validates extends |
 | 2.5 | `ai-toolkit config create-base` command | P1 | **Done** | 2d | `scripts/config_scaffold.py` — full npm package scaffold |
-| 3.1 | Audit trail in state.json | P1 | **Done** | 1d | `install_state.py` extends field + `.ai-toolkit-extends.json` |
-| 3.2 | Lock file (`.ai-toolkit.lock.json`) | P1 | **Done** | 1.5d | `scripts/config_lock.py` — generate/consume/staleness check |
+| 3.1 | Audit trail in state.json | P1 | **Done** | 1d | `install_state.py` extends field + `.softspark-toolkit-extends.json` |
+| 3.2 | Lock file (`.softspark-toolkit.lock.json`) | P1 | **Done** | 1.5d | `scripts/config_lock.py` — generate/consume/staleness check |
 | 3.3 | Base config scaffolder (npm package template) | P1 | **Done** | 1.5d | Part of `config_scaffold.py` `create_base_package()` |
 | 3.4 | CI enforcement (`ai-toolkit config check`) | P2 | **Done** | 1d | `config_cli.py` `cmd_check()` — JSON output, exit codes |
 | 4.1 | Tests | P1 | **Done** | 3d | 39 tests: resolver (7), merger (13), CLI (10), install integration (9) |
@@ -189,7 +189,7 @@ Audit trail (3.1) ──┐
 
 ### Phase 1: Core Engine (week 1-2)
 
-#### 1.1 Configuration Schema (`.ai-toolkit.json`)
+#### 1.1 Configuration Schema (`.softspark-toolkit.json`)
 
 > **v1 scope:** The full schema below shows the target state. v1 implements only: `extends`, `profile`, `agents`, `rules`, `constitution`, and `enforce`. See section 6a for the v1/v2 field breakdown.
 
@@ -331,9 +331,9 @@ Audit trail (3.1) ──┐
 | Local path | `"extends": "../shared-config"` | Resolve relative to project root |
 | ~~Multiple bases~~ | ~~`"extends": ["@mycompany/base", "@mycompany/typescript-extra"]`~~ | Deferred to v2 — multi-base merge ordering is a complexity trap |
 
-**Cache directory:** `~/.ai-toolkit/config-cache/`
+**Cache directory:** `~/.softspark/ai-toolkit/config-cache/`
 ```
-~/.ai-toolkit/config-cache/
+~/.softspark/ai-toolkit/config-cache/
   @mycompany/
     ai-toolkit-config/
       2.1.0/
@@ -391,7 +391,7 @@ def resolve_extends(extends_value: str, project_root: str,
 **Max recursion depth:** 5 levels (prevent circular extends). Circular detection via visited set.
 
 **Offline handling:** If the npm/git source is unavailable:
-1. Check cache (`~/.ai-toolkit/config-cache/`)
+1. Check cache (`~/.softspark/ai-toolkit/config-cache/`)
 2. If cached version found → use with warning: "Using cached config v2.1.0 (offline)"
 3. If not cached → error with instructions: "Run `ai-toolkit config update` when online"
 
@@ -532,7 +532,7 @@ def merge_constitution(base: dict, project: dict) -> dict:
 
 ```python
 # During install --local:
-# 1. Check for .ai-toolkit.json in project root
+# 1. Check for .softspark-toolkit.json in project root
 # 2. If found and has "extends":
 #    a. Resolve base config(s)
 #    b. Merge base → project
@@ -543,7 +543,7 @@ def merge_constitution(base: dict, project: dict) -> dict:
 
 **CLI flags:**
 ```bash
-ai-toolkit install --local                           # auto-detect .ai-toolkit.json
+ai-toolkit install --local                           # auto-detect .softspark-toolkit.json
 ai-toolkit install --local --config ./custom.json    # explicit config file
 ai-toolkit update --local                            # re-resolve extends + update
 ai-toolkit update --local --refresh-base             # force re-fetch base config
@@ -591,7 +591,7 @@ ai-toolkit config diff
 ai-toolkit config validate
 
 # Checks:
-# ✓ .ai-toolkit.json schema valid
+# ✓ .softspark-toolkit.json schema valid
 # ✓ extends: @mycompany/ai-toolkit-config@2.1.0 resolved
 # ✓ No forbidden overrides
 # ✓ Required plugins installed: security-pack
@@ -616,12 +616,12 @@ ai-toolkit config init
 # Flow:
 # 1. "Does your organization have a shared ai-toolkit config? [y/n]"
 #    → y: "npm package name or git URL:" → resolves + validates
-#    → n: creates minimal .ai-toolkit.json without extends
+#    → n: creates minimal .softspark-toolkit.json without extends
 # 2. "Which profile? [minimal/standard/strict]" → default from base or standard
 # 3. "Which persona? [none/backend-lead/frontend-lead/devops-eng/junior-dev]"
 # 4. Auto-detect languages from project
 # 5. Auto-detect editors from project files
-# 6. Write .ai-toolkit.json
+# 6. Write .softspark-toolkit.json
 # 7. Run ai-toolkit install --local
 ```
 
@@ -685,7 +685,7 @@ ai-toolkit config create-base @mycompany/ai-toolkit-config
 
 ---
 
-#### 3.2 Lock File (`.ai-toolkit.lock.json`)
+#### 3.2 Lock File (`.softspark-toolkit.lock.json`)
 
 **Purpose:** Pin the exact resolved version of base configs for reproducible installs across team members and CI.
 
@@ -697,7 +697,7 @@ ai-toolkit config create-base @mycompany/ai-toolkit-config
       "version": "2.1.0",
       "resolved": "https://registry.npmjs.org/@mycompany/ai-toolkit-config/-/ai-toolkit-config-2.1.0.tgz",
       "integrity": "sha512-abc123...",
-      "cached": "~/.ai-toolkit/config-cache/@mycompany/ai-toolkit-config/2.1.0/"
+      "cached": "~/.softspark/ai-toolkit/config-cache/@mycompany/ai-toolkit-config/2.1.0/"
     }
   },
   "generated_at": "2026-04-10T10:30:00Z",
@@ -709,7 +709,7 @@ ai-toolkit config create-base @mycompany/ai-toolkit-config
 - `ai-toolkit install --local` → uses lock file if present (like `npm ci`)
 - `ai-toolkit update --local` → re-resolves and updates lock file (like `npm install`)
 - `ai-toolkit update --local --refresh-base` → force re-fetch ignoring cache
-- `.ai-toolkit.lock.json` should be committed to git (team synchronization)
+- `.softspark-toolkit.lock.json` should be committed to git (team synchronization)
 
 ---
 
@@ -723,7 +723,7 @@ ai-toolkit config check
 # Exit codes:
 # 0 — project complies with base config
 # 1 — violations found (missing required plugins, forbidden overrides, etc.)
-# 2 — .ai-toolkit.json not found
+# 2 — .softspark-toolkit.json not found
 ```
 
 **GitHub Actions example:**
@@ -796,7 +796,7 @@ v1 ships with a minimal schema. Each additional field adds merge logic, validati
 | **Offline** | Cached configs used when registry unavailable, with clear warning. |
 | **Security** | No secret exposure in config files or audit trail. npm auth via `.npmrc` (user-managed). `execFile` for npm CLI (no shell injection). |
 | **Error messages** | Every validation error includes: what failed, which config layer caused it, and what to do (e.g., "Contact your team lead to request an exemption"). |
-| **Backward compatibility** | 100% — projects without `.ai-toolkit.json` work exactly as today. Zero behavioral changes for existing users. |
+| **Backward compatibility** | 100% — projects without `.softspark-toolkit.json` work exactly as today. Zero behavioral changes for existing users. |
 | **Maintainability** | Each new schema field requires: merge logic, validation, diff output, test. Budget 0.5d per new field. |
 | **Quality gates** | `ruff check scripts/config_*.py` (0 errors), `mypy --strict scripts/config_*.py` (0 errors). Run before every commit. |
 | **Type safety** | 100% public API type hints (all function signatures). >60% internal. Use `TypedDict` for config schemas, `dataclass` for resolved configs. |
@@ -813,7 +813,7 @@ v1 ships with a minimal schema. Each additional field adds merge logic, validati
 | Constitution protection | 100% (Articles I-V immutable) |
 | Override justification | Required for all overrides |
 | Enforce constraints | 4 types (minHookProfile, requiredPlugins, forbidOverride, requiredAgents) |
-| Backward compatibility | 100% (projects without .ai-toolkit.json work as today) |
+| Backward compatibility | 100% (projects without .softspark-toolkit.json work as today) |
 | CI enforcement | Exit code 0/1 for governance compliance |
 | Lock file | Reproducible installs across team members |
 | Scaffold command | Ready-to-publish npm package template |
@@ -839,7 +839,7 @@ v1 ships with a minimal schema. Each additional field adds merge logic, validati
 
 ## 9. Pre-Mortem
 
-1. **"Config file fatigue"** — developers already have `.eslintrc`, `tsconfig.json`, `.prettierrc`. Another `.ai-toolkit.json` may feel like bloat. Mitigation: file is optional, all features work without it. The DX gain (organizational governance without per-repo updates) justifies the file.
+1. **"Config file fatigue"** — developers already have `.eslintrc`, `tsconfig.json`, `.prettierrc`. Another `.softspark-toolkit.json` may feel like bloat. Mitigation: file is optional, all features work without it. The DX gain (organizational governance without per-repo updates) justifies the file.
 2. **"Base config never gets updated"** — team lead creates base config, nobody maintains it. Mitigation: `ai-toolkit config check` in CI catches drift; lock file staleness warnings.
 3. **"Override justification is annoying"** — developers will write "needed" as justification. Mitigation: CI check can enforce minimum justification length (>20 chars); code review culture catches low-effort justifications.
 4. **"Merge semantics are confusing"** — "does project override or extend the base agent list?" Mitigation: explicit semantics documented in schema; `ai-toolkit config diff` shows exactly what happened.
@@ -865,7 +865,7 @@ v1 ships with a minimal schema. Each additional field adds merge logic, validati
 
 **MVP (ship first, ~3.5 weeks):**
 1. [x] Approve plan
-2. [x] Define `.ai-toolkit.json` JSON Schema — v1 scope only (1.1)
+2. [x] Define `.softspark-toolkit.json` JSON Schema — v1 scope only (1.1)
 3. [x] Implement config resolver (npm, git, local) with caching (1.2)
 4. [x] Implement merge engine with override validation (1.3)
 5. [x] Implement constitution immutability guard (1.4)
@@ -902,17 +902,15 @@ v1 ships with a minimal schema. Each additional field adds merge logic, validati
 
 ## 13. Cross-Plan Dependencies
 
-This plan shares modification targets with two other proposed plans:
+This plan shares modification targets with the Offline SLM plan:
 
-| Shared File | This Plan | Local Dashboard Plan | Offline SLM Plan |
-|-------------|-----------|---------------------|-----------------|
-| `scripts/install.py` | +80 LOC (extends resolution) | — | +30 LOC (offline-slm profile) |
-| `manifest.json` | +10 LOC (schema refs) | — | +5 LOC (offline-slm profile) |
-| `bin/ai-toolkit.js` | +40 LOC (config subcommands) | +15 LOC (ui command) | +10 LOC (compile-slm command) |
+| Shared File | This Plan | Offline SLM Plan |
+|-------------|-----------|-----------------|
+| `scripts/install.py` | +80 LOC (extends resolution) | +30 LOC (offline-slm profile) |
+| `manifest.json` | +10 LOC (schema refs) | +5 LOC (offline-slm profile) |
+| `bin/ai-toolkit.js` | +40 LOC (config subcommands) | +10 LOC (compile-slm command) |
 
-**If implementing in parallel:** coordinate merge order for shared files. Recommended sequence: Offline SLM (smallest changes) → Enterprise Config → Dashboard (no install.py changes).
-
-**Dashboard integration note:** If this plan ships before the Dashboard plan, the Dashboard's Config page (2.6) should display `.ai-toolkit.json` / `extends` status and the `config diff` output.
+**If implementing in parallel:** coordinate merge order for shared files. Recommended sequence: Offline SLM (smallest changes) → Enterprise Config.
 
 ---
 

package/kb/history/completed/offline-slm-profile-plan-20260411.md

@@ -88,8 +88,8 @@ ai-toolkit compile-slm [--budget 4096] [--persona backend-lead] [--lang typescri
   │    extended (16K) — near-full toolkit (for 32B+ models)   │
   │                                                          │
   │  Output Files:                                           │
-  │    ~/.ai-toolkit/compiled/slm-system-prompt.md           │
-  │    ~/.ai-toolkit/compiled/slm-skills-reference.md        │
+  │    ~/.softspark/ai-toolkit/compiled/slm-system-prompt.md           │
+  │    ~/.softspark/ai-toolkit/compiled/slm-skills-reference.md        │
   │    CLAUDE.md (or equivalent) — auto-generated            │
   │                                                          │
   │  Integration Targets:                                    │
@@ -429,7 +429,7 @@ ai-toolkit install --profile offline-slm
 # What happens:
 # 1. Standard install of core components
 # 2. Runs compile_slm.py with auto-detected settings
-# 3. Writes compiled output to ~/.ai-toolkit/compiled/
+# 3. Writes compiled output to ~/.softspark/ai-toolkit/compiled/
 # 4. Generates integration instructions for detected local model tools
 # 5. state.json records profile as "offline-slm"
 ```
@@ -532,7 +532,7 @@ ollama run my-coder "implement the payment API"
 ```
 1. ai-toolkit compile-slm --model-size 14b
 2. Open LM Studio → Chat → System Prompt
-3. Paste contents of ~/.ai-toolkit/compiled/slm-system-prompt.md
+3. Paste contents of ~/.softspark/ai-toolkit/compiled/slm-system-prompt.md
 ```
 
 **Aider:**
@@ -603,7 +603,7 @@ Post-compilation checks:
 
 ## 6b. Cache Invalidation & Recompile Triggers
 
-Compiled output (`~/.ai-toolkit/compiled/slm-system-prompt.md`) is a **derived artifact** — it must be recompiled when inputs change:
+Compiled output (`~/.softspark/ai-toolkit/compiled/slm-system-prompt.md`) is a **derived artifact** — it must be recompiled when inputs change:
 
 | Trigger | Action |
 |---------|--------|
@@ -622,7 +622,7 @@ The offline-slm feature is purely additive — removing it is trivial:
 1. Delete `scripts/compile_slm.py`, `scripts/slm_token_counter.py`, `scripts/slm_compression.py`, `scripts/slm_integration.py`
 2. Remove `"offline-slm"` and `"offline-slm-extended"` from `manifest.json` profiles
 3. Remove `compile-slm` from `SCRIPT_COMMANDS` in `bin/ai-toolkit.js`
-4. Delete `~/.ai-toolkit/compiled/` directory (user-side)
+4. Delete `~/.softspark/ai-toolkit/compiled/` directory (user-side)
 5. No hooks, no state files, no config entries to clean up
 
 ---
@@ -727,13 +727,13 @@ For teams needing enforcement, recommend `--profile offline-slm` combined with a
 
 ## 13. Cross-Plan Dependencies
 
-This plan shares modification targets with two other proposed plans:
+This plan shares modification targets with the Enterprise Config plan:
 
-| Shared File | This Plan | Enterprise Config Plan | Local Dashboard Plan |
-|-------------|-----------|----------------------|---------------------|
-| `scripts/install.py` | +30 LOC (offline-slm profile) | +80 LOC (extends resolution) | — |
-| `manifest.json` | +5 LOC (offline-slm profile) | +10 LOC (schema refs) | — |
-| `bin/ai-toolkit.js` | +10 LOC (compile-slm command) | +40 LOC (config subcommands) | +15 LOC (ui command) |
+| Shared File | This Plan | Enterprise Config Plan |
+|-------------|-----------|----------------------|
+| `scripts/install.py` | +30 LOC (offline-slm profile) | +80 LOC (extends resolution) |
+| `manifest.json` | +5 LOC (offline-slm profile) | +10 LOC (schema refs) |
+| `bin/ai-toolkit.js` | +10 LOC (compile-slm command) | +40 LOC (config subcommands) |
 
 **If implementing in parallel:** this plan has the smallest changes to shared files — merge first to minimize conflicts.
 

package/kb/planning/cloud-security-pack-plan.md

@@ -39,7 +39,7 @@ Create `cloud-security-pack` plugin pack that provides deterministic, read-only
 - **Deterministic** — reproducible results, no LLM-driven regex (same pattern as `hipaa_scan.py`)
 - **False positive aware** — context graph resolves "public endpoint behind gateway/App Check/WAF"
 - **CI-ready** — `--output json` + `--output sarif` (SARIF v2.1.0 for GitHub Advanced Security), exit code 1 on HIGH, 0 otherwise
-- **Credential isolation** — keys stored in `~/.ai-toolkit/credentials/`, accessible only by this pack's scripts
+- **Credential isolation** — keys stored in `~/.softspark/ai-toolkit/credentials/`, accessible only by this pack's scripts
 - **Static-first** — static mode (no credentials) is the default, live mode is opt-in upgrade
 - **Incremental** — `--changed` flag scans only files modified since last commit (PR workflow)
 - **IaC via `terraform show -json`** — wraps Terraform's own JSON output instead of parsing HCL directly
@@ -200,7 +200,7 @@ ai-toolkit credentials test aws
 
 **Storage structure:**
 ```
-~/.ai-toolkit/
+~/.softspark/ai-toolkit/
   credentials/
     gcp.json              # SA key file (copied, chmod 0600)
     gcp.meta.json         # { project_id, added_at, method: "file"|"gcloud" }
@@ -225,7 +225,7 @@ ai-toolkit credentials test aws
   - Connection works (GCP: `gcloud auth list`, AWS: `aws sts get-caller-identity`, Azure: `az account show`)
   - SA/role has **only read permissions** — **REFUSE to store** if write access detected (orchestration-review: warn-only is ignored by users). Override: `--force` flag with explicit acknowledgment
   - Project/subscription exists
-- `.gitignore`-proof — lives in `~/.ai-toolkit/`, never in project directory
+- `.gitignore`-proof — lives in `~/.softspark/ai-toolkit/`, never in project directory
 - Scripts access credentials via `gcp_auth.py` helper — single entry point, no direct file reads
 
 **Files to create/modify:**

package/kb/procedures/maintenance-sop.md

@@ -43,7 +43,7 @@ ai-toolkit install --local --lang python,typescript
 ai-toolkit install --local --lang python --editors all  # language rules propagated to all editors
 ```
 
-When `--editors` is combined with `--lang` (or auto-detected languages), language rules are propagated to all configured editors as `ai-toolkit-lang-<lang>` files — not just Claude's `CLAUDE.md`. Similarly, registered custom rules (`~/.ai-toolkit/rules/`) are propagated to directory-based editor configs as `ai-toolkit-custom-<name>` files.
+When `--editors` is combined with `--lang` (or auto-detected languages), language rules are propagated to all configured editors as `ai-toolkit-lang-<lang>` files — not just Claude's `CLAUDE.md`. Similarly, registered custom rules (`~/.softspark/ai-toolkit/rules/`) are propagated to directory-based editor configs as `ai-toolkit-custom-<name>` files.
 
 **Note:** Hooks are global-only — merged into `~/.claude/settings.json` by `ai-toolkit install`. Project-local `--local` does not install hooks; any legacy `.claude/hooks.json` is removed automatically.
 
@@ -121,7 +121,7 @@ Third-party repos (jira-mcp, rag-mcp, etc.) can register their own rules globall
 
 ```bash
 ai-toolkit add-rule ./my-project-rules.md
-# → copies to ~/.ai-toolkit/rules/my-project-rules.md
+# → copies to ~/.softspark/ai-toolkit/rules/my-project-rules.md
 
 ai-toolkit update
 # → injects the rule into ~/.claude/CLAUDE.md and all global editor configs
@@ -209,7 +209,7 @@ Install copies hooks/scripts, verifies agents+skills are linked, merges hooks in
 
 Memory-pack auto-prunes observations older than 90 days on every session end (configurable via `MEMORY_RETENTION_DAYS`).
 
-State tracked in `~/.ai-toolkit/plugins.json`.
+State tracked in `~/.softspark/ai-toolkit/plugins.json`.
 
 ## Adding a KB Document
 

package/kb/reference/architecture-overview.md

@@ -33,7 +33,7 @@ ai-toolkit/
     agents/                  # Agent definitions (.md + YAML frontmatter)
     skills/                  # skills: task, hybrid, knowledge
     rules/                   # Rules auto-injected into ~/.claude/CLAUDE.md
-    hooks/                   # Hook scripts (copied to ~/.ai-toolkit/hooks/)
+    hooks/                   # Hook scripts (copied to ~/.softspark/ai-toolkit/hooks/)
     hooks.json               # Hook definitions (merged into ~/.claude/settings.json)
     constitution.md          # Immutable safety rules, 5 articles (marker-injected)
     ARCHITECTURE.md          # System architecture reference (marker-injected)
@@ -80,7 +80,7 @@ All components use merge-friendly strategies — user content is never overwritt
 ```
 Machine (global)                              Project (local)
 ──────────────────────────────────────────    ──────────────────────────────────────
-~/.claude/                                    ~/.ai-toolkit/
+~/.claude/                                    ~/.softspark/ai-toolkit/
   agents/*.md    → per-file symlinks             rules/     ← registered rules
   skills/*/      → per-dir symlinks              hooks/     ← hook scripts (copied)
   settings.json  ← hooks merged here
@@ -120,8 +120,8 @@ Each editor gets directory-based format (`.cursor/rules/*.mdc`, `.windsurf/rules
 | `update` | `~/.claude/` | Re-apply after npm update or after add-rule/remove-rule |
 | `update --local` | `./` | Re-apply + refresh project-local configs |
 | `uninstall` | `~/.claude/` | Strips toolkit components (preserves user content) |
-| `add-rule <file>` | `~/.ai-toolkit/rules/` | Register rule — auto-applied on every `update` |
-| `remove-rule <name>` | `~/.ai-toolkit/rules/` + `~/.claude/CLAUDE.md` | Unregister rule and remove its block |
+| `add-rule <file>` | `~/.softspark/ai-toolkit/rules/` | Register rule — auto-applied on every `update` |
+| `remove-rule <name>` | `~/.softspark/ai-toolkit/rules/` + `~/.claude/CLAUDE.md` | Unregister rule and remove its block |
 | `validate` | toolkit | Integrity check |
 | `doctor` | toolkit | Install health, hooks, benchmark freshness, and artifact drift diagnostics |
 | `benchmark-ecosystem` | toolkit | Benchmark snapshot for official Claude Code and external ecosystem repos |
@@ -251,7 +251,7 @@ Agents (code-reviewer, debugger, devops-implementer, ...)
 | PreCompact | Before compaction | `pre-compact-save.sh` | Timestamped context snapshot to audit trail |
 | SessionEnd | Session end | `session-end.sh` | Persist handoff note for the next session |
 
-Scripts at `~/.ai-toolkit/hooks/`. See [hooks-catalog.md](hooks-catalog.md) for details.
+Scripts at `~/.softspark/ai-toolkit/hooks/`. See [hooks-catalog.md](hooks-catalog.md) for details.
 
 ## Constitution (5 Articles)
 

package/kb/reference/benchmark-config.md

@@ -57,6 +57,6 @@ affaan-m/everything-claude-code             152     397      2
 
 ## Data Sources
 
-- User config: `~/.claude/agents/`, `~/.claude/skills/`, `~/.ai-toolkit/hooks/`
+- User config: `~/.claude/agents/`, `~/.claude/skills/`, `~/.softspark/ai-toolkit/hooks/`
 - Toolkit: `app/agents/`, `app/skills/`, `app/hooks/`
 - Ecosystem: `benchmarks/ecosystem-dashboard.json`

package/kb/reference/competitive-features-implementation.md

@@ -347,7 +347,7 @@ All entries are tagged with "_source": "<source-name>" for idempotent updates.
 | `remove-rule <name>` | `~/.claude/CLAUDE.md` | Strip markers | Yes |
 | `inject-hook <file.json>` | `~/.claude/settings.json` | JSON `_source` tag | Yes |
 | `remove-hook <name>` | `~/.claude/settings.json` | Strip by `_source` | Yes |
-| `add-rule <file.md>` | `~/.ai-toolkit/rules/` | File copy + re-inject all | Yes |
+| `add-rule <file.md>` | `~/.softspark/ai-toolkit/rules/` | File copy + re-inject all | Yes |
 
 **Success Criteria:**
 - [x] `inject-hook ./my-hooks.json` merges hooks with auto-derived `_source` tag
@@ -426,7 +426,7 @@ All entries are tagged with "_source": "<source-name>" for idempotent updates.
 }
 ```
 
-**State tracking (~/.ai-toolkit/state.json):**
+**State tracking (~/.softspark/ai-toolkit/state.json):**
 ```json
 {
   "installed_version": "1.2.1",

package/kb/reference/enterprise-config-guide.md

@@ -18,7 +18,7 @@ description: "Comprehensive guide for setting up and using ai-toolkit configurat
 
 ## Overview
 
-Configuration inheritance enables organizations to define a shared base config published as an npm package, Git URL, or local path. Individual projects extend this base via an `extends` field in `.ai-toolkit.json`. Changes to the base propagate automatically on `ai-toolkit update --local`.
+Configuration inheritance enables organizations to define a shared base config published as an npm package, Git URL, or local path. Individual projects extend this base via an `extends` field in `.softspark-toolkit.json`. Changes to the base propagate automatically on `ai-toolkit update --local`.
 
 **Pattern:** Mirrors ESLint's `extends`, TypeScript's `extends`, and Prettier's shared configs.
 
@@ -47,7 +47,7 @@ ai-toolkit config init --extends @mycompany/ai-toolkit-config
 ai-toolkit install --local
 ```
 
-Or manually create `.ai-toolkit.json`:
+Or manually create `.softspark-toolkit.json`:
 
 ```json
 {
@@ -71,7 +71,7 @@ ai-toolkit config check       # CI enforcement check
 
 ## Configuration Reference
 
-### Project config (`.ai-toolkit.json`)
+### Project config (`.softspark-toolkit.json`)
 
 | Field | Type | Description |
 |-------|------|-------------|
@@ -195,7 +195,7 @@ Requirements:
 
 ### `ai-toolkit config validate [path]`
 
-Validates `.ai-toolkit.json` schema, resolves extends, checks enforcement.
+Validates `.softspark-toolkit.json` schema, resolves extends, checks enforcement.
 
 ```bash
 ai-toolkit config validate
@@ -220,7 +220,7 @@ ai-toolkit config diff
 
 ### `ai-toolkit config init [flags]`
 
-Create `.ai-toolkit.json` interactively or with flags.
+Create `.softspark-toolkit.json` interactively or with flags.
 
 ```bash
 ai-toolkit config init                                    # interactive
@@ -261,12 +261,12 @@ GitHub Actions example:
 
 ## Lock File
 
-`.ai-toolkit.lock.json` pins exact resolved versions for reproducible installs.
+`.softspark-toolkit.lock.json` pins exact resolved versions for reproducible installs.
 
 - `install --local` → creates/updates lock file
 - `update --local` → re-resolves and updates lock file
 - `update --local --refresh-base` → force re-fetch ignoring cache
-- Commit `.ai-toolkit.lock.json` to git for team synchronization
+- Commit `.softspark-toolkit.lock.json` to git for team synchronization
 
 ```json
 {
@@ -275,7 +275,7 @@ GitHub Actions example:
     "@mycompany/ai-toolkit-config": {
       "version": "2.1.0",
       "integrity": "sha256:abc123...",
-      "cached": "~/.ai-toolkit/config-cache/@mycompany/ai-toolkit-config/2.1.0/"
+      "cached": "~/.softspark/ai-toolkit/config-cache/@mycompany/ai-toolkit-config/2.1.0/"
     }
   }
 }
@@ -287,7 +287,7 @@ GitHub Actions example:
 
 When npm/git is unavailable:
 
-1. Checks cache (`~/.ai-toolkit/config-cache/`)
+1. Checks cache (`~/.softspark/ai-toolkit/config-cache/`)
 2. If cached version found → uses with warning
 3. If not cached → error with instructions
 

package/kb/reference/extension-api.md

@@ -25,7 +25,7 @@ This design is intentional: ai-toolkit is a generic toolkit. Consumers (MCP serv
 | `remove-rule <name>` | `~/.claude/CLAUDE.md` | Strip markers by block name | Yes |
 | `inject-hook <file.json>` | `~/.claude/settings.json` | JSON `_source` tag per entry | Yes |
 | `remove-hook <name>` | `~/.claude/settings.json` | Strip all entries with matching `_source` | Yes |
-| `add-rule <file.md>` | `~/.ai-toolkit/rules/` | File copy + re-inject all rules on next `update` | Yes |
+| `add-rule <file.md>` | `~/.softspark/ai-toolkit/rules/` | File copy + re-inject all rules on next `update` | Yes |
 | `mcp add <name...>` | `.mcp.json` | Merge `mcpServers` block from template | Yes |
 
 ## inject-rule

package/kb/reference/global-install-model.md

@@ -27,8 +27,8 @@ That means one machine-level install provides agents, skills, hooks, and rules t
 | `ai-toolkit install --local --lang <lang>` | current project | explicit language selection for rules (e.g. `--lang typescript`, `--lang go,python`); auto-detected when omitted |
 | `ai-toolkit install --modules <list>` | `~/.claude/` | selective module install (e.g. `--modules core,agents,rules-typescript`) |
 | `ai-toolkit update --local` | current project | refresh project configs; auto-detects editors from existing files |
-| `ai-toolkit add-rule` | `~/.ai-toolkit/rules/` | register a global rule |
-| `ai-toolkit remove-rule` | `~/.ai-toolkit/rules/` | unregister a global rule |
+| `ai-toolkit add-rule` | `~/.softspark/ai-toolkit/rules/` | register a global rule |
+| `ai-toolkit remove-rule` | `~/.softspark/ai-toolkit/rules/` | unregister a global rule |
 
 ## Why global install is the default