fablazing-cli 0.2.1__tar.gz → 0.2.2__tar.gz

{fablazing_cli-0.2.1 → fablazing_cli-0.2.2}/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.2.2
+
+- Reference: name the exact `meets_threshold` field on tech candidates and
+  document `data_through` on matchup responses (newest ingested match)
+
 ## 0.2.1
 
 - Matchup: when no card clears the tech-card significance bar (common in

{fablazing_cli-0.2.1 → fablazing_cli-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: fablazing-cli
-Version: 0.2.1
+Version: 0.2.2
 Summary: Fablazing analytics from your terminal - Flesh and Blood matchups, meta, cards, and tournaments.
 Project-URL: Homepage, https://fablazing.com
 Author: Fablazing

{fablazing_cli-0.2.1 → fablazing_cli-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "fablazing-cli"
-version = "0.2.1"
+version = "0.2.2"
 description = "Fablazing analytics from your terminal - Flesh and Blood matchups, meta, cards, and tournaments."
 readme = "README.md"
 requires-python = ">=3.10"

fablazing_cli-0.2.2/src/fablazing_cli/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.2"

{fablazing_cli-0.2.1 → fablazing_cli-0.2.2}/src/fablazing_cli/reference.py

@@ -34,14 +34,16 @@ analytics and paper tournament results for competitive Flesh and Blood.
   in deck1_transform / deck2_transform.
 - Tech cards are Wilson-scored against the matchup baseline, so a lucky
   streak on a small sample doesn't make the list. In close matchups no
-  card may clear the bar - then `tech_candidates` lists the closest
-  near-misses with their scores, explicitly marked below-threshold.
+  card may clear the bar - then `deck{1,2}_tech_candidates` lists the
+  closest near-misses with their scores; each entry carries
+  `meets_threshold: false` (that field, exactly) and the response
+  includes a `deck{1,2}_tech_note` explaining the situation.
 - Tournament standings and decklists come from official paper events.
 - Freshness: `matchup` queries live match data (ingested every ~5
   minutes). Meta snapshot/movers and card trends/popular are daily
-  aggregates (previous day processed at 03:00 / 02:00 UTC) - their
-  responses carry `data_through` in meta so you can see exactly how
-  fresh the numbers are.
+  aggregates (previous day processed at 03:00 / 02:00 UTC). Every one of
+  these responses carries `data_through` in meta - for matchup it is the
+  newest ingested match, for aggregates the latest processed day.
 
 ## Commands
 - `fablazing matchup EVO001 "Jarl" --days 30`

fablazing_cli-0.2.1/src/fablazing_cli/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.2.1"