feat: bring predicted extinction date from year 5174 to ~2030#50
Conversation
…js and unit test Agent-Logs-Url: https://github.com/nitrocode/token-deathclock/sessions/b85f10fb-f28f-495c-9000-2bbb1711db50 Co-authored-by: nitrocode <7775707+nitrocode@users.noreply.github.com>
👁️ PR Preview
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #50 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 233 233
Branches 107 107
=========================================
Hits 233 233
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
The "Days Until Extinction" life-blocks countdown targeted
MILESTONES[MILESTONES.length - 1](biosphere_collapseat 10 quintillion tokens), projecting to year 5174 — not viscerally meaningful. This decouples the countdown horizon from array position via a newextinctionMarkerboolean field.Changes
milestones.yaml/milestones-data.js— addshuman_extinctionat 77 quadrillion tokens (~Feb 2030) withextinctionMarker: true; all 33 existing milestones preservedscript.js—LB_LAST_MILESTONEresolves viaMILESTONES.find(m => m.extinctionMarker)with fallback to last milestonescripts/build-milestones.js— emits optionalextinctionMarkerfield; adds validation that at most one milestone carries the flagtests/death-clock.test.js— assertsextinctionMarker: trueappears on ≤ 1 milestone