Explain when runs.<case> becomes an array (same model x harness x effort,
several takes), the distinct-descriptive-file rule, the index.html trap,
and per-variant contributor.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A `note` disclosure does not separate a modified-harness run on the board:
leaderboard identity is only model × harness × effort, so a skill-boosted run
would still land in an Agent row it is explicitly not comparable with. Drop the
"disclose in note" escape hatch and make it a flat non-acceptance.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Address fairness concern from #24: the same harness can load completely
different skills / plugins / MCP / custom system prompts, which shifts the
output as much as swapping the harness and breaks Agent comparability.
- README.md / README.en.md: add a bullet to the Model + Harness section
stating the harness is evaluated in its default, out-of-the-box form.
- AGENTS.md: add a "Run the harness as it ships" rule — no extra skills
beyond what the harness bundles; disclose any deviation in `note`.
Enforcement stays honor-system + the PR generation screenshot.
Closes#24
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- AGENTS.md: public contributor/agent guide (two-file rule, model-centric
ids, one-entry-per-harness, bilingual notes, screenshot proof)
- PR template: require a generation proof screenshot; drop the manual
update-registry step; add id-naming and no-README-edit checks
- CI: PRs only run validate-data; pushes to main auto-regenerate and commit
the README registry (contents:write on that job, [skip ci], no loop)
- README/update-registry: reflect auto-synced registry; fix stale 'two cases'
-> three (mythos-craft, pelican-cycling, skeleton-watch); link AGENTS.md
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
