🤖 (aa-ffi-python): Bump aa-core/aa-proto/aa-sdk-client pin to v0.0.1-rc.3

[Chisanan232]

Auto-bump the three shared git-SHA pins (aa-core, aa-proto,
aa-sdk-client) in native/aa-ffi-python/Cargo.toml to track
agent-assembly release v0.0.1-rc.3 (commit
3193b4c5c8e63033e270ba2d933be8c5158a12e4).

Per ADR 0002 / AAASM-2559 the three pins must share one SHA so
cargo resolves a single checkout of the agent-assembly workspace.

Why: without this PR, the SDK source pin drifts behind the
published agent-assembly binaries (AAASM-2880 observed an 8-day
drift behind alpha-9). Merging this PR on python-sdk realigns
the native shim with the matching upstream tag.

Upstream tag: https://github.com/ai-agent-assembly/agent-assembly/releases/tag/v0.0.1-rc.3
Source workflow: https://github.com/ai-agent-assembly/agent-assembly/actions/runs/28666538071

[Chisanan232]

Claude Code — review record

1. CI: ✅ green (MERGEABLE; blocked only on required review).
2. Scope: ✅ aa-ffi-python pin bump to v0.0.1-rc.3 — Cargo.toml + Cargo.lock only.
3. Correctness / side-effects: ✅ git rev pin updated fc90f85d → 3193b4c5c8e63033e270ba2d933be8c5158a12e4, which is exactly the commit v0.0.1-rc.3 tags (the fixed master with the aa-auth publish fix). The fanout ran in the recovered release run, so it captured the correct post-fix SHA — not the withdrawn buggy commit. version literal rc.2 → rc.3. No source change.

Verdict: Ready to merge. Merging lands the rc.3 pin; the ai-agent-assembly/python-sdk rc.3 cut follows (per AAASM-3007).

🤖 Claude Code