[GatewayJ]

Summary

Add opt-in object transfer integration through the independently built optional executable. The ordinary CLI keeps its existing HTTP commands and dependency graph; protocol implementation stays in the private dependency.

Update the optional dependency pin to fa81f604902a510801b882322b7abb9539a005d4. Repair build-test fixtures to provide the independent workspace and source lock file expected by the build helper, and verify an existing optional-workspace lock file is preserved.

Verification

• Default workspace formatting and Clippy with -D warnings passed on Rust 1.97.1.
• Default cargo test --workspace: 1,950 tests passed.
• Build helper fixture tests: 7 passed.
• Private facade: 30 native software tests passed and all-target Clippy passed with -D warnings on Rust 1.98.1.
• The existing signed HTTPS harness also passed actual CLI upload/download and object interoperability cases.
• Whitespace checks passed. Default builds do not require initializing the optional private dependency.

The native tests used the pinned libraries on Linux/aarch64 with software transport. Physical RDMA/DPU and a newly rebuilt multi-node enterprise deployment require separate acceptance.

Hosted check snapshot

The fixture commit 4be1794's Actions snapshot has two failed checks: Dependency Advisories reports findings in the existing lockfile, and Clippy fails in unchanged rc-core code under Rust 1.99 (including async-trait double_must_use diagnostics). This update changes the build fixture and optional gitlink; it does not change those source files or the default lockfile. Those findings remain unresolved by the following dependency-pin update. Local Rust 1.97.1 results above are separate evidence.

Compatibility

Existing commands and default build behavior remain available. Optional builds require authorized access to the pinned private dependency and the documented native build environment. Reverting this update restores the preceding dependency pin and fixture.