Bug: hive-mind task command references non-existent MCP tool

# Bug: hive-mind task command references non-existent MCP tool

## Description

The `claude-flow hive-mind task` CLI command fails because it attempts to call an MCP tool `hive-mind_task` that does not exist in the tool registry.

## Version

- claude-flow: v3.0.0-alpha.185

## Steps to Reproduce

1. Initialize hive mind successfully:
```bash
claude-flow hive-mind init --force
# Returns success with Hive ID
```

2. Spawn workers successfully:
```bash
claude-flow hive-mind spawn --type worker --name test-worker
# Returns success, worker joins hive
```

3. Submit a task:
```bash
claude-flow hive-mind task -d "Any task description"
```

4. **Error occurs**:
```
[INFO] Submitting task to hive...
[ERROR] Task submission error: MCP tool not found: hive-mind_task
```

## Expected Behavior

The task should be submitted to the hive and assigned to an available worker.

## Actual Behavior

The CLI attempts to call `hive-mind_task` MCP tool which doesn't exist in the MCP server's tool registry.

## Available hive-mind Tools (for reference)

The following 9 hive-mind tools exist:
- `hive-mind_init`
- `hive-mind_spawn`
- `hive-mind_status`
- `hive-mind_join`
- `hive-mind_leave`
- `hive-mind_consensus`
- `hive-mind_broadcast`
- `hive-mind_shutdown`
- `hive-mind_memory`

**Missing**: `hive-mind_task`

## Suggested Fix

Add the `hive-mind_task` MCP tool to:
1. Accept task descriptions
2. Route tasks to available workers
3. Track task execution status

## Environment

- Platform: Windows 11
- Hive Status: Active (Queen + workers operational)

Start by tracing the `claude-flow hive-mind task` command to the MCP tool registry and compare its `hive-mind_task` reference with the nine available hive-mind tools listed in the issue. Confirm the expected task-submission flow and verify that tasks can be routed to an available worker and their execution status tracked without the reported missing-tool error.

Written by the indexing model from the issue text.