@squadrules/mcp 4.8.6 → 5.0.0

package/dist/embed-docs/mem/adapter-migration.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: adapter-migration
 title: Adapter Migration Protocol
 ---
@@ -12,7 +12,7 @@ per adapter, and re-trains only after user approval.
 
 This protocol handles structural migrations only — it preserves semantic content
 (steps, intent, examples) while updating format, headings, and contract shapes
-to match the latest KAIROS requirements.
+to match the latest SQUADRULES requirements.
 
 ## Activation Patterns
 

package/dist/embed-docs/mem/bulk-insert-adapters-via-cli.md

@@ -1,15 +1,15 @@
 ---
 slug: bulk-insert-adapters-via-cli
-version: "4.8.6"
-title: Bulk Insert Adapters via KAIROS CLI
+version: "5.0.0"
+title: Bulk Insert Adapters via SQUADRULES CLI
 ---
 
-# Bulk Insert Adapters via KAIROS CLI
+# Bulk Insert Adapters via SQUADRULES CLI
 
 ## Activation Patterns
 
-Batch-register multiple KAIROS adapters from a local directory tree using the
-`kairos train` CLI. Handles directory scanning, validation, space targeting,
+Batch-register multiple SQUADRULES adapters from a local directory tree using the
+`squadrules train` CLI. Handles directory scanning, validation, space targeting,
 and error recovery for bulk operations.
 
 **Run this protocol when the user says ANY of:**
@@ -17,8 +17,8 @@ and error recovery for bulk operations.
 - "bulk insert adapters" / "bulk train adapters"
 - "train all protocols in a directory"
 - "batch register adapters from folder"
-- "upload all .md files to KAIROS"
-- "sync local protocols to KAIROS" / "push protocols to KAIROS"
+- "upload all .md files to SQUADRULES"
+- "sync local protocols to SQUADRULES" / "push protocols to SQUADRULES"
 - "train directory recursively" / "train --recursive"
 
 **Trigger pattern:** **bulk** / **batch** / **all** / **directory** / **recursive** +
@@ -40,29 +40,29 @@ and error recovery for bulk operations.
 
 **Good trigger examples:**
 
-- "Train all adapters in kairos-v4/_personal/" → run this protocol
+- "Train all adapters in squadrules-v4/_personal/" → run this protocol
 - "Bulk insert the protocols from my export folder" → run this protocol
 - "Push all .md files in this directory to my personal space" → run this protocol
 
 **Bad trigger examples:**
 
-- "Train this one protocol" → use `kairos train <file>` directly
+- "Train this one protocol" → use `squadrules train <file>` directly
 - "Create a new protocol" → use `create-new-protocol`
-- "Export my adapters" → use `kairos export`
+- "Export my adapters" → use `squadrules export`
 
 ## Preflight Dependencies
 
 Verify before execution:
 
-1. `kairos` CLI is installed and callable (`kairos --version`).
-2. Authentication is valid (`kairos token` returns a token without error).
+1. `squadrules` CLI is installed and callable (`squadrules --version`).
+2. Authentication is valid (`squadrules token` returns a token without error).
 3. Target directory path exists and contains at least one `.md` file.
-4. If a space is specified, confirm it exists via `kairos spaces`.
+4. If a space is specified, confirm it exists via `squadrules spaces`.
 
 If any check fails, stop and report the issue with remediation guidance.
 
 ```json
-{"contract":{"type":"shell","shell":{"cmd":"kairos --version && kairos token > /dev/null 2>&1 && echo 'auth: ok'","timeout_seconds":15},"required":true}}
+{"contract":{"type":"shell","shell":{"cmd":"squadrules --version && squadrules token > /dev/null 2>&1 && echo 'auth: ok'","timeout_seconds":15},"required":true}}
 ```
 
 ## Confirm Scope
@@ -83,7 +83,7 @@ List the files that will be trained and ask for confirmation.
 
 ## Validate Structure
 
-Before training, validate each `.md` file against KAIROS adapter requirements:
+Before training, validate each `.md` file against SQUADRULES adapter requirements:
 
 - Has an H1 title.
 - First H2 is "Activation Patterns".
@@ -101,10 +101,10 @@ Report any files that fail validation. Ask user whether to:
 
 ## Execute Bulk Train
 
-Run the batch train operation using the KAIROS CLI:
+Run the batch train operation using the SQUADRULES CLI:
 
 ```
-kairos train <directory> --recursive --model <model> --space <space> [--force]
+squadrules train <directory> --recursive --model <model> --space <space> [--force]
 ```
 
 If the directory contains files that should NOT be trained (README, reference
@@ -115,7 +115,7 @@ docs), either:
 Capture stdout and stderr. The CLI reports per-file status.
 
 ```json
-{"contract":{"type":"shell","shell":{"cmd":"kairos train <directory> --recursive --model <model_id> --space <space>","timeout_seconds":120},"required":true}}
+{"contract":{"type":"shell","shell":{"cmd":"squadrules train <directory> --recursive --model <model_id> --space <space>","timeout_seconds":120},"required":true}}
 ```
 
 ## Report Results
@@ -134,7 +134,7 @@ For each failure, report:
 - Error message
 - Suggested fix
 
-If all succeeded, confirm adapter URIs are accessible via `kairos spaces`.
+If all succeeded, confirm adapter URIs are accessible via `squadrules spaces`.
 
 ```json
 {"contract":{"type":"comment","comment":{"min_length":80},"required":true}}
@@ -149,4 +149,4 @@ Protocol complete when:
 - Any failures have been documented with remediation guidance.
 
 A successful bulk insert means the user's local protocol library is now
-registered in KAIROS and available for activation by AI agents.
+registered in SQUADRULES and available for activation by AI agents.

package/dist/embed-docs/mem/challenge-type-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: challenge-type-guide
 title: Challenge Type Selection Guide
 ---
@@ -9,7 +9,7 @@ title: Challenge Type Selection Guide
 # Challenge Type Selection Guide
 
 Decision rules, JSON formats, interpreter selection, and anti-patterns for
-choosing KAIROS challenge types. Loaded by protocol-authoring agents during
+choosing SQUADRULES challenge types. Loaded by protocol-authoring agents during
 drafting and review.
 
 ## Activation Patterns
@@ -49,7 +49,7 @@ code — use `shell` or `mcp` instead.
 
 **Mode before challenge type:**
 - **clarify / approve** → `user_input`
-- **call a KAIROS / MCP tool** → `mcp`
+- **call a SQUADRULES / MCP tool** → `mcp`
 - **execute or verify local state** → `shell`
 - **pure reasoning with no observable artifact** → `comment`
 
@@ -81,7 +81,7 @@ Does the step call an MCP tool?
 
 **mcp with arguments (chain link)**
 ```json
-{"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"kairos://adapter/<slug>"}},"required":true}}
+{"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"squadrules://adapter/<slug>"}},"required":true}}
 ```
 
 Use the `arguments` form when the step's purpose is to invoke a specific
@@ -190,7 +190,7 @@ escaping, rewrite in Perl. If you need imports for data formats, use Python.
 
 ## Security and Working Directory Rules
 
-Use `$KAIROS_LOCAL_ARTIFACT_DIR` as the base directory for local handoff
+Use `$SQUADRULES_LOCAL_ARTIFACT_DIR` as the base directory for local handoff
 artifacts. File paths within it are provided as variables by the invoking agent
 to avoid collisions between parallel sessions.
 
@@ -198,10 +198,10 @@ to avoid collisions between parallel sessions.
 - all file paths in shell challenges reference variables (e.g., `$DRAFT_FILE`,
   `$VERDICT_FILE`) set by the parent agent — never hardcode filenames
 - the parent agent constructs collision-free paths under
-  `$KAIROS_LOCAL_ARTIFACT_DIR` (e.g., with a session ID or random suffix)
-- when using KAIROS MCP, the latest `activate` / `forward` / `next` response field `kairos_local_artifact_dir` is an ordered array of URI hints (`project://<rel>`, `user://<rel>`); pick one (`project://` when you have exactly one project context, otherwise `user://`), resolve on your machine, and `export KAIROS_LOCAL_ARTIFACT_DIR="<absolute>"` if your shell does not already define it
+  `$SQUADRULES_LOCAL_ARTIFACT_DIR` (e.g., with a session ID or random suffix)
+- when using SQUADRULES MCP, the latest `activate` / `forward` / `next` response field `squadrules_local_artifact_dir` is an ordered array of URI hints (`project://<rel>`, `user://<rel>`); pick one (`project://` when you have exactly one project context, otherwise `user://`), resolve on your machine, and `export SQUADRULES_LOCAL_ARTIFACT_DIR="<absolute>"` if your shell does not already define it
 - if the server-returned path is not usable on your local filesystem, resolve
-  locally to `$PROJECT_DIR/.local/kairos/work` and keep it stable for the run
+  locally to `$PROJECT_DIR/.local/squadrules/work` and keep it stable for the run
 - prerequisites create the directory
 - Reward Signal cleans it up
 - never write credentials or secrets to files
@@ -224,7 +224,7 @@ to avoid collisions between parallel sessions.
 - print the final status marker to stderr when stdout is machine-readable
 - preserve the original status exactly:
   ```bash
-  ( set -o pipefail; <command> ); rc=$?; printf '\nKAIROS_SHELL_EXIT=%s\n' "$rc" >&2; exit "$rc"
+  ( set -o pipefail; <command> ); rc=$?; printf '\nSQUADRULES_SHELL_EXIT=%s\n' "$rc" >&2; exit "$rc"
   ```
 - keep `&&` inside `<command>` for ordered checks; use the final
   `; rc=$?; ...` trailer only to capture, print, and return the process status
@@ -258,7 +258,7 @@ to avoid collisions between parallel sessions.
 - NOT a replacement for layers — layers remain the primary unit of work
 - example contract:
   ```json
-  {"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"kairos://adapter/implement-plan"}},"required":true}}
+  {"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"squadrules://adapter/implement-plan"}},"required":true}}
   ```
 
 ```json

package/dist/embed-docs/mem/create-new-protocol.md

@@ -1,14 +1,14 @@
 ---
 slug: create-new-protocol
-version: "4.8.6"
-title: Create / Review / Refactor KAIROS Protocol
+version: "5.0.0"
+title: Create / Review / Refactor SQUADRULES Protocol
 ---
 
 
 
-# Create / Review / Refactor KAIROS Protocol
+# Create / Review / Refactor SQUADRULES Protocol
 
-> **Note to the agent:** KAIROS protocols are interfaces for AI agents — you
+> **Note to the agent:** SQUADRULES protocols are interfaces for AI agents — you
 > are the primary user. When you author a protocol, you design behaviour for
 > yourself and others. Write for them: single source of truth (never duplicate
 > rules), explicit over implicit (agents fill ambiguity with hallucination),
@@ -18,7 +18,7 @@ title: Create / Review / Refactor KAIROS Protocol
 
 ## Activation Patterns
 
-KAIROS authoring lifecycle — create, review, or update adapters / protocols / workflows.
+SQUADRULES authoring lifecycle — create, review, or update adapters / protocols / workflows.
 In this context, those words refer to the same stored artifact and can be treated
 as synonyms. Supports three operations:
 
@@ -31,8 +31,8 @@ as synonyms. Supports three operations:
 
 **Run this protocol when the user says ANY of:**
 
-- "create a new KAIROS protocol" / "create new protocol adapter"
-- "register personal KAIROS adapter" / "register a personal adapter"
+- "create a new SQUADRULES protocol" / "create new protocol adapter"
+- "register personal SQUADRULES adapter" / "register a personal adapter"
 - "train adapter into personal" / "train protocol into personal"
 - "train a workflow" / "register a new adapter" / "create a new workflow"
 - "review protocol" / "audit adapters" / "check protocol families for gaps"
@@ -63,7 +63,7 @@ as synonyms. Supports three operations:
 - Enforce the 350-line limit per file.
 
 **Good trigger examples:**
-- "Create a new KAIROS protocol for code review" → run this protocol (create)
+- "Create a new SQUADRULES protocol for code review" → run this protocol (create)
 - "No match found; I want to create a new protocol" → run this protocol (create)
 - "Review all v4 protocol families for missing cross-references" → run this protocol (review)
 - "Update the MR adapter to include a review step" → run this protocol (update)
@@ -146,7 +146,7 @@ For `update`: ask which adapter to update and what the issue is.
 and which parts stay in the router vs extensions.
 
 **4. If Chain pattern:** Load `protocol-linking-guide` for full rules
-(`forward` with `kairos://adapter/protocol-linking-guide`). Collect: chain
+(`forward` with `squadrules://adapter/protocol-linking-guide`). Collect: chain
 links and concerns, minimum number of links, entry point (matched by
 `activate`), and artifacts flowing between links.
 
@@ -202,7 +202,7 @@ Draft the full markdown for `train`.
 
 Write a structured gap report to `$REVIEW_FINDINGS_FILE` (an absolute path
 provided by the invoking agent or chosen by you under
-`$KAIROS_LOCAL_ARTIFACT_DIR` with a session-unique segment). For each finding
+`$SQUADRULES_LOCAL_ARTIFACT_DIR` with a session-unique segment). For each finding
 include:
 
 - adapter title
@@ -217,7 +217,7 @@ Apply the identified change and show a diff-style summary of what changed.
 
 ### Shared drafting rules (all operations)
 
-**Core KAIROS rule — right mode at the right time:**
+**Core SQUADRULES rule — right mode at the right time:**
 
 Every protocol must help the agent recognise whether the current step is for
 exploration, clarification, ideation, planning, execution, validation, review,
@@ -257,7 +257,7 @@ Every protocol gets a short, unique, lowercase-hyphenated `slug`.
 
 Store scripts or config blobs as artifacts via `train` (set `mime`,
 `artifact_name`, `adapter_uri`). Retrieve with `export` using
-`kairos://artifact/{uuid}`.
+`squadrules://artifact/{uuid}`.
 
 **Protocol structure:** H1 title, first H2 Activation Patterns, second H2
 Preflight Dependencies, middle H2s one per step with JSON contract block, last
@@ -265,10 +265,10 @@ H2 Reward Signal. Frontmatter: `slug` (required), `version` (optional),
 `chain_root` (required for mid-chain adapters).
 
 **Challenge types:** Load `challenge-type-guide` for decision rules and JSON
-formats (`forward` with `kairos://adapter/challenge-type-guide`).
+formats (`forward` with `squadrules://adapter/challenge-type-guide`).
 
 **Phase-critic and mutation gates:** Load `phase-critic-guide` for placement,
-FAIL gate, and solution check rules (`forward` with `kairos://adapter/phase-critic-guide`).
+FAIL gate, and solution check rules (`forward` with `squadrules://adapter/phase-critic-guide`).
 
 **If Router pattern:** draft the router and each extension as separate files.
 
@@ -284,7 +284,7 @@ For `create` and `update`: run phase-critic against the drafted markdown before
 presenting to the user. This is the quality gate — the agent owns content, the
 critic owns quality.
 
-1. Invoke phase-critic via `forward` with `kairos://adapter/phase-critic`.
+1. Invoke phase-critic via `forward` with `squadrules://adapter/phase-critic`.
    Provide the drafted markdown as `input_file`, the slug as
    `calling_protocol_slug`, and "structural compliance and agent behaviour"
    as `verification_target`.
@@ -342,5 +342,5 @@ Protocol complete when:
 - `review` — findings report delivered and acknowledged
 - `update` — corrected adapter trained with `force_update: true` + review_evidence, repo file updated
 
-A successful result means the resulting KAIROS adapter is more truthful,
+A successful result means the resulting SQUADRULES adapter is more truthful,
 phase-aware, agent-readable, and aligned with human–AI harmony.

package/dist/embed-docs/mem/phase-critic-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: phase-critic-guide
 title: Phase Critic Integration and Mutation Gate Guide
 ---
@@ -87,7 +87,7 @@ pattern is a `mcp` contract that requires calling `forward` with the
 ### After a planning phase
 
 ```json
-{"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"kairos://adapter/phase-critic"}},"required":true}}
+{"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"squadrules://adapter/phase-critic"}},"required":true}}
 ```
 
 ### After an implementation phase

package/dist/embed-docs/mem/phase-critic.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: phase-critic
 title: Phase Critic
 ---
@@ -17,7 +17,7 @@ for contradictions.
 
 **Typically invoked by:** another protocol at the end of a plan, implement,
 validation, or review phase via `forward` with the stored adapter URI
-`kairos://adapter/phase-critic`.
+`squadrules://adapter/phase-critic`.
 
 **Can be invoked directly when agent needs:**
 - "review phase output" / "verify plan" / "audit implementation"

package/dist/embed-docs/mem/protocol-linking-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: protocol-linking-guide
 title: Protocol Linking Guide
 ---
@@ -122,12 +122,12 @@ When you are executing **`forward`** inside a **multi-layer** adapter (for examp
 a root conductor), each continuation follows **`next_call`** for the **same**
 `execution_id` until the last layer directs **`reward`**. A layer that mentions
 another adapter URI only as routing guidance — for example
-`kairos://adapter/e2e-coding-pr-delivery` — does **not** cause the server to
+`squadrules://adapter/e2e-coding-pr-delivery` — does **not** cause the server to
 switch executions: the next **`forward`** in that run still advances the
 **current** adapter’s next layer.
 
 To run an extension adapter, call **`forward`** with
-`kairos://adapter/<slug>` as a **new** first call (adapter URI; omit
+`squadrules://adapter/<slug>` as a **new** first call (adapter URI; omit
 `solution`). That starts a **separate** execution with its own layers. Common
 pattern: complete the conductor with **`reward`**, then **`forward`** to the
 extension slug when coding or PR-shaped work should run under that adapter’s
@@ -142,8 +142,8 @@ contracts.
 Both system and user-authored adapters chain using slugs in `next_action`:
 
 ```text
-call forward with kairos://adapter/phase-critic ...
-call forward with kairos://adapter/implement-terraform ...
+call forward with squadrules://adapter/phase-critic ...
+call forward with squadrules://adapter/implement-terraform ...
 ```
 
 Slugs are globally unique (enforced by `train`), so resolution is
@@ -164,7 +164,7 @@ A bare `mcp` contract checks only the tool name:
 An `mcp` contract **with `arguments`** verifies the exact target:
 
 ```json
-{"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"kairos://adapter/code-review-policy"}},"required":true}}
+{"contract":{"type":"mcp","mcp":{"tool_name":"forward","arguments":{"uri":"squadrules://adapter/code-review-policy"}},"required":true}}
 ```
 
 The server validates that `solution.mcp.arguments` is a superset of the

package/dist/embed-docs/mem/refine-search.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: refine-search
 title: Get help refining your search
 ---
@@ -12,7 +12,7 @@ title: Get help refining your search
 / ambiguous matches. This adapter helps you turn a vague request into a better
 query so the next `activate` can find the right adapter.
 
-KAIROS principle: before acting, understand the user better. The goal is not to
+SQUADRULES principle: before acting, understand the user better. The goal is not to
 repeat the failed phrase with minor edits. The goal is to recover the user's
 real intent.
 
@@ -49,7 +49,7 @@ From the user's original message, identify:
 - the real goal
 - relevant context
 - missing constraints
-- likely wording that would help KAIROS find the right adapter
+- likely wording that would help SQUADRULES find the right adapter
 
 Write your analysis as the solution.
 

package/dist/embed-docs/mem/skill-format-guide.md

@@ -1,5 +1,5 @@
 ---
-version: "4.8.6"
+version: "5.0.0"
 slug: skill-format-guide
 title: Skill Format and Local Authoring Guide
 ---
@@ -9,9 +9,9 @@ title: Skill Format and Local Authoring Guide
 # Skill Format and Local Authoring Guide
 
 Decision rules for authoring SKILL.md files, choosing between local (git) and
-server (KAIROS) storage, and quality gates for skill content. Fetches the
+server (SQUADRULES) storage, and quality gates for skill content. Fetches the
 current Agent Skills format spec (Context7 or agentskills.io) as the
-authoritative generic format, then layers KAIROS customizations on top. Loaded
+authoritative generic format, then layers SQUADRULES customizations on top. Loaded
 by protocol-authoring agents during drafting and review when the output format
 is `skill`.
 
@@ -23,7 +23,7 @@ is `skill`.
 **Can be invoked directly when agent needs:**
 - "SKILL.md format reference" / "how to write a skill"
 - "latest SKILL.md spec" / "current agentskills format"
-- "skill vs adapter" / "local skill or KAIROS adapter"
+- "skill vs adapter" / "local skill or SQUADRULES adapter"
 - "skill quality gates" / "SKILL.md structure"
 - "project-level skill" / "where to put a skill"
 
@@ -31,7 +31,7 @@ is `skill`.
 
 **Must Never:**
 - Be used as an execution protocol.
-- Recommend storing a skill in both git AND KAIROS server simultaneously.
+- Recommend storing a skill in both git AND SQUADRULES server simultaneously.
 - Confuse SKILL.md (agent instruction file) with protocol markdown (adapter).
 - Hardcode the generic SKILL.md format from memory when the current spec is
   reachable via Context7 or agentskills.io.
@@ -39,7 +39,7 @@ is `skill`.
 **Must Always:**
 - Be consulted before writing any SKILL.md file.
 - Fetch the current Agent Skills spec before authoring or reviewing generic
-  format, and apply KAIROS customizations after it.
+  format, and apply SQUADRULES customizations after it.
 - Enforce single source of truth: each skill lives in exactly one place.
 - Match storage location to the skill's scope and discoverability needs.
 
@@ -59,8 +59,8 @@ Every skill has ONE home. Choose at authoring time. Never both.
 | Scope | Storage | Discovery | Source of Truth |
 |---|---|---|---|
 | Project-specific (deploy, test, release) | Git: `.agents/skills/{name}/` or `.cursor/skills/{name}/` | IDE host scans description field | Git repo |
-| Personal cross-project (universal) | KAIROS server via `train` | `activate` embedding search | KAIROS server |
-| Team/group shared | KAIROS server (group space) | `activate` | KAIROS server |
+| Personal cross-project (universal) | SQUADRULES server via `train` | `activate` embedding search | SQUADRULES server |
+| Team/group shared | SQUADRULES server (group space) | `activate` | SQUADRULES server |
 
 ### Decision Tree
 
@@ -69,9 +69,9 @@ Is this skill specific to ONE project's codebase?
  ├─ YES → Does it reference repo files, paths, or project-specific tools?
  │         ├─ YES → LOCAL (git)
  │         └─ NO  → Could it help in other projects?
- │                   ├─ YES → SERVER (KAIROS)
+ │                   ├─ YES → SERVER (SQUADRULES)
  │                   └─ NO  → LOCAL (git)
- └─ NO → SERVER (KAIROS)
+ └─ NO → SERVER (SQUADRULES)
 ```
 
 ### Local Storage Paths
@@ -90,7 +90,7 @@ Is this skill specific to ONE project's codebase?
 **Local → Server (skill graduates to universal):**
 1. Read existing SKILL.md
 2. Optionally wrap in protocol structure (Activation Patterns, contracts)
-3. `train` to KAIROS server
+3. `train` to SQUADRULES server
 4. Delete local copy or mark deprecated
 5. Git commit the deletion
 
@@ -108,7 +108,7 @@ Is this skill specific to ONE project's codebase?
 Do NOT rely on a frozen copy of the SKILL.md format. The Agent Skills format
 evolves (new frontmatter fields, directory conventions, size guidance). Before
 authoring or reviewing a SKILL.md, fetch the **current** specification and treat
-it as authoritative for the generic format. The KAIROS customizations in the
+it as authoritative for the generic format. The SQUADRULES customizations in the
 sections *after* this one layer on top of that generic spec.
 
 **Authoritative source (fetch fresh — do not guess):**
@@ -145,19 +145,19 @@ sections *after* this one layer on top of that generic spec.
 {"contract":{"type":"comment","comment":{"min_length":30},"required":true}}
 ```
 
-## KAIROS Customizations (apply after the generic spec)
+## SQUADRULES Customizations (apply after the generic spec)
 
-Everything below is KAIROS-specific and layers on top of the fetched Agent
+Everything below is SQUADRULES-specific and layers on top of the fetched Agent
 Skills spec. When the generic spec and these rules disagree on generic format,
-follow the spec; these rules add KAIROS storage, integrity, and routing
+follow the spec; these rules add SQUADRULES storage, integrity, and routing
 behavior the generic spec does not cover.
 
-### KAIROS additions to structure
+### SQUADRULES additions to structure
 
-- **`SHA256SUMS`** — required for KAIROS-exported skill bundles (GNU
-  `sha256sum` format, paths relative to the skill dir). This is a KAIROS
+- **`SHA256SUMS`** — required for SQUADRULES-exported skill bundles (GNU
+  `sha256sum` format, paths relative to the skill dir). This is a SQUADRULES
   integrity requirement, not part of the generic Agent Skills spec.
-- **`disable-model-invocation`** — when the host supports it, KAIROS-authored
+- **`disable-model-invocation`** — when the host supports it, SQUADRULES-authored
   skills default this to `true` (explicit load only) unless the skill is meant
   to auto-trigger. Only add fields the fetched spec actually recognizes.
 - **Reference depth** — keep references one level deep (SKILL.md → reference
@@ -236,7 +236,7 @@ When `{target}=local`:
 
 Do NOT call `train`. The skill lives only in git.
 
-### Path B: Server Train (KAIROS-routable adapter)
+### Path B: Server Train (SQUADRULES-routable adapter)
 
 When `{target}=server`:
 
@@ -248,17 +248,17 @@ When `{target}=server`:
 3. Verify adapter URI returned
 4. Report URI and slug to user
 
-Do NOT write to local disk. The adapter lives only in KAIROS.
+Do NOT write to local disk. The adapter lives only in SQUADRULES.
 
 ### Path C: Hybrid Authoring (skill that is also an adapter)
 
 When `{target}=hybrid` (rare — use only when explicitly requested):
 
-1. Author as a KAIROS protocol (Activation Patterns, contracts, Reward Signal)
+1. Author as a SQUADRULES protocol (Activation Patterns, contracts, Reward Signal)
 2. `train` to server
 3. `export` with `format: skill_zip` to produce local SKILL.md bundle
 4. The exported SKILL.md is a **read-only derived artifact**, not a source of truth
-5. Document in the SKILL.md header that it was exported from KAIROS
+5. Document in the SKILL.md header that it was exported from SQUADRULES
 
 ```json
 {"contract":{"type":"comment","comment":{"min_length":30},"required":true}}
@@ -271,7 +271,7 @@ Only reachable after all prior steps are solved.
 The agent can now:
 1. Fetch the current Agent Skills spec (Context7 or agentskills.io) instead of
    relying on a frozen copy, and apply it as the authoritative generic format
-2. Layer the KAIROS customizations (storage, `SHA256SUMS`, routing) on top of
+2. Layer the SQUADRULES customizations (storage, `SHA256SUMS`, routing) on top of
    that fetched spec
 3. Choose the correct storage location for a skill
 4. Author SKILL.md with valid frontmatter and structure per the current spec

package/dist/http/bearer-validate.d.ts

@@ -4,7 +4,7 @@ export interface AuthPayload {
     groups: string[];
     /** Raw issuer retained for deterministic space-id derivation across Keycloak hosts. */
     iss: string;
-    /** Realm from token issuer (e.g. kairos) for space isolation. */
+    /** Realm from token issuer (e.g. the deployment realm) for space isolation. */
     realm: string;
     preferred_username?: string;
     name?: string;

package/dist/http/bearer-validate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"bearer-validate.d.ts","sourceRoot":"","sources":["../../src/http/bearer-validate.ts"],"names":[],"mappings":"AAaA,OAAO,EAKL,KAAK,WAAW,EACjB,MAAM,0BAA0B,CAAC;AAElC,MAAM,WAAW,WAAW;IAC1B,GAAG,EAAE,MAAM,CAAC;IACZ,MAAM,EAAE,MAAM,EAAE,CAAC;IACjB,uFAAuF;IACvF,GAAG,EAAE,MAAM,CAAC;IACZ,iEAAiE;IACjE,KAAK,EAAE,MAAM,CAAC;IACd,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B,iGAAiG;IACjG,YAAY,CAAC,EAAE,WAAW,CAAC;IAC3B,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AA6ED;;;GAGG;AACH,wBAAsB,mBAAmB,CACvC,KAAK,EAAE,MAAM,EACb,cAAc,EAAE,MAAM,EAAE,EACxB,gBAAgB,EAAE,MAAM,EAAE,GACzB,OAAO,CAAC,WAAW,GAAG,IAAI,CAAC,CAoF7B"}
+{"version":3,"file":"bearer-validate.d.ts","sourceRoot":"","sources":["../../src/http/bearer-validate.ts"],"names":[],"mappings":"AAaA,OAAO,EAKL,KAAK,WAAW,EACjB,MAAM,0BAA0B,CAAC;AAElC,MAAM,WAAW,WAAW;IAC1B,GAAG,EAAE,MAAM,CAAC;IACZ,MAAM,EAAE,MAAM,EAAE,CAAC;IACjB,uFAAuF;IACvF,GAAG,EAAE,MAAM,CAAC;IACZ,+EAA+E;IAC/E,KAAK,EAAE,MAAM,CAAC;IACd,kBAAkB,CAAC,EAAE,MAAM,CAAC;IAC5B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,cAAc,CAAC,EAAE,OAAO,CAAC;IACzB,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B,iGAAiG;IACjG,YAAY,CAAC,EAAE,WAAW,CAAC;IAC3B,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AA6ED;;;GAGG;AACH,wBAAsB,mBAAmB,CACvC,KAAK,EAAE,MAAM,EACb,cAAc,EAAE,MAAM,EAAE,EACxB,gBAAgB,EAAE,MAAM,EAAE,GACzB,OAAO,CAAC,WAAW,GAAG,IAAI,CAAC,CAoF7B"}

package/dist/http/export-skill-zip-http.js

@@ -9,9 +9,9 @@ export async function streamSkillZipHttpResponse(res, memoryStore, qdrantService
     const flat = flattenSkillItemsToZipPaths(items.map((it) => ({ slug: it.slug, files: it.files })));
     res.setHeader('Content-Type', 'application/zip');
     res.setHeader('Content-Disposition', `attachment; filename="${DEFAULT_EXPORT_SKILL_ZIP_FILENAME}"`);
-    res.setHeader('X-KAIROS-Primary-Export-Uri', primaryUri);
-    res.setHeader('X-KAIROS-Export-Adapter-Count', String(items.length));
-    res.setHeader('X-KAIROS-Export-Binary', '1');
+    res.setHeader('X-SQUADRULES-Primary-Export-Uri', primaryUri);
+    res.setHeader('X-SQUADRULES-Export-Adapter-Count', String(items.length));
+    res.setHeader('X-SQUADRULES-Export-Binary', '1');
     // Dual headers for SquadRules migration: both sets emitted so clients reading either name work.
     res.setHeader('X-SquadRules-Primary-Export-Uri', primaryUri);
     res.setHeader('X-SquadRules-Export-Adapter-Count', String(items.length));

package/dist/http/export-skill-zip-http.js.map

@@ -1 +1 @@
-{"version":3,"file":"export-skill-zip-http.js","sourceRoot":"","sources":["../../src/http/export-skill-zip-http.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAC1C,OAAO,EAAE,QAAQ,EAAE,MAAM,sBAAsB,CAAC;AAGhD,OAAO,EAAE,6BAA6B,EAAE,MAAM,gCAAgC,CAAC;AAC/E,OAAO,EAAE,uBAAuB,EAAE,MAAM,8BAA8B,CAAC;AACvE,OAAO,EAAE,2BAA2B,EAAE,sBAAsB,EAAE,MAAM,qCAAqC,CAAC;AAC1G,OAAO,EAAE,iCAAiC,EAAE,MAAM,kCAAkC,CAAC;AAErF,MAAM,CAAC,KAAK,UAAU,0BAA0B,CAC9C,GAAa,EACb,WAA8B,EAC9B,aAAwC,EACxC,WAAqB;IAErB,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,GAAG,MAAM,6BAA6B,CAAC,WAAW,EAAE,aAAa,EAAE,WAAW,CAAC,CAAC;IAC3G,MAAM,IAAI,GAAG,2BAA2B,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,IAAI,EAAE,EAAE,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,CAAC;IAElG,GAAG,CAAC,SAAS,CAAC,cAAc,EAAE,iBAAiB,CAAC,CAAC;IACjD,GAAG,CAAC,SAAS,CAAC,qBAAqB,EAAE,yBAAyB,iCAAiC,GAAG,CAAC,CAAC;IACpG,GAAG,CAAC,SAAS,CAAC,6BAA6B,EAAE,UAAU,CAAC,CAAC;IACzD,GAAG,CAAC,SAAS,CAAC,+BAA+B,EAAE,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC;IACrE,GAAG,CAAC,SAAS,CAAC,wBAAwB,EAAE,GAAG,CAAC,CAAC;IAC7C,gGAAgG;IAChG,GAAG,CAAC,SAAS,CAAC,iCAAiC,EAAE,UAAU,CAAC,CAAC;IAC7D,GAAG,CAAC,SAAS,CAAC,mCAAmC,EAAE,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC;IACzE,GAAG,CAAC,SAAS,CAAC,4BAA4B,EAAE,GAAG,CAAC,CAAC;IAEjD,IAAI,eAAe,GAAG,CAAC,CAAC;IACxB,MAAM,IAAI,GAAG,IAAI,WAAW,EAAE,CAAC;IAC/B,IAAI,CAAC,EAAE,CAAC,MAAM,EAAE,CAAC,KAAa,EAAE,EAAE;QAChC,eAAe,IAAI,KAAK,CAAC,MAAM,CAAC;IAClC,CAAC,CAAC,CAAC;IAEH,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;IACf,MAAM,sBAAsB,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC;IACzC,MAAM,QAAQ,CAAC,GAAG,CAAC,CAAC;IACpB,uBAAuB,CAAC,eAAe,CAAC,CAAC;AAC3C,CAAC"}
+{"version":3,"file":"export-skill-zip-http.js","sourceRoot":"","sources":["../../src/http/export-skill-zip-http.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAC1C,OAAO,EAAE,QAAQ,EAAE,MAAM,sBAAsB,CAAC;AAGhD,OAAO,EAAE,6BAA6B,EAAE,MAAM,gCAAgC,CAAC;AAC/E,OAAO,EAAE,uBAAuB,EAAE,MAAM,8BAA8B,CAAC;AACvE,OAAO,EAAE,2BAA2B,EAAE,sBAAsB,EAAE,MAAM,qCAAqC,CAAC;AAC1G,OAAO,EAAE,iCAAiC,EAAE,MAAM,kCAAkC,CAAC;AAErF,MAAM,CAAC,KAAK,UAAU,0BAA0B,CAC9C,GAAa,EACb,WAA8B,EAC9B,aAAwC,EACxC,WAAqB;IAErB,MAAM,EAAE,KAAK,EAAE,UAAU,EAAE,GAAG,MAAM,6BAA6B,CAAC,WAAW,EAAE,aAAa,EAAE,WAAW,CAAC,CAAC;IAC3G,MAAM,IAAI,GAAG,2BAA2B,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,CAAC,EAAE,IAAI,EAAE,EAAE,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,KAAK,EAAE,CAAC,CAAC,CAAC,CAAC;IAElG,GAAG,CAAC,SAAS,CAAC,cAAc,EAAE,iBAAiB,CAAC,CAAC;IACjD,GAAG,CAAC,SAAS,CAAC,qBAAqB,EAAE,yBAAyB,iCAAiC,GAAG,CAAC,CAAC;IACpG,GAAG,CAAC,SAAS,CAAC,iCAAiC,EAAE,UAAU,CAAC,CAAC;IAC7D,GAAG,CAAC,SAAS,CAAC,mCAAmC,EAAE,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC;IACzE,GAAG,CAAC,SAAS,CAAC,4BAA4B,EAAE,GAAG,CAAC,CAAC;IACjD,gGAAgG;IAChG,GAAG,CAAC,SAAS,CAAC,iCAAiC,EAAE,UAAU,CAAC,CAAC;IAC7D,GAAG,CAAC,SAAS,CAAC,mCAAmC,EAAE,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC;IACzE,GAAG,CAAC,SAAS,CAAC,4BAA4B,EAAE,GAAG,CAAC,CAAC;IAEjD,IAAI,eAAe,GAAG,CAAC,CAAC;IACxB,MAAM,IAAI,GAAG,IAAI,WAAW,EAAE,CAAC;IAC/B,IAAI,CAAC,EAAE,CAAC,MAAM,EAAE,CAAC,KAAa,EAAE,EAAE;QAChC,eAAe,IAAI,KAAK,CAAC,MAAM,CAAC;IAClC,CAAC,CAAC,CAAC;IAEH,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;IACf,MAAM,sBAAsB,CAAC,IAAI,EAAE,IAAI,CAAC,CAAC;IACzC,MAAM,QAAQ,CAAC,GAAG,CAAC,CAAC;IACpB,uBAAuB,CAAC,eAAe,CAAC,CAAC;AAC3C,CAAC"}

package/dist/http/http-api-snapshot.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"http-api-snapshot.d.ts","sourceRoot":"","sources":["../../src/http/http-api-snapshot.ts"],"names":[],"mappings":"AAAA,OAAO,OAAO,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AAYnE,wBAAgB,kBAAkB,CAAC,GAAG,EAAE,OAAO,CAAC,OAAO,EAAE,aAAa,EAAE,aAAa,QA0BpF"}
+{"version":3,"file":"http-api-snapshot.d.ts","sourceRoot":"","sources":["../../src/http/http-api-snapshot.ts"],"names":[],"mappings":"AAAA,OAAO,OAAO,MAAM,SAAS,CAAC;AAC9B,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,+BAA+B,CAAC;AAYnE,wBAAgB,kBAAkB,CAAC,GAAG,EAAE,OAAO,CAAC,OAAO,EAAE,aAAa,EAAE,aAAa,QAuCpF"}

package/dist/http/http-api-snapshot.js

@@ -1,5 +1,5 @@
 import { triggerQdrantSnapshot } from '../services/qdrant/snapshots.js';
-import { QDRANT_SNAPSHOT_DIR } from '../config.js';
+import { QDRANT_SNAPSHOT_DIR, isQdrantConfigured } from '../config.js';
 /**
  * Set up API route for Qdrant snapshot
  * @param app Express application instance
@@ -9,6 +9,18 @@ import { QDRANT_SNAPSHOT_DIR } from '../config.js';
 const SNAPSHOT_NOT_CONFIGURED_MESSAGE = 'Backup directory is not defined in server settings.';
 export function setupSnapshotRoute(app, qdrantService) {
     app.post('/api/snapshot', async (_req, res) => {
+        // Server-side snapshots are a Qdrant feature. On the embedded LanceDB
+        // backend there is no Qdrant to snapshot, so report that honestly instead
+        // of attempting a Qdrant call and returning a misleading failure.
+        if (!isQdrantConfigured) {
+            res.status(400).json({
+                error: 'SNAPSHOT_UNSUPPORTED',
+                status: 'unsupported',
+                target: 'embedded-lancedb',
+                message: 'Server-side snapshots require Qdrant and are not supported on the embedded LanceDB backend. Stop the server and back up its data directory instead.'
+            });
+            return;
+        }
         if (!QDRANT_SNAPSHOT_DIR) {
             res.status(503).json({
                 error: 'Backup not configured',