# Name the selected metric's peak in the history annotations · lucenx/codexbar-plasma

[View on GitCafe](https://git.cafe/lucenx/codexbar-plasma/commit/e65bb376ab307fd0984eff2f00f9819b33591d08)

Repository: [lucenx/codexbar-plasma](https://git.cafe/lucenx/codexbar-plasma)

Visibility: public

Requested revision: e65bb376ab307fd0984eff2f00f9819b33591d08

Requested commit: e65bb376ab307fd0984eff2f00f9819b33591d08

Commit: e65bb376ab307fd0984eff2f00f9819b33591d08

Tree: b16f6307055dfe7c58bb4e05bf34cfcaa93721c1

Author: Simone

Committer: Simone

## Message

```
Name the selected metric's peak in the history annotations

Third Codex finding on #59, and the same class of bug as the previous
two: the seven-day rows scaled and bolded by tokens while `costPeakLine`
and `costAverageDailyLine` still scanned `point.cost`. A provider tab
could bold 2026-08-14 as the token peak while the label above read
"Peak: 2026-07-18 - $471,76" next to a currency average.

Both helpers now read the selected metric and format with
`tokenCountString` in token mode. The chart's own summary line already
follows it through `displayValue`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

```

## Parents

- [c43c0438a655c8f983987d62c9caec3f4cc88e62](https://git.cafe/lucenx/codexbar-plasma/commit/c43c0438a655c8f983987d62c9caec3f4cc88e62?format=markdown)

[Source at this commit](https://git.cafe/lucenx/codexbar-plasma/tree/e65bb376ab307fd0984eff2f00f9819b33591d08?format=markdown)