feat: keep skill context out of both judge prompts

[igmarin]

Why

feat/blind-judge-comparisons had a dirty tree mixed with leftover docs already on main. The real WIP was never submitted: both judges still received different skill_context on main.

What

• Evaluation::Runner always calls Judge::Prompt with skill_context: nil
• Keyword skill_context: stays on the public API
• Test: three treatment strings produce one identical judge prompt
• docs/blind-comparisons.md protocol note

Leftover docs (README, AGENTS, help printer, etc.) were discarded; they were stale copies of #100–#112.

Proof

bundle exec ruby -Itest test/evaluation_runner_test.rb
# 7 runs, 0 failures

[coderabbitai]

Warning

Review limit reached

Next included review available in 14 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: CHILL

Plan: Advanced

Run ID: 8b515514-020f-4c9f-aa21-2391a9ea1505

📥 Commits

Reviewing files that changed from the base of the PR and between adc56e0 and 0a6d16f.

📒 Files selected for processing (5)

• CHANGELOG.md
• docs/architecture.md
• docs/blind-comparisons.md
• lib/skill_bench/evaluation/runner.rb
• test/evaluation_runner_test.rb

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}