agenticdome-python-sdk 1.2.35__tar.gz → 1.2.37__tar.gz

{agenticdome_python_sdk-1.2.35 → agenticdome_python_sdk-1.2.37}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agenticdome-python-sdk
-Version: 1.2.35
+Version: 1.2.37
 Summary: Official Python SDK for AgenticDome security guardrails, DLP, tool authorization, and multi-agent delegation enforcement.
 Author: AgenticDome
 License-Expression: Apache-2.0
@@ -33,7 +33,7 @@ Requires-Dist: requests>=2.31.0
 Requires-Dist: urllib3>=2.0.0
 Requires-Dist: cryptography>=42.0.0
 Provides-Extra: crewai
-Requires-Dist: crewai<=1.15.22,>=1.15.5; extra == "crewai"
+Requires-Dist: crewai<=1.15.23,>=1.15.5; extra == "crewai"
 Provides-Extra: redis
 Requires-Dist: redis>=4.5.0; extra == "redis"
 Provides-Extra: pop
@@ -46,7 +46,7 @@ Requires-Dist: pydantic-ai<=2.51.0,>=2.16.0; extra == "pydantic"
 Requires-Dist: anyio>=4.0.0; extra == "pydantic"
 Provides-Extra: langgraph
 Requires-Dist: langgraph<=1.2.12,>=1.2.9; extra == "langgraph"
-Requires-Dist: langchain-core<=1.6.5,>=1.5.0; extra == "langgraph"
+Requires-Dist: langchain-core<=1.6.6,>=1.5.0; extra == "langgraph"
 Requires-Dist: langchain-openai==1.3.5; extra == "langgraph"
 Requires-Dist: anyio>=4.0.0; extra == "langgraph"
 Provides-Extra: microsoft
@@ -64,9 +64,9 @@ Requires-Dist: openai-agents<=0.22.3,>=0.18.3; extra == "openai-agents"
 Provides-Extra: mcp
 Requires-Dist: mcp<=2.2.0,>=1.26.0; extra == "mcp"
 Provides-Extra: bedrock
-Requires-Dist: boto3<=1.43.103,>=1.43.54; extra == "bedrock"
+Requires-Dist: boto3<=1.43.105,>=1.43.54; extra == "bedrock"
 Provides-Extra: aws-bedrock
-Requires-Dist: boto3<=1.43.103,>=1.43.54; extra == "aws-bedrock"
+Requires-Dist: boto3<=1.43.105,>=1.43.54; extra == "aws-bedrock"
 Provides-Extra: llamaindex
 Requires-Dist: llama-index<=0.14.25,>=0.14.23; extra == "llamaindex"
 Provides-Extra: llama-index
@@ -76,19 +76,19 @@ Requires-Dist: google-adk<=2.10.0,>=2.5.0; extra == "google-adk"
 Provides-Extra: adk
 Requires-Dist: google-adk<=2.10.0,>=2.5.0; extra == "adk"
 Provides-Extra: claude
-Requires-Dist: claude-agent-sdk<=0.2.160,>=0.2.126; extra == "claude"
+Requires-Dist: claude-agent-sdk<=0.2.162,>=0.2.126; extra == "claude"
 Provides-Extra: claude-agent-sdk
-Requires-Dist: claude-agent-sdk<=0.2.160,>=0.2.126; extra == "claude-agent-sdk"
+Requires-Dist: claude-agent-sdk<=0.2.162,>=0.2.126; extra == "claude-agent-sdk"
 Provides-Extra: smolagents
 Requires-Dist: smolagents==1.26.0; extra == "smolagents"
 Provides-Extra: all
-Requires-Dist: crewai<=1.15.22,>=1.15.5; extra == "all"
+Requires-Dist: crewai<=1.15.23,>=1.15.5; extra == "all"
 Requires-Dist: redis>=4.5.0; extra == "all"
 Requires-Dist: cryptography>=42.0.0; extra == "all"
 Requires-Dist: pydantic-ai<=2.51.0,>=2.16.0; extra == "all"
 Requires-Dist: anyio>=4.0.0; extra == "all"
 Requires-Dist: langgraph<=1.2.12,>=1.2.9; extra == "all"
-Requires-Dist: langchain-core<=1.6.5,>=1.5.0; extra == "all"
+Requires-Dist: langchain-core<=1.6.6,>=1.5.0; extra == "all"
 Requires-Dist: langchain-openai==1.3.5; extra == "all"
 Requires-Dist: autogen-agentchat==0.7.5; extra == "all"
 Requires-Dist: agno<=3.0.11,>=2.8.0; extra == "all"
@@ -96,10 +96,10 @@ Requires-Dist: azure-ai-projects<=2.7.0,>=2.3.0; extra == "all"
 Requires-Dist: azure-identity==1.25.3; extra == "all"
 Requires-Dist: openai-agents<=0.22.3,>=0.18.3; extra == "all"
 Requires-Dist: mcp<=2.2.0,>=1.26.0; extra == "all"
-Requires-Dist: boto3<=1.43.103,>=1.43.54; extra == "all"
+Requires-Dist: boto3<=1.43.105,>=1.43.54; extra == "all"
 Requires-Dist: llama-index<=0.14.25,>=0.14.23; extra == "all"
 Requires-Dist: google-adk<=2.10.0,>=2.5.0; extra == "all"
-Requires-Dist: claude-agent-sdk<=0.2.160,>=0.2.126; extra == "all"
+Requires-Dist: claude-agent-sdk<=0.2.162,>=0.2.126; extra == "all"
 Requires-Dist: smolagents==1.26.0; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0.0; extra == "dev"
@@ -177,16 +177,60 @@ agenticdome inspect --output agenticdome-inspection.json
 
 `init` writes the secret-free inspection and local configuration. For the
 certified onboarding path, obtain the assigned sidecar and a dedicated
-`integration_copilot` key, run `agenticdome integrate preview`, review its
+`integration_copilot` key, run `agenticdome integrate preview` and
+`agenticdome integrate status`, review the saved
 local exact diff and change summary, explicitly approve a supported edit or
 attach other boundaries manually, then run
 `agenticdome verify --run-tests --output .agenticdome/verification.json`.
-Preview obtains the private, signed, catalog-bound semantic plan and keeps
+
+If a coding assistant has already made and tested the application edits,
+import its canonical `AgenticDome_Integration.md` in the customer portal and
+run `agenticdome validate-report --report AgenticDome_Integration.md` from
+that same deployable workload. Import the two generated, hash-bound JSON files
+in Onboarding. This avoids repeating the guided edit plan; the Markdown counts
+remain AI-reported and a real action-path test is still required before
+claiming protection. See the [customer onboarding guide](docs/customer-onboarding.md).
+
+For the Pilot path, preview obtains the private, signed, catalog-bound semantic plan and keeps
 application source on your machine. `agenticdome integrate apply` creates a
 local Git review branch but never commits, pushes or deploys. Existing-source
-automatic edits are currently limited to one exact certified smolagents run
-pattern; all other paths need manual integration. The older `agenticdome plan`
+automatic edits cover unambiguous CrewAI bootstrap, PydanticAI `Agent(...)`,
+LangChain `create_agent(...)`, Google ADK agent construction, Claude options,
+Agno `Agent(...)`, direct LlamaIndex `FunctionTool.from_defaults(...)`, direct
+OpenAI Agents `FunctionTool(...)` handlers, explicit custom-Python tool
+dispatchers, and the exact smolagents run pattern.
+The CLI leaves dynamic construction,
+existing handwritten AgenticDome calls, MCP forwarding and other framework
+paths for explicit review; a patch never proves all routes are intercepted.
+The older `agenticdome plan`
 and `agenticdome scaffold` remain available as advanced review-only commands.
+Preview auto-selects an application or pure-MCP review path and reports
+existing Python SDK call-site candidates, including handwritten local
+wrappers. Discovery uses the versioned framework hook catalog plus documented
+prompt, tool, A2A/delegation, MCP and output API methods; categories may
+overlap and TypeScript call sites are not parsed by this Python checker. Mixed
+application/MCP workloads get a separate MCP review path.
+Each preview rescans the selected workload. If code added a framework after
+`init`, its certified hook contract is included in the new plan and flagged for
+review without changing `.agenticdome/config.json`; a framework still in that
+config but absent from the current scan is flagged for confirmation. Run
+`agenticdome integrate status` for the saved next action and import a fresh
+`agenticdome inspect --output agenticdome-inspection.json` after reviewing it.
+These static observations do not prove interception; the CLI avoids
+overlapping automatic rewrites and requires real blocked-action tests.
+
+For one consequential tool, run your own safe integration test through the
+actual application route with an `ExecutionSpy` around its test handler, then
+correlate the SDK adapter call, live-mode verdict and handler invocation:
+
+```bash
+agenticdome verify-action --tool billing.refund --expect-verdict BLOCKED --expect-executed no -- pytest -q tests/test_blocked_refund.py
+```
+
+The test must call `spy.assert_calls(0)` (or `1` for an allowed test); see the
+[real action-path test guide](docs/customer-onboarding.md#prove-one-real-action-path).
+This opt-in command does not execute a business action itself, and a fixed
+`agenticdome verify` probe is not a substitute for the real-path test.
 
 For an MCP client, host, gateway or server workload, use the focused path:
 
@@ -224,6 +268,7 @@ openclaw plugins install npm:agenticdome-openclaw-security
 openclaw plugins enable agenticdome-security
 openclaw config set plugins.entries.agenticdome-security.hooks.allowConversationAccess true
 openclaw gateway restart
+openclaw gateway status --require-rpc
 agenticdome openclaw protect
 # With AGENTICDOME_API_BASE, AGENTICDOME_TENANT_ID and the dedicated
 # AGENTICDOME_COPILOT_API_KEY set, generate and review the signed plan:
@@ -232,8 +277,11 @@ agenticdome plan
 agenticdome openclaw verify --output .agenticdome/verification.json
 ```
 
-`openclaw protect` fails unless the active OpenClaw runtime reports the loaded
-AgenticDome plugin, explicit consent and the exact certified typed hooks.
+`openclaw protect` checks the AgenticDome plugin, explicit consent and exact
+typed hooks in the inspecting CLI process. `gateway status` checks the serving
+Gateway's RPC reachability; neither proves that this Gateway ran a hook on a
+customer tool call. Exercise a safe tool through the actual Gateway and inspect
+the matching AgenticDome runtime decision before claiming that route is protected.
 The official `openclaw plugins install`, `enable`, `config set` and gateway
 restart commands are the actual runtime configuration change; the Python CLI
 does not apply or undo them. No application source patch is needed for native
@@ -246,7 +294,8 @@ includes the MCP transport rehearsal and both `mcp_verification` and
 `openclaw_verification` in one report. Both sections must be ready before the
 report is imported; `mcp verify` alone is not a combined-workload proof. The
 customer Control Panel separately confirms tenant binding and retained
-telemetry; neither command silently modifies customer source.
+telemetry for its probes; neither command silently modifies customer source or
+proves that every live Gateway tool route was intercepted.
 
 When `.agenticdome/inspection.json` is imported into Developer Integration,
 the Control Panel adds its detected frameworks to the workload. Frameworks,
@@ -1582,6 +1631,13 @@ async def lookup_customer(customer_id: str) -> str:
     )
 ```
 
+If you construct `agents.FunctionTool` directly, its `on_invoke_tool`
+handler receives JSON text. Use `handler_args_format="json"` with
+`wrap_tool_handler` so the approved or sanitized arguments reach the original
+handler in that same format. The guided integration preview offers this edit
+only for a direct, statically named `FunctionTool` with an identifiable
+handler; other tool factories require manual review and a real-route test.
+
 **Delegated specialist tool pattern:**
 
 ```python

{agenticdome_python_sdk-1.2.35 → agenticdome_python_sdk-1.2.37}/README.md

@@ -64,16 +64,60 @@ agenticdome inspect --output agenticdome-inspection.json
 
 `init` writes the secret-free inspection and local configuration. For the
 certified onboarding path, obtain the assigned sidecar and a dedicated
-`integration_copilot` key, run `agenticdome integrate preview`, review its
+`integration_copilot` key, run `agenticdome integrate preview` and
+`agenticdome integrate status`, review the saved
 local exact diff and change summary, explicitly approve a supported edit or
 attach other boundaries manually, then run
 `agenticdome verify --run-tests --output .agenticdome/verification.json`.
-Preview obtains the private, signed, catalog-bound semantic plan and keeps
+
+If a coding assistant has already made and tested the application edits,
+import its canonical `AgenticDome_Integration.md` in the customer portal and
+run `agenticdome validate-report --report AgenticDome_Integration.md` from
+that same deployable workload. Import the two generated, hash-bound JSON files
+in Onboarding. This avoids repeating the guided edit plan; the Markdown counts
+remain AI-reported and a real action-path test is still required before
+claiming protection. See the [customer onboarding guide](docs/customer-onboarding.md).
+
+For the Pilot path, preview obtains the private, signed, catalog-bound semantic plan and keeps
 application source on your machine. `agenticdome integrate apply` creates a
 local Git review branch but never commits, pushes or deploys. Existing-source
-automatic edits are currently limited to one exact certified smolagents run
-pattern; all other paths need manual integration. The older `agenticdome plan`
+automatic edits cover unambiguous CrewAI bootstrap, PydanticAI `Agent(...)`,
+LangChain `create_agent(...)`, Google ADK agent construction, Claude options,
+Agno `Agent(...)`, direct LlamaIndex `FunctionTool.from_defaults(...)`, direct
+OpenAI Agents `FunctionTool(...)` handlers, explicit custom-Python tool
+dispatchers, and the exact smolagents run pattern.
+The CLI leaves dynamic construction,
+existing handwritten AgenticDome calls, MCP forwarding and other framework
+paths for explicit review; a patch never proves all routes are intercepted.
+The older `agenticdome plan`
 and `agenticdome scaffold` remain available as advanced review-only commands.
+Preview auto-selects an application or pure-MCP review path and reports
+existing Python SDK call-site candidates, including handwritten local
+wrappers. Discovery uses the versioned framework hook catalog plus documented
+prompt, tool, A2A/delegation, MCP and output API methods; categories may
+overlap and TypeScript call sites are not parsed by this Python checker. Mixed
+application/MCP workloads get a separate MCP review path.
+Each preview rescans the selected workload. If code added a framework after
+`init`, its certified hook contract is included in the new plan and flagged for
+review without changing `.agenticdome/config.json`; a framework still in that
+config but absent from the current scan is flagged for confirmation. Run
+`agenticdome integrate status` for the saved next action and import a fresh
+`agenticdome inspect --output agenticdome-inspection.json` after reviewing it.
+These static observations do not prove interception; the CLI avoids
+overlapping automatic rewrites and requires real blocked-action tests.
+
+For one consequential tool, run your own safe integration test through the
+actual application route with an `ExecutionSpy` around its test handler, then
+correlate the SDK adapter call, live-mode verdict and handler invocation:
+
+```bash
+agenticdome verify-action --tool billing.refund --expect-verdict BLOCKED --expect-executed no -- pytest -q tests/test_blocked_refund.py
+```
+
+The test must call `spy.assert_calls(0)` (or `1` for an allowed test); see the
+[real action-path test guide](docs/customer-onboarding.md#prove-one-real-action-path).
+This opt-in command does not execute a business action itself, and a fixed
+`agenticdome verify` probe is not a substitute for the real-path test.
 
 For an MCP client, host, gateway or server workload, use the focused path:
 
@@ -111,6 +155,7 @@ openclaw plugins install npm:agenticdome-openclaw-security
 openclaw plugins enable agenticdome-security
 openclaw config set plugins.entries.agenticdome-security.hooks.allowConversationAccess true
 openclaw gateway restart
+openclaw gateway status --require-rpc
 agenticdome openclaw protect
 # With AGENTICDOME_API_BASE, AGENTICDOME_TENANT_ID and the dedicated
 # AGENTICDOME_COPILOT_API_KEY set, generate and review the signed plan:
@@ -119,8 +164,11 @@ agenticdome plan
 agenticdome openclaw verify --output .agenticdome/verification.json
 ```
 
-`openclaw protect` fails unless the active OpenClaw runtime reports the loaded
-AgenticDome plugin, explicit consent and the exact certified typed hooks.
+`openclaw protect` checks the AgenticDome plugin, explicit consent and exact
+typed hooks in the inspecting CLI process. `gateway status` checks the serving
+Gateway's RPC reachability; neither proves that this Gateway ran a hook on a
+customer tool call. Exercise a safe tool through the actual Gateway and inspect
+the matching AgenticDome runtime decision before claiming that route is protected.
 The official `openclaw plugins install`, `enable`, `config set` and gateway
 restart commands are the actual runtime configuration change; the Python CLI
 does not apply or undo them. No application source patch is needed for native
@@ -133,7 +181,8 @@ includes the MCP transport rehearsal and both `mcp_verification` and
 `openclaw_verification` in one report. Both sections must be ready before the
 report is imported; `mcp verify` alone is not a combined-workload proof. The
 customer Control Panel separately confirms tenant binding and retained
-telemetry; neither command silently modifies customer source.
+telemetry for its probes; neither command silently modifies customer source or
+proves that every live Gateway tool route was intercepted.
 
 When `.agenticdome/inspection.json` is imported into Developer Integration,
 the Control Panel adds its detected frameworks to the workload. Frameworks,
@@ -1469,6 +1518,13 @@ async def lookup_customer(customer_id: str) -> str:
     )
 ```
 
+If you construct `agents.FunctionTool` directly, its `on_invoke_tool`
+handler receives JSON text. Use `handler_args_format="json"` with
+`wrap_tool_handler` so the approved or sanitized arguments reach the original
+handler in that same format. The guided integration preview offers this edit
+only for a direct, statically named `FunctionTool` with an identifiable
+handler; other tool factories require manual review and a real-route test.
+
 **Delegated specialist tool pattern:**
 
 ```python

{agenticdome_python_sdk-1.2.35 → agenticdome_python_sdk-1.2.37}/agenticdome_python_sdk.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agenticdome-python-sdk
-Version: 1.2.35
+Version: 1.2.37
 Summary: Official Python SDK for AgenticDome security guardrails, DLP, tool authorization, and multi-agent delegation enforcement.
 Author: AgenticDome
 License-Expression: Apache-2.0
@@ -33,7 +33,7 @@ Requires-Dist: requests>=2.31.0
 Requires-Dist: urllib3>=2.0.0
 Requires-Dist: cryptography>=42.0.0
 Provides-Extra: crewai
-Requires-Dist: crewai<=1.15.22,>=1.15.5; extra == "crewai"
+Requires-Dist: crewai<=1.15.23,>=1.15.5; extra == "crewai"
 Provides-Extra: redis
 Requires-Dist: redis>=4.5.0; extra == "redis"
 Provides-Extra: pop
@@ -46,7 +46,7 @@ Requires-Dist: pydantic-ai<=2.51.0,>=2.16.0; extra == "pydantic"
 Requires-Dist: anyio>=4.0.0; extra == "pydantic"
 Provides-Extra: langgraph
 Requires-Dist: langgraph<=1.2.12,>=1.2.9; extra == "langgraph"
-Requires-Dist: langchain-core<=1.6.5,>=1.5.0; extra == "langgraph"
+Requires-Dist: langchain-core<=1.6.6,>=1.5.0; extra == "langgraph"
 Requires-Dist: langchain-openai==1.3.5; extra == "langgraph"
 Requires-Dist: anyio>=4.0.0; extra == "langgraph"
 Provides-Extra: microsoft
@@ -64,9 +64,9 @@ Requires-Dist: openai-agents<=0.22.3,>=0.18.3; extra == "openai-agents"
 Provides-Extra: mcp
 Requires-Dist: mcp<=2.2.0,>=1.26.0; extra == "mcp"
 Provides-Extra: bedrock
-Requires-Dist: boto3<=1.43.103,>=1.43.54; extra == "bedrock"
+Requires-Dist: boto3<=1.43.105,>=1.43.54; extra == "bedrock"
 Provides-Extra: aws-bedrock
-Requires-Dist: boto3<=1.43.103,>=1.43.54; extra == "aws-bedrock"
+Requires-Dist: boto3<=1.43.105,>=1.43.54; extra == "aws-bedrock"
 Provides-Extra: llamaindex
 Requires-Dist: llama-index<=0.14.25,>=0.14.23; extra == "llamaindex"
 Provides-Extra: llama-index
@@ -76,19 +76,19 @@ Requires-Dist: google-adk<=2.10.0,>=2.5.0; extra == "google-adk"
 Provides-Extra: adk
 Requires-Dist: google-adk<=2.10.0,>=2.5.0; extra == "adk"
 Provides-Extra: claude
-Requires-Dist: claude-agent-sdk<=0.2.160,>=0.2.126; extra == "claude"
+Requires-Dist: claude-agent-sdk<=0.2.162,>=0.2.126; extra == "claude"
 Provides-Extra: claude-agent-sdk
-Requires-Dist: claude-agent-sdk<=0.2.160,>=0.2.126; extra == "claude-agent-sdk"
+Requires-Dist: claude-agent-sdk<=0.2.162,>=0.2.126; extra == "claude-agent-sdk"
 Provides-Extra: smolagents
 Requires-Dist: smolagents==1.26.0; extra == "smolagents"
 Provides-Extra: all
-Requires-Dist: crewai<=1.15.22,>=1.15.5; extra == "all"
+Requires-Dist: crewai<=1.15.23,>=1.15.5; extra == "all"
 Requires-Dist: redis>=4.5.0; extra == "all"
 Requires-Dist: cryptography>=42.0.0; extra == "all"
 Requires-Dist: pydantic-ai<=2.51.0,>=2.16.0; extra == "all"
 Requires-Dist: anyio>=4.0.0; extra == "all"
 Requires-Dist: langgraph<=1.2.12,>=1.2.9; extra == "all"
-Requires-Dist: langchain-core<=1.6.5,>=1.5.0; extra == "all"
+Requires-Dist: langchain-core<=1.6.6,>=1.5.0; extra == "all"
 Requires-Dist: langchain-openai==1.3.5; extra == "all"
 Requires-Dist: autogen-agentchat==0.7.5; extra == "all"
 Requires-Dist: agno<=3.0.11,>=2.8.0; extra == "all"
@@ -96,10 +96,10 @@ Requires-Dist: azure-ai-projects<=2.7.0,>=2.3.0; extra == "all"
 Requires-Dist: azure-identity==1.25.3; extra == "all"
 Requires-Dist: openai-agents<=0.22.3,>=0.18.3; extra == "all"
 Requires-Dist: mcp<=2.2.0,>=1.26.0; extra == "all"
-Requires-Dist: boto3<=1.43.103,>=1.43.54; extra == "all"
+Requires-Dist: boto3<=1.43.105,>=1.43.54; extra == "all"
 Requires-Dist: llama-index<=0.14.25,>=0.14.23; extra == "all"
 Requires-Dist: google-adk<=2.10.0,>=2.5.0; extra == "all"
-Requires-Dist: claude-agent-sdk<=0.2.160,>=0.2.126; extra == "all"
+Requires-Dist: claude-agent-sdk<=0.2.162,>=0.2.126; extra == "all"
 Requires-Dist: smolagents==1.26.0; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0.0; extra == "dev"
@@ -177,16 +177,60 @@ agenticdome inspect --output agenticdome-inspection.json
 
 `init` writes the secret-free inspection and local configuration. For the
 certified onboarding path, obtain the assigned sidecar and a dedicated
-`integration_copilot` key, run `agenticdome integrate preview`, review its
+`integration_copilot` key, run `agenticdome integrate preview` and
+`agenticdome integrate status`, review the saved
 local exact diff and change summary, explicitly approve a supported edit or
 attach other boundaries manually, then run
 `agenticdome verify --run-tests --output .agenticdome/verification.json`.
-Preview obtains the private, signed, catalog-bound semantic plan and keeps
+
+If a coding assistant has already made and tested the application edits,
+import its canonical `AgenticDome_Integration.md` in the customer portal and
+run `agenticdome validate-report --report AgenticDome_Integration.md` from
+that same deployable workload. Import the two generated, hash-bound JSON files
+in Onboarding. This avoids repeating the guided edit plan; the Markdown counts
+remain AI-reported and a real action-path test is still required before
+claiming protection. See the [customer onboarding guide](docs/customer-onboarding.md).
+
+For the Pilot path, preview obtains the private, signed, catalog-bound semantic plan and keeps
 application source on your machine. `agenticdome integrate apply` creates a
 local Git review branch but never commits, pushes or deploys. Existing-source
-automatic edits are currently limited to one exact certified smolagents run
-pattern; all other paths need manual integration. The older `agenticdome plan`
+automatic edits cover unambiguous CrewAI bootstrap, PydanticAI `Agent(...)`,
+LangChain `create_agent(...)`, Google ADK agent construction, Claude options,
+Agno `Agent(...)`, direct LlamaIndex `FunctionTool.from_defaults(...)`, direct
+OpenAI Agents `FunctionTool(...)` handlers, explicit custom-Python tool
+dispatchers, and the exact smolagents run pattern.
+The CLI leaves dynamic construction,
+existing handwritten AgenticDome calls, MCP forwarding and other framework
+paths for explicit review; a patch never proves all routes are intercepted.
+The older `agenticdome plan`
 and `agenticdome scaffold` remain available as advanced review-only commands.
+Preview auto-selects an application or pure-MCP review path and reports
+existing Python SDK call-site candidates, including handwritten local
+wrappers. Discovery uses the versioned framework hook catalog plus documented
+prompt, tool, A2A/delegation, MCP and output API methods; categories may
+overlap and TypeScript call sites are not parsed by this Python checker. Mixed
+application/MCP workloads get a separate MCP review path.
+Each preview rescans the selected workload. If code added a framework after
+`init`, its certified hook contract is included in the new plan and flagged for
+review without changing `.agenticdome/config.json`; a framework still in that
+config but absent from the current scan is flagged for confirmation. Run
+`agenticdome integrate status` for the saved next action and import a fresh
+`agenticdome inspect --output agenticdome-inspection.json` after reviewing it.
+These static observations do not prove interception; the CLI avoids
+overlapping automatic rewrites and requires real blocked-action tests.
+
+For one consequential tool, run your own safe integration test through the
+actual application route with an `ExecutionSpy` around its test handler, then
+correlate the SDK adapter call, live-mode verdict and handler invocation:
+
+```bash
+agenticdome verify-action --tool billing.refund --expect-verdict BLOCKED --expect-executed no -- pytest -q tests/test_blocked_refund.py
+```
+
+The test must call `spy.assert_calls(0)` (or `1` for an allowed test); see the
+[real action-path test guide](docs/customer-onboarding.md#prove-one-real-action-path).
+This opt-in command does not execute a business action itself, and a fixed
+`agenticdome verify` probe is not a substitute for the real-path test.
 
 For an MCP client, host, gateway or server workload, use the focused path:
 
@@ -224,6 +268,7 @@ openclaw plugins install npm:agenticdome-openclaw-security
 openclaw plugins enable agenticdome-security
 openclaw config set plugins.entries.agenticdome-security.hooks.allowConversationAccess true
 openclaw gateway restart
+openclaw gateway status --require-rpc
 agenticdome openclaw protect
 # With AGENTICDOME_API_BASE, AGENTICDOME_TENANT_ID and the dedicated
 # AGENTICDOME_COPILOT_API_KEY set, generate and review the signed plan:
@@ -232,8 +277,11 @@ agenticdome plan
 agenticdome openclaw verify --output .agenticdome/verification.json
 ```
 
-`openclaw protect` fails unless the active OpenClaw runtime reports the loaded
-AgenticDome plugin, explicit consent and the exact certified typed hooks.
+`openclaw protect` checks the AgenticDome plugin, explicit consent and exact
+typed hooks in the inspecting CLI process. `gateway status` checks the serving
+Gateway's RPC reachability; neither proves that this Gateway ran a hook on a
+customer tool call. Exercise a safe tool through the actual Gateway and inspect
+the matching AgenticDome runtime decision before claiming that route is protected.
 The official `openclaw plugins install`, `enable`, `config set` and gateway
 restart commands are the actual runtime configuration change; the Python CLI
 does not apply or undo them. No application source patch is needed for native
@@ -246,7 +294,8 @@ includes the MCP transport rehearsal and both `mcp_verification` and
 `openclaw_verification` in one report. Both sections must be ready before the
 report is imported; `mcp verify` alone is not a combined-workload proof. The
 customer Control Panel separately confirms tenant binding and retained
-telemetry; neither command silently modifies customer source.
+telemetry for its probes; neither command silently modifies customer source or
+proves that every live Gateway tool route was intercepted.
 
 When `.agenticdome/inspection.json` is imported into Developer Integration,
 the Control Panel adds its detected frameworks to the workload. Frameworks,
@@ -1582,6 +1631,13 @@ async def lookup_customer(customer_id: str) -> str:
     )
 ```
 
+If you construct `agents.FunctionTool` directly, its `on_invoke_tool`
+handler receives JSON text. Use `handler_args_format="json"` with
+`wrap_tool_handler` so the approved or sanitized arguments reach the original
+handler in that same format. The guided integration preview offers this edit
+only for a direct, statically named `FunctionTool` with an identifiable
+handler; other tool factories require manual review and a real-route test.
+
 **Delegated specialist tool pattern:**
 
 ```python

{agenticdome_python_sdk-1.2.35 → agenticdome_python_sdk-1.2.37}/agenticdome_python_sdk.egg-info/SOURCES.txt

@@ -15,6 +15,7 @@ agenticdome_python_sdk.egg-info/top_level.txt
 agenticdome_sdk/__init__.py
 agenticdome_sdk/_framework_firewall.py
 agenticdome_sdk/_mode.py
+agenticdome_sdk/action_path_proof.py
 agenticdome_sdk/agno.py
 agenticdome_sdk/attestation.py
 agenticdome_sdk/autogen.py
@@ -27,6 +28,9 @@ agenticdome_sdk/copilot_ir.py
 agenticdome_sdk/copilot_ir_collector.cjs
 agenticdome_sdk/crewai.py
 agenticdome_sdk/demo.py
+agenticdome_sdk/existing_integration.py
+agenticdome_sdk/framework_edits.py
+agenticdome_sdk/generic_python.py
 agenticdome_sdk/google_adk.py
 agenticdome_sdk/guided_integration.py
 agenticdome_sdk/hook_catalog.py

{agenticdome_python_sdk-1.2.35 → agenticdome_python_sdk-1.2.37}/agenticdome_python_sdk.egg-info/requires.txt

@@ -9,13 +9,13 @@ google-adk<=2.10.0,>=2.5.0
 agno<=3.0.11,>=2.8.0
 
 [all]
-crewai<=1.15.22,>=1.15.5
+crewai<=1.15.23,>=1.15.5
 redis>=4.5.0
 cryptography>=42.0.0
 pydantic-ai<=2.51.0,>=2.16.0
 anyio>=4.0.0
 langgraph<=1.2.12,>=1.2.9
-langchain-core<=1.6.5,>=1.5.0
+langchain-core<=1.6.6,>=1.5.0
 langchain-openai==1.3.5
 autogen-agentchat==0.7.5
 agno<=3.0.11,>=2.8.0
@@ -23,29 +23,29 @@ azure-ai-projects<=2.7.0,>=2.3.0
 azure-identity==1.25.3
 openai-agents<=0.22.3,>=0.18.3
 mcp<=2.2.0,>=1.26.0
-boto3<=1.43.103,>=1.43.54
+boto3<=1.43.105,>=1.43.54
 llama-index<=0.14.25,>=0.14.23
 google-adk<=2.10.0,>=2.5.0
-claude-agent-sdk<=0.2.160,>=0.2.126
+claude-agent-sdk<=0.2.162,>=0.2.126
 smolagents==1.26.0
 
 [autogen]
 autogen-agentchat==0.7.5
 
 [aws-bedrock]
-boto3<=1.43.103,>=1.43.54
+boto3<=1.43.105,>=1.43.54
 
 [bedrock]
-boto3<=1.43.103,>=1.43.54
+boto3<=1.43.105,>=1.43.54
 
 [claude]
-claude-agent-sdk<=0.2.160,>=0.2.126
+claude-agent-sdk<=0.2.162,>=0.2.126
 
 [claude-agent-sdk]
-claude-agent-sdk<=0.2.160,>=0.2.126
+claude-agent-sdk<=0.2.162,>=0.2.126
 
 [crewai]
-crewai<=1.15.22,>=1.15.5
+crewai<=1.15.23,>=1.15.5
 
 [dev]
 pytest>=8.0.0
@@ -67,7 +67,7 @@ google-adk<=2.10.0,>=2.5.0
 
 [langgraph]
 langgraph<=1.2.12,>=1.2.9
-langchain-core<=1.6.5,>=1.5.0
+langchain-core<=1.6.6,>=1.5.0
 langchain-openai==1.3.5
 anyio>=4.0.0
 

{agenticdome_python_sdk-1.2.35 → agenticdome_python_sdk-1.2.37}/agenticdome_sdk/__init__.py

@@ -3,6 +3,8 @@ from .identity import IDENTITY_CONTEXT_VERSION, canonicalize_identity_context, e
 from .proof import create_dpop_proof, generate_rsa_proof_key, jwk_thumbprint
 from ._mode import LIVE_MODE, LOCAL_SIM_MODE, is_local_sim_mode, resolve_mode
 from .lifecycle import VerifiedActionContext, VerifiedActionDenied, VerifiedActionReporter, verified_action
+from .action_path_proof import ExecutionSpy
+from .generic_python import AgenticDomeActionDenied, guarded_tool_executor
 
 __all__ = [
     "AgenticDomeClient",
@@ -22,4 +24,7 @@ __all__ = [
     "VerifiedActionDenied",
     "VerifiedActionReporter",
     "verified_action",
+    "ExecutionSpy",
+    "AgenticDomeActionDenied",
+    "guarded_tool_executor",
 ]