GET /v1/llms.txt endpoint's public accessibility

This `unprotected-endpoint` false positive for `GET /v1/llms.txt` further solidifies the trend of developers intentionally exposing public, static content for AI and developer discovery. The explicit use of `Access-Control-Allow-Origin: *`, `Cache-Control: public`, and clear documentation on a `/developers` page demonstrates a deliberate architectural choice, not a vulnerability. The presence of a rate limit indicates a mature approach to public endpoint management. The pain point is the security tool's inability to interpret these explicit public declarations and contextual cues, leading to repetitive false positives. Market demand exists for security analysis tools that can parse and understand developer intent, configuration, and documentation to accurately assess risk, rather than generating noise from intended public interfaces.