Enhancement request: Reduce friction accessing code usage data when building codelists

Summary

Users need access to code-level usage data within OpenCodelists to make better decisions when selecting and building codelists without switching tools.

What would you like to achieve?

Currently there is a link to the OpenCodeCounts tool in the OpenCodelist builder. This was an experiment to see the uptake. There's been some modest use of the link but less evidence of repeat usage.
Bristol (and other users) have suggested that they'd like to be able to see how frequently individual codes are used directly within codelists, so they can more easily identify relevant codes and make confident decisions when building or refining codelists.

• For existing codelists - to see code usage details per code
• For building new codelists - to see code usage details as codes are listed (to be included/excluded)
  Providing this information within OpenCodelists would make codelist building less cumbersome as users wouldn't have to switch between tools as often.

Who would benefit and how?

OpenCodelist users - builders would be more confident selecting codes for their codelists without switching tools

No files, tests, or entry points are named. Start by reviewing the existing OpenCodeCounts link and the codelist builder flow, then clarify the usage-data source, where per-code details should appear for existing and new codelists, and what acceptance criteria define completion.