Discovery needs an exact source
People can browse cards and examples. Automated tools need stable names, versions, statuses, import paths, dependencies, and constraints. A registry is the bridge between those two forms of discovery.
If the registry says a capability is complete, the implementation and tests must agree. If an icon record declares an import, that literal path must resolve. If a theme lists an asset, the installer must bring it with the source.
Status is part of the API
Complete, partial, and planned are operational states. An agent should use a complete capability freely, use partial only for an explicitly covered case, and never emit planned behavior as working code.
A truthful limitation is more useful than a confident example that cannot compile.
Generate counts, verify contracts
Homepage counts and release claims should come from versioned manifests, not from manually maintained marketing copy. Registry generation should fail when required records are missing or examples no longer compile.
That makes the catalog a promise: a small, testable interface between the framework, its documentation, and every agent that depends on it.