# Chronicler Dispatch — Dashboard Badges: v1.1.0 Implementation Plan

**Date:** 2026-04-12
**From:** Chronicler #84 — The Meridian
**To:** Code

---

## Gemini Consultation Complete ✅

Full doc: `firefrost-operations-manual/docs/consultations/gemini-blueprint-css-build-2026-04-12.md`

## The Plan

**Path A wins.** Add smart Node version detection to build.sh. Gemini confirmed `--openssl-legacy-provider` is safe on Node 24 (build-time only, no runtime impact). Vanilla JS badges rejected as too brittle.

**DO NOT implement Path D (pre-built bundle)** — Gemini flagged this as dangerous; it would overwrite Pterodactyl's unified `public/assets/main.js` and break all other Blueprint extensions on the customer's panel.

## build.sh Changes for v1.1.0

Add this block near the top of build.sh, before any injection logic:

```bash
# Node version detection
NODE_MAJOR_VERSION=$(node -v | grep -oE '[0-9]+' | head -1)
echo "Detected Node.js version: v$NODE_MAJOR_VERSION"

# Fail fast on Node < 16
if [ "$NODE_MAJOR_VERSION" -lt 16 ]; then
    echo "ERROR: ModpackChecker requires Node.js 16 or higher."
    echo "Please upgrade Node.js on your panel and try again."
    exit 1
fi

# Apply OpenSSL legacy provider for Node 17+ (fixes css-loader MD4 hashing)
if [ "$NODE_MAJOR_VERSION" -ge 17 ]; then
    echo "Applying OpenSSL legacy provider for Node 17+ compatibility..."
    export NODE_OPTIONS=--openssl-legacy-provider
fi
```

## BuiltByBit Listing Copy (v1.1.0 section)

Gemini's suggested wording:
> "v1.1.0 includes our new interactive Dashboard Badges! This feature requires a standard panel asset compilation. Our smart installer handles the heavy lifting, ensuring full compatibility with modern Node.js environments."

## Timeline

This is post-launch work — v1.1.0 milestone. No rush. Current v1.0.0 ships clean without badges.

*— Chronicler #84, The Meridian*
**Fire + Frost + Foundation** 💙🔥❄️
