[ericksondelacruz]

Summary

Extends EBTE (Explanation-Bound Tool Execution) tool-call claims from #276 (OpenAI Agents, MCP, LangChain; Python) to six more SDKs. Each SDK gets the same three rules: no claim (info), claim declared but never read (medium), claim only printed, logged, serialized or returned (medium). Stacks on #276 and adds 18 rules, from 364 to 382.

Commit	Schema	Rules	What it adds
cd59e99	—	—	LangChain factory tools (StructuredTool.from_function(fn), StructuredTool(func=fn), Tool.from_function(fn)) get the claim_use fact from the wrapped function, so LC-029 / LC-030 apply to them
897a7ef	32 → 33	CREW-016..018, PYD-016..018	claim_use on CrewAI and Pydantic AI tools. New repo-level pass analysis.ApplyClaimMediators treats the SDK's pre-tool hook (CrewAI before_tool_call family, Pydantic AI tool-execution Hooks, a tool args_validator=) as a possible mediator
0c32fb3	33 → 34	CSDK-026..028	Claude Agent SDK @tool handlers. New ToolDef.InputKeys records the input-schema keys, so tool_claim_use sees a claim in the schema and classifies args["claim"] / args.get("claim") reads. A PreToolUse hook, or can_use_tool without allowed_tools / bypassPermissions, counts as a possible mediator
4d68031	34 → 35	OAI-037..039	TypeScript @openai/agents tool({...}) with a zod claim parameter. Reads destructured bindings and input.claim in the inline execute. inputGuardrails counts as a possible mediator
cb97906	35 → 36	ADK-024..026, AG2-023..025	Google ADK FunctionTool(fn) and AutoGen register_function / register_for_llm / register_for_execution tools. An ADK before_tool_callback (agent keyword or plugin method) counts as a possible mediator. AutoGen's registering decorators do not
4ca2139	—	—	Docs: the schema reference and FactClaimUse comment describe every discovery path and mediator

Each commit bumps SupportedSchemaVersion and the fixture manifest, with a schema note in internal/rules/schema_version.go.

Notes for review

• Stacked on feat(rules): detect missing EBTE tool-call claims and mediation (schema 32) #276. The base is feat/analyzer-ebte-claims. Branches aren't deleted on merge in this repo, so after feat(rules): detect missing EBTE tool-call claims and mediation (schema 32) #276 merges, change this PR's base to main (or delete the parent branch, and GitHub retargets it). CI only runs on PRs into main, so the checks start after the retarget.
• Rules and docs: the rules land in agent-reliability-rules and trustabl-rulebook on branches with the same name (feat/ebte-claims-coverage). Their CI pairs with this branch. Merge order: this PR, then feat(tool_call_claims): EBTE tool-call claims for six more SDKs (schemas 33–36) agent-reliability-rules#206, then docs(tool_call_claims): rationale for the EBTE claims rules on six more SDKs trustabl-rulebook#157.
• The no-claim rules are info for the same reason as in feat(rules): detect missing EBTE tool-call claims and mediation (schema 32) #276.
• Another schema bump landing on main first means renumbering this stack.

Test plan

• go build ./..., go vet ./..., go test ./... (27 packages ok) on every commit; go test -race on internal/analysis, internal/rules and internal/scanner at the tip
• scripts/check-rules-sync.sh against the rules branch: in sync (144 files)
• trustabl rules validate on the rules branch: OK: 143 rule pack(s), 382 rule(s) valid under rule schema version 36
• CI passes