Heatmap variant with the T2 bounty row outlined - #78
Merged
Merged
Conversation
The article names T2 (single fetch asserted) as the criterion that waited two generations for its model; the highlighted variant marks that row so the text can point at the picture. Base PNGs re-rendered, pixel-identical. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0112rjaT9dWVPXhqm2FCQQPh
This was referenced Sep 5, 2026
szjanikowski
added a commit
that referenced
this pull request
Sep 9, 2026
The `CVE audit (pip-audit)` gate has been red on `main` since the 2026-08-10 TestPyPI canary — five advisories across three transitive packages, none introduced by a change of ours. `pip-audit` reads a live advisory database, so the gate went red on an unchanged tree (main is still at 61a91c3) and every PR inherits the failure; #78 has been red on exactly this since 2026-08-24 with all other jobs green. aiohttp 3.14.1 PYSEC-2026-3545/3546/3547 fix 3.14.3 cryptography 49.0.0 PYSEC-2026-3552 fix 50.0.0 h2 4.3.0 PYSEC-2026-3628 fix 4.4.1 No first-party code is affected: nasde serves no HTTP and decrypts no PKCS#7. The pins are there to keep the supply chain clean and the gate green, not to patch a reachable bug. `h2` gets its first explicit floor — it reaches the tree through harbor's e2b / grpclib / httpx path and had no lower bound of its own. Resolution moves exactly four packages (aiohttp 3.14.1->3.14.3, cryptography 49.0.0->50.0.1, h2 4.3.0->4.4.1, hpack 4.1.0->4.2.0); harbor stays at 0.19.0 and litellm at 1.87.0. A blanket `uv lock --upgrade` would also clear the advisories but drags ~40 packages including rich 14->15, which carries the whole CLI surface — deliberately not taken here. Verified: ruff check + format clean, mypy clean, 463 tests green, and `pip-audit --strict --ignore-vuln PYSEC-2025-183` (the CI command, on py3.12) reports no known vulnerabilities. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9M7964Dzo5cHXsL13GZpj
szjanikowski
added a commit
that referenced
this pull request
Sep 9, 2026
The `CVE audit (pip-audit)` gate has been red on `main` since the 2026-08-10 TestPyPI canary — five advisories across three transitive packages, none introduced by a change of ours. `pip-audit` reads a live advisory database, so the gate went red on an unchanged tree (main is still at 61a91c3) and every PR inherits the failure; #78 has been red on exactly this since 2026-08-24 with all other jobs green. aiohttp 3.14.1 PYSEC-2026-3545/3546/3547 fix 3.14.3 cryptography 49.0.0 PYSEC-2026-3552 fix 50.0.0 h2 4.3.0 PYSEC-2026-3628 fix 4.4.1 No first-party code is affected: nasde serves no HTTP and decrypts no PKCS#7. The pins are there to keep the supply chain clean and the gate green, not to patch a reachable bug. `h2` gets its first explicit floor — it reaches the tree through harbor's e2b / grpclib / httpx path and had no lower bound of its own. Resolution moves exactly four packages (aiohttp 3.14.1->3.14.3, cryptography 49.0.0->50.0.1, h2 4.3.0->4.4.1, hpack 4.1.0->4.2.0); harbor stays at 0.19.0 and litellm at 1.87.0. A blanket `uv lock --upgrade` would also clear the advisories but drags ~40 packages including rich 14->15, which carries the whole CLI surface — deliberately not taken here. Verified: ruff check + format clean, mypy clean, 463 tests green, and `pip-audit --strict --ignore-vuln PYSEC-2025-183` (the CI command, on py3.12) reports no known vulnerabilities. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V9M7964Dzo5cHXsL13GZpj
szjanikowski
added a commit
that referenced
this pull request
Sep 9, 2026
…81) The `CVE audit (pip-audit)` gate has been red on `main` since the 2026-08-10 TestPyPI canary — five advisories across three transitive packages, none introduced by a change of ours. `pip-audit` reads a live advisory database, so the gate went red on an unchanged tree (main is still at 61a91c3) and every PR inherits the failure; #78 has been red on exactly this since 2026-08-24 with all other jobs green. aiohttp 3.14.1 PYSEC-2026-3545/3546/3547 fix 3.14.3 cryptography 49.0.0 PYSEC-2026-3552 fix 50.0.0 h2 4.3.0 PYSEC-2026-3628 fix 4.4.1 No first-party code is affected: nasde serves no HTTP and decrypts no PKCS#7. The pins are there to keep the supply chain clean and the gate green, not to patch a reachable bug. `h2` gets its first explicit floor — it reaches the tree through harbor's e2b / grpclib / httpx path and had no lower bound of its own. Resolution moves exactly four packages (aiohttp 3.14.1->3.14.3, cryptography 49.0.0->50.0.1, h2 4.3.0->4.4.1, hpack 4.1.0->4.2.0); harbor stays at 0.19.0 and litellm at 1.87.0. A blanket `uv lock --upgrade` would also clear the advisories but drags ~40 packages including rich 14->15, which carries the whole CLI surface — deliberately not taken here. Verified: ruff check + format clean, mypy clean, 463 tests green, and `pip-audit --strict --ignore-vuln PYSEC-2025-183` (the CI command, on py3.12) reports no known vulnerabilities. Claude-Session: https://claude.ai/code/session_01V9M7964Dzo5cHXsL13GZpj Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
szjanikowski
pushed a commit
that referenced
this pull request
Sep 9, 2026
claude-fable-5-1 at $10/$50 per 1M tokens, 1-hour cache write $20, and a cache read rate of $0.25 — 0.025x base input, where every other Claude model reads at 0.1x. That exception is published per-model on the pricing page, so the catalog header and a dedicated test pin it down: on our cache-heavy grids (93–98% of input is cache reads) treating it as 0.1x would overstate a Fable 5.1 run's cost by roughly 3.5x. All Claude entries re-verified against the pricing page on 2026-09-04 and their as_of bumped; the two economics tests that assert the stamped as_of follow. gpt entries unchanged (still 2026-06-08). Also records the missing CHANGELOG entry for claude-sonnet-5 (#78). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018vLdNDXktXCC5brNXSZTfe
szjanikowski
pushed a commit
that referenced
this pull request
Sep 9, 2026
claude-fable-5-1 at $10/$50 per 1M tokens, 1-hour cache write $20, and a cache read rate of $0.25 — 0.025x base input, where every other Claude model reads at 0.1x. That exception is published per-model on the pricing page, so the catalog header and a dedicated test pin it down: on our cache-heavy grids (93–98% of input is cache reads) treating it as 0.1x would overstate a Fable 5.1 run's cost by roughly 3.5x. All Claude entries re-verified against the pricing page on 2026-09-04 and their as_of bumped; the two economics tests that assert the stamped as_of follow. gpt entries unchanged (still 2026-06-08). Also records the missing CHANGELOG entry for claude-sonnet-5 (#78). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018vLdNDXktXCC5brNXSZTfe
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional
highlightparameter toverdict_heatmap.pyand rendersverdict_heatmap{,_en}_t2.pngwith the T2 (single fetch asserted) row outlined and its label bolded. The jagged-frontier article names T2 as the criterion no model met for two generations until Opus 5; the outline lets the text point at the exact row. Base charts unchanged.🤖 Generated with Claude Code
https://claude.ai/code/session_0112rjaT9dWVPXhqm2FCQQPh