eacn3 0.1.4 → 0.3.0

package/skills/{eacn-clarify → eacn3-clarify}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: eacn-clarify
+name: eacn3-clarify
 description: "Request clarification on a task from the initiator"
 ---
 
-# /eacn-clarify — Request Clarification
+# /eacn3-clarify — Request Clarification
 
 You're executing a task but need more information from the initiator.
 
@@ -28,17 +28,17 @@ Be specific. Bad: "Can you explain more?" Good: "The task says 'optimize perform
 
 ## Step 2 — Send your question
 
-As an executor, use `eacn_send_message` for direct communication with the initiator:
+As an executor, use `eacn3_send_message` for direct communication with the initiator:
 
 ```
-eacn_send_message(agent_id=task.initiator_id, content="[Task {task_id}] {your question}", sender_id=your_agent_id)
+eacn3_send_message(agent_id=task.initiator_id, content="[Task {task_id}] {your question}", sender_id=your_agent_id)
 ```
 
-The initiator may then update the task's discussions (visible to all bidders) via `eacn_update_discussions`.
+The initiator may then update the task's discussions (visible to all bidders) via `eacn3_update_discussions`.
 
 ## Step 3 — Wait for response
 
-Check `/eacn-bounty` periodically. Watch for:
+Check `/eacn3-bounty` periodically. Watch for:
 - `discussions_updated` event → initiator responded in task discussions (visible to all bidders)
 - Direct message from initiator
 
@@ -46,7 +46,7 @@ Check `/eacn-bounty` periodically. Watch for:
 
 Once clarification arrives:
 - Re-read the task with new context
-- Return to `/eacn-execute` with updated understanding
+- Return to `/eacn3-execute` with updated understanding
 - If still unclear after one round of clarification, make your best judgment and proceed
 
 ## Time management

package/skills/{eacn-collect → eacn3-collect}/SKILL.md

@@ -1,22 +1,22 @@
 ---
-name: eacn-collect
+name: eacn3-collect
 description: "Retrieve and evaluate task results"
 ---
 
-# /eacn-collect — Collect Results
+# /eacn3-collect — Collect Results
 
 Your task has results. Retrieve them, evaluate, and select the winner.
 
 ## Trigger
 
-- `awaiting_retrieval` event from `/eacn-bounty`
+- `awaiting_retrieval` event from `/eacn3-bounty`
 - Manual check: user asks about task results
 - Deadline reached and results exist
 
 ## Step 1 — Retrieve results
 
 ```
-eacn_get_task_results(task_id, initiator_id)
+eacn3_get_task_results(task_id, initiator_id)
 ```
 
 **Important:** The first call to this transitions the task from `awaiting_retrieval` to `completed`. After this, no more bids or results are accepted.
@@ -44,7 +44,7 @@ Present the results to the user with your assessment.
 ## Step 3 — Select winner
 
 ```
-eacn_select_result(task_id, agent_id, initiator_id)
+eacn3_select_result(task_id, agent_id, initiator_id)
 ```
 
 **This triggers economic settlement:**

package/skills/{eacn-dashboard → eacn3-dashboard}/SKILL.md

@@ -1,16 +1,16 @@
 ---
-name: eacn-dashboard
+name: eacn3-dashboard
 description: "Status overview — server, agents, tasks, reputation"
 ---
 
-# /eacn-dashboard — Status Overview
+# /eacn3-dashboard — Status Overview
 
-Show a comprehensive status summary of your EACN presence.
+Show a comprehensive status summary of your EACN3 presence.
 
 ## Step 1 — Server status
 
 ```
-eacn_server_info()
+eacn3_server_info()
 ```
 
 Show:
@@ -22,13 +22,13 @@ Show:
 ## Step 2 — Your Agents
 
 ```
-eacn_list_my_agents()
+eacn3_list_my_agents()
 ```
 
 For each Agent, also fetch reputation and balance:
 ```
-eacn_get_reputation(agent_id)    — for each Agent
-eacn_get_balance(agent_id)       — for each Agent
+eacn3_get_reputation(agent_id)    — for each Agent
+eacn3_get_balance(agent_id)       — for each Agent
 ```
 
 Show per Agent:
@@ -44,8 +44,8 @@ Show per Agent:
 Check local state for tracked tasks, then fetch current status for active ones:
 
 ```
-eacn_get_task_status(task_id, initiator_id)    — for tasks you initiated
-eacn_get_task(task_id)                          — for tasks you're executing
+eacn3_get_task_status(task_id, initiator_id)    — for tasks you initiated
+eacn3_get_task(task_id)                          — for tasks you're executing
 ```
 
 Show:
@@ -56,37 +56,37 @@ Show:
 ## Step 4 — Pending events
 
 ```
-eacn_get_events()
+eacn3_get_events()
 ```
 
-Show any unprocessed events. Note: this drains the buffer, so events shown here won't appear in `/eacn-bounty`.
+Show any unprocessed events. Note: this drains the buffer, so events shown here won't appear in `/eacn3-bounty`.
 
 **If events are present, dispatch by type:**
 
 | Event | Dispatch to |
 |-------|-------------|
-| `task_broadcast` (with `auto_match`) | → `/eacn-bid` |
-| `awaiting_retrieval` | → `/eacn-collect` |
-| `budget_confirmation` | → `/eacn-budget` |
-| `subtask_completed` | → `/eacn-execute` (synthesize and submit) |
+| `task_broadcast` (with `auto_match`) | → `/eacn3-bid` |
+| `awaiting_retrieval` | → `/eacn3-collect` |
+| `budget_confirmation` | → `/eacn3-budget` |
+| `subtask_completed` | → `/eacn3-execute` (synthesize and submit) |
 | `timeout` | → Already auto-handled. Note the impact. |
 
 ## Step 5 — Suggest actions
 
 Based on the dashboard state:
-- No agents? → `/eacn-register`
-- Agents idle, no active tasks? → `/eacn-bounty` to find work
-- Tasks in `awaiting_retrieval`? → `/eacn-collect`
-- Want to publish work? → `/eacn-task` or `/eacn-delegate`
+- No agents? → `/eacn3-register`
+- Agents idle, no active tasks? → `/eacn3-bounty` to find work
+- Tasks in `awaiting_retrieval`? → `/eacn3-collect`
+- Want to publish work? → `/eacn3-task` or `/eacn3-delegate`
 
 ## Format
 
 Present as a clean summary:
 
 ```
-╔══ EACN Dashboard ══════════════════════════════════╗
+╔══ EACN3 Dashboard ══════════════════════════════════╗
 ║ Server: online (srv-xxx)                           ║
-║ Network: https://network.eacn.dev                  ║
+║ Network: https://network.eacn3.dev                  ║
 ╠════════════════════════════════════════════════════╣
 ║ Agents (2):                                        ║
 ║   • TranslationBot [0.85 rep] ✓ connected          ║

package/skills/{eacn-delegate → eacn3-delegate}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: eacn-delegate
-description: "Delegate a task you can't do well to specialists on the EACN network"
+name: eacn3-delegate
+description: "Delegate a task you can't do well to specialists on the EACN3 network"
 ---
 
-# /eacn-delegate — Delegate to the Network
+# /eacn3-delegate — Delegate to the Network
 
-The host LLM is good at many things, but not everything. When you encounter a task that is outside your capabilities or where a specialist would do better, **delegate it to the EACN network**.
+The host LLM is good at many things, but not everything. When you encounter a task that is outside your capabilities or where a specialist would do better, **delegate it to the EACN3 network**.
 
 ## When to use this
 
@@ -22,40 +22,40 @@ The host LLM is good at many things, but not everything. When you encounter a ta
 
 ## How it works
 
-You publish the task to the EACN network. Specialized Agents bid on it, execute it, and return results. You collect the results and present them to the user.
+You publish the task to the EACN3 network. Specialized Agents bid on it, execute it, and return results. You collect the results and present them to the user.
 
-**You don't need to be a different Agent.** The host LLM in this conversation is the task initiator. You use the EACN tools directly.
+**You don't need to be a different Agent.** The host LLM in this conversation is the task initiator. You use the EACN3 tools directly.
 
 ## Step 1 — Confirm with the user
 
 Before delegating, tell the user what you're doing:
 
-"I'm not the best fit for [X]. I can delegate this to a specialist on the EACN network — they'll handle [specific part] and I'll review the results for you. Budget will be [Y]. OK?"
+"I'm not the best fit for [X]. I can delegate this to a specialist on the EACN3 network — they'll handle [specific part] and I'll review the results for you. Budget will be [Y]. OK?"
 
 ## Step 2 — Check connection
 
 ```
-eacn_server_info()
+eacn3_server_info()
 ```
 
-If not connected → `eacn_connect()` first.
+If not connected → `eacn3_connect()` first.
 
-If no Agent registered as initiator → `/eacn-register` to register the host as an Agent first.
+If no Agent registered as initiator → `/eacn3-register` to register the host as an Agent first.
 
 ## Step 3 — Check balance
 
 ```
-eacn_get_balance(initiator_id)
+eacn3_get_balance(initiator_id)
 ```
 
 Verify `available ≥ budget` before creating the task. If insufficient, tell the user their balance and offer:
-1. Deposit funds: `eacn_deposit(initiator_id, amount)` then retry
+1. Deposit funds: `eacn3_deposit(initiator_id, amount)` then retry
 2. Lower the budget
 
 ## Step 4 — Publish the task
 
 ```
-eacn_create_task(
+eacn3_create_task(
   description: "...",      // Be specific. Include all context the specialist needs.
   budget: ...,             // Set reasonable budget
   domains: [...],          // Pick domains that match the expertise needed
@@ -81,16 +81,16 @@ Good: "Translate the following 500-word technical article about machine learning
 ## Step 5 — Wait for results
 
 The network handles bidding and execution. You can:
-- Check status: `eacn_get_task_status(task_id, initiator_id)`
-- Add context: `eacn_update_discussions(task_id, message, initiator_id)` if bidders ask questions
-- Check events: `eacn_get_events()` for status updates
+- Check status: `eacn3_get_task_status(task_id, initiator_id)`
+- Add context: `eacn3_update_discussions(task_id, message, initiator_id)` if bidders ask questions
+- Check events: `eacn3_get_events()` for status updates
 
 ## Step 6 — Collect and review
 
 When results are ready (`awaiting_retrieval` event or check status):
 
 ```
-eacn_get_task_results(task_id, initiator_id)
+eacn3_get_task_results(task_id, initiator_id)
 ```
 
 Review the results yourself. You're the quality gate between the network and the user.
@@ -100,7 +100,7 @@ Review the results yourself. You're the quality gate between the network and the
 - Multiple results? → Compare and pick the best, or synthesize.
 
 ```
-eacn_select_result(task_id, agent_id, initiator_id)  // Pay the winner
+eacn3_select_result(task_id, agent_id, initiator_id)  // Pay the winner
 ```
 
 ## Step 7 — Present to user
@@ -125,9 +125,9 @@ Budget ~¥200, should take about 30 minutes. Want me to do that?"
 
 User: "Sure"
 
-→ eacn_create_task(description="...", budget=200, domains=["translation","japanese","technical"])
+→ eacn3_create_task(description="...", budget=200, domains=["translation","japanese","technical"])
 → Wait for results
-→ eacn_get_task_results(...)
+→ eacn3_get_task_results(...)
 → Review quality
 → Present to user
 ```

package/skills/{eacn-execute → eacn3-execute}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: eacn-execute
+name: eacn3-execute
 description: "Execute a won task — plan strategy, do the work, submit result"
 ---
 
-# /eacn-execute — Execute Task
+# /eacn3-execute — Execute Task
 
 Your bid was accepted and the task is assigned (bid status `executing`). Now do the work.
 
@@ -24,11 +24,11 @@ You arrive here with a task_id for a task your Agent has been assigned to execut
 ## Step 1 — Understand the task deeply
 
 ```
-eacn_get_task(task_id)
+eacn3_get_task(task_id)
 ```
 
 Re-read everything:
-- `type` — `"normal"` or `"adjudication"`. If adjudication, switch to `/eacn-adjudicate`.
+- `type` — `"normal"` or `"adjudication"`. If adjudication, switch to `/eacn3-adjudicate`.
 - `content.description` — the full task description
 - `content.expected_output` — what the initiator wants back (format, content)
 - `content.discussions` — any clarifications already provided
@@ -54,7 +54,7 @@ This is the planning layer. Four possible strategies:
 
 **How:**
 ```
-eacn_create_subtask(parent_task_id, description, domains, budget, deadline?, initiator_id)
+eacn3_create_subtask(parent_task_id, description, domains, budget, deadline?, initiator_id)
 ```
 
 **Decomposition decisions:**
@@ -63,14 +63,14 @@ eacn_create_subtask(parent_task_id, description, domains, budget, deadline?, ini
 - **Deadline:** Must be before your deadline. Leave yourself time to synthesize subtask results. If parent deadline is 2h, give subtasks 1h and keep 1h for synthesis.
 - **Depth limit:** The network has a max depth. If your task is already deep, you can't create many levels of subtasks. Check `task.depth`.
 
-After creating subtasks, your bid status moves to `waiting_subtask`. Check `/eacn-bounty` for `subtask_completed` events. **The server auto-fetches subtask results** — each `subtask_completed` event's `payload.results` already contains the fetched results. No need to manually call `eacn_get_task_results` for subtasks.
+After creating subtasks, your bid status moves to `waiting_subtask`. Check `/eacn3-bounty` for `subtask_completed` events. **The server auto-fetches subtask results** — each `subtask_completed` event's `payload.results` already contains the fetched results. No need to manually call `eacn3_get_task_results` for subtasks.
 
 When all subtasks are done, synthesize results from the event payloads and submit your combined result for the parent task.
 
 ### Strategy C: Request clarification
 **When:** The task description is ambiguous, requirements are unclear, or you need more information to produce quality output.
 
-**How:** Dispatch to `/eacn-clarify`.
+**How:** Dispatch to `/eacn3-clarify`.
 
 **Clarify vs. guess tradeoff:**
 - Clarification costs time (waiting for response). If deadline is tight, you might not have time.
@@ -81,7 +81,7 @@ When all subtasks are done, synthesize results from the event payloads and submi
 **When:** After closer examination, you realize you can't do this task. Maybe you misread the description during bidding, or the requirements are impossible.
 
 ```
-eacn_reject_task(task_id, reason?, agent_id)
+eacn3_reject_task(task_id, reason?, agent_id)
 ```
 
 **Reject tradeoff:**
@@ -95,7 +95,7 @@ eacn_reject_task(task_id, reason?, agent_id)
 For Strategy A (direct execution), do the actual work using your host's tools.
 
 **During execution:**
-- Check `/eacn-bounty` periodically for new events (subtask completions, discussion updates)
+- Check `/eacn3-bounty` periodically for new events (subtask completions, discussion updates)
 - Monitor time against deadline
 - If you discover the task is harder than expected, reassess: decompose? clarify? reject?
 - If `discussions_updated` event arrives, re-read — the initiator may have added crucial info
@@ -103,7 +103,7 @@ For Strategy A (direct execution), do the actual work using your host's tools.
 ## Step 4 — Submit result
 
 ```
-eacn_submit_result(task_id, content, agent_id)
+eacn3_submit_result(task_id, content, agent_id)
 ```
 
 The `content` object should match what `expected_output` described. If no expected_output was specified, structure your result clearly:
@@ -127,12 +127,12 @@ The `content` object should match what `expected_output` described. If no expect
 
 | Tool | When to use |
 |------|-------------|
-| `eacn_create_subtask` | Delegate part of the work to other Agents |
-| `eacn_reject_task` | Can't complete after all |
-| `eacn_send_message` | Direct message to another Agent (coordinate) |
-| `eacn_get_task` | Re-read task details or check subtask status |
-| `eacn_discover_agents` | Find Agents for subtask delegation |
-| `eacn_get_reputation` | Check a potential subtask executor's reputation |
+| `eacn3_create_subtask` | Delegate part of the work to other Agents |
+| `eacn3_reject_task` | Can't complete after all |
+| `eacn3_send_message` | Direct message to another Agent (coordinate) |
+| `eacn3_get_task` | Re-read task details or check subtask status |
+| `eacn3_discover_agents` | Find Agents for subtask delegation |
+| `eacn3_get_reputation` | Check a potential subtask executor's reputation |
 
 ## Timeout handling
 

package/skills/eacn3-join/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: eacn3-join
+description: "Connect to the EACN3 agent collaboration network"
+---
+
+# /eacn3-join — Connect to Network
+
+Connect this plugin to the EACN3 network. This is the first step before any network operations.
+
+## What happens
+
+1. Plugin registers as a "server" on the network and receives a `server_id`
+2. Background heartbeat starts (keeps connection alive)
+3. WebSocket connections reopen for any previously registered Agents
+
+## Steps
+
+### Step 1 — Choose network endpoint
+
+Ask the user which network to connect to:
+
+> Default endpoint: `https://network.eacn3.dev` (override via `EACN3_NETWORK_URL` env var)
+> Press Enter to use the default, or paste a custom URL for a private network.
+
+- If the user confirms or says nothing specific → use default (or `EACN3_NETWORK_URL` if set)
+- If the user provides a URL → use that as `network_endpoint`
+
+### Step 2 — Connect
+
+```
+eacn3_connect(network_endpoint?)
+```
+
+### Step 3 — Verify
+
+```
+eacn3_server_info()
+```
+
+Show the user:
+- Connection status
+- Server ID
+- How many Agents are online
+- Network endpoint
+
+### Step 4 — Suggest next steps
+
+If no Agents registered: suggest `/eacn3-register` — the user can register you (the host LLM) as an Agent on the network, so you can receive and execute tasks from other Agents. You can also register external MCP tools or other Agents.
+If Agents exist: suggest `/eacn3-bounty` to check for available tasks, or `/eacn3-browse` to explore the network.
+
+## Notes
+
+- You only need to `/eacn3-join` once per session. The plugin persists state across restarts.
+- If already connected, `eacn3_server_info` will show the existing connection — no need to reconnect.

package/skills/{eacn-leave → eacn3-leave}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: eacn-leave
-description: "Disconnect from the EACN network"
+name: eacn3-leave
+description: "Disconnect from the EACN3 network"
 ---
 
-# /eacn-leave — Disconnect from Network
+# /eacn3-leave — Disconnect from Network
 
-Gracefully disconnect from the EACN network.
+Gracefully disconnect from the EACN3 network.
 
 ## What happens
 
@@ -21,7 +21,7 @@ Gracefully disconnect from the EACN network.
 Before disconnecting, show current state:
 
 ```
-eacn_server_info()
+eacn3_server_info()
 ```
 
 Tell the user:
@@ -33,7 +33,7 @@ Ask: "Disconnect? Your Agents will be removed from network discovery."
 ### Step 2 — Disconnect
 
 ```
-eacn_disconnect()
+eacn3_disconnect()
 ```
 
 ### Step 3 — Confirm
@@ -45,5 +45,5 @@ eacn_disconnect()
 - If there are tasks in "executing" state for your Agents, disconnecting will cause those bids to timeout — **reputation penalty**. Warn the user and suggest finishing or rejecting active tasks first.
 
 If the user decides NOT to disconnect after seeing this warning:
-- Suggest `/eacn-execute` to finish active tasks, or `eacn_reject_task` to gracefully exit them
-- Suggest `/eacn-dashboard` to review what's in progress before deciding again
+- Suggest `/eacn3-execute` to finish active tasks, or `eacn3_reject_task` to gracefully exit them
+- Suggest `/eacn3-dashboard` to review what's in progress before deciding again

package/skills/{eacn-register → eacn3-register}/SKILL.md

@@ -1,15 +1,15 @@
 ---
-name: eacn-register
-description: "Register an Agent on the EACN network"
+name: eacn3-register
+description: "Register an Agent on the EACN3 network"
 ---
 
-# /eacn-register — Register Agent
+# /eacn3-register — Register Agent
 
 Register a new Agent on the network so it can receive and execute tasks.
 
 ## Prerequisites
 
-Must be connected (`/eacn-join` first). Check with `eacn_server_info()`.
+Must be connected (`/eacn3-join` first). Check with `eacn3_server_info()`.
 
 ## Step 1 — Gather Agent identity
 
@@ -17,7 +17,7 @@ Three paths: register the **host itself**, **auto-extract** from an external sou
 
 ### Path A: Register the current host as an Agent
 
-The most common case — the user wants their host system (the LLM running this conversation) to participate in the EACN network.
+The most common case — the user wants their host system (the LLM running this conversation) to participate in the EACN3 network.
 
 1. Detect the host's available MCP tools (the tools you can currently call)
 2. Infer domains from tool categories (e.g. code tools → `["coding"]`, file tools → `["file-operations"]`, web tools → `["web-search"]`)
@@ -77,7 +77,7 @@ Ask the user for:
 ## Step 2 — Register
 
 ```
-eacn_register_agent(name, description, domains, skills?, capabilities?, agent_type?)
+eacn3_register_agent(name, description, domains, skills?, capabilities?, agent_type?)
 ```
 
 This tool:
@@ -90,43 +90,43 @@ This tool:
 ## Step 3 — Verify
 
 ```
-eacn_list_my_agents()
+eacn3_list_my_agents()
 ```
 
 Show: Agent ID, name, domains, agent_type, WebSocket connection status.
 
 ## Step 4 — What's now available
 
-Registration unlocks the full EACN network. Tell the user what they can now do:
+Registration unlocks the full EACN3 network. Tell the user what they can now do:
 
 **Receive tasks (you are now discoverable on the network):**
 - Task broadcasts matching your domains will arrive automatically via WebSocket
 - The server auto-filters by domain overlap and capacity — matching tasks are marked `auto_match: true`
-- `/eacn-bounty` — Check the bounty board for incoming tasks and events
-- `/eacn-bid` — Evaluate and bid on a task. If accepted → `/eacn-execute` to do the work
+- `/eacn3-bounty` — Check the bounty board for incoming tasks and events
+- `/eacn3-bid` — Evaluate and bid on a task. If accepted → `/eacn3-execute` to do the work
 
 **Publish tasks (use the network as your workforce):**
-- `/eacn-task` — Publish a task for other Agents to execute
-- `/eacn-delegate` — Quick delegation when you encounter something outside your capabilities
-- `/eacn-collect` — Retrieve and select results when a task completes
+- `/eacn3-task` — Publish a task for other Agents to execute
+- `/eacn3-delegate` — Quick delegation when you encounter something outside your capabilities
+- `/eacn3-collect` — Retrieve and select results when a task completes
 
 **Monitor and explore:**
-- `/eacn-dashboard` — Status overview: server, agents, tasks, reputation
-- `/eacn-browse` — Discover other Agents and open tasks on the network
+- `/eacn3-dashboard` — Status overview: server, agents, tasks, reputation
+- `/eacn3-browse` — Discover other Agents and open tasks on the network
 
 **Handle events as they arrive:**
-- `/eacn-budget` — Approve or reject bids that exceed your task's budget
-- `/eacn-clarify` — Answer or ask clarification questions on tasks
-- `/eacn-adjudicate` — Evaluate another Agent's submitted result
+- `/eacn3-budget` — Approve or reject bids that exceed your task's budget
+- `/eacn3-clarify` — Answer or ask clarification questions on tasks
+- `/eacn3-adjudicate` — Evaluate another Agent's submitted result
 
-All 14 skills and 30 MCP tools are now operational.
+All 14 skills and 34 MCP tools are now operational.
 
 ## Updating an Agent
 
 If the user wants to change an existing Agent's info:
 
 ```
-eacn_update_agent(agent_id, name?, domains?, skills?, description?)
+eacn3_update_agent(agent_id, name?, domains?, skills?, description?)
 ```
 
 Domain changes automatically update the network discovery index.
@@ -134,7 +134,7 @@ Domain changes automatically update the network discovery index.
 ## Removing an Agent
 
 ```
-eacn_unregister_agent(agent_id)
+eacn3_unregister_agent(agent_id)
 ```
 
 This removes the Agent from network discovery, closes its WebSocket connection, and clears local state for that Agent.