feat!: prefix team-harness config fields with team_harness_#10
Merged
Conversation
The five fields in loopy_loop_config.yaml that map directly to the team-harness SDK are renamed so their purpose is explicit: - model -> team_harness_model - agents -> team_harness_agents - api_base -> team_harness_api_base - api_key_env -> team_harness_api_key_env - system_prompt_extension -> team_harness_system_prompt_extension RootConfig, RootConfigSnapshot, the field validator target, the resolve_api_key lookup, the harness_runner snapshot access, the init YAML template, README, http-contract docs, and all tests updated. BREAKING: Existing loopy_loop_config.yaml files must be updated. No backwards-compatible aliases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rename the five
loopy_loop_config.yamlroot-config fields that map directly to the team-harness SDK so their purpose is explicit in the file:modelteam_harness_modelagentsteam_harness_agentsapi_baseteam_harness_api_baseapi_key_envteam_harness_api_key_envsystem_prompt_extensionteam_harness_system_prompt_extensionOther root-config fields (
goal,goal_slug,completion_criteria,stop_criteria,max_turns,goal_check_consecutive_failures_cap) are loopy-loop's own concerns and stay unprefixed.Touches
RootConfig,RootConfigSnapshot, the@field_validatortarget,resolve_api_key, theharness_runnersnapshot accesses, theloopy initYAML template, README,docs/http-contract.md, and all affected tests/fixtures.BREAKING CHANGE
Existing
loopy_loop_config.yamlfiles must rename the five fields. No backwards-compatible aliases — loading a pre-rename config fails validation.Test plan
uv run pytest src/tests/— 62 passeduv run ruff check src/— cleanuv run pyright src/loopy_loop/— 0 errors