PASS_APIFY_LOCAL_SCRAPER_CURRENT_RUNTIME_BOARD

Local-scraper MCP current runtime board

Current proof that the Apify cloud replacement MCP remains schema-stable under heartbeat use.

Runtime gates

GateResult
npm run buildPASS
npm testPASS
npm run check:no-apifyPASS
mcporter stdio listingPASS

Critical tool/schema guard

local_maps_rank_snapshot_fixture_parser is present; no Invalid schema / missing properties errors in the current log.

Evidence

Artifact: /home/openclaw/.openclaw/workspace/projects/apify-mcp-integration/artifacts/local-scraper-mcp-heartbeat-runtime-recheck-clean-20260519T062638-0400.md

Log: /home/openclaw/.openclaw/workspace/projects/apify-mcp-integration/artifacts/local-scraper-mcp-heartbeat-runtime-recheck-clean-20260519T062638-0400.log

Boundary

No Apify cloud/API/OAuth/token/Actor call, no external write, no live scrape, no Gateway restart, no production mutation.