Problem

Current ToolAvailability contains tier requirements only for legacy granular tools (list_merge_requests, get_merge_request, etc.), but new CQRS tools (browse_merge_requests, manage_merge_request) are not registered.

This means tier badges in --export documentation are missing for most CQRS tools.

Proposed Solution

Add action-level tier requirements mapping:

// Example: manage_merge_request tier requirements by action
const CQRS_TOOL_TIERS = {
  "manage_merge_request": {
    "create": { tier: "free", minVersion: 8.0 },
    "update": { tier: "free", minVersion: 8.0 },
    "merge": { tier: "free", minVersion: 8.0 },
    "approve": { tier: "premium", minVersion: 10.6 },
    "unapprove": { tier: "premium", minVersion: 10.6 },
    "rebase": { tier: "free", minVersion: 11.6 }
  },
  "browse_merge_requests": {
    "list": { tier: "free" },
    "get": { tier: "free" },
    "diffs": { tier: "free" },
    "compare": { tier: "free" }
  }
  // ... etc
};

Tasks

• Create mapping structure for CQRS tool action tiers
• Migrate existing granular tool requirements to new structure
• Update getToolTierInfo() to support action-level tiers
• Update --export to show highest tier required for any action
• Add documentation for tier requirements

Related

• Depends on CQRS migration completed in feat: Dynamic action filtering with multi-level description customization #32
• Enhances feat(cli): Add --export flag to list-tools for TOOLS.md generation #47 (list-tools --export)