Skip to content

feat: add PerformanceConfig to RootConfig for YAML-driven quality scoring configuration #1061

@Aureliolo

Description

@Aureliolo

Summary

_build_performance_tracker in app.py falls back to default PerformanceConfig() because RootConfig has no performance field. This means YAML-configured quality_judge_model, quality_judge_provider, and custom CI/LLM weights are ignored at auto-wiring time.

Acceptance Criteria

  • Add performance: PerformanceConfig = Field(default_factory=PerformanceConfig) to RootConfig
  • Update YAML config loader to parse the performance: section
  • Pass effective_config.performance to _build_performance_tracker in create_app
  • Update config design spec page
  • Add tests for YAML round-trip of performance config fields

Context

Found during PR #1057 review. The auto-wiring code works correctly with defaults, but user-configured values in company YAML are not respected.

Design Spec Reference

  • Operations page (providers/config section)
  • Agents page SS8.3 (quality scoring config fields)

Metadata

Metadata

Assignees

No one assigned

    Labels

    prio:mediumShould do, but not blockingscope:smallLess than 1 day of workspec:hrDESIGN_SPEC Section 8 - HR & Workforce Managementtype:featureNew feature implementationv0.6Minor version v0.6

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions