Skip to content

feat: remove target_paths from check definitions#54

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

feat: remove target_paths from check definitions#54
fazpu merged 1 commit into
mainfrom
feat/remove-target-paths

Conversation

@fazpu

@fazpu fazpu commented May 6, 2026

Copy link
Copy Markdown
Member

Summary

  • Remove target_paths field entirely from check definitions
  • Harness judges spawn real agents (CC, Codex, Gemini CLI) that read files on their own
  • Deterministic scripts receive project_root in context.json and can locate files independently
  • Removes ~200 lines of unnecessary indirection

Test plan

  • make all-check passes (lint + format + types + 115 tests)
  • YAML with target_paths is now rejected by extra="forbid" validation

🤖 Generated with Claude Code

target_paths was unnecessary indirection — harness judges spawn real
agents (CC, Codex, Gemini CLI) that read files on their own, and
deterministic scripts receive project_root in context.json.

- Remove target_paths field and validator from BaseCheckDefinition
- Remove file content inlining from harness judge prompt builder
- Remove targets array from deterministic context payload
- Remove related tests (missing target file, prompt includes targets,
  prompt truncation)
- Update skill docs

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@fazpu fazpu merged commit 7143915 into main May 6, 2026
6 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