Repository navigation
Keep and score pages a benchmark run writes, and record scenario 11 - #21
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
The benchmark now keeps and scores the Markdown pages an agent writes besides the README, and scenario 11 has its first recorded run under Claude Code. Both close the TODO list of #18.
Why
Since #16 the skill can move an oversized section to
docs/<slug>.md. The runner copied onlyREADME.mdout of the workspace, and the scorer resolved links against the original fixture, so the README's link to a moved page counted as a broken link and the page's own links were never checked.tests/evals/run.mjscopies every Markdown page the agent wrote or changed — outside hidden and dependency directories — topages/in the case directory and lists them inmeta.jsonaswrittenPages.tests/evals/score.mjsaccepts those pages as link targets, checks the links inside each page from the page's own directory, and counts them as checked statements. A link still cannot escape the fixture or the pages directory.tests/scenarios.mdrecords the scenario 11 run, and notes that a copy in~/.claude/skills/shadows the workspace copy: the first attempt silently ran the installed 1.0.0-beta skill, which has no section split. A clean run needs--setting-sources project.Checks
node --test tests/repository.test.mjspassesnode --test tests/evals/*.test.mjspasses — four new tests: a written page as a link target, a broken link inside a page, no escape from the pages directory, and which files the runner keepsCHANGELOG.mdupdated under the current unreleased headingSKILL.mdis changed everywhere it appears inreferences/— no skill rule changedtests/scenarios.md, and the run recorded in its host coverage log — scenario 11, two runsClaims this adds to the documentation
claude -pruns on a workspace built to the scenario's setup. Run 1 moved the 30-skill section todocs/skills.md(one#, intro, four-group index with counts, promoted headings, 54 of 54 relative links resolving), leftTestingunchanged, kept the 20-rule list in the README becausedocs/rules.mdexists, and named that collision. Run 2 produced no diff. The workspace is not committed; the setup is reproducible from the scenario text.