From 6050d80f6311f7498d4425f4b0d0bc8772ad2902 Mon Sep 17 00:00:00 2001 From: Chris Troutner Date: Wed, 16 Sep 2026 21:35:09 -0700 Subject: [PATCH] Note gherkin-mutator empty-manifest behavior for intrinsic survivors By architect. --- docs/architect-process-notes.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/architect-process-notes.md b/docs/architect-process-notes.md index 2747ebc..2ea4205 100644 --- a/docs/architect-process-notes.md +++ b/docs/architect-process-notes.md @@ -113,6 +113,15 @@ the captured output before the tool's `System/exit`; the JSON report (`--json`) did. Redirect stdout to a file and use `--json` for a reliable, parseable record of killed/survived mutations. +- **`gherkin-mutator` writes an empty `scenarios` manifest when every scenario + has an intrinsic survivor.** `new-manifest` records only scenarios with + `Survived = 0` and `Errors = 0`. When all mutations are single-character case + changes of example values used consistently on both the setup and assertion + sides, every scenario survives and the committed manifest is + `"scenarios":[]` with no `# mutation-stamp`. This is the tool's expected + output (those scenarios are intentionally re-mutated next run), not a partial + write; commit it as-is and document the equivalents in the review summary. + - **`gherkin-mutator` can run from `tmp/aps` with absolute component paths.** The Babashka task must run where `bb.edn` defines it (`tmp/aps`), but the runner worker resolves the job's `feature_json`/`work_dir`/`generated_dir`