feat: add config command with dot-notation support

[Hweinstock]

Description

Add a new agentcore config [key] [value] command for reading and writing global CLI configuration values using dot-notation keys.

• agentcore config — lists all config
• agentcore config telemetry.enabled — gets a value
• agentcore config telemetry.enabled true — sets a value

Also introduces:

• resilientParse: a util for parsing zod schemas field by field, and allow for fallbacks, skipping, and additional fields. Unifies implementation with existing telemetry implementation.
• Refactored global-config.ts to use a single strict schema as source of truth

Related Issue

Closes #

Documentation PR

N/A

Type of Change

• New feature

Testing

How have you tested the change?

• I ran npm run test:unit and npm run test:integ
• I ran npm run typecheck
• I ran npm run lint
• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[github-actions]

Package Tarball

aws-agentcore-0.15.0.tgz

How to install

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

[agentcore-devx-automation]

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

[agentcore-cli-automation]

Nice work on this — the schema split between strict (write) and lenient (read) is a clean pattern, and the integ tests are thorough. I found one issue that I think needs to be addressed before merging, plus a softer note about telemetry instrumentation.

Main concern: validating the merged config against a strict schema is incompatible with the documented behavior that readGlobalConfig preserves unknown keys (see existing test preserves unknown fields via passthrough in src/cli/__tests__/global-config.test.ts). Any user whose config file contains a legacy or future field will be unable to set any config value. Details inline.

Softer note: telemetry instrumentation — see inline comment on command.ts.

[agentcore-devx-automation]

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

[agentcore-devx-automation]

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

[Hweinstock]

we should move this to another file, IMO its not intuitive that descriptions are in src/cli/tui/copy.ts