pikuri-mcp 0.0.3 → 0.0.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3b512b9e2c5bacf829cee8104a9198b36d94d7d09b110060e7524e5e82ae70a0
-  data.tar.gz: c36e458112d63a32ca0dad35c3b0ab4b07cd934347b7bfd4fe488ac252ccd64c
+  metadata.gz: c066dca9ef2c73cfa77613804066d2ca86db07a798d879f62d0b48c82906f677
+  data.tar.gz: 396a24732a4a023760f7c396e7c2a8bb9fd6274480f1f8bc4b823861cc4bfc24
 SHA512:
-  metadata.gz: 89059a85a63a60cc2f69d64e881df7fb3fb005b64850040a5b696f4b4c6e862d28af77cb8e815f1a4bf259b3fd5ff720684c1a4fb5a16529c68596a7459ccd5e
-  data.tar.gz: 5e31d7cc61ba3f802b2888d9078ba22de7fd132b82f2874e7daf483212de42b53aa608aa76e961bb69f44877acfa03871139acbba2caf594d7c128f95eeafa45
+  metadata.gz: 9356e92ffb908e79ae87217573b5cdd111665d2747dad2e9cd87fc31b07a335acb1aa75c747b515fb09a70bd89d5b665737998a9032bf70257aa29acea9ba5c7
+  data.tar.gz: 30e6add87c9b4d824b84e59d6abc62ee8911929aa7890124e4045a29340d2152f153419c60262824d6ae2409406d8c120e601d60113e21300b48a4588834c9d4

data/README.md

@@ -52,3 +52,16 @@ the system prompt, and registers a close handler so the agent's
 per-agent `mcp_connect` tool — sub-agents share the live MCP clients
 via the same extension instance but each has its own connect tool +
 activation set.
+
+## Further reading
+
+- **Narrative walkthrough:** [chapter 5 of the
+  guide](../docs/guide/05-mcp.md) is the gentle MCP intro — one
+  low-stakes server, no Docker, the verifier and synthesizer in
+  depth. [Chapter 10](../docs/guide/10-mcp-revisited.md) picks
+  the thread back up at the harder end: the official GitHub MCP
+  in Docker, npx- and pip-based community servers, Playwright,
+  and the full threat model.
+- **API reference:** browse the YARD docs at
+  <https://rubydoc.info/gems/pikuri-mcp> (once published), or run
+  `bundle exec yard` in this directory for a local copy.

data/lib/pikuri/mcp/extension.rb

@@ -13,14 +13,14 @@ module Pikuri
     # == Configure / bind split
     #
     # +configure+ runs once on the parent's Configurator and creates
-    # the *shared* {Mcp::Servers} runtime — that's the resource
-    # extensions own. +bind+ fires per agent (parent + each
-    # sub-agent in Step 4's world) and creates a *fresh* {Connect}
-    # tool keyed to whichever agent is being bound, registered via
-    # {Agent#internal_add_tool} so it lands only on that agent's
-    # +RubyLLM::Chat+ (not in pikuri's +@tools+ list — sub-agents
-    # therefore don't inherit the parent's connect tool through the
-    # snapshot, and each agent's activation Set stays per-agent).
+    # the *shared* {Mcp::Servers} runtime — that's the resource the
+    # extension owns. +bind+ fires once on the parent agent and
+    # installs a +Connect+ tool keyed to it, registered via
+    # {Agent#internal_add_tool} so the tool's +execute+ closure can
+    # call back into the right chat when the LLM activates a server.
+    # Sub-agents do not inherit extensions, so they receive neither
+    # the +Connect+ tool nor any MCP-backed tools — personas own
+    # their toolset by construction.
     #
     # == Usage
     #

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pikuri-mcp
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
 platform: ruby
 authors:
 - Martin Vysny
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-05-22 00:00:00.000000000 Z
+date: 2026-05-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: pikuri-core
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.0.3
+        version: 0.0.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 0.0.3
+        version: 0.0.4
 - !ruby/object:Gem::Dependency
   name: mcp
   requirement: !ruby/object:Gem::Requirement