Fix claude-specific references in agents, skills and references

references/agent-orchestration.md

@@ -1,6 +1,6 @@
 # Agent Orchestration Protocol
 
-This document defines how agents coordinate through the **dispatcher** (`CLAUDE.md`). Agents do NOT communicate directly with each other — the dispatcher handles all routing and chaining.
+This document defines how agents coordinate through the **dispatcher** (`DISPATCHER.md`). Agents do NOT communicate directly with each other — the dispatcher handles all routing and chaining.
 
 ---
 
@@ -25,7 +25,7 @@ Skills are checked **before** agents. They handle complex, multi-step workflows
 
 ### How it works
 
-- The dispatcher maintains a **skill routing table** (defined in `CLAUDE.md`) with trigger phrases in multiple languages.
+- The dispatcher maintains a **skill routing table** (defined in `DISPATCHER.md`) with trigger phrases in multiple languages.
 - If a user message matches a skill trigger, the skill is invoked via the **Skill tool** (not the Agent tool). The dispatcher does NOT also invoke the source agent.
 - Skills run in the **main conversation context**, preserving multi-turn state. This is different from agents, which run as subprocesses.
 - If no skill matches, the dispatcher falls through to the **agent routing table**.
@@ -39,7 +39,7 @@ Skills can still produce output that triggers agent chaining:
 
 ### List of skills
 
-See `.claude/references/agents.md` (Skills section) for the full table of skills, their source agents, and purposes.
+See `.platform/references/agents.md` (Skills section) for the full table of skills, their source agents, and purposes.
 
 ---
 
@@ -132,13 +132,13 @@ If the dispatcher would need a 4th agent, it:
 
 ## Custom Agent Lifecycle
 
-Custom agents are created by the Architect and stored in `.claude/agents/`. They participate fully in the orchestration system:
+Custom agents are created by the Architect and stored in `.platform/agents/`. They participate fully in the orchestration system:
 
 1. **Creation**: the Architect creates the agent file, adds a row to `agents-registry.md`, and updates `agents.md`
-2. **Discovery**: Claude Code auto-discovers the agent from its frontmatter in `.claude/agents/`
+2. **Discovery**: Claude Code auto-discovers the agent from its frontmatter in `.platform/agents/`
 3. **Routing**: the dispatcher checks `agents-registry.md` for custom agents when no core agent matches
 4. **Chaining**: custom agents can suggest (and be suggested by) any other agent, following the same protocol
-5. **Maintenance**: the Librarian audits custom agents during vault health checks. For every row in agents-registry.md with status=active, the corresponding file must exist in `.claude/agents/`
+5. **Maintenance**: the Librarian audits custom agents during vault health checks. For every row in agents-registry.md with status=active, the corresponding file must exist in `.platform/agents/`
 6. **Deletion**: only the Architect can remove a custom agent (with user confirmation). The agent file is deleted, and the registry row is set to `disabled`
 
 ---
@@ -146,7 +146,7 @@ Custom agents are created by the Architect and stored in `.claude/agents/`. They
 ## What Agents Should NOT Do
 
 - ❌ **Do NOT reference `Meta/agent-messages.md`** — the shared message board is deprecated
-- ❌ **Do NOT edit other agents' prompt/config files** (e.g., `.claude/agents/*.md`) — normal vault notes/MOC edits are still allowed per your responsibilities; all coordination goes through the dispatcher
+- ❌ **Do NOT edit other agents' prompt/config files** (e.g., `.platform/agents/*.md`) — normal vault notes/MOC edits are still allowed per your responsibilities; all coordination goes through the dispatcher
 - ❌ **Do NOT block waiting for another agent** — finish your task and suggest next steps in your output
 - ❌ **Do NOT call other agents** — only the dispatcher invokes agents
 
@@ -191,5 +191,5 @@ last-run: "YYYY-MM-DDTHH:MM:SS"
 
 ## Reference Files
 
-- **Agent registry**: `.claude/references/agents-registry.md` — the single source of truth for all agents
-- **Agent directory**: `.claude/references/agents.md` — detailed descriptions of each agent's responsibilities
+- **Agent registry**: `.platform/references/agents-registry.md` — the single source of truth for all agents
+- **Agent directory**: `.platform/references/agents.md` — detailed descriptions of each agent's responsibilities

references/agent-template.md

@@ -100,8 +100,8 @@ If you detect that the user needs functionality that NO existing agent provides,
 - The user is asking something outside the vault's scope entirely
 - The task is a one-off that does not warrant a dedicated agent
 
-For the full orchestration protocol, see `.claude/references/agent-orchestration.md`.
-For the agent registry, see `.claude/references/agents-registry.md`.
+For the full orchestration protocol, see `.platform/references/agent-orchestration.md`.
+For the agent registry, see `.platform/references/agents-registry.md`.
 
 ---
 
@@ -210,7 +210,7 @@ When generating a custom agent from this template:
 2. **Tools are minimal** by default. Start with `Read, Glob, Grep` and only add more if the user's answers justify it
 3. **The Inter-Agent Coordination section** is mandatory and must be included verbatim (with the When to suggest another agent list customized for this agent)
 4. **The Core Responsibilities section** must be deeply detailed. Ask the user enough questions to fill this section thoroughly. A vague agent is a useless agent
-5. **Every custom agent** gets a row in `.claude/references/agents-registry.md` and a section in `.claude/references/agents.md`
-6. **File location**: `.claude/agents/{{agent-name}}.md`
+5. **Every custom agent** gets a row in `.platform/references/agents-registry.md` and a section in `.platform/references/agents.md`
+6. **File location**: `.platform/agents/{{agent-name}}.md`
 7. **Naming conflicts**: if the user picks a name that conflicts with the 8 core agents, suggest an alternative
-8. **Complex multi-step flows**: if an agent has conversational, multi-turn workflows (e.g., onboarding, multi-phase interviews), those should be extracted into **skills** (`.claude/skills/`) rather than kept in the agent body. Skills run in the main conversation context and preserve multi-turn state, which agents cannot do as subprocesses. See the 13 core skills in `.claude/references/agents.md` (Skills section) for examples
+8. **Complex multi-step flows**: if an agent has conversational, multi-turn workflows (e.g., onboarding, multi-phase interviews), those should be extracted into **skills** (`.platform/skills/`) rather than kept in the agent body. Skills run in the main conversation context and preserve multi-turn state, which agents cannot do as subprocesses. See the 13 core skills in `.platform/references/agents.md` (Skills section) for examples

references/agents-registry.md

@@ -1,6 +1,6 @@
 # Agent Registry
 
-This file is the **single source of truth** for all active agents in the crew. The dispatcher (`CLAUDE.md`) and all agents reference this file for routing decisions and inter-agent coordination.
+This file is the **single source of truth** for all active agents in the crew. The dispatcher (`DISPATCHER.md`) and all agents reference this file for routing decisions and inter-agent coordination.
 
 The registry is designed to grow: custom agents (see Issue #12) are added as new rows following the same schema.
 
@@ -47,7 +47,7 @@ Custom agents are created by the Architect through a conversational flow with th
 
 1. The user asks the Architect to create a new agent (or an existing agent suggests one via `### Suggested new agent`)
 2. The Architect conducts a detailed conversation to understand requirements
-3. The Architect generates the agent file in `.claude/agents/`, adds a row to the Registry table above, and updates `agents.md`
+3. The Architect generates the agent file in `.platform/agents/`, adds a row to the Registry table above, and updates `agents.md`
 4. Claude Code auto-discovers the new agent from its frontmatter
 
 ### Naming Rules
@@ -85,7 +85,7 @@ Skills handle complex, multi-step workflows extracted from agents. They are chec
 
 ### How Skills Are Routed
 
-1. The dispatcher checks the **skill routing table** (in `CLAUDE.md`) before the agent routing table
+1. The dispatcher checks the **skill routing table** (in `DISPATCHER.md`) before the agent routing table
 2. If a trigger matches, the skill is invoked via the **Skill tool** — not the Agent tool
 3. If no skill matches, the dispatcher falls through to agent routing
 4. Skills can produce `### Suggested next agent` output, which the dispatcher handles using the same chaining rules as agents

references/agents.md

@@ -6,7 +6,7 @@ This reference is shared across all agents. Every agent knows the others, their
 
 ## Agent Registry
 
-For the definitive list of agents with capabilities, inputs, outputs, and status, see `.claude/references/agents-registry.md`. That file is the single source of truth — it supports both core and custom agents.
+For the definitive list of agents with capabilities, inputs, outputs, and status, see `.platform/references/agents-registry.md`. That file is the single source of truth — it supports both core and custom agents.
 
 ---
 
@@ -128,7 +128,7 @@ The dispatcher routes triggers to skills FIRST, then falls through to agents.
 
 ## Quick Reference: When to Suggest Another Agent
 
-When an agent detects work for another agent, it includes a `### Suggested next agent` section in its output. The dispatcher reads this and decides whether to chain the next agent. See `.claude/references/agent-orchestration.md` for the full protocol.
+When an agent detects work for another agent, it includes a `### Suggested next agent` section in its output. The dispatcher reads this and decides whether to chain the next agent. See `.platform/references/agent-orchestration.md` for the full protocol.
 
 | Situation | Suggest |
 |-----------|---------|
@@ -151,9 +151,9 @@ When an agent detects work for another agent, it includes a `### Suggested next
 
 ## Custom Agents
 
-Custom agents are created by the Architect and live in `.claude/agents/` alongside the core agents. They follow the same conventions: YAML frontmatter, trigger phrases written in the user's language, inter-agent coordination sections, and dispatcher-driven orchestration.
+Custom agents are created by the Architect and live in `.platform/agents/` alongside the core agents. They follow the same conventions: YAML frontmatter, trigger phrases written in the user's language, inter-agent coordination sections, and dispatcher-driven orchestration.
 
-For the definitive list of all agents (core + custom) with capabilities, inputs, outputs, and status, see `.claude/references/agents-registry.md`.
+For the definitive list of all agents (core + custom) with capabilities, inputs, outputs, and status, see `.platform/references/agents-registry.md`.
 
 <!-- MBIFC:CUSTOM_AGENTS_START -->
 <!-- MBIFC:CUSTOM_AGENTS_END -->