releases.sh Release Notes

**Added** - Blume changelogs — sites built on the Blume self-hosted Astro changelog generator are now auto-detected and ingested via their native RSS feed. - AI-scored importance now reaches collection and category timelines, the following feed, live stream, search results, related rails, and MCP `search` results; a hover card on the flame glyph explains the 4 vs. 5 score. - Collection weekly digests available as Markdown, JSON, and Atom — `.md`, `.json`, and `.atom` format adapters on the digest index; individual week pages support `.md` and `.json`. - Recent digests surface in the collection right rail with a browse-all link; digest pages now include an AI-generated content disclaimer. **Fixed** - Collection digest pages polished — headings render at the correct depth, a covered-orgs facepile shows which companies are featured, breadcrumbs link back to the digest archive, and prev/next cards navigate between weeks. - Geist Pixel wordmark now uses the variable font at true weight 400 — the faux-bold smear from stacked bold utilities is gone.

Minor Changes

• 88999c9: releases search --json now passes AI-scored importance (1–5) through in the slim search-hit shape, normalized to null when unscored — same norm as get / tail / latest. The TTY search table also marks importance ≥ 4 with the quiet glyph. Bumps @buildinternet/releases-api-types to ^0.48.0 for the search/related/digest wire field (monorepo #2135).

Patch Changes

• e97462a: Surface a NODE_EXTRA_CA_CERTS / SSL_CERT_FILE hint on TLS certificate verification failures, and document custom-CA support (TLS-intercepting proxies) in the README.

**Added** - Weekly collection digests — AI-written weekly summaries for curated collections, published at `/collections/[slug]/digest/[week]`; browse past digests at `/collections/[slug]/digest`; `GET /v1/collections/:slug/digests` and `GET /v1/collections/:slug/digests/:weekStart` expose the list and detail via the REST API; each digest links to the releases it covers, grouped by org. - Release sitemap — `GET /v1/sitemap/releases` surfaces importance-gated releases (importance ≥ 3 with an AI summary) for search engine indexing; `sitemap-releases.xml` is now declared in `robots.txt`. **Changed** - Release pages now show a labeled divider between the AI summary and the original release note — a "From the original release note" section header with an inline "View original ↗" link makes the two-source layout explicit; the lede is suppressed when the body isn't meaningfully longer than the summary. - Web interface polish — buttons now have press-scale feedback on click; release thumbnails in tickers and org teasers display a consistent image outline; the homepage agent use-cases copy has been rewritten in plainer language.

Minor Changes

• 0b1a45e: Remove the deprecated get_source_changelog tool from the local stdio MCP bridge. It was deprecated in 0.71.0 in favor of get_catalog_entry with the changelog_* params (include_changelog / changelog_path / changelog_offset / changelog_limit / changelog_tokens); calling get_source_changelog by name now returns MCP's standard unknown-tool error. The REST helper sourceChangelog() is unchanged — get_catalog_entry and the admin source changelog CLI command still use it.
• e7d50b4: releases search gains --category <slug> and --collection <slug> filters. --category scopes hits to organizations in a category (the API validates and resolves curator aliases like e-commerce → commerce, so the value is forwarded as-is); --collection scopes to a curated collection's member orgs (unknown slugs report "no collection matching …", mirroring --domain). Both forward to the new /v1/search params and compose with the existing --domain / --product / --kind / --since / --until scopes. …

**Added** - Release importance scoring (1–5) — all newly ingested releases receive an AI-scored significance rating; a flame glyph marks high-impact (4) and landmark (5) releases on feed cards and detail pages; `GET /v1/releases/latest` gains a `?minImportance=` filter; MCP `get_latest_releases` and `whats_changed` expose a matching parameter. - `/updates` redesigned with a timeline rail and composition glyphs — month rows and area chips (CLI / Web) filter the feed client-side; per-release meta lines render composition counts as filled, half, and dash glyphs; Follow, Digest, and Atom links appear in the page header. - Category and collection scoping for search — `GET /v1/search` now accepts `?category=` and `?collection=` to narrow results to a taxonomy category or a curated collection's member orgs. - Wider catalog and collection layouts with an export rail — `/catalog` and `/collections` expand to a wider shell; the collections index uses a two-column grid; collection detail pages gain a sticky rail with Export (`.json` / `.md` / `.atom`) and a Report a problem button. **Changed** - Digest emails and collection daily summaries now bias toward higher-importance releases — within each org section in digests and when selecting releases for collection date tiles, items with a higher importance score surface first. **Fixed** - Digest emails now capture releases ingested after the check window opened — editorial posts published hours befor…