fix: exclude room-less Property from every price bound

[kernvex]

Closes #10.

The bug

filterHotels (src/domain/search.ts) guarded only the max_price side of the band. A room-less Property has price_from = Infinity, and Infinity < minPrice is false, so such a Property passed a min_price floor — e.g. GET /hotels?min_price=1000 would surface a Property whose price_from is null.

Root cause

Confirmed with a red test first: the asymmetric guard. Infinity > maxPrice already excluded room-less Properties from the ceiling, but nothing excluded them from the floor.

Fix

A Property with no bookable rate has no price and should satisfy neither bound. Guard the non-finite price_from up front so it fails both sides symmetrically.

Documentation

• ADR-0003 (consequences) and ASSUMPTIONS.md now record the room-less ruling.

Verification

• Red → green: extended the room-less case in test/search.test.ts to cover the min_price floor and a full band (the existing max_price ceiling assertion stays).
• npm run verify (typecheck → lint → test): clean, 54/54 pass.

Impact

Defensive-path only — the seed has 0 room-less Properties (40/40 have Rooms), so there is no observable change today.

🤖 Generated with Claude Code

[kernvex]

Post-mortem — what would have caught this earlier

The original GET /hotels work (PR #9) added a room-less test that asserted only the max_price side (filterHotels([roomless], { maxPrice: 1000 }) === []). Because Infinity > maxPrice is true, that path happened to be correct — which masked the asymmetric guard. A symmetric test that also exercised the min_price floor for the same room-less fixture would have gone red at the time and caught this on PR #9.

The regression test in this PR closes that gap: the room-less case now covers the floor, the ceiling, and a full band together, so the two sides can't drift apart again. No architectural change needed — the seam was fine; the test coverage was one-sided.