fix: resolve target-based AB test target name mismatch

[notgitika]

Summary

• Fixes resolveTargetName() in post-deploy-ab-tests.ts which had a false-positive startsWith check that prevented the project prefix from being applied to target names
• The target-based AB test was referencing "ProjectName-prod" while the actual AWS gateway target was created as "ProjectName-ProjectName-prod" by post-deploy-http-gateways.ts, causing the AB test to stay in NOT_STARTED forever
• This has been causing the e2e-tests-full.yml workflow to fail on every run since the feature was introduced

Closes #1179
Closes #1091

Root Cause

post-deploy-http-gateways.ts (lines 104, 146, 315) unconditionally writes targets as ${projectName}-${tgt.name}.

ABTestPrimitive.createTargetBasedABTest() (line 634-635) stores the variant targetName as ${runtime}-${endpoint} — i.e., always the unprefixed logical name.

The old resolveTargetName() had a startsWith guard that misfired when runtime === projectName (the common default): "MyAgent-prod".startsWith("MyAgent-") → true, so it skipped prefixing. The AB test then referenced "MyAgent-prod" while the actual AWS target was "MyAgent-MyAgent-prod".

Unconditional prefixing is the right call since the config always stores the unprefixed logical name.

Changes

1. post-deploy-ab-tests.ts: Remove the startsWith heuristic, always apply the project prefix
2. post-deploy-ab-tests.test.ts: Add two unit tests covering target-based variant resolution:
   • runtime === projectName (the case the old check broke)
   • Different project/runtime names (standard prefixing)

Test plan

• Unit tests pass (25/25 in post-deploy-ab-tests.test.ts, including 2 new)
• Lint, prettier, typecheck all pass
• Integration tests unaffected (only test local add/remove, not deploy)
• Full e2e suite should now pass shard 5/6 (ab-test-target-based.test.ts)

[agentcore-cli-automation]

Fix itself looks correct and the root-cause analysis matches what I see in the code: post-deploy-http-gateways.ts (lines 104, 146, 315) unconditionally writes targets as ${projectName}-${tgt.name}, and createTargetBasedABTest (ABTestPrimitive.ts line 634-635) stores the variant targetName as ${runtime}-${endpoint} — i.e., always the unprefixed logical name. So unconditional prefixing in resolveTargetName is the right call. The old startsWith check only misfired when runtime === projectName, which is the common default and is exactly what the e2e test was hitting.

One thing worth addressing before merge — see the inline comment on the test file.

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	43.31%	9076 / 20954
🔵	Statements	42.59%	9639 / 22627
🔵	Functions	40.16%	1567 / 3901
🔵	Branches	40.15%	5856 / 14583

Generated in workflow #2688 for commit 9cfed0d by the Vitest Coverage Report Action

[github-actions]

Package Tarball

aws-agentcore-0.13.1.tgz

How to install

npm install https://github.com/aws/agentcore-cli/releases/download/pr-1188-tarball/aws-agentcore-0.13.1.tgz

[notgitika]

Empirical verification

Reproduced the e2e test flow manually against my account:

1. Created project TestABFix (runtime name == project name, matching the e2e test)
2. Added runtime endpoints prod/staging, evaluator, online eval configs, target-based AB test with --enable
3. Deployed

Result with the fix:

{
  "executionStatus": "RUNNING",
  "variants": [
    {"name": "C", "variantConfiguration": {"target": {"name": "TestABFix-TestABFix-prod"}}, "weight": 90},
    {"name": "T1", "variantConfiguration": {"target": {"name": "TestABFix-TestABFix-staging"}}, "weight": 10}
  ]
}

The AB test transitions to RUNNING immediately after deploy. Target names are correctly double-prefixed (TestABFix-TestABFix-prod), matching what post-deploy-http-gateways.ts creates on the gateway.

Without the fix, resolveTargetName would have returned TestABFix-prod (no prefix added due to the false-positive startsWith check), the targets wouldn't match any gateway target, and the test would stay NOT_STARTED — exactly what the e2e suite has been seeing.