Simplify agent configurations and fix team bundle builds

Major refactoring to streamline agent configuration structure and improve build reliability:

Agent Configuration Simplification:
- Remove environment sections from all agent YAML files
- Add single 'persona' property to agent configs pointing to persona file
- All agents now use consistent, simplified structure without web/ide environment splits
- Fix dev agent to be available for web environment (was causing team-dev bundle build failure)

Build System Updates:
- Update dependency-resolver.js to use new persona property instead of environments.web.persona_file
- Update bundle-optimizer.js to load personas using agent's persona property
- Remove environment availability checks since all agents are now web-compatible
- Change output directory from dist/web/bundles/ to dist/web/teams/ for clarity

File Organization:
- Move IDE-specific personas (dev.ide.md, devops-pe.ide.md, sm.ide.md) to bmad-core/ide-agents/
- Rename team bundles for clarity:
  - team-full.yml → team-full-app.yml (web application teams)
  - team-planning.yml → team-small-service.yml (backend service teams)
- Remove team-full-ide.yml (IDE teams will be handled separately)

This change ensures all 3 web team bundles build successfully and simplifies future agent maintenance.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

bmad-core/utils/orchestrator-commands.md

@@ -18,7 +18,8 @@ When these commands are used, perform the listed action:
 ## Agent-Specific Commands
 
 The `/{agent}` command switches to any agent included in the bundle. The command accepts either:
+
 - The agent's role identifier (e.g., `/pm`, `/architect`, `/dev`)
 - The agent's configured name (e.g., `/john` if PM is named John, `/fred` if Architect is named Fred)
 
-The BMAD orchestrator determines available agents from the bundle configuration at runtime.
+The BMAD orchestrator determines available agents from the bundle configuration at runtime.