cursus.mcp.tools.steps

steps.* — the agent-facing step connection / I-O view (FZ 31e1d3d follow-up).

Under the Strategy + Facade design the per-step builder is a near-empty shell, so the container source/destination paths, the runtime property_path references, and the nested training-channel fan-out are no longer readable from a builder class — they live in the .step.yaml + the bound handler. steps.io exposes that wiring so an agent can see, for a step:

• per dependency (consumer): container path, required, type, compatible_sources, and the SageMaker training channel(s) the input fans into (e.g. input_path -> [train, val, test]);

• per output (producer): container path + the runtime property_path a downstream step resolves against.

It is the path/wiring complement to catalog.step_spec (which gives the ports + property_path but not the container paths or the channel fan-out). Reads the same interface + handler the builder uses (steps.interfaces.io_view.describe_step_io), so it cannot drift. Read-only.