How the parser and generator registry drives discovery

The web app should not guess which pairs exist. The SDK registry describes parsers, generators, support status, and route capabilities in one place.

From registrations to routes

The route presenter reads registered source and target formats, asks the SDK for capabilities, and creates stable slugs. New combinations therefore appear in the directory and can link into the same Playground flow without a web type change.

Why metadata matters

Support status alone is not enough. IR coverage, limitations, and option catalogs tell users whether a route is ready for a quick experiment or deserves a careful review. Keeping this metadata close to registration also gives tests a stable contract.

Extension boundary

The current product uses the SDK default registry. Custom registries can be added later through an explicit injection boundary instead of silently changing the source of truth.