[AAASM-3537] ✨ (examples): Add Agno tool-policy example

[Chisanan232]

Description

Adds python/agno-tool-policy, a runnable offline example that governs a real
Agno (formerly Phidata) agent's tools through the SDK's native Agno
adapter — not a no-op.

Agno runs every function-tool call through agno.tools.function.FunctionCall.execute;
the SDK's Agno adapter patches that chokepoint so governance runs before the tool
body. The example drives real Agno @tool functions exactly as an Agno Agent
does (FunctionCall(...).execute()), wired to a local offline policy:

• get_weather, summarize_docs → allowed, run and return their real output;
• execute_sql → denied, body short-circuited before it runs.

Mirrors the existing *-tool-policy examples (src/main.py, src/tools.py,
src/policy.py, tests/test_smoke.py, README, .env.example) and adds a CI job to
verify-python.yml.

The smoke tests are a genuine governance proof: the deny test asserts the denied
tool's body never executed (a no-op patch would let it run), and the allow
test asserts the real body ran.

Cross-repo dependency

The example imports agent_assembly.adapters.agno, which ships in the python-sdk
AAASM-3537 branch (PR ai-agent-assembly/python-sdk#162). Until that lands and
a release is published to PyPI, uv sync should install the SDK from that branch.
This is noted in the example's pyproject.toml and README.

Verification

Validated locally against the python-sdk AAASM-3537 branch:

$ uv run python src/main.py
  → get_weather({'city': 'London'})        ✅ ALLOWED
  → summarize_docs({'topic': '...'})        ✅ ALLOWED
  → execute_sql({'sql': 'DROP TABLE ...'})  ❌ BLOCKED — deny_arbitrary_execution

$ uv run pytest tests/ -q
  6 passed

Refs AAASM-3537

🤖 Generated with Claude Code

[Chisanan232]

Claude Code — review result (Agno example)

⚠️ agno-tool-policy smoke job is red for release-ordering only — ModuleNotFoundError: No module named 'agent_assembly.adapters.agno'. Adapter ships in python-sdk #162 (unmerged); resolves after #162 merges + a python-sdk b5 release.

Two non-defect reds to note:

• The run check failing is the unrelated "Auto-assign issue" workflow (Couldn't find issue info in current context) — pre-existing repo automation, not this PR.
• SonarCloud — acceptance gate, ignored per standing rule.

Validated locally: 6 smoke tests pass; main.py runs allow/allow/blocked. Merge order: LAST — after python-sdk #162 + b5 release. Full cross-repo review on AAASM-3535.

[Chisanan232]

Claude Code — SonarCloud new-code review (round 2)

Found + fixed 1 security finding: hotspot verify-python.yml:99 — "use full commit SHA for this dependency." SHA-pinned the agno job's actions — astral-sh/setup-uv@d4b2f3b6ecc6e67c4457f6d3e41ec42d3d0fcb86 # v5 and actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4 (commit eb75335c).

✅ SonarCloud quality gate flipped to OK; 0 new-code issues, hotspot resolved. (The agno-tool-policy smoke job stays red for release-ordering only — resolves after python-sdk #162 + a b5 release; the run/Auto-assign check is unrelated repo automation.)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud