`stacker agent install` creates cloud-context deployment instead of targeting existing server

[vsilent]

Description

stacker agent install creates a new deployment in the cloud project context instead of targeting the existing server. stacker target server refuses to switch because no server deployment lock exists.

Affected Projects

activepieces

Steps to Reproduce

1. Configure existing server in stacker.yml
2. Run stacker target server
   • Error: No server deployment lock found
3. Run stacker agent install --json
4. Check stacker status — new cloud-context deployment created

Expected Behavior

If stacker agent install is meant for existing servers, it should target that path or fail clearly saying a server deployment/lock is required first.

Environment

• Stacker CLI version: latest
• Deploy target: server