On the commits page, tags and branches are rendered using the same color, so the two kinds of refs are visually indistinguishable at a glance. This makes it harder to scan the page and quickly tell whether a given ref is a tag or a branch.

Expected behavior

• Tags and branches should use distinct visual treatments (e.g. different colors and/or shapes) so each ref type is immediately recognizable.
• The distinction should rely on more than color alone, so it remains usable for people with color vision deficiencies (pair color with a secondary cue such as shape, icon, or label styling).
• Colors should be chosen for sufficient contrast against the background and should read clearly in both light and dark themes.

Rationale

• Ref types are semantically different and should be visually distinguishable.
• Clear, consistent, accessible color usage follows well-established interface design principles (legibility, redundancy of encoding, and respect for accessibility).

Acceptance criteria

•  Tag refs and branch refs on the commits page render with visually distinct styling.
•  The distinction is not conveyed by color alone.
•  Styling meets contrast requirements in light and dark themes.