- 已装运
- 2026年8月25日 17:40 UTC
- 作者
- Kamo
- 提交
- ade4740
It was required, and requiring it was wrong. A site is a hint for whoever picks the report up — a member who is not certain which of five surfaces they were looking at is better off saying nothing than guessing, because a wrong site sends the work somewhere it does not belong while no site sends it nowhere in particular, which is where it already was. An unrecognised name is still refused. That is a different rule: "I did not answer" comes from a member, "MARKETNIG" comes from a client this server does not agree with, and swallowing it would file a report whose site silently vanished. parseSites and parseSite are static now so the boundary can be exercised without a Spring context, matching visibilityScope and likePattern above them.