refactor(create-expert): make ecosystem-builder instruction declarative

[FL4TLiN3]

Summary

Replace procedural "Step 1/2" language with declarative policies.

Changes

Before (procedural)

## Ecosystem Generation Strategy

### Step 1: Analyze Dependencies
From the properties, identify:
- Required API keys...

### Step 2: Generate Ecosystem
...

After (declarative)

## Ecosystem Structure

Every ecosystem includes:
- **Main Expert**: Core functionality
- **Demo Expert**: Works without configuration...

When external dependencies exist:
- **Setup Expert**: Guides users through configuration
- **Doctor Expert**: Diagnoses configuration issues

Template Changes

• Setup Expert: Replaced 4 numbered phases with "Configuration Policies"
• Doctor Expert: Replaced 3 numbered checks with "Diagnostic Areas"

Rationale

Per docs/making-experts/best-practices.md:

The LLM knows how to have a conversation. What it doesn't know is your company's policies.

Test plan

• CI passes

Closes #353

🤖 Generated with Claude Code

---

Note

Shifts from procedural "Step 1/2" flow to declarative policies for building expert ecosystems.

• Renames/rewrites ECOSYSTEM_BUILDER_INSTRUCTION to define Ecosystem Structure: always include Main and Demo; add Setup/Doctor only when external deps exist
• Simplifies Setup Expert template: replaces numbered phases with Configuration Policies and explicit Success Output; emphasizes quick (<2 min) completion
• Simplifies Doctor Expert template: replaces numbered checks with Diagnostic Areas and a concise Output Format
• No changes to skills, delegates, or runtime; content-only refactor
• Adds patch changeset (.changeset/declarative-ecosystem-builder.md)

^{Written by Cursor Bugbot for commit d7109ea. This will update automatically on new commits. Configure here.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!