🤖 (aa-ffi-node): Bump agent-assembly git pins to v0.0.1-rc.3

[Chisanan232]

Auto-bump every agent-assembly git-SHA pin (aa-sdk-client,
aa-proto, and any other shared crate) in
native/aa-ffi-node/Cargo.toml to track agent-assembly release
v0.0.1-rc.3 (commit 3193b4c5c8e63033e270ba2d933be8c5158a12e4).

Per ADR 0003 all aa-* git deps must share one rev so cargo resolves
a single checkout of the agent-assembly workspace; this PR bumps them
in lockstep (AAASM-3468).

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 node-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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[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

[Chisanan232]

Claude Code — review record

1. CI: ✅ green (MERGEABLE; blocked only on required review).
2. Scope: ✅ aa-ffi-node 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/node-sdk rc.3 cut follows (per AAASM-3007).

🤖 Claude Code