create --network-mode VPC fails for harness projects: '--subnets is required' even when --subnets is passed

[aidandaly24]

Summary

Creating a harness project in VPC mode with agentcore create fails with --subnets is required when network mode is VPC, even when --subnets (and --security-groups / --vpc-id) are supplied. The same VPC configuration works through the agent path of create and through add harness, so a VPC harness is a supported configuration that simply can't be reached via create.

Reproduction

On @aws/agentcore@0.22.0:

mkdir repro && cd repro
echo "FROM public.ecr.aws/lambda/python:3.12" > Dockerfile

agentcore create --name vh --container ./Dockerfile \
 --network-mode VPC \
 --subnets subnet-0123456789abcdef0 \
 --security-groups sg-0123456789abcdef0 \
 --vpc-id vpc-0123456789abcdef0 \
 --model-provider bedrock --dry-run

Actual: exit 1, --subnets is required when network mode is VPC (even though --subnets was passed).

Expected: the project is created (or, for --dry-run, the preview succeeds). When --vpc-id is omitted for a container build, the expected error is --vpc-id is required for Container builds with --network-mode VPC.

Scope

• Affects: agentcore create for harness projects (any --container value) in --network-mode VPC.
• Not affected: agentcore create for agent projects (--build Container --network-mode VPC ... works), and agentcore add harness --network-mode VPC ... (works and persists networkConfig.vpcId).

Root cause

validateCreateHarnessOptions validates the VPC options, but the two call sites in src/cli/commands/create/command.tsx (the --dry-run path and the main path) do not pass container, subnets, securityGroups, or vpcId into it. Those fields read as undefined inside the validator, so the "subnets required" check triggers even when they were provided, and the intended --vpc-id validation is never reached.

Fix

Forward container, subnets, securityGroups, and vpcId into validateCreateHarnessOptions at both call sites, bringing create for harnesses to parity with add harness and the agent path.