chore(catalog): record the Spring Boot 3.x backfill (45 releases)

[amondnet]

Summary

Registers the 45 Spring Boot 3.x releases published by release.yml today — boot-3.3.0 through
boot-3.5.16 — in catalog.json and markdown/boot/<version>/.

One pull request instead of 45. Every catalog branch the release workflow cuts is based on the
default branch, so the 45 automatic pull requests each rewrote the same projects object and only
the first could have merged; the rest would have needed a conflict resolution or a re-run apiece.

Provenance

Content is the published archives, not a local rebuild. For each version:

1. gh release download boot-<v> --pattern 'boot-<v>.tar.gz*'
2. shasum -a 256 -c boot-<v>.tar.gz.sha256 — the checksum asset published beside it
3. extract, then scripts/promote-markdown.ts on the extracted tree
4. scripts/update-catalog.ts --released-at <the release's publishedAt>

So the committed trees are byte-identical to what consumers fetch, and released_at is each
release's actual publication time. bun run validate-catalog passes: 1 project, 47 versions.

Notes

• 3.x trees are smaller than 4.x (≈390 KB vs 526 KB archived) because the generated appendix —
  auto-configuration listings and configuration-property tables — is a Gradle build output with no
  published equivalent. The prose corpus is complete. See ADR-0004.
• The 45 automatic catalog/boot-3.* pull requests are superseded by this one and will be closed
  with their branches.
• Two release runs first failed at the availability gate with The socket connection was closed unexpectedly while ~30 runs probed Maven Central at once; both passed on re-run. Adding
  retry/backoff to artifact-availability.ts is filed as follow-up in ci(release): add a workflow_dispatch recovery path for an existing tag #61.

---

Summary by cubic

Registers the 45 Spring Boot 3.x releases (boot-3.3.0 through boot-3.5.16) in the catalog as one PR, replacing the 45 automatic PRs that each rewrote the same catalog.json and could not all merge.

Content provenance

• Trees are built from the published archives: downloaded, verified against their .sha256 asset, extracted, and promoted.
• released_at comes from each release's actual publishedAt time.
• bun run validate-catalog passes: 1 project, 47 versions.

Rollout notes

• The 45 automatic catalog/boot-3.* PRs are superseded and will be closed with their branches.
• 3.x trees are smaller than 4.x because the generated appendix is a Gradle build output with no published equivalent; the prose corpus is complete.
• Two release runs hit the availability gate with The socket connection was closed unexpectedly; both passed on re-run. Retry/backoff is filed as follow-up in ci(release): add a workflow_dispatch recovery path for an existing tag #61.

^{Written for commit c0c5e1c. Summary will update on new commits.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[codacy-production]

Not up to standards ⛔

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[greptile-apps]

Too many files changed for review (3000 files, 100 file limit).