fix: expose conversation distill proxy tool

Merged after local bridge syntax validation and successful GitHub checks.

Author: autogame-17

README.md

@@ -41,6 +41,7 @@ local EvoMap Proxy mailbox as tools:
 | `evolver_search_assets` | Search the network for reusable genes/capsules by signal. |
 | `evolver_fetch_asset` | Fetch full asset content by id. |
 | `evolver_publish_asset` | Queue a gene/capsule for Hub review. |
+| `evolver_distill_conversation` | Distill a high-confidence reusable conversation outcome into a local Gene/Capsule and queue it for Hub review. |
 | `evolver_poll` | Poll the local mailbox (asset results, hub events, tasks). |
 
 It also ships a **`capability-evolver` skill** (recall → work → record loop) and

commands/distill.md

@@ -6,6 +6,8 @@ allowed-tools: Bash
 
 Distill Evolver run history into a reusable skill/gene.
 
+If `evolver_distill_conversation` is available in the MCP tool list and the reusable lesson came from this conversation, prefer calling that tool first with a concrete summary, signals, strategy, artifacts, and validation evidence. It lets the local Proxy quality-gate, persist, and queue Hub publishing for the resulting Gene/Capsule.
+
 ```bash
 EVOLVER="evolver"; command -v evolver >/dev/null 2>&1 || EVOLVER="npx -y @evomap/evolver"
 $EVOLVER distill $ARGUMENTS

mcp/evolver-proxy.mjs

@@ -141,6 +141,32 @@ const TOOLS = [
     },
     handler: (a) => proxyFetch('POST', '/asset/submit', { assets: a.assets }),
   },
+  {
+    name: 'evolver_distill_conversation',
+    description: 'Distill a reusable Gene/Capsule from the current Claude Code conversation. Provide a concrete summary, strategy/evidence, artifacts, and validation; the Proxy gates quality, stores locally, and queues Hub publishing.',
+    inputSchema: {
+      type: 'object',
+      properties: {
+        title: { type: 'string' },
+        summary: { type: 'string', description: 'Concrete reusable lesson or capability distilled from the conversation.' },
+        platform: { type: 'string', default: 'claude-code' },
+        thread_id: { type: 'string' },
+        user_prompt: { type: 'string' },
+        assistant_summary: { type: 'string' },
+        transcript: { type: 'string' },
+        signals: { type: 'array', items: { type: 'string' } },
+        strategy: { type: 'array', items: { type: 'string' } },
+        artifacts: { type: 'array', items: { type: 'string' } },
+        validation: { type: 'array', items: { type: 'string' } },
+        persist: { type: 'boolean', default: true },
+        publish: { type: 'boolean', default: true },
+        min_score: { type: 'integer', minimum: 1, maximum: 10, default: 5 },
+      },
+      required: ['summary'],
+      additionalProperties: false,
+    },
+    handler: (a) => proxyFetch('POST', '/conversation/distill', { ...a, platform: a.platform || 'claude-code' }),
+  },
   {
     name: 'evolver_poll',
     description: 'Poll the local mailbox for inbound messages by type, e.g. "asset_submit_result" (Hub review decisions), "hub_event", or "task_available". Returns and does not auto-acknowledge.',

skills/capability-evolver/SKILL.md

@@ -82,7 +82,9 @@ EvoMap Proxy mailbox:
 - `evolver_search_assets` — find reusable genes/capsules by signal. **Call this
   before substantive work** to reuse proven approaches instead of reinventing them.
 - `evolver_status` — Proxy state (node id, pending counts, last sync).
-- `evolver_fetch_asset` / `evolver_publish_asset` / `evolver_poll`.
+- `evolver_fetch_asset` / `evolver_publish_asset` / `evolver_distill_conversation` / `evolver_poll`.
+
+Use `evolver_distill_conversation` only when the current conversation produced a concrete reusable capability. Include a summary, strategy steps, artifact paths/links, and validation evidence so the Proxy can reject weak or noisy candidates.
 
 The tools degrade gracefully when the Proxy isn't running (the local memory hooks
 still work). The richer, full `gep_*` surface is the separate