Add custom backend configuration

docs/config.md

@@ -39,11 +39,39 @@ do not override a prior value. Raw API-key fields are not accepted.
 | `server.max_artifact_bytes` | `16777216` | Maximum HTTP file-input artifact bytes; `0` disables the limit. |
 | `server.max_response_bytes` | `16777216` | Maximum encoded HTTP response bytes; `0` disables the limit. |
 | `defaults.render_format` | `text` | Default prepared-run output format: `text` or `json`. |
+| `backends` | unset | Optional mapping of custom Promptkit backend IDs to engine-scoped connection and capacity settings. |
 
 The size fields must be zero or greater. The [HTTP API](api.md) defines how
 each limit is enforced and reported. `server.artifact_root` configures an HTTP
 deployment boundary; see [operations](operations.md) for deployment handling.
 
+## Custom Backends
+
+Use `backends` when a profile selects an application-defined backend ID:
+
+```yaml
+backends:
+  local-gpu:
+    endpoint: http://localhost:11434/v1
+    api_key_env: LOCAL_GPU_API_KEY
+    extra_params:
+      provider_option: enabled
+    concurrency_limit: 2
+    queue_capacity: 0
+```
+
+Each mapping key is the case-sensitive backend ID. `endpoint` is required;
+`api_key_env`, `extra_params`, `concurrency_limit`, and `queue_capacity` are
+optional. `concurrency_limit: 0` leaves the backend unlimited. Omitting
+`queue_capacity` lets Promptkit use its default for a limited backend, while
+an explicit `queue_capacity: 0` disables queueing.
+
+Configuration strictly owns the YAML shape and rejects unknown fields. Promptkit
+validates backend IDs, endpoints, environment-variable names, extra parameters,
+and capacity relationships when Scriptorium constructs its engine. There are no
+backend command-line overrides. Store only an environment-variable name in
+`api_key_env`; raw API-key fields are not accepted.
+
 ## Framework Source Mapping
 
 Scriptorium passes `prompt_dir`, `profile_dir`, and `schema_dir` to Promptkit

docs/internal/adapters.md

@@ -38,6 +38,12 @@ resolves its own defaults and definition-required inputs.
 with `promptkit.WithArtifactReader`, passes the engine through the HTTP
 adapter's consumer-owned `Runner` interface, and starts the server.
 
+All three CLI paths assemble the engine from the same resolved prompt, profile,
+and schema directories plus configured custom backends. Each backend is mapped
+to Promptkit's public `Backend` value and registered during engine construction,
+so one constructed server engine retains one immutable backend registry and its
+associated capacity state.
+
 ### HTTP
 
 The handler enforces transport limits and strict JSON decoding before mapping

docs/internal/sources.md

@@ -10,9 +10,11 @@ owned by the tagged
 ## Application Source Locations
 
 `internal/config` resolves `prompt_dir`, `profile_dir`, and `schema_dir` from
-Scriptorium defaults, configuration files, and CLI overrides.
-`internal/adapter/cli` passes those paths into `promptkit.Config` when
-constructing the engine.
+Scriptorium defaults, configuration files, and CLI overrides. It also resolves
+the application-owned `backends` mapping into sorted engine settings.
+`internal/adapter/cli` passes the directories into `promptkit.Config` and maps
+each configured backend to Promptkit's public engine registration when
+constructing an engine shared by the command path.
 
 Scriptorium does not search, parse, validate, or overlay framework source files
 itself. Promptkit owns prompt selection, profile built-ins and overlays, schema

docs/roadmap/implementation.md

@@ -145,6 +145,8 @@ no inputs; only Promptkit rejects missing definition-required data.
 
 ## Stage 3: Add Engine-Scoped Custom Backend Configuration
 
+**Completion: Complete.**
+
 Add the application-owned configuration needed for Promptkit profiles to select
 custom backend IDs and capacity policies.