tuipet 0.5.330__tar.gz → 0.5.332__tar.gz

{tuipet-0.5.330/src/tuipet.egg-info → tuipet-0.5.332}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tuipet
-Version: 0.5.330
+Version: 0.5.332
 Summary: A terminal virtual pet (Digimon V-Pet style) rendered with halfblock sprites, built on data from the real devices.
 Author-email: Joel Taylor <joeltaylor734@gmail.com>
 License-Expression: MIT

{tuipet-0.5.330 → tuipet-0.5.332}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tuipet"
-version = "0.5.330"
+version = "0.5.332"
 description = "A terminal virtual pet (Digimon V-Pet style) rendered with halfblock sprites, built on data from the real devices."
 readme = "README.md"
 requires-python = ">=3.10"

{tuipet-0.5.330 → tuipet-0.5.332}/src/tuipet/app.py

@@ -150,7 +150,7 @@ class TuiPetApp(ActionsMixin, App):
     """
     # the release-news line (title-screen msg box, first launch per build) --
     # UPDATE THIS WITH EVERY RELEASE that ships something player-visible
-    WHATS_NEW = ("A CARE MISTAKE NOW TELLS YOU WHAT YOU MISSED: the counter used to just tick up on the card with no explanation, which is a rough way to learn about the one thing that can kill a Mega. Every slip names itself as it happens — 'left hungry too long', 'the lights left on', 'acting up, not scolded', 'empty effort gauge'. And to settle it: POOP HAS NEVER COST YOU A CARE MISTAKE, not at one pile and not at four. A dirty room makes your pet sick and makes it act up; it is not a missed call, and the counter does not move for it.")
+    WHATS_NEW = ("THAT LITTLE SPRITE IN THE CORNER IS A FESTIVAL, NOT A STUCK PIXEL: on four days a year a decoration appears in your arena — the Crest of Courage on Odaiba Memorial Day, a present at Christmas, candy at Halloween, cake at New Year — and until now nothing on the home screen said so. The card names the day above your vitals whenever one is on, on the egg screen too. It was only ever labelled on the adventure card before.")
 
     BINDINGS = [
         # jogress is LOBBY-ONLY (fusion needs a real partner from the

{tuipet-0.5.330 → tuipet-0.5.332}/src/tuipet/petbase.py

@@ -679,8 +679,17 @@ LIGHTS_MISTAKE_POSTPONE = -60.0         # AfterMistakeMinutesPostponed: the NEXT
 LIGHTS_MISTAKE_OBED = -1                # LightsOnMistakeObedienceChange (once per night)
 HUNGER_MISTAKE_OBED = 1                 # HungerMistakeObedienceChange (canon: +1!)
 HUNGER_MISTAKE_OBED_GLUTTON = -1        # ...ChangeGlutton
-LIGHTS_MISTAKE_SEC = 60.0               # MinutesToMistakeLights(60) as ~12% of the sleep,
-#                                         scaled to tuipet's ~6-min night -- one mistake/night
+LIGHTS_MISTAKE_SEC = 60.0               # MinutesToMistakeLights(60): the FIRST lit mistake
+#                                         lands 60 game-min into the sleep, then every 120
+#                                         (LIGHTS_MISTAKE_POSTPONE).  ⚠ THE OLD TAIL HERE
+#                                         CLAIMED "~6-min night -- one mistake/night" AND IT
+#                                         WAS WRONG BOTH WAYS: measured on a live Mega the
+#                                         night runs ~600 game-min, so a fully lit one books
+#                                         FIVE (canon's own ~8h night gives 4 -- _tick_asleep
+#                                         has always said so).  The number is canon and stays;
+#                                         only this comment lied.  Diagnosed 2026-07-31 when
+#                                         Joel asked what was eating his care mistakes: it was
+#                                         this, 5 of his 6 a day.
 MORNING_MOOD_CHANCE = 5                 # MorningMoodChance: 1/5 bad, 1/5 terrible-if-happy, 1/5 good
 BAD_MORNING_MOOD = {"Happy": -150, "Neutral": -100, "Unhappy": -10, "Depressed": -10}
 GOOD_MORNING_MOOD = {"Happy": 50, "Neutral": 100, "Unhappy": 150, "Depressed": 150}

{tuipet-0.5.330 → tuipet-0.5.332}/src/tuipet/petbody.py

@@ -128,15 +128,30 @@ class BodyMixin:
         anyone else loses 50 -- then the counters tick (care-mistake audit
         2026-07-05: the counters ticked silently).
 
+        ⭐⭐THE THREE CALLS, AND ONLY THE THREE (2026-08-01, Joel: "canonize
+        all care mistakes").  ⛔DO NOT ADD A FOURTH CALLER TO THIS METHOD.
+        THE BANDAI DEVICE RECORD IS THE AUTHORITY on what a care mistake IS:
+        a MISSED CALL, and the device makes exactly three calls --
+            1. hunger empty        (petbody, the hunger call)
+            2. strength empty      (petbody, the effort call)
+            3. tired / wants sleep (petbody, the lights call)
+        The manual also names things that are explicitly NOT care mistakes:
+        overfeeding, injury, and waking a sleeper.  Two impostors were cut on
+        that ruling -- the ignored TANTRUM (`_tick_mortality`; the device has
+        no scold mechanic at all, so ignoring one cannot cost a mistake) and
+        the CHEESEBURGER (`petcare._junk`; that is overfeeding, named in the
+        manual as not-a-mistake).  Both keep their own penalties in tuipet's
+        own currencies -- obedience and weight.
+        FILTH books nothing either, and never did: `_open_scold` raises only
+        `scold_window`, never `discipline_call`, so the timeout cannot reach
+        it.  Measured 2026-07-31: 4.2 game-days pegged at poop 4 with the
+        calls answered books ZERO.
+
         ⭐`reason` NAMES THE SLIP (bug report 2026-07-31, Joel: "mon is getting
-        a care mistake after 4 poops, not 1... correct?").  It is not the poop
-        -- filth books NO mistake, by the LINES_SPEC §5 / Pen20 ruling above
-        `_open_scold`, and measured: 4.2 game-days pegged at poop 4 with the
-        other calls answered books ZERO.  But he could not know that, because a
-        care mistake was SILENT: the counter moved on the card and nothing ever
-        said which of the four calls went unanswered -- for a Mega, where five
-        of them turn lethal.  The app reads this on the tick edge and flashes
-        it (an unheard verdict is a silent failure)."""
+        a care mistake after 4 poops, not 1... correct?").  A care mistake was
+        SILENT: the counter moved on the card and nothing ever said which call
+        went unanswered -- on a Mega, where five turn lethal.  The app reads
+        this on the tick edge and flashes it."""
         self.care_mistakes += 1
         self.mistake_reason = reason
         self.mistake_day += 1                        # MistakeIncMissedDayChange
@@ -676,23 +691,28 @@ class BodyMixin:
             self._obed_t -= _lapse
             self._set_obedience(self.obedience + OBEDIENCE_LAPSE_DEC * -1   # noqa: F405
                                 + OBEDIENCE_FILTH_SCALE * self.poop)        # noqa: F405
-        # THE TANTRUM (canon restoration B, 2026-07-23 -- adapted
-        # checkDisciplineCall): an awake pet AT HOME acts up about once
-        # per 5400 game-min (~90 REAL minutes of play -- the label used to
-        # read "90 game-min", the P0b mislabel); SCOLD inside the window
-        # pays obedience +25, IGNORING it past the window costs a care
-        # mistake and -5 (canon: ignored calls cost).  Never on the road,
-        # never asleep.
+        # THE TANTRUM: an awake pet AT HOME acts up about once per 5400
+        # game-min (~90 REAL minutes of play); SCOLD inside the window pays
+        # obedience +25, IGNORING it past the window costs obedience -5.
+        # Never on the road, never asleep.
+        #
+        # ⭐IT IS NOT A CARE MISTAKE (2026-08-01, Joel: "not scolding an acting
+        # out mon is canonically a care mistake?" -> "canon is bandai").  THE
+        # BANDAI DEVICE RECORD IS THE AUTHORITY, and it is unambiguous: a care
+        # mistake is a MISSED CALL, and the device has exactly three calls --
+        # hunger empty, strength empty, and tired/wants-sleep (the lights).
+        # The manual carries no praise, no scold, no acting-up mechanic at all,
+        # so ignoring one cannot cost a mistake there.  The line that stood
+        # here booked one anyway under a citation it never had.
+        # The TANTRUM ITSELF stays: it is tuipet's own system, so it pays in
+        # tuipet's own currency (obedience), and it no longer touches the
+        # Bandai-defined counter that gates evolution and kills at 20.
         if (not self.asleep and not getattr(self, "away", False)
                 and self.stage not in ("Egg", "Fresh")):
             if self.discipline_call:
                 if self.world_seconds > getattr(self, "scold_window", 0.0):
                     self.discipline_call = False
                     self.scold_window = 0.0
-                    # through the front door: the bare += here skipped the
-                    # mood sting + the birthday mistake_day tally every
-                    # other mistake pays (incMistake; audit 2026-07-25)
-                    self._inc_mistake("acting up, not scolded")
                     self._set_obedience(self.obedience - 5)
             else:
                 # canon checkDisciplineCall: a check every DisciplineCallMin

{tuipet-0.5.330 → tuipet-0.5.332}/src/tuipet/petcare.py

@@ -798,12 +798,15 @@ class CareMixin:
         return "...it was DELICIOUS. And fatal."
 
     def _junk(self):
+        # ⭐NOT A CARE MISTAKE (2026-08-01, Joel: "canonize all care mistakes").
+        # THE BANDAI DEVICE RECORD IS THE AUTHORITY and it is explicit on this
+        # one: a care mistake is a MISSED CALL, and OVERFEEDING is called out
+        # by name as something that is NOT one.  The burger is junk food -- it
+        # fills the belly and it makes the pet fat, which is the whole penalty.
+        # It has no business touching the counter that gates evolution and
+        # kills at 20.
         self.hunger = FULL_HUNGER
         self._set_weight(self.weight + 4)
-        # the real mistake pipeline: the bare counter bumped care_mistakes
-        # without the mood sting or mistake_day, so the burger slip was
-        # invisible to the birthday judgment
-        self._inc_mistake("that cheeseburger")
         return "Delicious. Regrettable."
 
     def _premium_meat(self):

{tuipet-0.5.330 → tuipet-0.5.332}/src/tuipet/shop.py

@@ -75,7 +75,7 @@ _AUTHORED = {
     "vegetable":       ("Vegetable",       "f:3",  150,  "Feed", "hunger +1 · weight -1", "crunchy diet fare"),
     "tuna":            ("Tuna",            "f:14", 400,  "Feed", "hunger +2 · energy +1", "a hearty catch"),
     "cake":            ("Cake",            "f:6",  300,  "Feed", "hunger +1 · energy +2 · weight +2", "a celebration slice"),
-    "cheese_burger":   ("Cheese burger",   "f:57", 50,   "Feed", "fills belly · weight +4 · a care mistake", "greasy, regrettable"),
+    "cheese_burger":   ("Cheese burger",   "f:57", 50,   "Feed", "fills the belly · weight +4", "greasy, regrettable"),
     "giga_meal":       ("Giga Meal",       "f:28", 800,  "Feed", "fills belly · energy +4 · weight +6", "a feast fit for a Mega"),
     "steak":           ("Steak",           "f:8",  2000, "Feed", "fills belly · 12h satiety", "the premium table"),
     "poison_mushroom": ("Poison Mushroom", "f:13", 200,  "Feed", "DO NOT FEED", "it does look delicious"),
@@ -249,7 +249,9 @@ _TOUCHES = {
     "cupcake": ("hunger", "energy"),
     "cookie": ("hunger", "energy"),
     "candy": ("hunger", "energy"),
-    "cheese_burger": ("hunger", "weight", "care_mistakes"),
+    # (care_mistakes dropped 2026-08-01, "canonize all care mistakes": the
+    #  Bandai record names OVERFEEDING as explicitly NOT a care mistake)
+    "cheese_burger": ("hunger", "weight"),
     "giga_meal": ("hunger", "energy", "weight"),
     "steak": ("hunger", "full_until"),
     "poison_mushroom": ("dead",),          # _die(): the one lethal entry

{tuipet-0.5.330 → tuipet-0.5.332}/src/tuipet/statusbox.py

@@ -198,6 +198,21 @@ def adventure_line(pet):
     return f"Quest   {count}[dim]▸ {_frontier_name(pet, 16 - len(count))}[/]"
 
 
+def festival_line():
+    """TODAY's festival, named -- or None on an ordinary day.
+
+    ⭐Bug report 2026-08-01 (Joel): "whyyyy is there a sun pixel sprite stuck
+    on the lcd screen?"  It was the Crest of Courage, the Odaiba Memorial Day
+    decoration (arenafx.HOLIDAY_DECOR) -- a prop that quietly appears in the
+    arena's corner on four dates a year.  The festival was named NOWHERE on
+    the home screen, so the only thing a player could conclude was that a
+    pixel had got stuck.  A prop with no label is a glitch; a prop with a
+    label is a holiday.  (The road card has always named it -- statusbox.road
+    -- and that is the only place it was ever said.)"""
+    from . import tournament
+    return tournament.holiday()
+
+
 def home_lines(pet):
     from . import lines as _lines           # DMX level: exp vs canon thresholds
     T = theme
@@ -206,9 +221,11 @@ def home_lines(pet):
     age = age_compact(pet.age_seconds)
     xm = f" [b {T.ACCENT}]X[/]" if pet.x_antibody != "None" else ""
     lvl = _lines._pet_level(pet)
+    fest = festival_line()
     return [
         f"[b]{pet.name[:22]}[/]{xm}",
         f"[dim]{pet.stage}{(' · ' + pet.attribute) if pet.attribute else ''}[/]",
+    ] + ([f"[{T.COIN}]★ {fest[:24]}[/]"] if fest else []) + [
         DIV,
         f"Hunger  {hearts(pet.hunger)}",
         f"Effort  {hearts(pet.strength)}",
@@ -252,9 +269,14 @@ def home_lines(pet):
 
 def egg_lines(pet):
     mins, secs = divmod(int(pet.age_seconds), 60)
+    # the festival prop draws over an EGG's arena too (arenafx._effect_overlay
+    # blits it before the `pet.num == -1` return), so the egg card names the
+    # day for the same reason the home card does -- 12 rows, room to spare
+    fest = festival_line()
     return [
         "[b]Digitama[/] [dim]· egg[/]",
         DIV,
+    ] + ([f"[{theme.COIN}]★ {fest[:24]}[/]", ""] if fest else []) + [
         "[dim]a new life is warming[/]",
         "",
         "Destined to hatch",

{tuipet-0.5.330 → tuipet-0.5.332/src/tuipet.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tuipet
-Version: 0.5.330
+Version: 0.5.332
 Summary: A terminal virtual pet (Digimon V-Pet style) rendered with halfblock sprites, built on data from the real devices.
 Author-email: Joel Taylor <joeltaylor734@gmail.com>
 License-Expression: MIT

{tuipet-0.5.330 → tuipet-0.5.332}/tests/test_canon_discipline.py

@@ -48,15 +48,20 @@ def test_the_tantrum_never_fires_on_the_road_or_asleep(monkeypatch):
     assert not road.discipline_call
 
 
-def test_an_ignored_tantrum_costs(monkeypatch):
+def test_an_ignored_tantrum_costs_manners_not_a_care_mistake(monkeypatch):
+    """⭐2026-08-01, Joel: "canonize all care mistakes".  The BANDAI device
+    record defines a care mistake as a MISSED CALL and the device makes three
+    -- hunger, strength, tired/sleep.  It has no scold mechanic at all, so
+    ignoring a tantrum cannot be one.  The tantrum is TUIPET'S OWN system, so
+    it keeps paying in tuipet's own currency: obedience."""
     p = _pet(discipline_call=True)
     p.scold_window = p.world_seconds - 1.0            # the window has passed
     monkeypatch.setattr(petbody.random, "random", lambda: 0.99)
     m0, o0 = p.care_mistakes, p.obedience
     p.tick(1.0)
-    assert not p.discipline_call
-    assert p.care_mistakes == m0 + 1                  # canon: ignored calls cost
-    assert p.obedience == o0 - 5
+    assert not p.discipline_call                      # the window closed
+    assert p.obedience == o0 - 5                      # manners, yes
+    assert p.care_mistakes == m0                      # the counter, NO
 
 
 def test_scold_answers_the_call_and_wrong_scold_lands_nothing():
@@ -359,15 +364,14 @@ def test_a_new_pet_is_not_born_disobedient():
     assert p.manners_refusal("feed") is False
 
 
-def test_an_ignored_tantrum_pays_the_full_mistake(monkeypatch):
-    """The ignored-call path bumped the bare counter, skipping incMistake --
-    whose one LIVE side effect is the birthday mistake_day tally (the mood
-    sting is an inert citation; _set_mood is a no-op).  Every other mistake
-    pays the tally; this one didn't (claims audit 2026-07-25)."""
+def test_an_ignored_tantrum_touches_neither_counter(monkeypatch):
+    """It used to route through incMistake, which pays BOTH the care-mistake
+    counter and the birthday mistake_day tally.  Canonized 2026-08-01: the
+    device has no scold mechanic, so an ignored tantrum feeds neither."""
     p = _pet(discipline_call=True)
     p.scold_window = p.world_seconds - 1.0
     monkeypatch.setattr(petbody.random, "random", lambda: 0.99)
     d0, m0 = p.mistake_day, p.care_mistakes
     p.tick(1.0)
-    assert p.care_mistakes == m0 + 1
-    assert p.mistake_day == d0 + 1                    # the birthday tally
+    assert p.care_mistakes == m0
+    assert p.mistake_day == d0                        # nor the birthday tally

{tuipet-0.5.330 → tuipet-0.5.332}/tests/test_filth_system.py

@@ -147,11 +147,16 @@ def test_filth_never_books_a_care_mistake():
         f"filth booked {p.care_mistakes} care mistakes -- it must book none")
 
 
-def test_every_care_mistake_names_itself():
-    """The real defect behind that report: a care mistake was SILENT.  The
-    counter moved on the card, the mood took its sting, and nothing said WHICH
-    call was missed -- on a Mega, where the fifth slip turns lethal.  Every
-    source stamps a reason, and each fits the 40-cell HUD line."""
+def test_a_care_mistake_is_a_missed_call_and_nothing_else():
+    """⭐THE THREE CALLS (2026-08-01, Joel: "canonize all care mistakes").
+    The BANDAI device record defines a care mistake as a MISSED CALL, and the
+    device makes exactly three: hunger empty, strength empty, tired/wants
+    sleep.  It also names what is NOT one -- overfeeding, injury, waking a
+    sleeper.  Two impostors were cut on that ruling: the ignored TANTRUM (the
+    device has no scold mechanic at all) and the CHEESEBURGER (overfeeding).
+    ⛔THIS PIN IS A FENCE: a fourth `_inc_mistake` caller fails it.
+
+    Each source also NAMES itself, and each fits the 40-cell HUD line."""
     import inspect
     import os
     import re
@@ -164,7 +169,10 @@ def test_every_care_mistake_names_itself():
     from tuipet.pet import Pet
     src = inspect.getsource(petbody) + inspect.getsource(petcare)
     calls = re.findall(r"_inc_mistake\((.*?)\)", src)
-    assert len(calls) >= 5, calls
+    reasons = [a.strip('"') for a in calls if not a.startswith("self")]
+    assert sorted(reasons) == sorted([
+        "left hungry too long", "empty effort gauge", "the lights left on",
+    ]), f"the three calls, and only the three -- got {reasons}"
     for arg in calls:
         if arg.startswith("self"):            # the definition's own signature
             continue
@@ -194,3 +202,78 @@ def test_the_first_slip_of_a_session_still_flashes():
     assert src.index("cm0 = self.pet.care_mistakes") < src.index("self.pet.tick(1.0)")
     assert src.index("self.pet.tick(1.0)") < src.index("if p.care_mistakes > cm0")
     assert not re.search(r"_cm_seen\s*=", src)      # no lazy latch, ever again
+
+
+def test_a_lit_night_is_the_dominant_mistake_source():
+    """Diagnosed 2026-07-31 (Joel: "ok so what's actually causing my care
+    mistakes then").  His cloud save carried lights=True; measured on his own
+    numbers, one game-day costs FIVE lights mistakes and one ignored tantrum,
+    against ONE with the lights off.  Canon: the first lit mistake lands 60
+    game-min in, then every 120 (LIGHTS_MISTAKE_POSTPONE = -60).  The number
+    is canon and stays -- this pins the SHAPE so the constants block's old
+    "one mistake/night" claim can never quietly come back."""
+    import os
+    import random
+    import tempfile
+    os.environ.setdefault("TUIPET_SAVE_DIR", tempfile.mkdtemp())
+    from tuipet.pet import Pet
+
+    def day(lights):
+        random.seed(12)
+        p = Pet(num=399, name="Omni", stage="Mega", attribute="Vaccine",
+                obedience=111)
+        p.hunger, p.strength = 4, 4
+        p.sleep_limit, p.world_seconds = 840.0, 12607.0
+        p.max_energy = 38
+        p._set_energy(26)
+        p.lights = lights
+        seen = []
+        real = type(p)._inc_mistake
+        type(p)._inc_mistake = lambda s, reason="": (seen.append(reason),
+                                                     real(s, reason))[1]
+        try:
+            for _ in range(1440):
+                p.tick(1.0)
+        finally:
+            type(p)._inc_mistake = real
+        return seen
+
+    lit = day(True)
+    dark = day(False)
+    assert lit.count("the lights left on") >= 4, lit
+    assert "the lights left on" not in dark, dark
+    assert len(lit) > len(dark), (lit, dark)
+
+
+def test_the_two_cut_impostors_keep_their_own_penalties():
+    """Canonizing the counter must not quietly delete the SYSTEMS.  An ignored
+    tantrum still costs obedience (tuipet's own currency), and the burger
+    still packs on weight -- they just no longer touch the Bandai-defined
+    counter that gates evolution and kills at 20."""
+    import os
+    import tempfile
+    os.environ.setdefault("TUIPET_SAVE_DIR", tempfile.mkdtemp())
+    from tuipet.pet import Pet
+
+    # the ignored tantrum: obedience yes, care mistake no
+    p = Pet(num=399, name="Omni", stage="Mega", attribute="Vaccine",
+            obedience=111)
+    p.hunger, p.strength = 4, 4
+    p.world_seconds = 12607.0
+    p.discipline_call = True
+    p.scold_window = p.world_seconds - 1.0          # already expired
+    obed0, cm0 = p.obedience, p.care_mistakes
+    p._tick_mortality(1.0)
+    assert p.discipline_call is False                # the window closed
+    assert p.obedience == obed0 - 5                  # it still stings manners
+    assert p.care_mistakes == cm0                    # ...and NOT the counter
+
+    # the cheeseburger: weight yes, care mistake no
+    q = Pet(num=399, name="Omni", stage="Mega", attribute="Vaccine")
+    q.world_seconds = 600.0
+    q.hunger = 1
+    q.add_item("cheese_burger")
+    w0, cm0 = q.weight, q.care_mistakes
+    q.use_item("cheese_burger")
+    assert q.weight > w0 and q.hunger == 4           # fat and fed
+    assert q.care_mistakes == cm0                    # overfeeding is not a slip

{tuipet-0.5.330 → tuipet-0.5.332}/tests/test_shop_dossier_audit.py

@@ -37,8 +37,13 @@ def test_food_dials_match_their_blurbs():
 
 def test_the_big_meals_and_the_mushroom():
     p = _pet()
+    w0 = p.weight
     _use(p, "cheese_burger")
-    assert p.hunger == FULL_HUNGER and p.care_mistakes == 1   # "a care mistake"
+    # "fills the belly · weight +4" -- and NOT a care mistake since the
+    # canonization (2026-08-01): the Bandai record names overfeeding as
+    # explicitly not one, so the blurb no longer promises it either
+    assert p.hunger == FULL_HUNGER and p.weight - w0 == 4
+    assert p.care_mistakes == 0
     p = _pet()
     w0, e0 = p.weight, p.energy
     _use(p, "giga_meal")

{tuipet-0.5.330 → tuipet-0.5.332}/tests/test_status_box.py

@@ -192,3 +192,41 @@ def test_battle_card_wraps_the_result_note():
     statusbox.battle(app)
     _fits(app.stats_w, "battle")
     _no_words_lost(app.stats_w, "battle", _M.hud_note)
+
+
+def test_the_home_and_egg_cards_name_the_festival():
+    """⭐Bug report 2026-08-01 (Joel): "whyyyy is there a sun pixel sprite
+    stuck on the lcd screen?"  It was the Crest of Courage — the Odaiba
+    Memorial Day decoration (arenafx.HOLIDAY_DECOR), a prop that appears in
+    the arena corner on four dates a year and was named NOWHERE on the home
+    screen.  A prop with no label reads as a stuck pixel.
+
+    ⛔THIS ALSO FENCES THE ROW BUDGET.  The festival banner is the 16th row of
+    a 16-row card, so a future 17th row would break the home card on four days
+    a year and pass every other day.  Forcing a festival here turns that
+    landmine into an always-on gate."""
+    import datetime
+    from tuipet import statusbox, tournament
+    from tuipet.arenafx import HOLIDAY_DECOR
+    fake = _FakeStats()
+    p = _pet()
+    e = Pet(num=-1, name="", stage="Egg")
+    e.world_seconds = 600.0
+    for name, (m, d) in {"Odaiba Memorial Day": (8, 1),
+                         "Christmas Festival": (12, 25),
+                         "Halloween Festival": (10, 31),
+                         "New Year Festival": (1, 1)}.items():
+        tournament._today = (lambda mm, dd: (lambda: datetime.date(2026, mm, dd)))(m, d)
+        assert name in HOLIDAY_DECOR, f"{name} draws a prop with no decor entry"
+        for lines, tag in ((statusbox.home_lines(p), "home"),
+                           (statusbox.egg_lines(e), "egg")):
+            fake.txt = "\n".join(lines)
+            _fits(fake, f"{tag} on {name}")
+            assert name in fake.txt, f"{tag} card never names {name}"
+    # ...and an ordinary day carries no banner at all
+    tournament._today = lambda: datetime.date(2026, 6, 17)
+    fake.txt = "\n".join(statusbox.home_lines(p))
+    _fits(fake, "home, ordinary day")
+    # (not a bare "★" check -- the Battle row wears ★{trophies} every day)
+    for name in ("Odaiba", "Christmas", "Halloween", "New Year"):
+        assert name not in fake.txt