henitai 0.5.1 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 321426b14e3d03dae68885665b6abee8e11ea48d7a00036664dd0b6a10af2659
-  data.tar.gz: 262e708c7393a11e57f8fe25b9588b8b6aa04c026bebef1dec0aa77fedd782ba
+  metadata.gz: 4c9ef6e2d806e8d12acfd36adda062192c5cf4ba700ee140ce7d6ad848eff0c8
+  data.tar.gz: 800ba49ba72ce0ab6090e1ab9b40ea5146559738e59af5a81ceeb80923bc974e
 SHA512:
-  metadata.gz: 4ef8ed1d823903bceca334c81a895a1734745480e0966ab55e100ea95b8479201824ebbd048ea86f0465c0a98fd39dd561a62876614e20bed7b1f64460d10e20
-  data.tar.gz: b152279d4854b7aeb55afb5696a77054184947f0ea16570dd9e3f90a62388295b6f4f6499f101d323a8fa0071c9d83d8847e3348c878061c980587ab6ddfd53f
+  metadata.gz: 60acc4fc6df82c4d273c110302af6a73b7c4f7d6f3ebb2ae9fdcea06ca69e5cef2e61945c396b38810f978b8ace3db2b988d224b637d0f8f11c02ccb03eee368
+  data.tar.gz: 9fe40adf6368041348247af329f3153a0027e89bbbe60e9dcdef27a4a666512446ab7569188e891ec7eb2f5fe8419c33eeee2ed1778a5b034c97901ca94a095c

data/CHANGELOG.md

@@ -7,9 +7,262 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.6.0] - 2026-10-20
+
+Minor release with a deliberate score break: false kills and harness
+failures no longer count as detected mutants, so most projects, including
+Henitai's own dogfood run, will report lower Mutation Scores. Re-measure
+before adjusting thresholds.
+
+### Changed
+
+- **Scores will drop, by design.** A mutant now counts as detected only when a
+  test failed because of its mutation (ADR-14). Harness failures that used to
+  be credited as kills are now reported as `CompileError` or `RuntimeError`,
+  with the reason in `statusReason`. On an assertion-free test suite, 0.5.3
+  reported 130 of 137 mutants as killed; this release reports none. Projects
+  should expect lower Mutation Scores. Re-measure before adjusting thresholds.
+- **Flaky-test handling.** Survivors are no longer retried: a retry could only
+  turn a survivor into a kill and inflate the score. Kills are re-checked, up
+  to `max_flaky_retries`, only when every failing test file is known to be
+  flaky, as found by the new opt-in `mutation.flaky_detection` (baseline suite
+  runs twice; flaky files go to `henitai_flaky_tests.json`, removed by
+  `henitai clean`). Without it nothing is retried, so runtime on survivor-heavy
+  suites drops. The ">5% of mutants needed a retry" warning is replaced by a
+  report of flaky tests and re-checked kills. Child reports now carry
+  `failed_tests`. Failures outside an example (an `after(:context)` hook error,
+  a suite-level hook, a Minitest result without a file) are attributed to their
+  spec file when RSpec names it; otherwise the run is flagged
+  `unattributed_failures`, which makes a kill genuine (never retried) and makes
+  the flaky baseline reject the run. Baseline runs that fail on a file the two
+  runs cannot call flaky (for example one seen in a single run) now abort
+  instead of being accepted. Minitest outcomes are keyed to the file defining
+  the test class, not to a shared module that supplies the test method.
+- Mutant runs are classified from an explicit report written by the child
+  process instead of from its exit status. An exception while activating the
+  mutant (for example a `NameError` from a superclass defined in another file)
+  is `CompileError`, not `Killed`. A child killed by a signal, or one that
+  exits without reporting, is `RuntimeError`, not `Killed`. A `SystemExit`
+  raised by the code under test is `RuntimeError`, not `Survived`.
+- Mutants are activated only after the spec or test files have loaded, so a
+  subject whose superclass or constants live in other files can be tested.
+  Previously the child loaded the subject file on its own and failed with a
+  `NameError` (every `ApplicationRecord` model, for example).
+- Mutants are activated by re-evaluating the subject's own `def` inside its
+  original module and class openers (ADR-13), not through `define_method`.
+  Constant lookup through enclosing modules, implicit `super`, `yield`,
+  `block_given?`, argument forwarding, default values, `__FILE__`/`__LINE__`,
+  `frozen_string_literal` and visibility now behave as in the original method.
+  Mutations in default values take effect, and splices no longer shift after
+  multibyte characters or leave heredoc bodies behind. Activation recipes from
+  earlier versions are ignored and regenerated.
+
+### Added
+
+- `mutation.sampling.seed` (integer >= 0, default `0`) and real stratified
+  sampling: per subject `max(1, ceil(size * ratio))` mutants, strata by
+  operator ordered by `SHA256(seed, stable_id)`, visited round-robin, original
+  order kept. The report records `"sampling": {strategy, ratio, seed}`.
+- Report fields: top-level `completeFiles` (non-authoritative runs) and
+  per-file `sessionId` and `gitSha` provenance.
+- `rake oracle:reuse` (run in CI): on a scratch copy of the oracle corpus, the
+  `--incremental` verdicts must equal a fresh full run after scripted edits to
+  source, tests, a helper and the configuration.
+- **Fork server for Minitest and parallel runs.** `mutation.fork_server`
+  (opt-in, ADR-15) now supports Minitest and `jobs > 1`: the environment is
+  booted once and each mutant process is forked from the server. Falls back to
+  per-mutant boot with a warning if the server is unavailable.
+- A fidelity check rejects, before execution, every mutant whose activated
+  code differs from the original method by more than the reported mutation.
+  Examples are a negated condition that lost its parentheses, keyword
+  arguments re-rendered as a positional hash, `|x|` re-rendered as `|x,|`, a
+  splice shifted by a multibyte character, and a removed assignment that turns
+  a later local-variable read into a method call. Such mutants are reported as
+  `CompileError` with the reason.
+- `mutation.control_runs` (default `true`): after execution, every subject
+  with a detected verdict runs once more with its unmutated method injected.
+  If its tests fail, the subject's detected verdicts are reclassified as
+  `CompileError`, because the injection itself broke them.
+- Methods defined in a constructor block assigned to a constant
+  (`Point = Struct.new(:x) do ... end`, likewise `Data.define` and
+  `Class.new`) and in `class << CONST` are now subjects. Top-level
+  `def Const.name` methods are subjects as well.
+- `rake oracle` runs a corpus whose verdicts follow from its construction and
+  fails on false kills or false survivors. CI runs it.
+
+### Fixed
+
+- **Verdict reuse is bound to a reuse context.** `--incremental` reused stale
+  `Killed` verdicts after a spec helper, the configuration or the henitai
+  version changed. Every cached `Killed` and `Survived` verdict now stores a
+  `ReuseContext` fingerprint (test dependency files, henitai version,
+  integration, operators, `test_excludes`, `coverage_criteria`) and is reused
+  only under an identical one; rows recorded without it are never reused.
+  `rake oracle:reuse` reproduced 121 mismatches against fresh runs after a
+  helper edit before the fix and none after it.
+- **`--survivors-from` no longer skips survivors on a git heuristic.** The
+  selected survivors go through the same content-fingerprint reuse rules as
+  `--incremental`, always: new or edited tests and helpers invalidate them,
+  reused survivors are reported with `fromCache`, and recipe stubs without a
+  source range are always re-executed. `SurvivorTestFilter` is removed.
+  The recipe fast path now refreshes coverage (Gate 0) so new or edited tests
+  are selected, recipe stubs also run their name-matched tests, and survivor
+  reruns never sample (sampling had dropped prior survivors before matching).
+  `--force` now also bypasses this reuse. Duplicate programs are collapsed
+  before sampling, so a sampled run keeps the same representative as an
+  unsampled survivor rerun and its survivors are found again.
+- A survived verdict whose covering-test fingerprint cannot be recomputed keeps
+  stored fingerprints only from a survived row of the same subject source,
+  never from a killed row or an edited method.
+- Gate 1 source selection has its own per-test coverage instance, so reuse and
+  history read the post-bootstrap per-test map.
+- Recipe stubs keep their precomputed stable ID and persist the `replacement`
+  source in the history store.
+- **Trend history only records authoritative runs.** `--since`,
+  subject-scoped and survivor-rerun results no longer add a `runs` row.
+- **Canonical report merge.** A scoped run that mutated every subject of a file
+  replaces that file's prior entry wholesale (and removes it when it has no
+  mutants), so stale mutants of edited or deleted code no longer linger.
+  `--survivors-from <canonical report>` redirects to the session snapshot only
+  when every file entry carries the report's `sessionId`; a file whose every
+  prior mutant was re-run takes the new run's provenance.
+- `--since` diffs against the merge base (`REF...HEAD`) instead of the ref's
+  tip, so commits that landed on the base branch after the fork point are not
+  treated as changes.
+- The dashboard reporter uploads the merged canonical report for scoped runs
+  instead of the partial one.
+- `Pending` mutants are excluded from the MS and MSI denominators; MSI is
+  `killed / (total - pending)`.
+- **Equivalence detection only flags sound cases.** `false || x` and
+  `true && x` (left literal only); `n + 0`, `n * 1` and siblings only for
+  Integer/Float literal receivers (not `-0.0`); `==` <-> `eql?` only when both
+  operands are string literals; `==` <-> `equal?` for singleton literals.
+  Unsound rules (`x || false`, `x && true`, unknown receivers, a single string
+  literal) no longer mark mutants `Equivalent`.
+- **`mutation.ignore_patterns` is line-scoped.** A pattern is matched against
+  the source line where the mutant's node starts, in `StaticFilter`; matching
+  mutants are reported as `Ignored` with an `ignore_reason` instead of being
+  dropped at generation time. An enclosing construct whose body matches is no
+  longer suppressed. The line is decoded honouring a magic encoding comment,
+  so a non-UTF-8 source file no longer aborts filtering.
+- **Review follow-ups.** The slot scheduler no longer signals the process
+  group of a reaped pid that owns no mutant slot. Minitest results for tests
+  added by reopening a class in another file are attributed to the file that
+  defines the method, so coverage-first selection no longer misses them. With
+  the fork server active, calibrated timeouts keep the measured suite boot
+  (served mutants still run `before(:suite)` hooks). The `fork_server` schema
+  description and the remediation plan now state the real scope (RSpec and
+  Minitest, any `jobs`).
+- **`--incremental` no longer reuses stale survived verdicts for def-line
+  mutants.** Their test selection is widened with name-matched tests that the
+  survivor fingerprint does not cover, so survived verdicts for mutants on a
+  method's def line always re-execute (killed reuse is unaffected: a kill by
+  an unchanged covering test remains valid).
+- **Output capture no longer delays or races on lingering grandchildren.**
+  Closing a mutant child's captured stdout/stderr no longer waits up to 1 s
+  per stream for EOF and no longer kills the drain thread mid-write (which
+  could exceed the cap or write the truncation marker twice). The drain
+  thread is stopped cooperatively through a stop pipe and takes what is
+  already readable.
+- **Fork-server lifecycle.** A server lost or stalled mid-run no longer turns
+  its in-flight mutants into `runtime_error`: they are rerun through the
+  per-mutant-boot fallback. Fallback runs use boot-inclusive timeouts. Mutant
+  processes forked by the server are cleaned up on timeout, loss and teardown
+  even before they lead a process group, and the connection and wake-pipe fds
+  are no longer inherited by mutant processes. The parallel event loop no
+  longer stalls on an exit event already buffered in the client, and the
+  SIGTERM drain window always runs its full length.
+- The "negated condition" mutant now negates the whole condition
+  (`!(a > b)`), not just its left operand (`!a > b`).
+- Source files are read as UTF-8 regardless of the process locale. With `LANG`
+  unset or `C`, any non-ASCII source file used to abort subject resolution.
+- Per-test coverage now narrows RSpec test selection. RSpec records test files
+  as `./spec/x_spec.rb` while candidates arrive as `spec/x_spec.rb`, so the
+  lookup never matched and every mutant ran all candidate files.
+- `--since` and the dirty-source and survivor checks now work for a project in
+  a sub-directory of its git repository and for non-ASCII file names.
+- A corrupt or locked `mutation-history.sqlite3` no longer discards the run's
+  reports. History recording and export now warn instead.
+- Forked mutant children reset the INT, TERM, HUP and CHLD handlers inherited
+  from the parent, so a draining SIGTERM is no longer ignored.
+- A zero-example check no longer matches `10 examples, 0 failures`, nor a
+  `No examples found.` or `0 examples, 0 failures` quoted in failure output;
+  only the run's last summary line counts. Such kills were reported as
+  `CompileError`.
+- A run in which harness errors (`CompileError`) left no mutant to score now
+  exits `1` with a warning instead of passing its threshold with nothing
+  tested.
+- Mutating an `elsif` condition no longer rewrites the whole `if` chain; only
+  the condition changes.
+- String parts of interpolated strings, symbols, backticks and regexps, and
+  elements of `%w` arrays, are no longer mutated as standalone strings. Their
+  replacement text changed the literal's syntax rather than its value.
+- Operator replacements are parenthesised when spliced, so `a && b && c`
+  mutated to `a || b` no longer reads as `a || (b && c)`.
+- Two mutants at the same position with the same description no longer share
+  one stable identity and history entry.
+- `ReturnValue` mutates only the method's final expression, not every
+  expression that happens to equal it.
+- Subject expressions for predicate, bang, setter and operator methods, such
+  as `Foo#empty?`, `Foo#save!`, `Foo#name=` and `Foo#==`, select their method
+  instead of nothing.
+- Mutants from different operators that produce the same program run once.
+- The implicit value of a shorthand hash pair (`build(config:)`) is no longer
+  mutated. Its replacement rewrote the key to `build(nil:)`.
+- A mutant that removes the only assignment of a local variable read later in
+  the method is no longer generated. Ruby parses the later read as a method
+  call, so every such mutant failed with a `NameError` wherever it ran.
+- Subjects are attributed to the right namespace. A `class ::Top` inside
+  `module Outer` is `Top`, not `Outer::Top`. A `def Other.name` inside `Outer`
+  belongs to `Other`, not `Outer`. Methods of `class << obj` or `def obj.name`
+  for a non-constant `obj` are no longer reported as class methods of the
+  enclosing class.
+- "replaced method call with nil" on a call with a block replaces the call
+  together with its block. Replacing only the call left `nil { ... }`, which
+  does not parse, so these sites were never tested. Blocks attached to
+  logger, output and debug calls stay arid.
+- `RegexMutator` no longer drops the interpolations and later lines of a
+  dynamic or multi-line regexp, which it now leaves unmutated. It skips
+  escaped characters and the contents of character classes, so `[^0-9]` is
+  no longer reported as a removed `^` anchor and `[+-]` no longer as a
+  quantifier swap.
+
+## [0.5.3] - 2026-08-26
+
+### Fixed
+
+- A timed-out Minitest baseline suite is now actually killed. Its child was
+  spawned without `pgroup: true`, so the parent's group-wide `SIGTERM` named a
+  process group that never existed, raised `ESRCH`, and left the suite running;
+  the parent then blocked in `Process.wait` until the suite finished on its own
+  — minutes past the timeout it had already reported, and long after the log
+  tail quoted in the error had stopped describing reality. The suite child now
+  leads its own group, as the RSpec baseline child already did, and post-run
+  cleanup signals that group instead of the single pid, so a Rails test server
+  or browser driver started by the suite is torn down with it.
+
+## [0.5.2] - 2026-08-26
+
+### Changed
+
+- `test_excludes` now also applies to the coverage-bootstrap suite, not only to
+  per-mutant test selection. Slow end-to-end or integration suites could be kept
+  away from mutant children but still had to run in full during the baseline,
+  where the fixed suite timeout aborts the run with
+  `Henitai::CoverageError: Configured test suite failed while generating
+  coverage` even though the suite itself was green. Excluded files are also
+  dropped from the coverage freshness watch list, so a test that no longer
+  contributes to the baseline no longer invalidates it. Lines covered only by
+  excluded tests now count as uncovered and are not mutated — matching what
+  already happened at execution time, where such mutants could never be killed.
+  A `test_excludes` set that leaves no test file now aborts with
+  `Henitai::ConfigurationError` instead of running an empty suite and then
+  reporting missing coverage.
+
 ## [0.5.1] - 2026-08-25
 
 ### Changed
+
 - `minitest` runtime dependency widened from `~> 5.25` to `>= 5.25, < 7`.
   The floor is unchanged; only the ceiling moved. `~> 5.25` capped the
   range below 6.0, so bundles resolving minitest 6.x could not install
@@ -20,6 +273,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.5.0] - 2026-08-21
 
 ### Security
+
 - `sqlite3` requirement raised from `~> 1.7` to `>= 2.9.5, < 3`, excluding the
   vulnerable releases up to and including 2.9.4. This is a runtime major bump:
   applications pinned to `sqlite3` 1.x will need to upgrade before installing
@@ -28,6 +282,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   floors so a regression fails the suite rather than shipping quietly
 
 ### Changed
+
 - `coverage_criteria` now actually affects scoring. The block was documented,
   defaulted and validated since it was introduced, but nothing ever read it —
   `Result` hardcoded the `MS` numerator as `killed + timeout + runtime_error`,
@@ -50,6 +305,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   4.0-only form), and CI runs the floor alongside 4.0.2
 
 ### Fixed
+
 - Forked mutant children no longer outlive a parent that dies without warning.
   Children run in their own process group, and all parent-side cleanup —
   timeout kills, graceful drain, signal traps — only runs while the parent's
@@ -84,6 +340,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   0.3.1; this restores it
 
 ### Internal
+
 - Test-suite coupling to private implementation details is now guarded by
   `spec/infra/private_method_reach_spec.rb`, a ratchet: every spec that reaches
   a private method through `send` or an instance-variable poke carries a
@@ -104,6 +361,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.4.0] - 2026-07-14
 
 ### Added
+
 - `hard` operator set (`mutation.operators: hard` / `--operators hard`), a
   strict superset of `full` for usually-unkillable mutations (ADR-12):
   currently `EqualityIdentityOperator` and the new `HashKeyType`
@@ -113,6 +371,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   single-pair hashes and double-splat entries are skipped
 
 ### Changed
+
 - `full` now means "usually killable": the symbol-key -> string-key mutation
   moved from `HashLiteral` into the new hard-set `HashKeyType`, and
   `EqualityIdentityOperator` moved from `full` to `hard` — `full` runs emit
@@ -121,6 +380,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.3.1] - 2026-07-13
 
 ### Fixed
+
 - Per-mutant log capture no longer crashes with
   `Encoding::UndefinedConversionError` when the host app sets
   `Encoding.default_internal` (as Rails test environments do) and a child
@@ -130,6 +390,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   from corrupting the file.
 
 ### Changed
+
 - `--since REF` now includes the working tree: tracked files with
   uncommitted changes and untracked files count as changed, matching what
   actually gets tested. Previously only committed changes in `REF..HEAD`
@@ -146,6 +407,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.3.0] - 2026-07-13
 
 ### Added
+
 - `henitai run --incremental`: verdict reuse from the history store. Killed
   verdicts are reused when the subject's source and every covering test file
   are byte-identical to what was recorded; Survived verdicts are additionally
@@ -181,6 +443,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   moved out of the default light set into its own operator (ADR-10)
 
 ### Fixed
+
 - Mutants in `module_function` modules were unkillable: `module_function`
   copies the method onto the module's singleton and activation only replaced
   the instance side, so callers kept running original code and every such
@@ -200,6 +463,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Flaky-retry counter no longer inflates when a respawned child fails again
 
 ### Changed
+
 - Terminal reporter renders original nodes from their source slice and reuses
   a memoized unparse of the mutated node shared with the JSON reporter
   (a dogfood profile spent 27% of wall time re-unparsing survivors)
@@ -213,6 +477,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   redefinition warnings into their logs
 
 ### Internal
+
 - Architecture documentation gained §8.11 (incremental verdict reuse) and
   ADR-11 (content-fingerprint verdict reuse, not git scoping); new backlog
   tickets for CI warm verdict cache, child null formatter, and auto-`--since`
@@ -224,12 +489,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.2.1] - 2026-06-25
 
 ### Fixed
+
 - `henitai run` now exits 0 when a run evaluates no valid mutants, instead of
   failing a CI gate on a vacuous result
 - Flaky-retry counts are now recorded on the parallel execution path (they were
   always reported as 0 regardless of actual retries)
 
 ### Changed
+
 - `Result` and `Reporter::Json` take their IO as an injected dependency,
   restoring the domain/infrastructure boundary (no public API change)
 - Decomposed the monolithic `integration.rb` into single-responsibility files
@@ -238,6 +505,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Narrowed broad rescues in `safe_unparse` and per-test coverage snapshotting
 
 ### Internal
+
 - De-mocked runner specs, added `process_wakeup` and helper coverage, and
   removed sleep- and chdir-based flakiness from the suite
 - Enabled full-operator dogfooding configuration and isolated the
@@ -247,6 +515,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.2.0] - 2026-04-30
 
 ### Added
+
 - `--survivors-from <path>` flag on `henitai run` for survivor-only reruns:
   re-execute only the mutants that survived a prior full run without re-running
   the whole suite
@@ -281,6 +550,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - x86_64 platform added to gem platform list
 
 ### Changed
+
 - JSON mutation report vendor extension now always includes `sessionId`
   (and `gitSha` when available) to support survivor-only reruns
 - Terminal reporter labels partial reruns as "Partial survivor rerun" and
@@ -295,6 +565,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `max_flaky_retries: 3` added
 
 ### Fixed
+
 - Minitest autorun hook suppressed in mutation child processes to prevent
   spurious re-runs of the full suite inside each fork
 - Coverage bootstrap RSpec subprocess ARGV leakage resolved — child processes
@@ -307,6 +578,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   preventing stale cache hits after edits
 
 ### Performance
+
 - File discovery cached in the integration layer; repeated calls within one
   run no longer re-scan the filesystem
 - Polling sleep removed from the scheduler hot loop; slots are refilled
@@ -315,6 +587,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.10] - 2026-04-16
 
 ### Fixed
+
 - RuboCop `RSpec/MultipleExpectations` offenses in `coverage_formatter_spec` and
   `per_test_coverage_collector_spec` resolved by splitting each two-assertion
   example into focused single-expectation examples
@@ -322,6 +595,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.9] - 2026-04-16
 
 ### Fixed
+
 - SimpleCov is now suppressed during Minitest mutant child runs: `SimpleCov.start`
   is turned into a no-op before test files are required, eliminating the
   "Stopped processing SimpleCov as a previous error has been detected" warning
@@ -330,12 +604,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.8] - 2026-04-16
 
 ### Added
+
 - Minitest integration now supports per-test coverage: a `MinitestCoverageReporter`
   snapshots `Coverage.peek_result` after each test and writes `henitai_per_test.json`,
   enabling targeted mutation runs that only execute the tests covering the mutated lines —
   the same efficiency that was previously available only to RSpec projects
 
 ### Fixed
+
 - RSpec integration now respects `--exclude-pattern` entries in `.rspec` so excluded
   spec files are not passed to the runner during mutation runs
 - Per-test source file filter corrected to check only the project-relative path prefix
@@ -345,11 +621,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.7] - 2026-04-14
 
 ### Added
+
 - Committed integration smoke projects for RSpec and Minitest, runnable via
   `bundle exec rake smoke:integration:all`, to exercise `henitai` against
   small real projects that depend on the local source checkout
 
 ### Fixed
+
 - Child-process stdout/stderr restoration after captured test runs now keeps
   the standard streams usable, preventing passing mutant executions from being
   misclassified because the child exited with a closed stdio handle
@@ -360,6 +638,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.6] - 2026-04-14
 
 ### Fixed
+
 - Minitest is no longer required eagerly when `henitai/integration` loads, so
   projects that do not include Minitest in their bundle can still boot and use
   non-Minitest integrations without a parent-process `LoadError`
@@ -367,6 +646,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.5] - 2026-04-14
 
 ### Fixed
+
 - Steep type errors in `Runner` after removing targeted-run bootstrap scoping:
   updated `bootstrap_mutants` RBS signature to match the new single-argument
   form and removed stale signatures for `refresh_coverage_for_targeted_run`,
@@ -375,6 +655,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   workspace setup and report writing into helper methods
 
 ### Changed
+
 - Targeted-run coverage bootstrap no longer scopes the initial run to the
   subject's test files; the full suite is always used for the baseline,
   trading a minor performance optimisation for reliability
@@ -382,6 +663,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.4] - 2026-04-14
 
 ### Fixed
+
 - `StringLiteral` operator no longer generates no-op mutations where the
   replacement equals the original value (e.g. the spurious `"" → ""` mutant
   that was emitted for methods already returning an empty string literal)
@@ -397,6 +679,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   runner's configured reports directory
 
 ### Changed
+
 - `ScenarioExecutionResult.build` factory method consolidates status and
   exit-status derivation that was previously spread across `Integration`,
   reducing the mutation surface of the value object
@@ -404,6 +687,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.3] - 2026-04-13
 
 ### Added
+
 - Four new mutation operators: `UnaryOperator` (negates boolean and numeric
   unary expressions), `UpdateOperator` (swaps `+=`/`-=`/`*=` and targets
   compound-assignment nodes), `RegexMutator` (replaces regex literals with
@@ -422,6 +706,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `x || false`, `true && x`, `x && true` are suppressed as equivalent mutants
 
 ### Changed
+
 - Per-line mutation cap (`max_mutants_per_line`) removed from the generator,
   configuration schema, and validator — see ADR-08. All syntactically valid
   mutations on a line are now generated unconditionally
@@ -436,6 +721,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   without reflection
 
 ### Performance
+
 - Coverage bootstrap freshness check: the baseline RSpec run is skipped when
   `.resultset.json` is newer than every watched source and test file,
   eliminating ~83 % of bootstrap wall time on repeated runs within a session
@@ -457,6 +743,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   AST node
 
 ### Fixed
+
 - Mutant child processes now run in isolated process groups (`setpgid`);
   `cleanup_process_group` sends `SIGTERM` to the entire group on timeout or
   error, preventing orphaned subprocesses
@@ -472,10 +759,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.2] - 2026-04-07
 
 ### Added
+
 - Method coverage is now enabled in both RSpec and Minitest bootstraps, and
   the static filter merges method-level coverage into the line map
 
 ### Fixed
+
 - Coverage baseline regeneration now happens on every `henitai run`, so stale
   coverage state does not leak between runs
 - Coverage handling now accepts symbol-keyed `Coverage.peek_result` output and
@@ -492,6 +781,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.1] - 2026-04-03
 
 ### Added
+
 - Minitest integration for Rails projects: injects SimpleCov for coverage
   collection, sets `RAILS_ENV=test` and `PARALLEL_WORKERS=1` in the baseline
   subprocess, preloads `config/environment.rb` before mutant activation, adds
@@ -499,6 +789,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `simplecov` runtime dependency (required by the Minitest integration)
 
 ### Fixed
+
 - `rspec/core` was unconditionally required at load time, causing a `LoadError`
   in projects that do not have RSpec installed — now loaded lazily only when the
   RSpec integration is used
@@ -508,6 +799,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.0] - 2026-03-01
 
 ### Added
+
 - Initial gem scaffold with Ruby 4.0.2 support
 - Dev Container configuration (official `ruby:4.0.2-alpine` base image, Codex CLI preinstalled)
 - CI pipeline (RuboCop + RSpec + incremental mutation testing on PRs)
@@ -516,7 +808,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - CLI critical path: `henitai run` now executes the full pipeline, supports `--since`, returns CI-friendly exit codes, and `henitai version` prints `Henitai::VERSION`
 - RSpec per-test coverage output: `henitai/coverage_formatter` now writes `coverage/henitai_per_test.json`
 
-[Unreleased]: https://github.com/martinotten/henitai/compare/v0.5.1...HEAD
+[Unreleased]: https://github.com/martinotten/henitai/compare/v0.6.0...HEAD
+[0.6.0]: https://github.com/martinotten/henitai/compare/v0.5.3...v0.6.0
+[0.5.3]: https://github.com/martinotten/henitai/compare/v0.5.2...v0.5.3
+[0.5.2]: https://github.com/martinotten/henitai/compare/v0.5.1...v0.5.2
 [0.5.1]: https://github.com/martinotten/henitai/compare/v0.5.0...v0.5.1
 [0.5.0]: https://github.com/martinotten/henitai/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/martinotten/henitai/compare/v0.3.1...v0.4.0