Retire completed plans and outline named inheritance

This commit is contained in:
2026-09-29 20:11:42 +00:00
parent b604aa167b
commit 0a4b774bfe
9 changed files with 301 additions and 1318 deletions

View File

@@ -16,8 +16,7 @@ The following remain deliberately excluded:
- automatic `conf.d` discovery;
- remote imports, arbitrary providers, and additional configuration formats;
- custom merge strategies, sequence merging, and reset operators;
- named overlay inheritance, tracked separately in the
[PromptKit inheritance request](feature-request-promptkit-inheritance.md);
- named overlay inheritance;
- parser-specific or custom structural-decoding extension APIs;
- generic dynamic-subtree conversion and module-registry APIs;
- automatic schema migrations;
@@ -28,3 +27,8 @@ The following remain deliberately excluded:
Applications may build their own validate, effective-value, source, bootstrap, and
explanation commands around the library. Broadening these boundaries requires
concrete consumer evidence, compatibility review, and an explicit design change.
Opt-in inheritance between named configuration entries is proposed in the
[named-inheritance roadmap](named-inheritance.md), based on the
[downstream request](feature-request-promptkit-inheritance.md). It is not yet
implemented and is distinct from inheritance between selected overlay files.