cctally 1.96.2 → 1.98.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -55,13 +55,18 @@ AXIS_REGISTRY: "tuple[AlertAxisDescriptor, ...]" = (
55
55
  "project_budget", "PROJECT", "Project budget", "project_budget_milestones"
56
56
  ),
57
57
  # Per-vendor Codex budget alerts (calendar-period; calendar-period-codex-budgets
58
- # feature). Distinct "CODEX" chip vs the global "BUDGET" / per-project
59
- # "PROJECT" chips. As of #143 it shares the unified vendor-tagged
58
+ # feature). #556 S3 §4.3: the chip reads "BUDGET", the same as the Claude
59
+ # budget axis, because it names the METRIC. Attribution is the row's source
60
+ # chip, which under All reads "Codex" — a chip reading "CODEX" beside a
61
+ # source chip reading "Codex" said the same thing twice and named neither
62
+ # the metric nor anything the source chip did not already say. The two
63
+ # BUDGET chips stay visually distinct through `chip--codex_budget`, which
64
+ # keeps its own colour. As of #143 it shares the unified vendor-tagged
60
65
  # `budget_milestones` table with the Claude `budget` axis; the envelope
61
66
  # mapper's `WHERE vendor=?` filter does the row-level split (keyed on the
62
67
  # resolved period-window start instant period_start_at, threshold).
63
68
  AlertAxisDescriptor(
64
- "codex_budget", "CODEX", "Codex budget", "budget_milestones", vendor="codex"
69
+ "codex_budget", "BUDGET", "Codex budget", "budget_milestones", vendor="codex"
65
70
  ),
66
71
  )
67
72