v0.1.5
v0.1.5 - Add feed/read article engine
v0.1.5's headline update: This release turns the Feed and Read surfaces into a real article engine instead of a mostly MDX-only display path. It includes 4 merged pull requests with structured public notes, validation, and changelog sync metadata.
Why It Matters
The site already had feed UI, Firecrawl configuration, and DB-aware article detail code, but there was no crawler/writer pipeline that could discover sources, generate original Agent Mag coverage, record ingestion metadata, and publish validated articles. /read and the public machine-readable surfaces were still mostly tied to MDX, so generated articles would not consistently show up where readers, search engines, or AI crawlers expect them.
The workflow also needed a clear operator notification loop. Without a status email, you have to manually inspect GitHub Actions or database documents to know whether scraping, writing, and publishing actually worked.
The user-facing issue was that clicks could appear unreliable because Next client navigation was waiting on RSC/session payloads while the page also emitted console errors. The MetaMask/SES messages are browser-extension noise, but /api/sidebar returning 404 and render-time browser globals were real app-side issues that could contribute to noisy hydration and navigation behavior.
This keeps the first client render stable with the server-rendered HTML, then reads browser-only data after hydration through React's external-store API.
What Changed
- This update turns the Feed and Read surfaces into a real article engine instead of a mostly MDX-only display path. It adds a unified published-article reader that prefers active Cosmos articles, falls back to local MDX content, dedupes by slug/source URL, and feeds the homepage/feed helpers, /read, article detail pages, API responses, RSS, sitemap, AI sitemap, llms feeds, crawl manifest, and global search.
- It also adds ingestion status notifications so scheduled/manual article runs can email a scrape/write/publish summary to configured recipients.
- Added a Cosmos-first published article layer with MDX fallback and shared filtering/sorting helpers.
- Added a Firecrawl /v1/search + Azure OpenAI ingestion engine that discovers recent AI-agent sources, validates scraped markdown, rejects thin/duplicate/off-topic content, generates original cited Agent Mag articles, and records ingestion run/source metadata.
- Added protected POST /api/articles/ingest using configuration with dry-run support.
- Added scripts/feed/ingest.ts and a scheduled/manual GitHub Actions workflow for 4-hour article ingestion runs.
- Added optional ingestion status emails controlled by configuration.
- Updated /read with article archive copy, source badges, newest-first sorting, and unified search/category behavior.
- This update fixes the click/navigation failures seen on production pages where client navigation could feel like it only half-fired. The browser console showed a mix of extension noise, timed-out RSC/session requests, and one real app 404 from the right sidebar.
- Adds /api/sidebar so the right sidebar default content no longer calls a missing endpoint.
- Returns recent articles and trending topics from Cosmos-backed articles when available, with MDX article fallback and short-lived cache headers.
- Moves partner-dashboard host detection into a hydration-safe useSyncExternalStore hook instead of reading window.location.hostname during initial render.
- Moves platform detection for the command-key label out of initial render so the header does not produce server/client text drift.
- Updates partner dashboard link helpers, the app sidebar, header, and nav user menu to use the hydration-safe host hook.
Improvements
- Add feed/read article engine
- Fix click navigation errors
- Add read editorial pipeline
- Productionize editorial automation
Fixes
- fix(seo): auto-fix SEO issues from GPT-5.4 review