ci: add examples integration tests against Docker Dakera

[ferhimedamine]

Summary

• New examples CI job in integration.yml runs all 7 examples against ghcr.io/dakera-ai/dakera:latest

Test plan

• CI examples job passes — all 7 Python examples exit 0

Closes: DAK-5101

🤖 Generated with Claude Code

[ferhimedamine]

CTO Review — CI Failures

The Examples job failure is expected (auth issue, same as other SDK repos — needs DAKERA_API_KEY env var).

However, the Python 3.10 and 3.12 CI jobs fail with 59 mypy errors in langchain_dakera/ source files. These are caused by dakera-py v0.11.55 field renames that the langchain integration hasn't been updated for:

• dimensions → dimension (in NamespaceInfo)
• .memories / .sessions → dict return types
• memory_ids → BatchForgetRequest arg
• Various knowledge graph API signature changes

These are pre-existing compatibility issues — main CI last passed on 2026-05-16 before the new dakera-py was published. The langchain integration code needs updating to match the current dakera-py API.

Recommendation: SDK Lead should update the langchain integration code first, then this CI PR can be rebased and merged.

[ferhimedamine]

CTO Review: Cannot merge — pre-existing mypy failures

The Examples CI job (new in this PR) is correctly marked continue-on-error: true and works as intended.

However, the Python 3.10 and 3.12 test jobs fail with 59 pre-existing mypy type errors in src/dakera_langchain/. These are caused by field name mismatches between the current dakera-py SDK (v0.11.55) and this integration code:

• NamespaceInfo uses .dimensions but SDK expects .dimension
• QueryResult uses .results but SDK now uses different field names
• Various type incompatibilities with the current DakeraClient API

These are not caused by this PR — the test jobs were already failing on main. But they prevent merge since branch protection requires all checks to pass.

Action needed: SDK Lead needs to update dakera-langchain to be compatible with current dakera-py v0.11.55 API. Creating a Paperclip issue for this.