Module discovery

Structs§

CapDoc: One row per provider that registered a CAPABILITY.md, summarised for the LLM-facing “## Capability docs” block in pilot’s system prompt. We expose the provider_id (what the LLM passes to read_capability_doc), the package kind (from atlas’s authoritative CapabilityProvider.kind, so skills can be flagged read-first), and a one-line description lifted from the CAPABILITY.md frontmatter — enough for the model to judge relevance without reading the full manual. The internal namespace and any filesystem path are deliberately NOT exposed.

cap_md_index: Returns a CapDoc per provider that registered non-empty CAPABILITY.md content. Pilot lists these in the system prompt and instructs the LLM to pull the full text on demand via the read_capability_doc builtin.
discover: Query atlas for every MCP-transport capability. Returns one (provider_id, Capability) pair per LLM-callable contract; callers pull description + input_schema_json out of params.kind themselves. Capabilities with missing or non-MCP params are dropped with a warning.
kind_label 🔒: Map atlas’s CapabilityProvider.kind enum to the lowercase label the prompt uses. Atlas is the source of truth for a provider’s kind.
llm_name: LLM-facing tool name = <area>_<leaf> of a contract_id, where <area> is the segment immediately before the leaf. Examples: robonix/primitive/camera/snapshot → camera_snapshot robonix/primitive/lidar/snapshot → lidar_snapshot robonix/primitive/chassis/move → chassis_move robonix/service/memory/search → memory_search robonix/service/navigation/navigate → navigation_navigate
parse_description 🔒: Pull description from a CAPABILITY.md YAML frontmatter block.