v1.6 Changelog

Released: October 2026

The "Scorecard" release: numbers are judged by their goal, entered like in a spreadsheet, and a missed number goes to the Issues List in one click.

Highlights

The goal decides the colour: green when a number meets its goal, red when it misses it -- also after the goal changes
Edit in place: type in the cell, Enter or Tab to save, arrows to move between measurables
Ranges as goals: 90-110
Add to issues for missed numbers in the meeting's Scorecard Review

A value that can be compared with the goal is judged by it -- nobody marks it on or off track by hand. Changing a goal recolours the whole history.
Only values the goal can't read (text, ambiguous numbers) ask Met or Missed.
Goals accept ranges (90-110, inclusive) next to >, >=, <, <=, = and a bare number ("at least").
Cells are edited in place: Enter or clicking elsewhere saves, Tab/Shift+Tab moves across weeks, ↑/↓ across measurables, Esc cancels. The colour follows the value while typing. An empty cell clears the week.
Each cell shows an icon (✓ / ⚠) and has a description for screen readers, so the status doesn't rely on colour.
The goal is shown under each measurable's name and the table opens at the latest weeks.
On a phone the number pad opens for numeric goals.

The Scorecard Review enters this week's values the same way.
Every missed number has Add to issues: it creates an issue such as New Leads: 42 leads (goal >50) linked to the meeting, which shows up in IDS.

DELETE /api/v1/metrics/{id}/values/{week} clears a week's value; the MCP server has delete_metric_value.
onTrack follows the goal: reads report the current goal's verdict, and a write whose onTrack contradicts the goal is refused with 422.

No database migration. Existing values are judged by their current goals when displayed; values the goal can't read keep their recorded status.