Skip to content

docs: correct stale agent lists, five broken anchors, and two wrong repo URLs - #35

Merged
shekharprateek merged 1 commit into
mainfrom
docs/stale-agent-lists-and-broken-links
Oct 20, 2026
Merged

shekharprateek merged 1 commit into
mainfrom
docs/stale-agent-lists-and-broken-links

Conversation

@shekharprateek

Copy link
Copy Markdown
Contributor

Why

Loose ends from PRs #31 and #32, plus link rot that PRs #28 and #29 could not catch because they resolved file paths only, never anchors.

Stale agent lists

Both are user-facing help text, not comments:

  • run-benchmark-batch.sh:45 listed pi (default), claude, omp, kiro. The flag is parsed generically and forwarded to the orchestrator, and -h prints the script's own header block — so that line is the help. Added codex, strands, strands-harness.
  • .claude/skills/benchmark/SKILL.md offered --agent claude|pi|omp|codex|kiro, missing both agents PR fix(harness): wire the Strands runner into the harness so --agent strands runs #32 wired up.

Five broken anchors

Each verified absent on both sides before retargeting:

Link Problem
path-open-weight-on-bedrock-litellm.md → path-anthropic-on-bedrock.md#anthropic-only Self-inflicted: d92bf64 renamed that heading to "Supported models" without touching the inbound link
docs/vision.md → ../README.md#results-a-worked-example Twice (lines 3 and 26). No such heading here or upstream
docs/vision.md → ../README.md#quality-by-dimension-where-models-are-strong-or-weak Same
benchmarks/README.md:103 → ../README.md#does-routing-beat-picking-one-model Same; repointed at docs/swe-router-evaluation.md

Two wrong repo identities

  • self-hosted/vllm/README.md:109 cloned sample-claude-code-multi-model — the predecessor repo — and the very next line cds into a script that lives in this one. Kept the ~/repo target so the following cd still works.
  • .claude/skills/benchmark/SKILL.md:69 was cd ~/agentic-coding-harness-benchmarks, the fork's clone directory name. Cloning this repo gives sample-agentic-coding-harness-benchmarks.

How GitHub builds a slug — worth recording

My first pass at an anchor checker reported 10 broken links. Seven were the checker's fault, not the repo's. GitHub lowercases, drops anything that is not a word character / space / hyphen (underscores are word characters and survive), then replaces each space with a hyphen without collapsing runs. So removed punctuation leaves a double hyphen:

  • API / CLI Design → #api--cli-design, not #api-cli-design

Links like #pagedattention--kv-cache and #client-test-programs-pyprojecttoml--uv are therefore correct as written and are deliberately untouched. Anyone adding an automated link check should encode that rule or it will generate noise.

With the rule right, a sweep of all 77 markdown files found exactly the five anchors above. After this PR it reports one item: SUPPORT.md → ../../issues, which is the GitHub relative-URL idiom for the repo's issues page and resolves on github.com. Left alone, as PR #29 left it.

Deliberately not in scope

README.md and docs/repository-structure.md both want one-line additions (an onboard-benchmark row in the documentation map, and a tree entry) — but PR #33 is already editing both files, so those go in a follow-up once it merges rather than creating a conflict now.

Checks

530 tests pass with no new failures; bash -n clean on the modified script.

…epo URLs

Loose ends from PRs #31 and #32, plus link rot two earlier link-fix PRs could
not catch because they resolved file paths only, never anchors.

Stale agent lists (both are user-facing help, not comments):
- run-benchmark-batch.sh:45 listed "pi (default), claude, omp, kiro". The flag
  is parsed generically and forwarded, and `-h` prints the script's own header
  block, so that line IS the help. Added codex, strands and strands-harness.
- .claude/skills/benchmark/SKILL.md: the example command line offered
  --agent claude|pi|omp|codex|kiro, missing both agents PR #32 wired up.

Broken anchors, all five verified absent on both sides before retargeting:
- path-open-weight-on-bedrock-litellm.md pointed at
  path-anthropic-on-bedrock.md#anthropic-only. Self-inflicted: d92bf64 renamed
  that heading to "Supported models" without touching the inbound link.
- docs/vision.md used ../README.md#results-a-worked-example TWICE (lines 3 and
  26) and #quality-by-dimension-where-models-are-strong-or-weak once. No such
  headings exist here or upstream. Repointed at the Step 1 heading and at
  cost-per-task-methodology.md.
- benchmarks/README.md:103 pointed at
  ../README.md#does-routing-beat-picking-one-model, also nonexistent.
  Repointed at docs/swe-router-evaluation.md.

Wrong repo identities:
- self-hosted/vllm/README.md:109 cloned sample-claude-code-multi-model, the
  predecessor repo, then cd'd into a script that lives in THIS one. The ~/repo
  target is kept so the following cd still works.
- .claude/skills/benchmark/SKILL.md:69 was `cd ~/agentic-coding-harness-
  benchmarks`, the fork's clone directory name.

Checked with an anchor-aware sweep of all 77 markdown files. Worth recording
how GitHub builds a slug, because getting it wrong manufactures false
positives: it lowercases, drops anything that is not a word character, space or
hyphen (underscores are word characters and survive), then replaces EACH space
with a hyphen without collapsing runs. So removed punctuation leaves a DOUBLE
hyphen -- "API / CLI Design" is #api--cli-design, not #api-cli-design. Links
like #pagedattention--kv-cache and #client-test-programs-pyprojecttoml--uv are
correct as written and are deliberately untouched.

After this the sweep reports one remaining item, SUPPORT.md -> ../../issues,
which is the GitHub relative-URL idiom for the repo's issues page and resolves
on github.com. Left alone, as PR #29 left it.

530 tests pass with no new failures; shell syntax checked.
@shekharprateek
shekharprateek merged commit 5a1abcd into main Oct 20, 2026
8 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