fix: resolve agent namespace issues across 11 plugins

Fixed 109 agent namespace issues where external agent references were
missing proper namespace prefixes (plugin-name::agent-name format).

Affected plugins (bumped to v1.2.1):
- tdd-workflows: Fixed 12 references in tdd-cycle, tdd-green, tdd-red
- incident-response: Fixed 29 references in incident-response, smart-fix
- data-engineering: Fixed 12 references in data-driven-feature
- backend-development: Fixed 11 references in feature-development
- framework-migration: Fixed 10 references in legacy-modernize
- git-pr-workflows: Fixed 7 references in git-workflow
- security-scanning: Fixed 7 references in security-hardening
- full-stack-orchestration: Fixed 6 references in full-stack-feature
- application-performance: Fixed 5 references in performance-optimization
- comprehensive-review: Fixed 5 references in full-review
- multi-platform-apps: Fixed 5 references in multi-platform

Changes:
- Added namespace prefixes for all external agent references
- Replaced 14 missing agents with appropriate equivalents
- Updated marketplace.json to bump affected plugin versions

Closes #95

plugins/full-stack-orchestration/commands/full-stack-feature.md

@@ -5,19 +5,19 @@ Orchestrate full-stack feature development across backend, frontend, and infrast
 ## Phase 1: Architecture & Design Foundation
 
 ### 1. Database Architecture Design
-- Use Task tool with subagent_type="database-architect"
+- Use Task tool with subagent_type="database-design::database-architect"
 - Prompt: "Design database schema and data models for: $ARGUMENTS. Consider scalability, query patterns, indexing strategy, and data consistency requirements. Include migration strategy if modifying existing schema. Provide both logical and physical data models."
 - Expected output: Entity relationship diagrams, table schemas, indexing strategy, migration scripts, data access patterns
 - Context: Initial requirements and business domain model
 
 ### 2. Backend Service Architecture
-- Use Task tool with subagent_type="backend-architect"
+- Use Task tool with subagent_type="backend-development::backend-architect"
 - Prompt: "Design backend service architecture for: $ARGUMENTS. Using the database design from previous step, create service boundaries, define API contracts (OpenAPI/GraphQL), design authentication/authorization strategy, and specify inter-service communication patterns. Include resilience patterns (circuit breakers, retries) and caching strategy."
 - Expected output: Service architecture diagram, OpenAPI specifications, authentication flows, caching architecture, message queue design (if applicable)
 - Context: Database schema from step 1, non-functional requirements
 
 ### 3. Frontend Component Architecture
-- Use Task tool with subagent_type="frontend-developer"
+- Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
 - Prompt: "Design frontend architecture and component structure for: $ARGUMENTS. Based on the API contracts from previous step, design component hierarchy, state management approach (Redux/Zustand/Context), routing structure, and data fetching patterns. Include accessibility requirements and responsive design strategy. Plan for Storybook component documentation."
 - Expected output: Component tree diagram, state management design, routing configuration, design system integration plan, accessibility checklist
 - Context: API specifications from step 2, UI/UX requirements
@@ -25,19 +25,19 @@ Orchestrate full-stack feature development across backend, frontend, and infrast
 ## Phase 2: Parallel Implementation
 
 ### 4. Backend Service Implementation
-- Use Task tool with subagent_type="python-pro" (or "golang-pro"/"nodejs-expert" based on stack)
+- Use Task tool with subagent_type="python-development::python-pro" (or "golang-pro"/"nodejs-expert" based on stack)
 - Prompt: "Implement backend services for: $ARGUMENTS. Using the architecture and API specs from Phase 1, build RESTful/GraphQL endpoints with proper validation, error handling, and logging. Implement business logic, data access layer, authentication middleware, and integration with external services. Include observability (structured logging, metrics, tracing)."
 - Expected output: Backend service code, API endpoints, middleware, background jobs, unit tests, integration tests
 - Context: Architecture designs from Phase 1, database schema
 
 ### 5. Frontend Implementation
-- Use Task tool with subagent_type="frontend-developer"
+- Use Task tool with subagent_type="frontend-mobile-development::frontend-developer"
 - Prompt: "Implement frontend application for: $ARGUMENTS. Build React/Next.js components using the component architecture from Phase 1. Implement state management, API integration with proper error handling and loading states, form validation, and responsive layouts. Create Storybook stories for components. Ensure accessibility (WCAG 2.1 AA compliance)."
 - Expected output: React components, state management implementation, API client code, Storybook stories, responsive styles, accessibility implementations
 - Context: Component architecture from step 3, API contracts
 
 ### 6. Database Implementation & Optimization
-- Use Task tool with subagent_type="sql-pro"
+- Use Task tool with subagent_type="database-design::sql-pro"
 - Prompt: "Implement and optimize database layer for: $ARGUMENTS. Create migration scripts, stored procedures (if needed), optimize queries identified by backend implementation, set up proper indexes, and implement data validation constraints. Include database-level security measures and backup strategies."
 - Expected output: Migration scripts, optimized queries, stored procedures, index definitions, database security configuration
 - Context: Database design from step 1, query patterns from backend implementation