fix: select native SDK contract in acceptance controllers #116

Affected template

Shared Express acceptance controllers and agents-cli SDK verifier (no image changes).

Environment

Python 3.11.15; Linux x86_64; current source-installed Python SDK from Alibaba-Agent-Sandbox/python-sdk#47 .

What happened?

After the SDK root Sandbox became the standard synchronous API, the controllers still imported it while awaiting native lifecycle and named commands. Named commands, inventory and recovery could select the wrong contract. The regression reproduces the failure with separate synchronous standard and asynchronous native doubles.

Expected behavior

Use the stable native API entry for async lifecycle/named commands and preserve borrowed sandbox ownership. Remove the obsolete claim that current sync factory helpers are broken.

Acceptance criteria

• Host controllers explicitly select the native API entry.
• A behavior regression rejects the synchronous root and checks named-command arguments and local close.
• Cleanup/recovery and agents-cli verifier regressions pass.
• Record verification honestly without changing catalog provider badges, runtime images or cloud/model Actions.

Related: #115 , Alibaba-Agent-Sandbox/agent-sandbox#40 .