MCP Agent Naming & Persistence Bug

## Summary

When initializing a swarm with a YAML specification containing more than three explicitly named agents, the Claude Flow MCP server ignores the specified names and spawns only three generic agents (`coordinator-1`, `researcher-1`, `coder-1`). All agents report `"persisted": false`, and `agent_list` shows only these default agents, regardless of the YAML spec.

## Environment

* **Platform**: Kilo Code (Claude Code integration)
* **MCP Server**: Claude Flow (alpha release)
* **Database Path**: `~/.swarm/memory.db`
* **Namespace**: `hivemind`
* **Spec**: YAML file with explicit agent names (>3), persistence enabled.

## Steps to Reproduce

1. Create a YAML swarm specification with **5 explicitly named agents**:

```yaml
swarm:
namespace: hivemind
persist: true
db_path: ~/.swarm/memory.db
agents:
- name: requirements-analyst
role: requirements
- name: context-researcher
role: researcher
- name: system-architect
role: architect
- name: conservative-coder
role: coder
- name: quality-tester
role: tester
```
2. Save the YAML in your swarm definition markdown file.
3. Run the swarm initialization prompt in Kilo Code via MCP Claude Flow.
4. After all agent spawns return `SUCCESS`, run `agent_list`.

## Expected Behavior

* All agents spawn exactly as named in the YAML.
* Each agent reports `"persisted": true`.
* `agent_list` matches the YAML exactly.

## Actual Behavior

* Only 3 generic agents spawn, ignoring specified names.
* All spawned agents report `"persisted": false`.
* `agent_list` omits most specified agents.

## Notes

* Occurs whether YAML specifies 5, 11, or more agents.
* SQLite DB path is valid and writable.
* All `agent_spawn` calls return `SUCCESS` but without persistence.

---

This prevents workflows requiring deterministic agent rosters from functioning as intended.