Language: English (canonical). Chinese: examples/attack/README.zh.md.

A minimal, illustrative example of the attack preset on a toy artifact.

• sample-claim.md — the artifact under attack: a 5-point argument with three planted flaws (an overgeneralized benchmark, a self-contradicting freshness claim, and a concurrency-blind "production-ready" conclusion).
• expected-out/confirmed.md — the primary deliverable: the three CONFIRMED critiques, each with file:line position, evidence, and a concrete proposed_fix.
• expected-out/tree.md — the same critiques in the docs/ENGINE.md §7.3 node format (root + 3 leaves).

⚠️ The files under expected-out/ are the hand-trimmed output of a real capped run (--width 3 --depth 1 --no-online --no-grill), reduced to the root + CONFIRMED leaves to document the output format. The trimming, not the cap, is why the rest is missing: any real run — capped or not — additionally writes tree.json, marginal.md, refuted.md, a REPORT.md, and a full 12-field derivation per node, because docs/ENGINE.md §F7 requires every visible leaf to be complete even when a cap trips. An uncapped run (/cc-tree:attack ./sample-claim.md) differs by exploring further, so it may surface more critiques than the three shown here. CI bounds-checks every file:line citation in these files against sample-claim.md (tools/validate_plugin.py cross-refs). These fixtures are canonical English snapshots; --lang <tag|auto> may localize a regenerated run's narrative while machine keys, verdict labels, statuses, filenames, and citations remain English.

/cc-tree:attack ./examples/attack/sample-claim.md --out ./attack-out/example/

The output goes to the repo's already-gitignored attack-out/ rather than next to the fixtures: one list of ignored output names is easier to keep true than two. Then compare attack-out/example/confirmed.md against expected-out/confirmed.md: the three planted flaws above should all appear as CONFIRMED, with file:line positions pointing into sample-claim.md.