fix(tui): improve BYOC flow in add agent (#201)

[notgitika]

Fix all issues I mention in issue closes #201

Description

• Fix Esc key navigation jumping to resource selection instead of previous step by disabling Screen exit handler when sub-components handle their own back navigation
• Fix codeLocation path missing app/ prefix for BYO agents
• Create app/<name>/ directory during BYO flow so users have a clear location for their code
• Show BYO agent code location in success/summary screens with guidance to copy code before deploying
• Remove incorrect "Python agent (Strands Agents SDK)" label from BYO success screen -- this was a bug

This is the new end of create screen if you add BYO agent....

Compare this to earlier in issue: #201

This is interactive add agent in existing project...

Related Issues

#201

Documentation PR

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• I ran npm run test:all
• 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]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	7.25%	473 / 6522
🔵	Statements	6.93%	481 / 6939
🔵	Functions	4.25%	57 / 1341
🔵	Branches	5.15%	194 / 3760

Generated in workflow #206 for commit e039290 by the Vitest Coverage Report Action

[notgitika]

re: Windows compatibility (AI review):

All flagged locations are Windows-safe. Here's why:                                                                                                      
                                                                                                                                                           
  1. join() from Node's path module normalizes separators automatically. join(projectRoot, 'app/MyAgent') produces C:\project\app\MyAgent on Windows.      
  2. replace(/\/$/, '') strips trailing forward slash. The codeLocation value is always stored in agentcore.json with forward slashes (e.g.,               
  "app/MyAgent/") — it's a config convention, not an OS path. The regex strips the trailing / before join() normalizes it to the OS separator.
  3. mkdirSync/mkdir with { recursive: true } works with both path separators on all platforms.
  4. Display paths (CreateScreen.tsx padEnd alignment) use forward slashes (app/MyAgent/) intentionally — this is display text shown to the user, not
  filesystem operations. Forward slashes in display are conventional even on Windows.

  The only theoretical edge case would be if a Windows user manually typed app\MyAgent\ in the TUI, but the default is always set with forward slashes via
  ${APP_DIR}/${name}/, and path.join normalizes regardless.