Module kit 

The component registry — the model support kit’s catalog of parts.

docs/design/model-support-kit.md: the kit is the catalog of composable support parts (a profile assembles a subset of them). This grows the flat KNOWN_TECHNIQUES string list into a typed registry: each part carries the four contract fields the kit needs to compose parts honestly — its axis, its kind (where it mounts), what it presupposes, and its tier (does it run headless).

This PR is internal — it changes no behavior. It is the substrate the bundle + loadout layers (and Config::validate’s presupposes check) build on.

Structs

RegistryEntry

One row in the COMPONENT_REGISTRY — a support part and its contract.

Enums

Axis

Which axis of support a component serves (docs/design/model-support-kit.md).

MountKind

Where a component mounts in the harness loop — tells a driver how to run it.

Tier

Whether a component runs in the headless flight tier (wyvern, no TUI) or needs the interactive surface — the amphibious split made a checked property.

Constants

COMPONENT_REGISTRY

The catalog of parts (the kit). The ids are exactly KNOWN_TECHNIQUES — pinned by a test so the two cannot drift.

Functions

component

Look up a component by its id, or None if unknown.

is_known

Whether id names a registered component.