feat(ci): add CI / all-required sentinel job

Renames workflow name from "Test" → "CI" and adds an all-required
sentinel job that aggregates the 3.11/3.12/3.13 matrix results into
a single CI / all-required (pull_request) context.

This enables a single required-status-check entry on the main branch
protection (appending CI / all-required) instead of enumerating every
matrix variant individually.

Implements: molecule-ai/molecule-sdk-python#11

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

.gitea/workflows/ci.yml

@@ -1,4 +1,4 @@
-name: Test
+name: CI
 
 on:
   push:
@@ -27,3 +27,24 @@ jobs:
 
       - name: Lint
         run: pip install ruff && ruff check molecule_agent/ molecule_plugin/
+
+  all-required:
+    name: all-required
+    needs: [test]
+    # required: all matrix variants must succeed
+    if: always()
+    runs-on: ubuntu-latest
+    steps:
+      - name: Verify all required jobs passed
+        run: |
+          # Collect results from all test matrix variants
+          results="${{ needs.test.result }}"
+          echo "Matrix results: $results"
+          # Any result that is not "success" is a failure condition
+          if [[ "$results" == *"failure"* ]] || \
+             [[ "$results" == *"cancelled"* ]] || \
+             [[ "$results" == *"skipped"* ]]; then
+            echo "One or more required jobs did not succeed: $results"
+            exit 1
+          fi
+          echo "All required jobs passed."

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

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