[gajewsky]

What does this PR do?

Adds Otodom as a provider for house-sale searches in Poland, for example:

https://www.otodom.pl/pl/wyniki/sprzedaz/dom/malopolskie/krakow/krakow/krakow?ownerTypeSingleSelect=ALL

It reads the search page's embedded __NEXT_DATA__ over plain HTTP (no browser), keeps the user's filters, sorts newest first and reads up to five pages per run. Prices come through in PLN using the currency support from #500, and addresses are geocoded within Poland.

Deliberately left out for now:

• Only /pl/wyniki/sprzedaz/dom/... searches. Rentals and flats are refused until they have fixtures and tests.
• No detail enrichment, add-by-URL, activity checks or price tracking. Adverts are keyed on their Otodom id, so a price change doesn't announce them again.
• Development groups without a single asking price are skipped, as are the rare adverts priced in EUR or USD.
• Otodom sits behind CloudFront. Plain Node requests worked in testing, but if a request gets blocked the job fails instead of reporting an empty search.

Screenshots

A live run against otodom.pl found 166 houses in Kraków, all priced in PLN, and 108 of them showed up on the map. Running it a second time sent no repeat notifications.

Related issue

None. Builds on #500, which is merged.

AI disclosure (required)

• ai:none
• ai:assisted
• ai:generated - AI produced most of this PR. I reviewed every line and tested the feature in the browser.

Which AI: Pi with gpt-6.1-sol for the implementationm Opus 5.5 for review fixes.

How much: Most of the code, tests, fixture-download wiring, docs and this description. The fixtures are recorded Otodom pages, trimmed for offline tests.

Why: To add a Polish portal that follows Fredy's existing provider conventions, tested against real payloads.

Checklist

• yarn test:offline passes (5,243 tests), and so does the live Otodom suite
• yarn lint and yarn format:check pass
• Works for any Polish house-sale search, not one hardcoded city
• AI disclosure answered honestly