Offer: self-updating EOL badge for your supported-versions table

Hi — I noticed you maintain the Node.js versions Bolt supports by hand in your README. We run endoflife.ai (lifecycle data for 488 products, built on the endoflife.date community dataset — we're contributors) and publish free Shields.io endpoint badges that show live support status:

[![Node.js EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fnodejs.json)](https://endoflife.ai/nodejs)

When a version reaches end of life, the badge updates itself — no README edits, no CI. There are per-version badges too (e.g. pin the minimum version you support, so the badge flips the day your floor goes EOL). No signup, no tracking, no API keys — they're static JSON endpoints in the Shields endpoint format, regenerated nightly from vendor lifecycle policies.

If it's useful, the copy-paste snippet for your stack is one click at endoflife.ai/badge; if not, feel free to close this — no hard feelings. Not affiliated with any of your dependencies; just trying to make EOL status visible where people actually look. (Background: why we built these.)

Start by reviewing the README section that lists the Node.js versions Bolt supports and the existing issue discussion. Determine whether the proposed endoflife.ai badge is an appropriate documentation change and what supported-version scope it should represent. Done means the maintainers have an agreed badge placement and wording, or have documented why the proposal is not being adopted.