Implemented support for loading configuration from nested subdirectories

docs/internal/adapters.md

@@ -30,7 +30,7 @@ HTTP adapter:
 
 Filesystem repositories:
 
-- Input: prompt/profile YAML files.
+- Input: prompt/profile YAML files under configured directories.
 - Output: normalized domain definitions/profiles or typed errors.
 
 Artifact reader:
@@ -79,6 +79,9 @@ Execution profile/request settings used through runner:
 Strict decoding and input checks:
 
 - config/prompt/profile loaders reject unknown YAML fields.
+- prompt/profile repositories scan nested subdirectories recursively.
+- prompt/profile lookup uses YAML `id` values; subdirectory paths are organizational only.
+- duplicate prompt/profile IDs are invalid and fail instead of using first-match behavior.
 - HTTP DTO decoder rejects unknown JSON fields.
 - raw API key payload fields are rejected by strict decoding in profile/http paths.
 
@@ -97,6 +100,7 @@ Validator:
 
 - `basic`, `json`, `json_schema` content failures return `ValidationFailed` results.
 - schema load/compile/path failures are runtime errors.
+- schema lookup uses explicit `schema_path` values relative to `schema_dir`; it does not recursively search by basename.
 
 HTTP error mapping: