The portal migration exposed multiple locations that independently define supported content types, ordering, labels, icons, and metadata. While the new Knowledge Collector centralizes much of this logic, several tools and utilities still maintain their own CPT arrays.
This task creates a single authoritative registry responsible for:
- supported post types
- ordering
- display labels
- icons
- colors
- section names
- future presentation metadata
Every collector, renderer, search tool, taxonomy page, portal, and developer utility should consume this registry instead of maintaining independent arrays.