fix(harness): surface managed-memory heads-up on dev deploy + validate session storage path in TUI

[aidandaly24]

Description

Fixes two bugs in the gated managed-memory / harness TUI flows (both gated behind ENABLE_GATED_FEATURES).

1. Managed-memory heads-up missing on agentcore dev deploys

The regular deploy path shows a heads-up when a harness uses managed memory ("this harness automatically provisions a dedicated AgentCore Memory resource… provisioning can take 3-5 minutes…"). The dev deploy path did not: useDevDeploy called handleDeploy without an onNotice callback, so the notice (emitted via onNotice) was dropped.

Fix: thread onNotice through useDevDeploy into a managedMemoryNotice state, and render it in DevScreen's "Deploying project resources…" view as a plain dim Note: (matching the deploy-screen convention). Verified live: the note now appears as the CFN apply starts and stays pinned through memory provisioning.

2. Session-storage mount path not validated in the add-harness wizard

The session-storage step only checked value.startsWith('/'), so a nested path like /mnt/data/workplace/ passed Enter and then failed later at schema-write/deploy. The other mount-path steps (EFS, S3 Files) already validate with validateBYOMountPath.

I confirmed the constraint against the API: the smithy MountPath shape (com.amazonaws.bedrockagentcorecontrol#MountPath) is pattern: ^/mnt/[a-zA-Z0-9._-]+/?$, length 6-200 — exactly one segment under /mnt — and the AWS::BedrockAgentCore::Harness CFN resource schema mirrors it. So nested paths are genuinely invalid at the API; the CLI regex is correct, the TUI step just wasn't using it.

Fix: use validateBYOMountPath in the session-storage step's customValidation. TextInput already blocks Enter and renders a red error/✗ when validation fails. Verified live: /mnt/data/workplace/ now shows a red error and Enter is blocked; /mnt/data shows ✓.

Related Issue

Closes #

Type of Change

• Bug fix

Testing

How have you tested the change?

• I ran npm run test:unit (added useDevDeploy tests for the onNotice → managedMemoryNotice wiring, set + unset; the mount-path validator already has direct coverage incl. nested-path rejection)
• I ran npm run typecheck
• I ran npm run lint (no new warnings; the 2 remaining in AddHarnessScreen.tsx are pre-existing and outside the changed lines)
• If I modified src/assets/ — n/a, no asset changes

Also verified end-to-end live (account 603141041947, ap-southeast-2, preview build) via the TUI harness:

• agentcore dev on a managed-memory harness now shows the Note: heads-up during the deploy phase (pinned through CREATE_IN_PROGRESS).
• add harness session-storage step: /mnt/data/workplace/ → red error + Enter blocked; /mnt/data → ✓.

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective
• I have updated the documentation accordingly — n/a (gated/unreleased surface)
• My changes generate no new warnings
• Any dependent changes have been merged and published

[github-actions]

Package Tarball

aws-agentcore-0.19.0.tgz

How to install

gh release download pr-1555-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-0.19.0.tgz

[agentcore-devx-automation]

Claude Security Review: no high-confidence findings. (run)

[agentcore-cli-automation]

Looks good to merge.

Both fixes are small, focused, and follow existing patterns:

• The onNotice → managedMemoryNotice wiring in useDevDeploy mirrors the deploy flow (useDeployFlow.ts/DeployScreen.tsx) exactly, including the !complete render gate and <Text dimColor>Note: …</Text> styling.
• The session-storage customValidation now uses validateBYOMountPath matching the existing EFS and S3 mount-path steps in the same file. Confirmed the regex matches the smithy/CFN MountPath constraint as described.
• Test additions cover both the set and unset paths for the notice; mocking is at the same I/O boundaries (handleDeploy, ConfigIO) the existing tests use — no new excessive mocking.
• No new telemetry needed: this is a UI-surfacing fix for a notice already emitted by handleDeploy; deploy-level telemetry already exists at the command boundary.

[tejaskash]

LGTM

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	36.77%	13437 / 36537
🔵	Statements	36.07%	14290 / 39613
🔵	Functions	31.21%	2286 / 7323
🔵	Branches	30.52%	8865 / 29040

Generated in workflow #3673 for commit 20067bf by the Vitest Coverage Report Action