Skip to content

fix(web): list the Nullius run tag before Harbor on benchmark cards - #141

Merged
aitianshi merged 1 commit into
mainfrom
fix/benchmark-card-nullius-tag-first
Nov 16, 2026
Merged

aitianshi merged 1 commit into
mainfrom
fix/benchmark-card-nullius-tag-first

Conversation

@aitianshi

Copy link
Copy Markdown
Collaborator

What

A benchmark card on the Benchmarks page listed its run tags as Harbor then Nullius. It now lists Nullius first, the order the benchmark's own page and the filter buttons already use.

Touches

Templates and static: app/templates/catalogue/benchmarks.html.

Before and after

Before: τ³-bench card showed Harbor Nullius. After: Nullius Harbor.

Verified

  • Route suite: python app/tests/parallel.py app/ui_tests, 431 tests OK.
  • Rendered /benchmarks with a temporary profile: all three cards with both tags list standard before harbor.

Risk

Display order only. Undone by a revert.

@github-actions

Copy link
Copy Markdown

🔴 PR judge · 4 of 6 yes · #141, no linked issue

Merge risk 🟢 MINOR the judge's reading of the diff
Priority 🟢 LOW no path reaches past the surface
Question Verdict
Changes do what the issue asks –
Issue and pull request describe the same change –
Description matches the diff, no more, no less ✅ yes
Diff stays in scope ✅ yes
Tests cover the change, or Verified says how ✅ yes
Docs follow the change ❌ no
Risk named in the description ✅ yes
Before and after shown · 0 images · the diff touches what is visible ❌ no
Checks the script runs itself, 4 of 4 pass
No machine attribution trailer in the commits or the description ✓
New code under app/, docs/, .github/ or .claude/ ✓
No Flask import under the backend package ✓
No key-shaped string in the diff ✓

@aitianshi
aitianshi merged commit 93dea67 into main Nov 16, 2026
2 checks passed
@aitianshi
aitianshi deleted the fix/benchmark-card-nullius-tag-first branch November 16, 2026 11:03
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