[jehrr]

This repo was bootstrapped from a Q&A-site sibling and a rental-site sibling. Their names had been scrubbed; their vocabulary and measurements had not.

Fixed

• User-visible help text in the engines (--mode, --category, --pages, --concurrency) and in scraper_api_client.py --url described questions, topics and vote counts. --pages/--concurrency also said no mode has per-page addresses, which contradicts --mode archive and the Playwright worker pool.
• Readiness log line named another site's card kind in all three engines; now "No story cards".
• Scraper API refusal messages claimed the API's exit gets nothing and that a rendered browser is required. The README measured the Scraper API served on all four modes, so the messages now say that and point at --retries / --cdp-url.
• diff_runs.py: docstring, comments, --price-tolerance-pct help and the source_changed output line rewritten for stories and tag/archive/author/post views. text_chars removed from the view fields because it is not a column here. Dropped an unmeasured "1,733 views" claim.
• output_writer.py: mode default was "topic", which is not a mode here. It is now "tag". Every engine passes its mode explicitly.
• CONTRIBUTING.md, bug_report.yml, site_changed.yml described another site's inline payload, card hooks, columns and URLs. They are rewritten from this repo's README and product_parser.py docstring, and every number in them comes from those files.
• requirements*.txt: another repo's name, and its browser measurements, including playwright install chrome. They now carry this repo's own findings (bundled Chromium is fine; pyppeteer's bundled Chrome/117 was refused 3/3).
• .dockerignore: donor output prefix replaced with medium_posts.* / medium_posts_*.*, taken from the engines' --out default.
• Stray wording in TROUBLESHOOTING.md and suite comments. A min_matches check exercised a mode called question; it now uses tag, plus a new post-mode assertion.
• Guard: the suite's foreign-vocabulary check now also scans .txt and .dockerignore, and it knows the Q&A sibling's vocabulary. Controlled: planting the old requirements.txt header, and separately the old Selenium log line, each turned the suite red on that check.

Kept, deliberately

• The sibling guard list in smoke_test.py, which exists on purpose.
• Explicit sibling provenance: foodpanda-scraper in the README and in a suite comment, the craigslist note in .gitignore, and the "a sibling repo …" comments in page_flow.py and the engines.
• Released CHANGELOG sections are untouched.
• fixtures_generated.json, which is real page data.
• README badges were already in family order. "runs without an account" is honest here, because the README measures every mode with no key and no proxy from a datacentre address.

Not changed, noted

• TROUBLESHOOTING.md says there is "nothing to hand 2Captcha" for the managed challenge, while the README and CHANGELOG 0.1.1 say the Turnstile parameters can be intercepted and solved. That is not a donor leftover, so it is out of scope for this PR.

Suite: green before and after (709 → 715 PASS). The three engine groups skip locally because no engine is installed. ci_checks.py --secret-check --help-check --sample-check all pass.

🤖 Generated with Claude Code