GET /v1/product.json endpoint's public accessibility

Floorplan's `unprotected-endpoint` detection highlights a common challenge in modern API design: distinguishing intentionally public, static data endpoints from genuine security vulnerabilities. Developers are explicitly designing public interfaces for AI consumption and developer tooling, leveraging `robots.txt` and `llms.txt` for discoverability. The pain point is the tool's inability to discern intended public access from actual exposure of sensitive data, leading to false positives. This indicates a market need for security analysis tools that understand explicit public API declarations and context, rather than flagging all unauthenticated endpoints. Such tools must integrate with documentation and configuration to reduce noise and improve developer trust.