Phase H.6 Cross-Format Adversarial Closure

Issue #193 in-scope JSON/YAML/TOML closure campaign

Generated: 2026-08-03

Source: adversarial-fuzzing/v1

PASS

Summary

Four bounded workers exercised 36 cases across Rust, CLI, and Python surfaces. All expected relations held; malformed and unsupported inputs matched their documented intentional boundaries.

Fuzz run descriptionIterationsPassResult
Cross-format scalar values, empty structure, and include filtering 6 6/6 PASS
CLI extraction diagnostics for malformed and unsupported format inputs 11 11/11 PASS
Python binding parity for JSON, YAML, TOML reports and diagnostics 15 15/15 PASS
Repeated variable ambiguity and TOML size/depth/occurrence hardening 4 4/4 PASS

Adversarial fuzz worker

shape-probe

Session h6-20260803-0001 · Worker shape-probe

PASS

Fuzz run descriptionIterationsPassResult
Cross-format scalar values, empty structure, and include filtering 6 6/6 PASS

Inputs exercised

CaseTemplate / inputOutcome
json-successJSON object name placeholder with static booleanPASS: name=Ada
yaml-filterYAML mapping with one included and one excluded variablePASS: only kept=yes was returned
toml-successTOML table scalar placeholder with static booleanPASS: name=example

Adversarial fuzz worker

boundary-probe

Session h6-20260803-0001 · Worker boundary-probe

PASS

Fuzz run descriptionIterationsPassResult
CLI extraction diagnostics for malformed and unsupported format inputs 11 11/11 PASS

Inputs exercised

CaseTemplate / inputOutcome
cli-json-successText CLI JSON extraction fixturePASS: format=json and JSON paths emitted
cli-yaml-successText CLI YAML extraction fixturePASS: frontmatter skipped and YAML paths emitted
json-cli-malformedJSON envelope for malformed rendered JSONPASS: ERR_EXTRACT_JSON_MALFORMED
json-cli-unsupportedJSON envelope for unsupported extraction format syntaxPASS: stable format-specific boundary

Adversarial fuzz worker

differential-probe

Session h6-20260803-0001 · Worker differential-probe

PASS

Fuzz run descriptionIterationsPassResult
Python binding parity for JSON, YAML, TOML reports and diagnostics 15 15/15 PASS

Inputs exercised

CaseTemplate / inputOutcome
py-json-realisticPython binding reads the shared JSON ATM fixturePASS: values and object paths match Rust contract
py-yaml-realisticPython binding reads the shared YAML ATM fixturePASS: values and sequence paths match Rust contract
py-toml-limitPython binding rejects an oversized TOML valuePASS: ERR_EXTRACT_INPUT_LIMIT

Adversarial fuzz worker

template-probe

Session h6-20260803-0001 · Worker template-probe

PASS

Fuzz run descriptionIterationsPassResult
Repeated variable ambiguity and TOML size/depth/occurrence hardening 4 4/4 PASS

Inputs exercised

CaseTemplate / inputOutcome
json-ambiguitySame variable at two JSON object pathsPASS: no value fabricated; ambiguity diagnostic retained
yaml-ambiguitySame variable at two YAML mapping pathsPASS: no value fabricated; ambiguity diagnostic retained
toml-occurrence-limit10,001 TOML placeholders exceed occurrence policyPASS: ERR_EXTRACT_INPUT_LIMIT

Recommendations

Metadata

Campaignh6-20260803-0001
Seed193
Baseline4474b67
Workers4
Cases36/36
Confirmed bugs0
Intentional boundaries6
Inconclusive0
Issuehttps://github.com/randlee/sc-compose/issues/193