cctally 1.99.0 → 1.99.1

package/CHANGELOG.md

@@ -5,6 +5,13 @@ based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.99.1] - 2026-08-15
+
+### Fixed
+- The dashboard now recognizes the previous calendar day as `Yesterday` across a fall-back daylight-saving transition instead of falling through to the absolute timestamp (#584).
+- Budget figures no longer depend on which Python version is running cctally. The dashboard's Claude and Codex budget blocks added their spend with the built-in `sum()`, which CPython changed in 3.12 to use compensated summation, so the same spend over the same entries produced `$49.20424485` on Python 3.12 and later and `$49.204244850000016` on Python 3.11. The rendered figure is rounded to cents and never differed to the eye, but the published payload did, which is why the repository's own byte-comparison of that payload failed on 3.11. These four sums now use the exactly-rounded helper the rest of the cost surfaces already use, so every supported interpreter publishes the same number.
+- `cctally account attribute --help` no longer prints `(default: None)` beneath `--since`, which is a required argument and therefore has no default. Python 3.13 already suppressed it and 3.11 and 3.12 did not, so the same command printed two different help texts depending on the interpreter. cctally now applies the 3.13 rule on every supported version, and this covers every required option on every subcommand, not only this one.
+
 ## [1.99.0] - 2026-08-15
 
 ### Added
@@ -18,6 +25,7 @@ based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 - Complete the Claude/Codex parity certification with current source-aware dashboard, analytics, sharing, conversation, privacy, and scale evidence; the TUI remains explicitly Claude-only under its bugfix-only maintenance policy (#322).
 
 ### Fixed
+- Failed authoritative test-gate records now retain the exact `test-remote` case function and source line even when private assertion detail is redacted, and the local record survives the next passing invocation (#579).
 - Schema tables, views, triggers and indexes in both cache stores now have a structural delivery guard, so a definition added without a migration cannot silently reach only fresh installations (#580).
 - Claude-active dashboard refreshes now incrementally update the `All` view's shared-range project and daily aggregates instead of rescanning and repricing the full thirty-day Claude history on every new entry. On the 60,000-entry benchmark with one live append before each warm run, the median added source-build time fell from about 404 ms to 2.5 ms while project and daily totals remained byte-identical to a cold rebuild (#567).
 - A Codex-active dashboard refresh now updates only changed rollout paths, accounts, and day/period/session/project aggregates instead of re-reading and re-aggregating the complete retained Codex history. On a copied production store with 154,600 Codex entries, a caught-up live dirty iteration including ingest completed in 4.77 seconds (9.77-second cooldown-adjusted publish period) while preserving the exact prior dashboard payload (#582).

package/bin/_cctally_dashboard_sources.py

@@ -2384,7 +2384,12 @@ def _configured_codex_budget_status(
     )
 
     def _sum_cost(start: dt.datetime, end: dt.datetime) -> float:
-        return sum(cost for timestamp, cost in resolved_events if start <= timestamp < end)
+        # stable_sum, not sum: this feeds the byte-compared budget wire, and
+        # the built-in sum() switched to Neumaier compensated summation for
+        # floats in CPython 3.12, so 3.11 renders a different figure.
+        return stable_sum(
+            cost for timestamp, cost in resolved_events if start <= timestamp < end
+        )
 
     recent_start = max(start_at, context.now_utc - dt.timedelta(hours=24))
     # #556 S5 §3.1/§3.3: ONE producer of the wire status, shared with Claude.
@@ -2819,7 +2824,9 @@ def _refresh_budget_status_clock(
             str(status["window_end_at"]).replace("Z", "+00:00")
         ).astimezone(UTC)
         recent_start = max(start_at, now_utc - dt.timedelta(hours=24))
-        recent_24h_usd = sum(
+        # stable_sum, not sum: same byte-compared budget wire as the producer
+        # above, and the same CPython 3.12 sum() change applies.
+        recent_24h_usd = stable_sum(
             float(cost) for timestamp, cost in cost_events
             if isinstance(timestamp, dt.datetime)
             and start_at <= timestamp.astimezone(UTC) < now_utc

package/bin/_cctally_parser.py

@@ -57,6 +57,22 @@ class CLIHelpFormatter(
         kwargs.setdefault("max_help_position", 30)
         super().__init__(prog, **kwargs)  # type: ignore[arg-type]
 
+    def _get_help_string(self, action: argparse.Action) -> "str | None":
+        """Never state a default for a required argument.
+
+        CPython 3.13 stopped appending ``(default: ...)`` to a required
+        argument's help; 3.11 and 3.12 still append it. Without this the same
+        parser prints two different help texts depending on the interpreter,
+        so `cctally account attribute --help` renders a meaningless
+        ``(default: None)`` under `--since` on the two older versions and the
+        goldened help diverges on every lane that is not 3.13. Pinning the
+        3.13 rule for every supported version is what makes `--help` a
+        property of this program rather than of the interpreter running it.
+        """
+        if action.required:
+            return action.help
+        return super()._get_help_string(action)
+
 
 _PHYSICAL_PROVIDER_SOURCES = ("claude", "codex")
 

package/bin/_cctally_tui.py

@@ -3209,11 +3209,16 @@ def _tui_claude_budget_domain(
             window_start_at=start_at,
             window_end_at=end_at,
             target_usd=target,
-            spent_usd=sum(
+            # stable_sum, not sum: both figures are published on the dashboard
+            # wire and byte-compared by the dashboard goldens, and the built-in
+            # sum() switched to Neumaier compensated summation for floats in
+            # CPython 3.12, so the same spend renders 49.20424485 on 3.12+ and
+            # 49.204244850000016 on 3.11.
+            spent_usd=stable_sum(
                 cost for timestamp, cost in events
                 if start_at <= timestamp < now_utc
             ),
-            recent_24h_usd=sum(
+            recent_24h_usd=stable_sum(
                 cost for timestamp, cost in events
                 if recent_start <= timestamp < now_utc
             ),