feat(wizard): interactive project add config-bundle

[notgitika]

Stacked on #2284 — review the last commit only (feat(wizard): interactive project add config-bundle). The earlier commits in this diff are #2284 and go away once it merges.

Adds the wizard behind a bare agentcore project add config-bundle: name → components → description → branch → commit → review. Enter on the success panel goes back to the add menu.

Bundle assembly moves out of the flag handler into toAddConfigBundleInput, which both paths call, so the wizard cannot accept a bundle the flags would reject. --components and the wizard's components step share one ComponentsSchema, and mainline is now a named default rather than a literal in the flag declaration.

No behaviour change on the flag path. Every other resource under project add stays command line only.

[agentcore-devx-automation]

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

[agentcore-devx-automation]

AgentCore Harness Review

Verdict: Changes requested

Really nice refactor — factoring the wizard shell out of ProjectCreateScreen into <Wizard>/<Step> and shared fields, threading duplicate‑step‑name detection through render, and driving the shared driveProgress/TaskList path uniformly all read very cleanly. Tests use real dependencies (project harness, renderScreen, ttyTestIO) rather than mocks, which is exactly the right shape. One issue worth addressing before merging:

add config-bundle no longer reports missing --components clearly

src/handlers/project/add/config-bundle/index.ts used to have:

const components = parseJsonFlagWithSchema("components", componentsText, ComponentsSchema);
if (components === undefined) {
  throw new InputValidationError("required option '--components <components>' not specified");
}

That explicit branch is gone. The new flow is:

const components = parseJsonFlag<unknown>("components", await source.resolveText("components", flags.components));
const input = toAddConfigBundleInput({ ..., components, ... });

When a user runs agentcore project add config-bundle --name foo (no --components), flags.components is undefined, source.resolveText will either surface an empty/undefined text, and the user ends up with either a parseJsonFlag JSON error or ComponentsSchema.safeParse(undefined) → Invalid value for option '--components': …expected record, received undefined. That's noticeably worse than the previous "required option '--components ' not specified" message, and there's no coverage for this case now that the check is removed (the headless dispatch test only covers missing --name).

Options:

1. Restore the explicit if (flags.components === undefined) throw new InputValidationError("required option '--components <components>' not specified") guard next to the existing !flags.name check.
2. Confirm parseJsonFlag/toAddConfigBundleInput produce a good message for the missing case and add a test asserting the exact user‑facing string.

Either way, please add a dispatch test for --name foo (no --components) so we don't regress this again.

Worth confirming (not blocking)

• src/handlers/project/add/runtime/index.ts: the --name flag schema tightens from z.string().max(42) to RuntimeNameSchema (letters/digits/underscores, must start with a letter). If RuntimeResourceConfigSchema was already enforcing the pattern downstream this is just moving validation earlier, but if any existing users have hyphenated runtime names (my-agent), this becomes a breaking flag‑path change. Please double‑check that AgentNameSchema is what RuntimeResourceConfigSchema already validated names against.
• AddRuntimeScreen/AddConfigBundleScreen default onError to "exit", so an addResource failure tears the TUI down rather than dropping back to the menu the user navigated from. That's inconsistent with the "one keystroke away from adding another resource" comment on onDone. Not a code correctness issue, but worth deciding intentionally — for add, either "retry" (if partial state is recoverable) or a menu‑return error path may be a better UX than exit.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 97.68935% with 18 lines in your changes missing coverage. Please review.
✅ Project coverage is 97.07%. Comparing base (4a23516) to head (0eb21c0).
⚠️ Report is 2 commits behind head on refactor.

Files with missing lines	Patch %	Lines
src/components/wizard/Wizard.tsx	94.65%	10 Missing ⚠️
src/components/wizard/fields.tsx	96.62%	6 Missing ⚠️
src/components/wizard/context.tsx	94.44%	1 Missing ⚠️
src/handlers/project/create/screen.tsx	98.46%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           refactor    #2288    +/-   ##
==========================================
  Coverage     97.06%   97.07%            
==========================================
  Files           569      576     +7     
  Lines         39322    39744   +422     
==========================================
+ Hits          38167    38580   +413     
- Misses         1155     1164     +9     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[notgitika]

Thanks — going through these.

Missing --components. The guard is still there. handle keeps both early checks, !flags.name and !flags.components, and the second one throws required option '--components <components>' not specified before resolveText or parseJsonFlag runs; only the parse and schema step moved into the shared builder. I checked it against the built CLI, and there is now a dispatch test asserting the exact string for --name foo with no --components, so it can't regress silently.

Runtime name schema. Not a breaking change. ProjectRuntimeSchema.shape.name is AgentNameSchema (/^[a-zA-Z][a-zA-Z0-9_]{0,47}$/), so a hyphenated name was already rejected downstream — the flag just says so earlier now, with the same message. The old max(42) cap is preserved by RuntimeNameSchema.

onError. Agreed, and applied to both add screens: a failed add now reports itself and hands the form back, so esc returns to the review step with every answer intact instead of exiting. project create keeps "exit" — that one owns the terminal it was launched in. Covered by a test that adds a duplicate runtime name and drives the form back.

One unrelated change in the latest push: the components step is now a textarea (enter inserts a newline, ctrl+d continues), since a components map is usually pasted pretty-printed, and the description step is gone — --description still sets one.

[agentcore-devx-automation]

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

[agentcore-devx-automation]

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

[agentcore-devx-automation]

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