Adopt ConfigKit and Go toolchain baseline

This commit is contained in:
2026-11-17 21:59:19 +00:00
parent 65d0e518e5
commit 341fe93e3b
45 changed files with 101 additions and 101 deletions

View File

@@ -147,7 +147,7 @@ Large pipeline configurations may be split into explicitly named fragments and
may use fixed-path selected overlays:
```yaml
configkit:
config:
imports:
- path: config/storage.yml
- path: config/integrations.yaml
@@ -194,7 +194,7 @@ including pipeline roots, imported files, selected overlay values, dynamic
artifact IDs, prompt-variable mappings, campaigns, sessions, and canonical-party
inputs. Rename any existing ordinary-data key named `extends`;
there is no opt-in or automatic conversion. See the pinned [ConfigKit v0.5.0
configuration contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/docs/config.md#sibling-inheritance)
configuration contract](https://forge.maximumdirect.net/base-layer/configkit/src/commit/51ef3144158db1a09fabdbd1c7ae59908c84923b/docs/config.md#sibling-inheritance)
for exact lookup, composition, presence, and provenance semantics.
Overlay names are case-sensitive and use ConfigKit's safe fixed-path naming