Public county data and discoverability

County Seats has a public, unauthenticated, read-only data export generated by Eleventy:

Visit status remains exclusively sourced from _data/county_status.json. No public route adds write access or uses the private ChatGPT API key. The authenticated /api/county-query and related APIs remain unchanged.

County detail pages with notes or images may be indexed. Pages with only generic visit metadata set noindex, follow to avoid publishing hundreds of duplicate/thin search results. All generated index URLs are stable, but visits are not proof of a courthouse's current condition.

When updating county notes or images in Netlify Blobs, the dynamically served public county page will reflect those changes without a new Eleventy build. The county list and sitemap still update when the site's normal build runs after status changes. The public export should never include admin tokens, private draft content, or exact personal travel plans.

Test after deploy: request /data/counties.json, verify expected 3,142 records and 291 visits, request a visited county page, inspect image links, and verify unknown/unvisited county paths return 404.