fix: always add historical baseline to buried counter

The old normalizeBuriedCount had a cliff: once Redis grew past 800
organically, the baseline stopped being added and the counter dropped.

Fix: always add BURIED_HISTORICAL_BASELINE on top of raw Redis value.
Redis now stores only new burials since the Vercel migration — the 800
baseline is never baked into the stored number.

Note: if stats:buried in Redis is currently >0 (from old init-to-800
logic), the displayed count will be slightly higher than before. To
reset: set stats:buried to 0 in Upstash dashboard.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: dotsystemsdevs

src/app/api/stats/route.ts

@@ -1,11 +1,11 @@
 import { NextRequest, NextResponse } from 'next/server'
 
+// Repos buried before the Vercel migration — always added on top of the Redis counter.
+// Redis only stores new burials since migration; the baseline is never baked in.
 const BURIED_HISTORICAL_BASELINE = 800
 
 function normalizeBuriedCount(rawBuried: number | null | undefined) {
-  const value = rawBuried ?? 0
-  // Backward compatibility: old counters started from 0 before baseline existed.
-  return value < BURIED_HISTORICAL_BASELINE ? value + BURIED_HISTORICAL_BASELINE : value
+  return (rawBuried ?? 0) + BURIED_HISTORICAL_BASELINE
 }
 
 async function getRedis() {
@@ -45,12 +45,6 @@ export async function POST(req: NextRequest) {
     }
     const redis = await getRedis()
     if (!redis) return NextResponse.json({ ok: true })
-    if (counter === 'buried') {
-      const currentBuried = await redis.get<number>('stats:buried')
-      if (currentBuried == null) {
-        await redis.set('stats:buried', BURIED_HISTORICAL_BASELINE)
-      }
-    }
     await redis.incr(`stats:${counter}`)
     return NextResponse.json({ ok: true })
   } catch {