Skip to content

feat: make target_paths optional for all check types#53

Merged
fazpu merged 1 commit into
mainfrom
feat/optional-target-paths
May 6, 2026
Merged

feat: make target_paths optional for all check types#53
fazpu merged 1 commit into
mainfrom
feat/optional-target-paths

Conversation

@fazpu

@fazpu fazpu commented May 6, 2026

Copy link
Copy Markdown
Member

Summary

  • Remove the validate_targets model validator that required target_paths to be non-empty for harness_judge checks
  • The harness judge spawns a real agent (CC, Codex, Gemini CLI) that can read files on its own — force-feeding content via target_paths is unnecessary
  • Deterministic scripts likewise receive project_root in context.json and can locate files independently
  • Skip the "Target Files:" prompt section when target_paths is empty
  • Update skill docs and YAML schema reference

Test plan

  • make all-check passes (lint + format + types + 118 tests)
  • New test: harness_judge without target_paths parses successfully

🤖 Generated with Claude Code

The harness judge spawns a real agent (CC, Codex, Gemini CLI) that can
read files on its own — force-feeding content via target_paths is
unnecessary. Deterministic scripts likewise receive project_root and
can locate files independently.

- Remove validate_targets model validator from HarnessJudgeCheckDefinition
- Skip "Target Files:" prompt section when target_paths is empty
- Update skill docs and YAML schema reference

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@fazpu fazpu merged commit c8dc9ac into main May 6, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant