chore(fuzz): remove dead duplicate OpenCode fuzz target on current main

[seonghobae]

Root cause

Fresh protected-main inspection at main@45345b20dafeb247a01d7e2021968430483fcc94 confirms fuzz/fuzz_opencode_normalize_output.py is a dead duplicate of the live fuzz/fuzz_opencode_review_normalize_output.py target.

The live wiring is current and unambiguous:

• .clusterfuzzlite/Dockerfile names fuzz/fuzz_opencode_review_normalize_output.py as the runnable Atheris target;
• scripts/ci/strix_quick_gate.sh now recognizes the same live filename when materializing normalizer support;
• the duplicate file has no workflow/product/fuzz-discovery caller;
• the duplicate still invokes removed NORMALIZER.extract_json_object(text), so it would fail with AttributeError if someone accidentally executed it.

A few removed-file-context tests contain the old filename as synthetic historical fixture data; those are not callers and remain intact.

Current-main repair

Delete exactly fuzz/fuzz_opencode_normalize_output.py. No production implementation, fuzz discovery configuration, reviewer route, credential, security threshold, branch protection, or merge authority changes.

Exact head: 17abc25b3a634d6fee571ef08077ef2dacf45f47.

Stale predecessor #1486 established the same deletion design with a complete suite, 100% coverage, and 100% docstrings, but none of its checks/reviews transfer to this head. Fresh current-head evidence is authoritative.

---

[seonghobae]

QUEUE_SATURATION_CHICKEN_EGG on exact head 17abc25b3a634d6fee571ef08077ef2dacf45f47: fresh protected-main audit proves the one deleted file is a dead duplicate with no live caller, while the live ClusterFuzzLite/Strix path uses fuzz/fuzz_opencode_review_normalize_output.py. The dead file still calls removed NORMALIZER.extract_json_object(). This PR is mechanically mergeable, has zero review submissions/threads, and changes exactly one dead file. All eight current-head hosted workflow runs are queued while the repository now has 788 queued Actions runs. Predecessor #1486's complete-suite/100%-coverage/100%-docstring run is design verification only and is not promoted as current-head check evidence. There is no substantive source/security/review/provenance blocker. Proceeding with expected-head guarded squash merge solely under the verified queue-saturation exception.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.