[P0] Remove all: Clears local CLI state but leaves resources in AWS account

[tejaskash]

Description

Running remove all clears the CLI's local agentcore.json state, but leaves all resources deployed in the AWS account. This creates an inconsistent state where the CLI thinks there are no resources but they still exist in AWS.

Reporter

davrthur

Category

Functional Bug

Steps to Reproduce

1. Create and deploy a project with agents, memory, etc.
2. Run agentcore remove all
3. Check AWS account - resources still exist
4. Run agentcore deploy - error "[error] Validate project → No agents defined in project. Add at least one agent with 'agentcore add agent' before deploying"

Expected Behavior

Either:

1. remove all should delete resources from AWS, or
2. remove all should clearly state it only removes local configuration and warn about orphaned AWS resources

Actual Behavior

• Local state is cleared
• AWS resources remain deployed
• Running deploy after remove all fails because CLI thinks project is empty
• Orphaned resources remain in AWS account

Impact

High - creates orphaned resources and confusing state.

Suggestion

Consider:

1. Renaming to remove all --local to be explicit about scope
2. Adding a remove all --aws flag to delete AWS resources
3. Warning users about orphaned resources when running remove all