holoctl-provider-mcplisted

# Provider MCP discovery Bridge between the user's external board and the holoctl work-item model. The transport (the MCP server itself) lives in Claude Code's `.mcp.json` — this skill just declares what URL patterns map to what MCP tools and tries to use them. ## Step 1 — Read the provider catalog ``` mcp__holoctl__config_show() // returns the resolved config ``` Extract `providers`. Each entry has: - `enabled` — `auto` (probe at runtime), `always` (assume tool exists), `disabled` (skip). - `url_pattern` — Python regex with at least `(?P<ref>...)`. - `mcp_fetch_tool` — name of the MCP tool to call. - `mcp_search_tool` — optional, for keyword search. - `label_template` — `"{ref}: {title}"` style template. Shipped defaults cover **Linear, GitHub, Trello, Azure DevOps, Jira, Slack**. The user may have added custom providers (e.g. an internal company board) via `hctl provider add`. ## Step 2 — Match the input The user passed either: - A full URL (e.g. `https://linear.app/eng/issue/ENG-42`), OR - A ref alone (e.g. `ENG-42`) — disambiguate by asking which provider, OR - Free-form text — skill should not fire; let `/spec` handle paste. For each provider entry with `enabled` in `{"auto", "always"}`: - Test `url_pattern` against the input. On match, capture `ref` and any other named groups. - Record `source_provider = <name>`, `source_ref = <ref>`, `source_url = <full URL>` as candidates. If multiple providers match, pick the most specific (longest pattern). If none, ski