Sloth-ninja brings Citation Checker into the Research fold

A small follow-up makes the citation-checking tool feel like part of one coherent research workspace.

searchworkflow

Sloth-ninja has aligned Citation Checker with the rest of the Research area, giving users the same navigation cues and clearer visual structure when moving between research tools.

The change also makes error messages easier to read at a glance. A broad loading or connection problem now uses a neutral treatment, while red remains reserved for a specific result that cannot be found. That distinction matters when a lawyer is checking several citations and needs to tell a page problem from a missing authority.

Behind the scenes, the team also corrected guidance on personal API keys: a user's configured key takes priority over the shared environment setting, matching the established behaviour.

So what Legal teams using the research tools should care because the workflow is becoming more predictable, especially when checking citations under time pressure.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from Sloth-ninja/JessicaOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

f04678ec WS7: composed-range review fixes sloth-ninja 2026-07-20 ↗ GitHub

SHA	Subject	Author	Date
`f04678ec`	WS7: composed-range review fixes	sloth-ninja	2026-07-20	↗ GitHub
commit body Cross-cutting cleanup from a composed-range review of the WS7 train. - citation-checker/page.tsx: align page header with the Research-group convention (shrink + Research/Citation Checker breadcrumbs, header/body border-t divider) that Company Search and Legislation established after #24 shipped; switch the top-level fetch-error text from red to neutral grey to match the other two Research pages (red stays reserved for per-citation "Not found" status). - routes/companies.ts: correct the stale key-precedence file comment left behind by the byo-key-precedence flip - the per-user BYO key always takes precedence; the server env key is the shared fallback. Verification: backend tsc clean; vitest 149/149; frontend tsc clean; lint unchanged from main baseline (changed file zero issues); evals:smoke 4/4 from the main checkout. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

commit body

Cross-cutting cleanup from a composed-range review of the WS7 train.

- citation-checker/page.tsx: align page header with the Research-group
  convention (shrink + Research/Citation Checker breadcrumbs, header/body
  border-t divider) that Company Search and Legislation established after
  #24 shipped; switch the top-level fetch-error text from red to neutral
  grey to match the other two Research pages (red stays reserved for
  per-citation "Not found" status).
- routes/companies.ts: correct the stale key-precedence file comment left
  behind by the byo-key-precedence flip - the per-user BYO key always
  takes precedence; the server env key is the shared fallback.

Verification: backend tsc clean; vitest 149/149; frontend tsc clean;
lint unchanged from main baseline (changed file zero issues);
evals:smoke 4/4 from the main checkout.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1165.md from inside the repo you want the changes in.

⬇ Download capture-thread-1165.md