mcp-scraper 0.57.3 → 0.60.0

package/CHANGELOG.md

@@ -4,6 +4,35 @@ All notable changes to MCP Scraper are documented here. The format is based on [
 
 ## [Unreleased]
 
+## [0.60.0] - 2026-08-17
+
+### Added
+
+- Transparent Commons has its own semantic search. `commons_index_documents` had carried `embedding_status`, `vector_ref` and provider columns since launch with 231 documents queued and none ever embedded. An embedding worker now drains that queue on every cron tick, using the same Jina model Memory uses, into a platform-scoped `commons_index_vectors` table in the shared Postgres. Nothing about it touches a personal Memory vault: the corpus is public and account-independent.
+- `commons_search_entities` gained `mode`: `hybrid` (default) fuses semantic candidates with exact term matching and ranks title-first, `lexical` matches terms only, `semantic` ignores term matching. Semantic candidates enter the result set rather than only re-ranking lexical hits, so a query with no shared vocabulary still finds the right entity — "tools that let an AI assistant browse the web" returns Web scraping, Model Context Protocol and AI agent, where lexical returns nothing.
+- `POST /commons/index/embed` and `GET /commons/index/status` for operating the index directly.
+
+## [0.59.0] - 2026-08-17
+
+### Added
+
+- Every published editorial article now has its own URL. `GET /commons/publications/{subdomain}/articles/{articleSlug}/site` server-renders a standalone article page with its own canonical, Open Graph tags, and `Article` JSON-LD that declares the edition as its `CollectionPage`. An edition-scoped form is available at `/editions/{editionSlug}/articles/{articleSlug}/site`.
+
+### Changed
+
+- The reading-room app reads and writes real article paths instead of an `?article=` query parameter, so an article is shareable, crawlable, and independently canonical. Legacy `?article=` links still resolve.
+
+## [0.58.0] - 2026-08-17
+
+### Added
+
+- `commons_update_editorial_article` replaces the Markdown of one article in a published edition without resupplying the others. Every edition already stored each article's source; the edit reads them, swaps the named article, re-renders, and publishes the next revision with the rest byte-identical. Guarded by `baseRevision` and `idempotencyKey`.
+- `commons_get_publication` accepts `includeArticles` to return stored article sources and slugs. Owner-only and off by default: reading a publication by name never returns sources, and the payload is large.
+
+### Fixed
+
+- Published editions never returned their article sources. `articles_json` was written on every publish and omitted from the edition mapper, so no API response carried it — which made a single-article edit look impossible and forced a full 100-article resubmission to change one paragraph.
+
 ## [0.57.3] - 2026-08-16
 
 ### Fixed

package/README.md

@@ -90,7 +90,7 @@ Build the branded one-click bundle:
 npm run build:mcpb
 ```
 
-The generated bundle is written to `build/mcpb/mcp-scraper-<version>.mcpb` and copied to `public/downloads/` for the hosted download. The current public bundle is `https://mcpscraper.dev/downloads/mcp-scraper.mcpb` (`0.57.3`, SHA-256 `b1edddd21790e7e5f24bacad85d992d8e995199c5d7e1d314500ba0abaab117c`). Install it by opening or dragging it into Claude Desktop. Claude displays the `MCP Scraper` install card, icon, and API-key configuration field from the bundle manifest.
+The generated bundle is written to `build/mcpb/mcp-scraper-<version>.mcpb` and copied to `public/downloads/` for the hosted download. The current public bundle is `https://mcpscraper.dev/downloads/mcp-scraper.mcpb` (`0.60.0`, SHA-256 `a364401f8bc5928735af71bcc254df5b9e64d164e57bfbe103942f5332225f21`). Install it by opening or dragging it into Claude Desktop. Claude displays the `MCP Scraper` install card, icon, and API-key configuration field from the bundle manifest.
 
 The MCPB install exposes every tool — web-intelligence plus all `browser_*` tools — through the one `mcp-scraper` server.
 
@@ -248,7 +248,7 @@ The `mcp-scraper` server (and the MCPB bundle, which runs it) exposes both secti
 
 All MCP tools expose output schemas and return `structuredContent` with the IDs, URLs, CSV paths, transcripts, browser session handles, replay paths, artifacts, recipe fields, or blueprint fields needed by the next step. Browser Agent tools keep a JSON text block for older clients, but structured data is the primary contract. All tools carry MCP annotations; file-writing tools such as replay downloads and annotations state their filesystem side effects.
 
-The canonical tool inventory is generated at `docs/mcp-tool-manifest.generated.json`. The unified server exposes 251 tools: 150 scraper, browser, workflow, billing, and connected-service tools plus 101 durable-memory tools. The scraper-side inventory includes governed Local Sourcebook tools, Transparent Commons entity, linkset, and publication tools, the searchable News Publisher and Editorial Reading Room template workflow, and 24 X-Ray tools for pixel administration, reporting, attribution journeys, campaign links, exports, and scheduled reports. Successful evidence-compiled Local Sourcebook revisions publish automatically to their canonical `localsourcebook.com` category profile and review URLs; administrator controls handle exceptional rejection or unpublishing. Release verification compares the exact local and hosted tool-name sets, not only the count.
+The canonical tool inventory is generated at `docs/mcp-tool-manifest.generated.json`. The unified server exposes 252 tools: 151 scraper, browser, workflow, billing, and connected-service tools plus 101 durable-memory tools. The scraper-side inventory includes governed Local Sourcebook tools, Transparent Commons entity, linkset, and publication tools, the searchable News Publisher and Editorial Reading Room template workflow, and 24 X-Ray tools for pixel administration, reporting, attribution journeys, campaign links, exports, and scheduled reports. Successful evidence-compiled Local Sourcebook revisions publish automatically to their canonical `localsourcebook.com` category profile and review URLs; administrator controls handle exceptional rejection or unpublishing. Release verification compares the exact local and hosted tool-name sets, not only the count.
 
 For contract parity, stdio and MCPB memory calls invoke the matching public tool on the hosted MCP Scraper `/mcp` endpoint. The hosted aggregate runtime owns MCP Scraper-specific billing, scheduling, credential, and in-process cutover policy; its internal `/memory/mcp-call` bridge is a fallback to the standalone memory service, not the public stdio execution path. Direct `mcp-memory` OAuth and stdio clients continue to use `memory.mcpscraper.dev` and must be verified as a separate dependent release surface.