Correct composed configuration example description
This commit is contained in:
@@ -59,7 +59,7 @@ documentation link/diff checks passed; no production code changed.
|
||||
|
||||
### R4: Update The Composed-Example Description
|
||||
|
||||
Priority: P3 (low). Status: Open.
|
||||
Priority: P3 (low). Status: Complete.
|
||||
|
||||
Location: `docs/config.md:95–96`, after the example migration in `2027b80`.
|
||||
|
||||
@@ -78,6 +78,13 @@ the old prose. The old backend fragment had no application defaults to preserve.
|
||||
Acceptance: the description matches the maintained files and the existing
|
||||
composed-overlay render command still succeeds offline.
|
||||
|
||||
Resolution: the configuration reference now links to the one imported
|
||||
application source-selection fragment and the separately selected framework
|
||||
backend file, retaining the local-overlay example. The existing composed-overlay
|
||||
render command passed offline with credential environment variables unset;
|
||||
the linked files and diff whitespace were checked. No configuration files or
|
||||
loading behavior changed.
|
||||
|
||||
### R5: Include Framework Configuration Inspection In Built-In Usage
|
||||
|
||||
Priority: P3 (low). Status: Open.
|
||||
|
||||
Reference in New Issue
Block a user