From 12a27e733ba597eb28ab7db86036ea703cc248c7 Mon Sep 17 00:00:00 2001 From: jedarden Date: Mon, 6 Jul 2026 12:49:51 -0400 Subject: [PATCH] docs(bf-qf5mh): document cargo fuzz build command correction --- notes/bf-qf5mh.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 notes/bf-qf5mh.md diff --git a/notes/bf-qf5mh.md b/notes/bf-qf5mh.md new file mode 100644 index 0000000..908c387 --- /dev/null +++ b/notes/bf-qf5mh.md @@ -0,0 +1,31 @@ +# Fix for bf-qf5mh: cargo fuzz build command correction + +## Problem +Parent bead bf-4o8a6 had incorrect cargo fuzz build syntax that caused repeated failures: +- Incorrect: `cargo fuzz build --harness profile_yaml` +- Correct: `cargo fuzz build profile_yaml` + +## Root cause +cargo-fuzz does not have a `--harness` flag. The target name is passed as a positional argument, not as a flag. + +## Verification +```bash +$ cargo fuzz build --help +cargo-fuzz-build 0.13.1 +Build fuzz targets + +USAGE: + cargo-fuzz build [OPTIONS] [TARGET] + +Arguments: + [TARGET] + Name of the fuzz target to build, or build all targets if not supplied +``` + +## Changes made +Updated bf-4o8a6 description to use correct syntax in both Implementation guidance and Acceptance criteria sections. + +## Acceptance criteria status +- PASS: Documented correct cargo fuzz build syntax (see note) +- PASS: Parent bead acceptance criteria updated to use `cargo fuzz build profile_yaml` +- PASS: No reference to --harness flag remains in parent bead