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

Hi — I noticed you maintain the JDK lines (8/17/21) lamp-cloud supports by hand in your README. We run [endoflife.ai](https://endoflife.ai) (lifecycle data for 488 products, built on the [endoflife.date](https://endoflife.date) community dataset — we're contributors) and publish free Shields.io endpoint badges that show live support status:

[](https://endoflife.ai/oracle-jdk)

```markdown
[](https://endoflife.ai/oracle-jdk)
```

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](https://shields.io/badges/endpoint-badge), regenerated nightly from vendor lifecycle policies.

If it's useful, the copy-paste snippet for your stack is one click at [endoflife.ai/badge](https://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](https://dev.to/endoflifeai/one-badge-that-tells-your-users-when-your-dependencies-die-1gbj).)

Start by reviewing the README's manually maintained JDK 8/17/21 supported-versions table. Compare the proposed Shields endpoint badge and its linked endoflife.ai page with the current README conventions. Done means the maintainers have either added an appropriate badge snippet or decided that no documentation change is wanted.

Written by the indexing model from the issue text.