Fix: AGENTS.md template is out of sync with create-expert-toml architecture

[FL4TLiN3]

Description

The AGENTS.md template generated by agents-md-template.ts describes a different expert architecture than what is actually implemented in create-expert-toml.ts.

Current Behavior

AGENTS.md template (agents-md-template.ts:37-49) describes:

create-expert (Coordinator)
├── property-extractor      → Extracts success criteria
├── happy-path-manager      → Stage 1: Normal operation testing
│   ├── expert-designer     → Creates/improves Expert definitions
│   └── expert-tester       → Runs tests and evaluates results
├── unhappy-path-manager    → Stage 2: Error handling testing
│   ├── expert-designer
│   └── expert-tester
├── adversarial-manager     → Stage 3: Security testing
│   ├── expert-designer
│   └── expert-tester
└── report-generator        → Final property achievement report

Actual implementation (create-expert-toml.ts) defines:

create-expert (Coordinator)
├── property-extractor
├── ecosystem-builder
├── integration-manager
│   ├── functional-manager
│   │   └── expert-tester
│   └── usability-manager
│       └── expert-tester
└── report-generator

Expected Behavior

The AGENTS.md template should accurately reflect the actual expert hierarchy.

Impact

Users reading the generated AGENTS.md will have an incorrect mental model of how the create-expert system works, leading to confusion when debugging or extending the system.

Affected Areas

• apps/create-expert/src/lib/agents-md-template.ts:37-49

Acceptance Criteria

• AGENTS.md template architecture diagram matches actual implementation
• All expert names in AGENTS.md exist in create-expert-toml.ts
• Non-existent experts (happy-path-manager, unhappy-path-manager, adversarial-manager, expert-designer) are removed or replaced with actual experts

[github-actions]

🤖 Processing...

---