Remove bundled catalog integration

This commit is contained in:
2026-10-17 06:08:35 +00:00
parent ee40a1bdd2
commit 13b60a72ac
21 changed files with 81 additions and 413 deletions

View File

@@ -39,8 +39,8 @@ of those inventories without consulting ConfigKit or copying definitions.
The root `DirectoryInputs` and `FilesystemInputs` helpers discover sorted YAML
files under an explicit root, provide resource context, and leave imports
disabled. Each returned slice belongs to one strict-composition group; file
order does not confer priority. The engine prepends selected catalog and
Promptkit-owned definitions, then caller underlays and optional main. The
order does not confer priority. Caller underlays are composed in their given
order, followed by the optional main input. The
[configuration tests](../../internal/configuration/load_test.go) exercise the
real loader and final-value handoff.
@@ -112,19 +112,7 @@ dependency-bearing range scopes make discovery incomplete. Uncalled definitions
and bypassed session templates are not traversed. This internal walker does not
change rendering behavior.
## Profiles And Built-Ins
`internal/catalog` selects the tagged OpenRouter `v3.20261013.0` and
Rakestrawhome `v3.20261013.0` assets as one ConfigKit underlay and PromptKit-owned
profiles as the next. The selected catalog tags are local candidates and may not
be publicly available. It discovers YAML inputs, including each catalog's
opt-in `smoke-tests` root in addition to its existing `catalog` root, and
supplies passive filesystem context without parsing or pre-validating catalog
definitions. Catalog metadata remains separate from existing `/v3` assets for
strict-loader compatibility. The configuration loader
validates only the final effective backend and profile values, including
consumer overlays of maintained bases or backends. There is no catalog-only
preflight, reserved source namespace, or replay of backend registration.
## Profiles
ConfigKit resolves profile inheritance before the handoff. The configuration
adapter validates effective references and field values, then builds target
@@ -135,8 +123,7 @@ provider work. Preparation applies runtime overrides and then checks target
completeness. Identity-only profile selection can identify a partial captured
profile without copying its target or requiring readiness. The
[target tests](../../internal/configuration/targets_test.go) cover effective
target interpretation, while the [catalog tests](../../internal/catalog/catalog_test.go)
cover selected released assets.
target interpretation.
The internal engine delegates listing through a narrow identity-inventory
interface directly to the configuration snapshot. The execution runner has no