agentic-dev-loop 0.9.2__tar.gz → 0.10.2__tar.gz

{agentic_dev_loop-0.9.2/src/agentic_dev_loop.egg-info → agentic_dev_loop-0.10.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentic-dev-loop
-Version: 0.9.2
+Version: 0.10.2
 Summary: Turn an LLM into a gated, sandboxed, resumable construction loop over your codebase.
 Author: Luke Wilson
 License-Expression: Apache-2.0
@@ -202,6 +202,17 @@ llm:
   api_key_env: OPENAI_API_KEY
   # reasoning_effort: medium                        # optional: low | medium | high | xhigh | none
 
+# Named LLM profiles (054): a step names one with `llm: <name>` to move the
+# whole profile (model, endpoint, key, effort default) together - no partial
+# merges. The `llm:` block above remains the default. Profile keys are
+# host-side: sandbox access still goes through `secrets:`, never a profile key.
+# llms:
+#   review:
+#     model: openai/deepseek-v4-pro
+#     base_url: https://api.deepseek.com
+#     api_key_env: REVIEW_API_KEY
+#     reasoning_effort: xhigh
+
 max_attempts: 10                                        # CLI --max-attempts overrides
 agents_dir: sdk_agents                                  # your <name>.agent.md files
 
@@ -231,7 +242,8 @@ steps:
     agent: review
     artifact: review-findings.md
     verdicts: { pass: APPROVED, fail: NEEDS CHANGES }
-    # reasoning_effort: xhigh                        # per-step override; falls back to the llm block, then SDK default
+    # reasoning_effort: xhigh                        # per-step override of the effective profile's effort
+    # llm: review                                    # (054) select a named `llms:` profile for this step
     on_pass: qa
     on_fail: { goto: dev, retry: true }
 
@@ -257,11 +269,13 @@ steps:
 | `terminal_timeout:` | Optional agent-step per-action timeout in seconds (gt 0). `SandboxTerminalExecutor` uses it when the agent leaves the terminal action timeout unset, overriding the SDK tool's default. `None` = current behavior. |
 | `finalize_nudge_turns:` | Optional agent-step final-response nudge (gt 0). Requires `max_iterations:` and must be less than it. At `max_iterations - finalize_nudge_turns` completed turns the engine injects one advisory turn ("`N turns remain: produce your final response now`"), exactly once; the agent may still exhaust its turns and existing stuck/unclear handling applies unchanged. Absent = current behavior. Provisional pending one consumer run (revert if noisy or the raised cap inflates cost). |
 | `custom_prompt:` | Planned (planning-docs/040). Optional agent-step value: literal text, or a path whose file contents are read at load time, appended verbatim to the agent prompt at context assembly (after the prompt, before the task/artifacts). A value that looks like a path but names no file is a validation error. Agent steps only. |
-| `reasoning_effort:` | Optional `low` / `medium` / `high` / `xhigh` / `none`. Set on the `llm` block (pipeline-global) or per-step (overrides the block). Unset anywhere = the field is not passed and the SDK default (`high`) applies, so today's behavior is unchanged. Forwarded only for models the SDK/LiteLLM mark as supporting it; an unsupported value fails at the first LLM call. See [Reasoning effort](#reasoning-effort-opt-in). |
+| `llms:` (top-level) / step `llm:` | Named LLM profiles, each a full `LlmConfig` (`model`, `base_url`, `api_key_env`, `timeout`, `reasoning_effort`). A step names one with `llm: <profile-name>`; the whole profile moves together (no partial merges). Allowed only on agent and brief steps. The top-level `llm:` block remains the default. Profile keys are host-side - sandbox access still goes through `secrets:`. |
+| `reasoning_effort:` | Optional `low` / `medium` / `high` / `xhigh` / `none`. Set on the `llm` block, a `llms:` profile, or per-step (a step value overrides the effective profile's). Unset anywhere = reasoning off: nothing is forwarded and reasoning is stripped from requests. A thinking model without an effort level is invalid config and fails at the first request (crap in, crap out). See [Reasoning effort](#reasoning-effort-opt-in). |
 | `on_pass:` / `on_fail:` | A step name, terminal `success`/`failure`, or `{goto: X, retry: true}`. No loops happen unless you write them. |
 | `env:` / `setup:` / `network:` | `env:` declares step vars (fixed safe base + declared vars only); `setup:` runs fresh at every step boundary in a one-shot provision container targeting the export (command or agent steps; network ON; no stamping); `network: true` lets a command/agent step reach the hosts its `egress:` allowlist names (default off) - see [Per-stage networking](#per-stage-networking). |
 | `mounts:` / `egress:` | Per-step workspace isolation. `mounts:` lists `{path, mode}` entries (`rw`/`ro`, default `ro`) and is **strict-by-default** - empty/missing mounts nothing; only declared-rw paths sync back to the repo. `egress:` is `{class, presets, targets}` (`class: browser` = broad-but-logged; otherwise a strict allowlist). See [Per-stage networking](#per-stage-networking) and [docs/setup.md](docs/setup.md). |
 | `secrets:` (top-level) / step `secrets:` | Declares secret **refs only - never values**; each step opts in to the refs it needs. Resolved host-side and injected into that step's exec env only. See [Secrets](#secrets--refs-only-never-values). |
+| `profile:` (top-level) | Names a bundled toolchain profile (`python`, `dotnet-node`) or a consumer profile file path. `load_config` merges the profile at load time: isolation key-wise with the pipeline winning, caches unioned profile-first. Absent = today's behavior. |
 | `isolation:` (optional) | Configures the sandbox - image override, resource caps, `allow_git_mutations`, `seccomp_profile`. It can never disable it. See [browser sandbox](docs/browser-sandbox.md). |
 | `state_dir` | Defaults to `~/.agentic-dev-loop/runs/<pipeline-hash>/` - artifacts and checkpoints live outside the sandbox mount. |
 | `extensions_dir` | Where consumer `extensions:` modules resolve - defaults to `~/.agentic-dev-loop/extensions`, **outside** the workspace. Workspace-resident extension/tool modules are refused at load. |
@@ -272,17 +286,25 @@ steps:
 
 ### Reasoning effort (opt-in)
 
-`reasoning_effort` is an opt-in latency dial on the pipeline `llm` block and
-on individual agent steps. It takes one of `low`, `medium`, `high`, `xhigh`,
-or `none`; unset means the field is never passed and the SDK default
-(`high`) applies, so a pipeline that omits it behaves exactly as before. A
-step's value overrides the `llm` block's value, so the review lane can hold
-a higher effort than the rest.
-
-The value is forwarded only for models the SDK/LiteLLM mark as supporting
-it; an unsupported value fails at the first LLM call (the schema rejects
-unknown names at load time, but cannot know provider capability). No
-pipeline ships a value: adopt one only after an observed run proves lower
+`reasoning_effort` is an opt-in latency dial on the pipeline `llm` block, a
+named `llms:` profile, and individual agent steps. It takes one of `low`,
+`medium`, `high`, `xhigh`, or `none`; unset means reasoning is off - the
+field is forwarded as none, reasoning is stripped from requests, and a
+thinking model whose history still carries reasoning fails fast with an
+actionable engine error rather than a provider 400. A step's value overrides
+the effective profile's value, so the review lane can hold a higher effort
+than the rest, or a named profile can move an entire lane to a different
+provider.
+
+Reasoning is opt-in and provider-generic: any openai-compatible endpoint
+expressible as an `LlmConfig` works, and reasoning passback is gated on the
+configured effort level, never on a model-name list. A thinking model without
+an effort level (or with `none` where the provider ignores it) is invalid
+config - it still reasons but its API requires the passback the engine strips,
+so the engine raises before the doomed request is sent. Set
+`reasoning_effort` on the step or its profile, or use a non-thinking model.
+The schema rejects unknown effort names at load time, but cannot know provider
+capability; adopt an effort value only after an observed run proves lower
 per-turn latency with a green suite and no provider 400s.
 
 Recommended lane defaults (guidance only, not enforced):
@@ -425,12 +447,39 @@ console.
 
 ## Authoring a loop for your own repo
 
-A consumer repo needs two things written by hand - a pipeline file and the
-agent files it names - both committed before the first run (the host-boundary
-check refuses dirty tooling, and the `commit` step never commits it). Two
-reference layouts ship today: this repo dogfoods the engine on itself
-(python + pytest, no frontend, CLI-only qa), and the consumer repo carries
-the wider shape (.NET + npm frontend + a networked browser-probing qa step).
+### Start with `agentic-dev-loop init`
+
+`init` writes the onboarding surface from a bundled toolchain profile:
+
+```bash
+agentic-dev-loop init --profile python        # or: --profile dotnet-node
+```
+
+It detects solution files, `package.json` directories, lockfiles, README, and
+AGENTS.md, asks only what detection cannot answer, and writes
+`agentic-dev-loop/pipeline.yaml`, the three agent files, an executable
+`trigger-agentic-dev-loop.sh`, `agentic-dev-loop/.engine-version` (the exact
+installed engine version), any missing premise files, gitignore additions, and
+an env-file template. It refuses to overwrite an existing
+`agentic-dev-loop/` directory. A consumer-authored profile file can be passed
+by path instead of a bundled name.
+
+Profiles carry the environment facts every app on a toolchain shares (image,
+cpus, caches, premise files, gitignore lines); recipes carry the gate shape and
+command vocabulary. The pipeline references a profile with the top-level
+`profile:` key, and `load_config` merges it at load time: the pipeline wins on
+scalars, caches union profile-first, and absence of the key behaves exactly as
+before.
+
+`agentic-dev-loop doctor --fast` is the per-run gate the trigger runs first.
+Hard failures abort the run (engine pin mismatch, engine runtime availability,
+API version, git repo, `.env*` files); warnings print and continue. `doctor
+--json` emits the same results mechanically. The trigger repairs a pin/install
+mismatch exactly once, then fails hard.
+
+A consumer repo needs a pipeline file and the agent files it names, both
+committed before the first run (the host-boundary check refuses dirty tooling,
+and the `commit` step never commits it). `init` writes them; the layout is:
 
 ```
 <repo>/agentic-dev-loop/pipeline.yaml
@@ -515,22 +564,22 @@ adapt per repo.
 Adaptation checklist for a new repo:
 
 1. `llm:` - model, `base_url`, `api_key_env`.
-2. `isolation:` - toolchain image override (the consumer repo pins a
-   toolchain image by digest) and `seccomp_profile: bundled:chromium-userns`
-   only if a stage runs Chromium.
-3. `caches:` - toolchain cache dirs as rw bind-mounts shared across runs
-   (`.nuget-packages`, `qa/node_modules`, `qa/.browsers`,
-   `frontend-editor/node_modules`); caches are never synced back, and a
+2. `llms:` (optional) - named profiles for multi-provider lanes (keep review on the strongest model); a step opts in with `llm: <name>`.
+3. `profile:` - name a bundled profile (`python`, `dotnet-node`) or a
+   consumer profile path. The profile supplies `isolation:` (image,
+   `seccomp_profile`, cpus) and `caches:`; pipeline keys override its scalars.
+4. `caches:` - profile-supplied toolchain caches plus any run-specific dirs
+   (`.nuget-packages`, `qa/.browsers`); caches are never synced back, and a
    step's `setup:` hook runs with them mounted so it can warm them.
-4. `sync_excludes:` - build output trees (`**/bin/**`, `**/obj/**`).
-5. `secrets:` - refs only, resolved from host env; each step opts in to the
+5. `sync_excludes:` - build output trees (`**/bin/**`, `**/obj/**`).
+6. `secrets:` - refs only, resolved from host env; each step opts in to the
    refs it needs.
-6. `egress:` - `presets: [package-registries]` for fetch steps;
+7. `egress:` - `presets: [package-registries]` for fetch steps;
    `class: browser` (broad-but-logged) for browser-tier qa only.
-7. `deps_policy:` and `lockfiles:` - see
+8. `deps_policy:` and `lockfiles:` - see
    [Dependency policy](#dependency-policy-locked-by-default).
-8. The dev prompt's impossible set - write it for your toolchain.
-9. `additional_files:` - the repo's `AGENTS.md`, coding standards, design
+9. The dev prompt's impossible set - write it for your toolchain.
+10. `additional_files:` - the repo's `AGENTS.md`, coding standards, design
    docs: shared context for every agent step.
 
 Validate before the first run - dry-run loads and prints the resolved plan

{agentic_dev_loop-0.9.2 → agentic_dev_loop-0.10.2}/README.md

@@ -158,6 +158,17 @@ llm:
   api_key_env: OPENAI_API_KEY
   # reasoning_effort: medium                        # optional: low | medium | high | xhigh | none
 
+# Named LLM profiles (054): a step names one with `llm: <name>` to move the
+# whole profile (model, endpoint, key, effort default) together - no partial
+# merges. The `llm:` block above remains the default. Profile keys are
+# host-side: sandbox access still goes through `secrets:`, never a profile key.
+# llms:
+#   review:
+#     model: openai/deepseek-v4-pro
+#     base_url: https://api.deepseek.com
+#     api_key_env: REVIEW_API_KEY
+#     reasoning_effort: xhigh
+
 max_attempts: 10                                        # CLI --max-attempts overrides
 agents_dir: sdk_agents                                  # your <name>.agent.md files
 
@@ -187,7 +198,8 @@ steps:
     agent: review
     artifact: review-findings.md
     verdicts: { pass: APPROVED, fail: NEEDS CHANGES }
-    # reasoning_effort: xhigh                        # per-step override; falls back to the llm block, then SDK default
+    # reasoning_effort: xhigh                        # per-step override of the effective profile's effort
+    # llm: review                                    # (054) select a named `llms:` profile for this step
     on_pass: qa
     on_fail: { goto: dev, retry: true }
 
@@ -213,11 +225,13 @@ steps:
 | `terminal_timeout:` | Optional agent-step per-action timeout in seconds (gt 0). `SandboxTerminalExecutor` uses it when the agent leaves the terminal action timeout unset, overriding the SDK tool's default. `None` = current behavior. |
 | `finalize_nudge_turns:` | Optional agent-step final-response nudge (gt 0). Requires `max_iterations:` and must be less than it. At `max_iterations - finalize_nudge_turns` completed turns the engine injects one advisory turn ("`N turns remain: produce your final response now`"), exactly once; the agent may still exhaust its turns and existing stuck/unclear handling applies unchanged. Absent = current behavior. Provisional pending one consumer run (revert if noisy or the raised cap inflates cost). |
 | `custom_prompt:` | Planned (planning-docs/040). Optional agent-step value: literal text, or a path whose file contents are read at load time, appended verbatim to the agent prompt at context assembly (after the prompt, before the task/artifacts). A value that looks like a path but names no file is a validation error. Agent steps only. |
-| `reasoning_effort:` | Optional `low` / `medium` / `high` / `xhigh` / `none`. Set on the `llm` block (pipeline-global) or per-step (overrides the block). Unset anywhere = the field is not passed and the SDK default (`high`) applies, so today's behavior is unchanged. Forwarded only for models the SDK/LiteLLM mark as supporting it; an unsupported value fails at the first LLM call. See [Reasoning effort](#reasoning-effort-opt-in). |
+| `llms:` (top-level) / step `llm:` | Named LLM profiles, each a full `LlmConfig` (`model`, `base_url`, `api_key_env`, `timeout`, `reasoning_effort`). A step names one with `llm: <profile-name>`; the whole profile moves together (no partial merges). Allowed only on agent and brief steps. The top-level `llm:` block remains the default. Profile keys are host-side - sandbox access still goes through `secrets:`. |
+| `reasoning_effort:` | Optional `low` / `medium` / `high` / `xhigh` / `none`. Set on the `llm` block, a `llms:` profile, or per-step (a step value overrides the effective profile's). Unset anywhere = reasoning off: nothing is forwarded and reasoning is stripped from requests. A thinking model without an effort level is invalid config and fails at the first request (crap in, crap out). See [Reasoning effort](#reasoning-effort-opt-in). |
 | `on_pass:` / `on_fail:` | A step name, terminal `success`/`failure`, or `{goto: X, retry: true}`. No loops happen unless you write them. |
 | `env:` / `setup:` / `network:` | `env:` declares step vars (fixed safe base + declared vars only); `setup:` runs fresh at every step boundary in a one-shot provision container targeting the export (command or agent steps; network ON; no stamping); `network: true` lets a command/agent step reach the hosts its `egress:` allowlist names (default off) - see [Per-stage networking](#per-stage-networking). |
 | `mounts:` / `egress:` | Per-step workspace isolation. `mounts:` lists `{path, mode}` entries (`rw`/`ro`, default `ro`) and is **strict-by-default** - empty/missing mounts nothing; only declared-rw paths sync back to the repo. `egress:` is `{class, presets, targets}` (`class: browser` = broad-but-logged; otherwise a strict allowlist). See [Per-stage networking](#per-stage-networking) and [docs/setup.md](docs/setup.md). |
 | `secrets:` (top-level) / step `secrets:` | Declares secret **refs only - never values**; each step opts in to the refs it needs. Resolved host-side and injected into that step's exec env only. See [Secrets](#secrets--refs-only-never-values). |
+| `profile:` (top-level) | Names a bundled toolchain profile (`python`, `dotnet-node`) or a consumer profile file path. `load_config` merges the profile at load time: isolation key-wise with the pipeline winning, caches unioned profile-first. Absent = today's behavior. |
 | `isolation:` (optional) | Configures the sandbox - image override, resource caps, `allow_git_mutations`, `seccomp_profile`. It can never disable it. See [browser sandbox](docs/browser-sandbox.md). |
 | `state_dir` | Defaults to `~/.agentic-dev-loop/runs/<pipeline-hash>/` - artifacts and checkpoints live outside the sandbox mount. |
 | `extensions_dir` | Where consumer `extensions:` modules resolve - defaults to `~/.agentic-dev-loop/extensions`, **outside** the workspace. Workspace-resident extension/tool modules are refused at load. |
@@ -228,17 +242,25 @@ steps:
 
 ### Reasoning effort (opt-in)
 
-`reasoning_effort` is an opt-in latency dial on the pipeline `llm` block and
-on individual agent steps. It takes one of `low`, `medium`, `high`, `xhigh`,
-or `none`; unset means the field is never passed and the SDK default
-(`high`) applies, so a pipeline that omits it behaves exactly as before. A
-step's value overrides the `llm` block's value, so the review lane can hold
-a higher effort than the rest.
-
-The value is forwarded only for models the SDK/LiteLLM mark as supporting
-it; an unsupported value fails at the first LLM call (the schema rejects
-unknown names at load time, but cannot know provider capability). No
-pipeline ships a value: adopt one only after an observed run proves lower
+`reasoning_effort` is an opt-in latency dial on the pipeline `llm` block, a
+named `llms:` profile, and individual agent steps. It takes one of `low`,
+`medium`, `high`, `xhigh`, or `none`; unset means reasoning is off - the
+field is forwarded as none, reasoning is stripped from requests, and a
+thinking model whose history still carries reasoning fails fast with an
+actionable engine error rather than a provider 400. A step's value overrides
+the effective profile's value, so the review lane can hold a higher effort
+than the rest, or a named profile can move an entire lane to a different
+provider.
+
+Reasoning is opt-in and provider-generic: any openai-compatible endpoint
+expressible as an `LlmConfig` works, and reasoning passback is gated on the
+configured effort level, never on a model-name list. A thinking model without
+an effort level (or with `none` where the provider ignores it) is invalid
+config - it still reasons but its API requires the passback the engine strips,
+so the engine raises before the doomed request is sent. Set
+`reasoning_effort` on the step or its profile, or use a non-thinking model.
+The schema rejects unknown effort names at load time, but cannot know provider
+capability; adopt an effort value only after an observed run proves lower
 per-turn latency with a green suite and no provider 400s.
 
 Recommended lane defaults (guidance only, not enforced):
@@ -381,12 +403,39 @@ console.
 
 ## Authoring a loop for your own repo
 
-A consumer repo needs two things written by hand - a pipeline file and the
-agent files it names - both committed before the first run (the host-boundary
-check refuses dirty tooling, and the `commit` step never commits it). Two
-reference layouts ship today: this repo dogfoods the engine on itself
-(python + pytest, no frontend, CLI-only qa), and the consumer repo carries
-the wider shape (.NET + npm frontend + a networked browser-probing qa step).
+### Start with `agentic-dev-loop init`
+
+`init` writes the onboarding surface from a bundled toolchain profile:
+
+```bash
+agentic-dev-loop init --profile python        # or: --profile dotnet-node
+```
+
+It detects solution files, `package.json` directories, lockfiles, README, and
+AGENTS.md, asks only what detection cannot answer, and writes
+`agentic-dev-loop/pipeline.yaml`, the three agent files, an executable
+`trigger-agentic-dev-loop.sh`, `agentic-dev-loop/.engine-version` (the exact
+installed engine version), any missing premise files, gitignore additions, and
+an env-file template. It refuses to overwrite an existing
+`agentic-dev-loop/` directory. A consumer-authored profile file can be passed
+by path instead of a bundled name.
+
+Profiles carry the environment facts every app on a toolchain shares (image,
+cpus, caches, premise files, gitignore lines); recipes carry the gate shape and
+command vocabulary. The pipeline references a profile with the top-level
+`profile:` key, and `load_config` merges it at load time: the pipeline wins on
+scalars, caches union profile-first, and absence of the key behaves exactly as
+before.
+
+`agentic-dev-loop doctor --fast` is the per-run gate the trigger runs first.
+Hard failures abort the run (engine pin mismatch, engine runtime availability,
+API version, git repo, `.env*` files); warnings print and continue. `doctor
+--json` emits the same results mechanically. The trigger repairs a pin/install
+mismatch exactly once, then fails hard.
+
+A consumer repo needs a pipeline file and the agent files it names, both
+committed before the first run (the host-boundary check refuses dirty tooling,
+and the `commit` step never commits it). `init` writes them; the layout is:
 
 ```
 <repo>/agentic-dev-loop/pipeline.yaml
@@ -471,22 +520,22 @@ adapt per repo.
 Adaptation checklist for a new repo:
 
 1. `llm:` - model, `base_url`, `api_key_env`.
-2. `isolation:` - toolchain image override (the consumer repo pins a
-   toolchain image by digest) and `seccomp_profile: bundled:chromium-userns`
-   only if a stage runs Chromium.
-3. `caches:` - toolchain cache dirs as rw bind-mounts shared across runs
-   (`.nuget-packages`, `qa/node_modules`, `qa/.browsers`,
-   `frontend-editor/node_modules`); caches are never synced back, and a
+2. `llms:` (optional) - named profiles for multi-provider lanes (keep review on the strongest model); a step opts in with `llm: <name>`.
+3. `profile:` - name a bundled profile (`python`, `dotnet-node`) or a
+   consumer profile path. The profile supplies `isolation:` (image,
+   `seccomp_profile`, cpus) and `caches:`; pipeline keys override its scalars.
+4. `caches:` - profile-supplied toolchain caches plus any run-specific dirs
+   (`.nuget-packages`, `qa/.browsers`); caches are never synced back, and a
    step's `setup:` hook runs with them mounted so it can warm them.
-4. `sync_excludes:` - build output trees (`**/bin/**`, `**/obj/**`).
-5. `secrets:` - refs only, resolved from host env; each step opts in to the
+5. `sync_excludes:` - build output trees (`**/bin/**`, `**/obj/**`).
+6. `secrets:` - refs only, resolved from host env; each step opts in to the
    refs it needs.
-6. `egress:` - `presets: [package-registries]` for fetch steps;
+7. `egress:` - `presets: [package-registries]` for fetch steps;
    `class: browser` (broad-but-logged) for browser-tier qa only.
-7. `deps_policy:` and `lockfiles:` - see
+8. `deps_policy:` and `lockfiles:` - see
    [Dependency policy](#dependency-policy-locked-by-default).
-8. The dev prompt's impossible set - write it for your toolchain.
-9. `additional_files:` - the repo's `AGENTS.md`, coding standards, design
+9. The dev prompt's impossible set - write it for your toolchain.
+10. `additional_files:` - the repo's `AGENTS.md`, coding standards, design
    docs: shared context for every agent step.
 
 Validate before the first run - dry-run loads and prints the resolved plan

{agentic_dev_loop-0.9.2 → agentic_dev_loop-0.10.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "agentic-dev-loop"
-version = "0.9.2"
+version = "0.10.2"
 description = "Turn an LLM into a gated, sandboxed, resumable construction loop over your codebase."
 readme = "README.md"
 requires-python = ">=3.12"
@@ -76,8 +76,10 @@ where = ["src"]
 
 [tool.setuptools.package-data]
 agentic_dev_loop = ["py.typed"]
+"agentic_dev_loop.core.profiles" = ["data/*.yaml"]
 "agentic_dev_loop.engine" = ["*.md"]
 "agentic_dev_loop.engine.seccomp" = ["*.json"]
+"agentic_dev_loop.engine.onboarding" = ["recipes/*.yaml", "templates/*"]
 
 [tool.pytest.ini_options]
 markers = [

{agentic_dev_loop-0.9.2 → agentic_dev_loop-0.10.2}/src/agentic_dev_loop/core/config.py

@@ -3,6 +3,7 @@
 from __future__ import annotations
 
 import hashlib
+import importlib.metadata
 import re
 import warnings
 from pathlib import Path
@@ -396,9 +397,13 @@ class StepConfig(BaseModel):
     terminal_timeout: float | None = Field(default=None, gt=0)  # seconds, agent steps only (032)
     finalize_nudge_turns: int | None = Field(default=None, gt=0)  # agent steps only (035)
     brief_inputs: BriefInputsSpec | None = None  # agent steps only (033)
-    # 047 (D7): per-step opt-in override; unset falls back to the llm block,
-    # then the SDK default. Full SDK literal, passthrough semantics.
+    # 047 (D7) / 054 (D6): per-step opt-in override; unset falls back to the
+    # effective profile's value (the named `llms:` profile, else the `llm:`
+    # block), else reasoning is off. Full SDK literal, passthrough semantics.
     reasoning_effort: ReasoningEffort | None = None
+    # 054 (D3): names a top-level `llms:` profile; the whole profile moves
+    # together (model, endpoint, key, effort default). None = the `llm:` block.
+    llm: str | None = None
     custom_prompt: str | None = None  # agent steps only (040); file path resolved at load
     env: dict[str, str | None] | None = None  # NFR-1: null = inherit host value
     setup: str | None = None  # command or agent steps; runs fresh at each step entry (052)
@@ -486,6 +491,16 @@ class StepConfig(BaseModel):
                 f"step {self.name!r}: exactly one of 'agent', 'action', "
                 "'command', or 'brief_inputs' is required"
             )
+        if self.llm is not None:
+            if not self.llm.strip():
+                raise ValueError(
+                    f"step {self.name!r}: 'llm' must be a non-empty profile name"
+                )
+            if self.kind not in ("agent", "brief"):
+                raise ValueError(
+                    f"step {self.name!r}: 'llm' names an LLM profile and is "
+                    "only allowed on 'agent' or 'brief_inputs' steps"
+                )
         if self.brief_inputs is not None:
             if self.produces:
                 raise ValueError(
@@ -587,9 +602,9 @@ class LlmConfig(BaseModel):
     base_url: str | None = None
     api_key_env: str
     timeout: float | None = None  # omitted → opinionated no-timeout default
-    # 047 (D1): opt-in passthrough; unset means the field is not passed at
-    # all, so the SDK default ("high") applies and today's behavior is
-    # byte-identical. No default may move without an observed run (D6).
+    # 047 (D1) / 054 (D6): opt-in passthrough; unset means reasoning is off
+    # (the engine forwards none and strips reasoning passback). The SDK
+    # "high" default never engages because build_llm always passes the value.
     reasoning_effort: ReasoningEffort | None = None
 
 
@@ -606,6 +621,9 @@ class PipelineConfig(BaseModel):
     extensions_dir: str = "~/.agentic-dev-loop/extensions"
     env_allowlist: list[str] = []
     llm: LlmConfig
+    # 054 (D1): named LLM profiles, each a strict LlmConfig. Optional and
+    # purely additive - the `llm:` block above remains the default.
+    llms: dict[str, LlmConfig] = {}
     isolation: IsolationConfig | None = None  # None = always-on defaults
     state_dir: str = ".pr"  # default relocated to ~/.agentic-dev-loop/runs/<hash>/ at load
     secrets: dict[str, SecretSpec] = {}  # ref name -> locator; values never appear here
@@ -630,6 +648,9 @@ class PipelineConfig(BaseModel):
     # edit instead of raising. Same declared-path vocabulary as
     # ``sync_excludes:``.
     merge_on_conflict: list[str] = []
+    # 055: the toolchain profile resolved at load time. Kept on the validated
+    # config so the run records which profile supplied its defaults.
+    profile: str | None = None
 
     @field_validator("deps_policy")
     @classmethod
@@ -690,6 +711,23 @@ class PipelineConfig(BaseModel):
                 "enforces, or set 'deps_policy: open'")
         return self
 
+    @model_validator(mode="after")
+    def _check_llm_profiles(self) -> "PipelineConfig":
+        """054 (D5): the registry is additive and referential. A profile
+        literally named 'default' is rejected (the `llm:` block already is the
+        default), and any step naming an undeclared profile fails at load,
+        never mid-run."""
+        if "default" in self.llms:
+            raise ValueError(
+                "'llms' cannot declare a profile named 'default' - the "
+                "top-level 'llm:' block is already the default")
+        for step in self.steps:
+            if step.llm is not None and step.llm not in self.llms:
+                raise ValueError(
+                    f"step {step.name!r}: unknown LLM profile {step.llm!r} - "
+                    f"declared profiles: {sorted(self.llms)}")
+        return self
+
     @model_validator(mode="after")
     def _mounts_avoid_state_dir(self) -> "PipelineConfig":
         """BR-1.3: the host-only run-state dir is never a mount path.
@@ -858,6 +896,21 @@ def load_config(path: Path) -> PipelineConfig:
         raise ValueError(
             f"pipeline config must be a mapping, got {type(data).__name__}: {path}"
         )
+    profile_ref = data.pop("profile", None)
+    if profile_ref is not None:
+        from agentic_dev_loop.core.profiles import (
+            ProfileError,
+            load_profile,
+            merge_profile,
+        )
+
+        try:
+            installed = importlib.metadata.version("agentic-dev-loop")
+            profile = load_profile(str(profile_ref), installed)
+            data = merge_profile(data, profile)
+        except ProfileError as exc:
+            raise ValueError(f"pipeline {path}: {exc}") from exc
+        data["profile"] = profile_ref
     if "state_dir" not in data:
         data["state_dir"] = default_state_dir(path)
     cfg = PipelineConfig.model_validate(data)