(Micro-Fix) CLI crash when exports/ directory is missing - #2348

Description

This PR fixes a first-run UX issue in the CLI where commands like framework list or framework shell fail if the exports/ directory does not exist.

Instead of immediately returning, the CLI now creates the exports/ directory when it’s missing. This aligns the runtime behavior with the documentation, which already assumes exports/ is the default location for agent packages.

This helps new users and contributors who run the CLI on a clean clone without manually creating the directory.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

Related Issues

Fixes #696

Changes Made

• Lazily create the exports/ directory when it does not exist instead of failing early
• Keep existing behavior unchanged once the directory is present
• Improve first-run CLI robustness without altering agent discovery logic

Testing

Describe the tests you ran to verify your changes:

• Unit tests pass (cd core && pytest tests/)
• Lint passes (cd core && ruff check .)
• Manual testing performed

manual verification:

• Ran python -m framework list on a clean clone → directory created, no crash
• Ran python -m framework shell with no agents → graceful message shown
• Existing behavior unchanged when exports/ already exists

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

Screenshots