dev: Agent Inspector Memory tab always says memory must be deployed; dev server lacks deploymentStatus and /api/memory routes #2735

Description

In agentcore dev --mode browser, the Agent Inspector's Memory tab always shows:

AgentCore Memory must be deployed before it can be used.
To test memory, run agentcore deploy and restart dev.

This happens even when the memory is deployed to the target's stack. Running agentcore deploy and restarting dev doesn't help.

The bundled inspector UI and the dev server in 1.0.1 don't agree on the API:

1. deploymentStatus is never set on memories. The Memory tab shows the warning when memories.some(m => m.deploymentStatus !== "deployed"). The dev server's handleResources (GET /api/resources, dist/main.js) builds memories from the spec as { name, strategies, expiryDays } and never adds deploymentStatus. So the field is always undefined and the warning always shows. (deploymentStatus appears nowhere in dist/main.js. Only the agentcore status path computes a deploymentState, via resolveProjectResources.)
2. The memory endpoints don't exist. The inspector calls GET /api/memory?memoryName=…&namespace=… and POST /api/memory/search. The dev server only routes /api/mcp, /api/resources, /api/start, /api/status and /api/traces (plus /invocations and the A2A card), so these calls return 404 and the UI shows "Memory browsing is only available in invoke mode." Without the warning, the tab still couldn't list or search records.

Steps to Reproduce

1. Create a project with a runtime and a memory (agentcore add → memory), and add a target to aws-targets.json.
2. agentcore deploy --target <target> and confirm the stack exports …-Memory-<name>-Arn.
3. agentcore dev --mode browser.
4. Open the Memory tab.

Expected Behavior

The deployed memory shows as deployed, and its records can be listed and searched by namespace.

Actual Behavior

The "must be deployed" warning always shows. Requests to /api/memory and /api/memory/search return 404.

CLI Version

1.0.1

Operating System

macOS

Additional Context

• Node.js 24.22.1, macOS 27.0, TypeScript (Node 22 CodeZip) runtime with a memory declared in agentcore.json.
• Possible fix: in dev, resolve memories against the target's deployed state (as agentcore status does via resolveProjectResources), set deploymentStatus in /api/resources, and add the /api/memory and /api/memory/search routes the inspector already calls.