[data] Structured amenity fields for beer-garden / dog-friendly facets

[iamjohnnymac]

Carved out of #32, which shipped every other high-intent landing page but deliberately did not build /[suburb]/beer-garden or /[suburb]/dog-friendly.

Why this was not built

The 3 June 2026 audit recorded on #32 checked the live pubs data behind the typed app model:

• dog-friendly: no structured field, 0 description matches for "dog"
• beer garden: no structured field, 2 description matches site-wide, 0 suburbs with >=3 matches
• for contrast, the amenity fields that do exist: cozy_pub 39, sunset_spot 24, kid_friendly 11, has_tab 56

#32's own rule is to publish a facet only where a suburb has at least 3 matching venues. Neither facet qualifies. Publishing them off description-text guessing would mean asserting amenities we cannot verify.

Confirmed 15 Aug 2026 on production: /perth-cbd/beer-garden, /fremantle/beer-garden and /fremantle/dog-friendly all return 404. That is the correct state until the data supports the claim.

Action

1. Add structured amenity fields, or a verified amenities table, covering at least beer garden and dog-friendly, with a source recorded per claim.
2. Backfill from a checkable source (venue site, menu, listing), not description keyword matching.
3. Generate /[suburb]/<facet> pages only for suburbs with >=3 verified matches.

Done when

• Amenity data is structured and sourced.
• Facet pages exist only where the >=3 threshold is met, or this issue is closed with a note that the data still does not support them.