probe-big-scan-test

Temporary diagnostic probe used to verify whether the ClawHub security scan pipeline accepts large minified JSON payloads from this account. This skill exists only to measure scan behavior and is deleted after the measurement.

Purpose

This bundle is a controlled diagnostic artifact. It contains one large minified JSON file with thousands of product-shaped records, mirroring the data files that our real skills ship. The goal is to observe how the automated security scan pipeline treats a large payload from this publisher account, so that we can distinguish between a payload-shape problem and a platform-wide pipeline outage affecting all uploads from this account.

Method

1. The publisher uploads this folder as version 1.0.0.
2. The registry records the release as pending and starts the security scan.
3. We then query the scan status endpoint repeatedly and record which engines complete, which fail, and what error message accompanies a failure.
4. A second, structurally similar bundle carries a small reference file instead of this large one, so the two runs differ in exactly one dimension.

What We Record

• The scan identifier returned when the scan is submitted.
• The status of each individual security engine in the scan report.
• The verbatim lastError string when the overall scan status becomes failed.
• Whether a scan that previously failed can be re-submitted and later succeed.

Interpretation

If the small bundle scans cleanly and the large bundle fails with a scanner internal error, the failure is caused by artifact size or shape rather than by the publisher account. If both bundles fail identically, the pipeline itself is unhealthy for this account and no content change on our side can make the release public.

Cleanup

This probe is temporary. Once the measurement is complete the folder is removed from disk and any reserved version number is abandoned deliberately, so that no permanent test artifact remains in the published catalog.