[Chisanan232]

Target

• Task summary:

  Core agent-assembly main d4093e89b added org_id and registration_key to AssemblyConfig. This repo pinned core at 0044d515 (1610 commits behind), and a bump does not compile as-is: the two AssemblyConfig { .. } literals in native/aa-ffi-node/src/lib.rs (connect, register) lack the new fields. This change bumps the pin to d4093e89b and sets both fields to None, so registration stays org-less and behaviour for callers is unchanged. The pin and the initializers are one commit because neither compiles without the other. node-sdk does not expose an org claim here; that is a separate design and secret-handling decision.

• Task tickets:

  • Task ID: AAASM-6457
  • Relative task IDs:
    • AAASM-6444 (python-sdk org identity, PR python-sdk#390), AAASM-6447, AAASM-6451
  • Relative PRs:
    • [AAASM-6444] ✨ (init): Add org_id and registration_key to init_assembly python-sdk#390; ai-agent-assembly/go-sdk (same bump, separate PR)

• Key point change (optional):

  native/aa-ffi-node/Cargo.toml: aa-sdk-client and aa-proto rev 0044d515 -> d4093e89b; Cargo.lock regenerated (cargo update -p aa-sdk-client -p aa-proto); src/lib.rs: org_id: None, registration_key: None at both literals. Note: a registration key in the process environment (AA_REGISTRATION_KEY) is still resolved by core during register.

Effecting Scope

• Action Types:
  • ✏️ Modifying existing something
    • 🟢 No breaking change
• Scopes:
  • 🪡 API client and transport
  • 🚀 Building
    • 🔗 Dependencies
• Additional description:
  Verified locally in native/aa-ffi-node against the new pin with an isolated target dir, on the disk-admission queue: cargo update -p aa-sdk-client -p aa-proto, cargo check --all-targets --locked, cargo clippy --all-targets --locked -- -D warnings, cargo test -p aa-ffi-node-core --locked all exit 0. Not run locally: the napi addon build and the TypeScript suites (pnpm native:build, pnpm typecheck, pnpm lint, pnpm test); the CI build-addon and test jobs are the authoritative check. The aa-proto build.rs differences between the old and new pin were not separately reviewed beyond the successful compile.

Description

• Bump core pin to d4093e89b07d8ba1c38e6caa92637d2e8edb65d7; set org_id and registration_key to None; regenerate the lockfile.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TLpw696KjUDUg4QjH83En4

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Chisanan232]

OWNER-MERGE-REVIEW head=8d237bf8b65b992b106b0efd0a38dc2cbddcd098 verdict=PASS blocking=0 reviewer=claude-independent-agent

[Chisanan232]

OWNER-MERGE-REVIEW head=ec595a1f16e15c3413148d8615bf3af004211d95 verdict=PASS blocking=0 reviewer=claude-independent-agent

[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]

OWNER-ADMIN-MERGE (same-identity REVIEW_REQUIRED deadlock exception, engineering-workflow exception 2) for head ec595a1. Verified identity: Chisanan232 (author; org ai-agent-assembly role=admin, checked just now via orgs//memberships). Only remaining blocker: GitHub required approving review, which the PR author cannot supply for their own PR. At this head: independent adversarial review clean (no Critical/High); one Medium (registration_key None now falls back to env AA_REGISTRATION_KEY via core) is disclosed in the shim comment and Jira AAASM-6457 comment 30539 and is non-blocking (below High; same core behaviour python-sdk#390 inherits); OWNER-MERGE-REVIEW PASS comment posted; 32 checks green after coverage re-run; mergeable, 0 unresolved threads, 0 REQUEST_CHANGES. Merge by merge commit, pinned to this head, on the owner explicit instruction; host Allow once / Deny prompt applies.