fix(examples): correct stale import path in remote-agent/run.py

The old path `sdk/python/` no longer exists in the standalone
molecule-sdk-python repo. Update the local-dev import path to add
the repo root to sys.path, which correctly resolves molecule_agent
when running the script from a repo checkout.

Also update the Usage section to use the correct relative path
(`examples/remote-agent/run.py` instead of `python3 run.py`)
and update the "What it doesn't do" docstring to reflect that
Phase 30.8b (inbound A2A) is now shipped.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

examples/remote-agent/README.md

@@ -27,7 +27,7 @@ curl -s -X POST http://localhost:8080/workspaces/<UUID>/secrets \
 
 # 3. Run the demo from any machine that can reach the platform:
 WORKSPACE_ID=<UUID> PLATFORM_URL=http://localhost:8080 \
-    python3 examples/remote-agent/run.py
+    python3 sdk/python/examples/remote-agent/run.py
 ```
 
 You should see log lines for each of the three phases, and then

examples/remote-agent/run.py

@@ -8,9 +8,11 @@ What this does:
 3. Runs a heartbeat + state-poll loop; exits cleanly when the platform
    reports the workspace paused or deleted.
 
-What it doesn't do (future 30.8b work):
-- Host an inbound A2A server. Platform-initiated calls to this agent
-  won't reach it unless you expose one yourself.
+What it doesn't do (see run_agent_loop for the full version):
+- Host an inbound A2A server. Use run_agent_loop(handler) instead of
+  run_heartbeat_loop() to also receive inbound A2A messages and reply
+  via the platform's /notify (canvas user) and /a2a (peer agent) endpoints.
+  The reply transport is auto-selected based on message source.
 
 Usage:
     # One-time setup on the platform side:
@@ -26,7 +28,7 @@ Usage:
         -d '{"key":"REMOTE_DEMO_KEY","value":"hello-from-remote"}'
 
     # Now run this script from any machine that can reach the platform:
-    WORKSPACE_ID=<id> PLATFORM_URL=http://localhost:8080 python3 run.py
+    WORKSPACE_ID=<id> PLATFORM_URL=http://localhost:8080 python3 examples/remote-agent/run.py
 
 Environment variables:
     WORKSPACE_ID    (required)
@@ -41,12 +43,14 @@ import os
 import sys
 
 # Local-dev import path — when installed via pip the molecule_agent package
-# resolves normally; when running from the repo checkout we add sdk/python/
-# to sys.path so you can run `python3 run.py` without a pip install.
+# resolves normally; when running from the repo checkout we add the repo root
+# to sys.path so you can run `python3 examples/remote-agent/run.py` without
+# a pip install.
 _here = os.path.dirname(os.path.abspath(__file__))
-_sdk = os.path.join(_here, "..", "..", "sdk", "python")
-if os.path.isdir(_sdk) and _sdk not in sys.path:
-    sys.path.insert(0, _sdk)
+_repo_root = os.path.normpath(os.path.join(_here, "..", ".."))
+_molecule_agent = os.path.join(_repo_root, "molecule_agent")
+if os.path.isdir(_molecule_agent) and _repo_root not in sys.path:
+    sys.path.insert(0, _repo_root)
 
 from molecule_agent import RemoteAgentClient  # noqa: E402
 

molecule_agent/README.md

@@ -60,7 +60,7 @@ print(f"loop exited: {terminal}")
 ```
 
 A runnable demo with full setup walkthrough lives at
-[`examples/remote-agent/`](https://git.moleculesai.app/Molecule-AI/molecule-sdk-python/-/tree/main/examples/remote-agent) — the runnable demo with full setup walkthrough.
+[`sdk/python/examples/remote-agent/`](../examples/remote-agent).
 
 ## What the SDK gives you
 
@@ -282,5 +282,5 @@ the security benefits of bearer auth until both sides upgrade.
 
 - [`molecule_plugin`](../molecule_plugin) — the *other* SDK in this
   package, for plugin authors. Different audience.
-- [`examples/remote-agent/run.py`](https://git.moleculesai.app/Molecule-AI/molecule-sdk-python/-/blob/main/examples/remote-agent/run.py)
+- [`sdk/python/examples/remote-agent/run.py`](../examples/remote-agent/run.py)
   — the runnable demo that proves all of the above end-to-end.

molecule_agent/__init__.py

@@ -20,7 +20,7 @@ Intended usage::
     env = client.pull_secrets()      # decrypted secrets dict
     client.run_heartbeat_loop()      # background heartbeat + state-poll
 
-See ``examples/remote-agent/`` for a runnable demo.
+See ``sdk/python/examples/remote-agent/`` for a runnable demo.
 
 Design notes:
 * **No async.** The SDK uses blocking ``requests`` so a remote agent author

molecule_agent/client.py

@@ -11,19 +11,10 @@ a Phase 30 endpoint:
 * :py:meth:`run_heartbeat_loop` — drives heartbeat + state-poll on a timer,
   returns when the platform reports the workspace paused or deleted.
 
-The client also exposes two inbound delivery paths for handling platform-initiated
-A2A messages:
-
-* **Push mode** — :class:`molecule_agent.a2a_server.A2AServer` hosts an HTTP server
-  in a background thread; platform pushes inbound A2A as HTTP requests. Use when the
-  agent has a publicly reachable URL (cloud VM, ngrok tunnel, etc.).
-* **Poll mode** — :class:`molecule_agent.inbound.PollDelivery` polls
-  ``GET /workspaces/:id/activity`` on a configurable interval; no public URL required.
-  The default when no explicit delivery is passed to :py:meth:`run_agent_loop`.
-
-Both feed the same :py:class:`molecule_agent.inbound.MessageHandler` callback.
-Reply routing (``/notify`` for canvas users, ``/a2a`` for peer agents) is handled
-automatically by :py:meth:`reply`.
+No inbound A2A server is bundled here yet — that requires hosting an HTTP
+endpoint the platform's proxy can reach, which is network-dependent.
+Use :class:`molecule_agent.a2a_server.A2AServer` to add inbound A2A support.
+See that module for usage and the Phase 30.8b contract.
 """
 from __future__ import annotations
 

molecule_plugin/__init__.py

@@ -26,7 +26,7 @@ Example: a minimal plugin that's installable on Claude Code and DeepAgents
         ├── claude_code.py   # `from molecule_plugin import AgentskillsAdaptor as Adaptor`
         └── deepagents.py    # same one-liner
 
-Full docs + cookiecutter template: see the repo root ``README.md``.
+Full docs + cookiecutter template: see ``sdk/python/README.md``.
 """
 
 from __future__ import annotations