A fumbled relief attempt puts a point on

Trying to steady somebody and making it worse is the most familiar thing on that
list, and until now it was the only outcome that cost nothing.

Done as a NEGATIVE relief rather than a second code path: panicReliefFor returns
-1 on a fumble, and easePanic already subtracts what it is given, so subtracting
a negative raises the track. One number, one direction, no branch that could
drift from the other. The clamp still holds — fumbling at 5 stays at 5.

The chat card had to be told, because otherwise it prints the word "Psychology"
over a number that has just gone UP and the table reads that as a bug rather than
as the rule. It now leads with a red FUMBLED tag.

Guarded three ways: a spot-check in check-rules for the -1 itself, and two
behaviour tests — one that the sign survives easePanic's subtraction and
actually raises the track, one that it cannot push past the top. A test on the
constant alone would have passed even if easePanic had healed on a fumble.

Verified live: 2 → fumble → 3 → success → 2 → special → 0, and a fumble at 5
staying at 5, with the cards reading correctly.

Version 1.1.2.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

packs/gear/CURRENT

@@ -1 +1 @@
-MANIFEST-000002
+MANIFEST-000004

packs/gear/LOG

@@ -1 +1,5 @@
-2026/08/17-21:58:29.403187 16e463000 Delete type=3 #1
+2026/08/17-23:24:47.248920 173d63000 Recovering log #3
+2026/08/17-23:24:47.249014 173d63000 Level-0 table #5: started
+2026/08/17-23:24:47.249313 173d63000 Level-0 table #5: 31614 bytes OK
+2026/08/17-23:24:47.249730 173d63000 Delete type=0 #3
+2026/08/17-23:24:47.249796 173d63000 Delete type=3 #2

packs/gear/LOG.old

@@ -0,0 +1 @@
+2026/08/17-23:24:31.475804 17004b000 Delete type=3 #1