Integrate released catalog sources with effective configuration

docs/internal/sources.md

@@ -88,15 +88,17 @@ publishes independently copied values from memory. It does not resolve profile
 inheritance. Configured consumer sources continue to use the lazy point lookup
 repositories described above.
 
-`internal/catalog` validates the imported immutable OpenRouter and
-Rakestrawhome asset modules as one private adapter boundary. It enforces their
-manifest, layout, profile ownership, inheritance, and secret-safety rules
-before returning raw catalog sources. Internal engine assembly uses those validated
-catalogs as the lowest-precedence profile source.
+`internal/catalog` selects the released keyed OpenRouter and Rakestrawhome
+assets as one ConfigKit underlay and PromptKit-owned profiles as the next.
+It discovers YAML inputs and supplies passive filesystem context without
+parsing or pre-validating catalog definitions. The configuration loader
+validates only the final effective backend and profile values, including
+consumer overlays of maintained bases or backends. The new path has no catalog
+source-layout, ownership-prefix, connection-field, or secret-key rejection.
 
-Normalized external catalog profile IDs with the exact `promptkit-` prefix are
-rejected at this adapter boundary. That reservation applies only to imported
-catalogs; configured consumer sources retain the ordinary profile-ID rules.
+Until public engine assembly switches to that loader, `internal/legacycatalog`
+supports the existing public construction path with the published flat `/v2`
+assets. The repository behavior below describes that temporary path.
 
 The overlay repository consults the next repository only when the
 higher-precedence repository reports that a profile is absent. A reliably