snap_diff-capybara 0.0.1 → 2.0.0.beta1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3b0ed0acab1f365fa867a736a6e191af5994ed247b89347d3139c52d2e6e0c2b
-  data.tar.gz: be3f02855e30d530d5afc801ad73c13424c0283dc77955fc9e5be53edb2c077b
+  metadata.gz: a063da3ec86978a0e66baaa0c64692c40f18db15ce66b40cab390df9a90be5a1
+  data.tar.gz: c34b6fe46a10353ed94d738832cd9dafca06ef0f7a53b2c678408010198f58d2
 SHA512:
-  metadata.gz: 0a5453eb7eb3a1f45a4c86d125ee6ccc9098ff84d75ec61197d54eceab335a75a265982601bd4b730aa6dbf8e5df351c3efb2809e7de4c36cd775c3ba0e41cc0
-  data.tar.gz: 3aa51d497d6195a33d5d36d3c15fd20e8f89083c0c353c9b9e150614af1d4003bb435fac42a624b93e7338271bd68eaf892e0889910dfb7acb34dca7e63820ef
+  metadata.gz: '0828945cb79fbf911727deeac0b4cf868f34b5787c37720bc216a6d893115a2d9486a43284cf3f3467834951d1ae438f969a7ea5e1dcdd8ae387fb2cf9f263b9'
+  data.tar.gz: 3fc96895702aac83fa636bf8cfd1ac73953b4049b2629104ccbde592af150f3829c3eda7e73e8912b0342793cbf3e45d07056ffffb68c4f3b5594758406cd932

data/CHANGELOG.md

@@ -0,0 +1,190 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [v2.0.0.beta1] - 2026-08-22
+
+Second prerelease of the 2.0 opt-in experiment (see the v2.0.0.alpha1 notes
+below for the namespace change, deprecation warnings, and caveats). Final
+2.0.0 remains gated on adopter feedback — [#166](https://github.com/snap-diff/snap_diff-capybara/issues/166).
+
+### Added
+- **Dual gem names** — releases now also publish as
+  [`snap_diff-capybara`](https://rubygems.org/gems/snap_diff-capybara):
+  identical content and versions under the forward-looking name matching this
+  repository (the alpha1 mirror was backfilled). Install either, not both.
+- **Migration guide** — [docs/UPGRADING.md](docs/UPGRADING.md) covers the v2
+  namespace move, every renamed constant, silencing, and the alpha caveats
+  ([#220](https://github.com/snap-diff/snap_diff-capybara/pull/220))
+
+### Internal
+- Test suite exercises the canonical `SnapDiff` names; legacy names remain
+  covered by dedicated forwarding/deprecation tests, and a strict warning
+  guard now fails the suite on any accidental legacy-name use
+  ([#221](https://github.com/snap-diff/snap_diff-capybara/pull/221))
+
+---
+
+## [v2.0.0.alpha1] - 2026-08-22
+
+**Opt-in experiment prerelease.** RubyGems never installs prereleases by default
+resolution — to try it: `gem "capybara-screenshot-diff", "2.0.0.alpha1"`. The
+final 2.0.0 ships only after adopter feedback on this train; please report
+anything surprising on [#166](https://github.com/snap-diff/snap_diff-capybara/issues/166).
+
+### Changed
+- **`SnapDiff` is the canonical namespace.** The implementation lives in
+  `lib/snap_diff/`; every legacy constant (`Capybara::Screenshot::Diff::*`,
+  `CapybaraScreenshotDiff::*`) still resolves to the *same object* and keeps
+  working ([#208](https://github.com/snap-diff/snap_diff-capybara/pull/208),
+  [#209](https://github.com/snap-diff/snap_diff-capybara/pull/209),
+  [#210](https://github.com/snap-diff/snap_diff-capybara/pull/210)):
+  `ImageCompare` → `SnapDiff::Comparison`, `Difference` →
+  `SnapDiff::ComparisonResult`, `Drivers::BaseDriver` → `SnapDiff::Driver` (mixin).
+- **Legacy constants warn on first use** — once per constant per process, naming
+  the replacement ([#218](https://github.com/snap-diff/snap_diff-capybara/pull/218)).
+  Silence with `SnapDiff.silence_deprecations = true` or
+  `SNAP_DIFF_SILENCE_DEPRECATIONS=1`. A few constants stay silent by design
+  (`Os`, `DSL`, `VERSION`, driver leaf classes — see `lib/snap_diff/legacy_shims.rb`).
+
+### Fixed
+- Annotation color constants resolve under the bare `require "snap_diff"` entry;
+  previously a differing comparison raised `NameError` there
+  ([#219](https://github.com/snap-diff/snap_diff-capybara/pull/219))
+
+### Known caveats (deliberate, alpha)
+- `defined?(...)` / `const_defined?` on lazily-shimmed legacy names returns
+  false/nil — feature detection like `defined?(Capybara::Screenshot::Diff::Drivers::VipsDriver)`
+  must move to the `SnapDiff::` name. Rescuing legacy error classes is unaffected
+  (they remain eagerly defined).
+- Reopening `module Capybara::Screenshot::Diff::Drivers` (historical custom-driver
+  monkey-patch pattern) defines a fresh module that shadows the shim; define custom
+  drivers under `SnapDiff::Drivers` instead.
+
+### Internal
+- Core simplification, behavior-preserving (the "5.5-lite" pass): pure
+  capture/comparison option partition ([#212](https://github.com/snap-diff/snap_diff-capybara/pull/212)),
+  stability failure as data ([#213](https://github.com/snap-diff/snap_diff-capybara/pull/213)),
+  explicit `ScreenshotAssertion#archive_baseline!` + `#inspect` on
+  assertion/result ([#214](https://github.com/snap-diff/snap_diff-capybara/pull/214)),
+  `SnapDiff::Capture::Viewport` seam with the future `anchor:` hook
+  ([#215](https://github.com/snap-diff/snap_diff-capybara/pull/215)), reporter vs
+  session lifecycle separation ([#216](https://github.com/snap-diff/snap_diff-capybara/pull/216)),
+  all behind a guard-test net ([#211](https://github.com/snap-diff/snap_diff-capybara/pull/211))
+
+---
+
+## [v1.15.1] - 2026-08-22
+
+### Fixed
+- **`VipsDriver#resize_image_to` resizes to the requested dimensions** — the vips driver passed a target aspect ratio where libvips expects a scale factor, so retina-halving on macOS/Selenium could enlarge screenshots (2560×1600 → 4096×2560) and save wrongly-sized baselines; now scales width and height independently via `resize(scale, vscale:)` ([#205](https://github.com/snap-diff/snap_diff-capybara/pull/205))
+
+### Internal
+- Driver contract tests pinning the shared ChunkyPNG/Vips driver seam (method surface, load/compare behavior, option handling) — the net that caught the resize bug ([#204](https://github.com/snap-diff/snap_diff-capybara/pull/204))
+
+---
+
+## [v1.15.0] - 2026-08-22
+
+### Added
+- **`SnapDiff::Config`** — one flat object consolidating all 27 settings behind `SnapDiff.config` / `SnapDiff.configure { |config| ... }`; purely additive, the existing accessors stay canonical and both views share one source of truth ([#200](https://github.com/snap-diff/snap_diff-capybara/pull/200))
+
+### Fixed
+- **`pending_if_new` no longer masks real failures** — a raising Minitest `teardown` or a raising RSpec `after` hook registered before the gem could previously be reported as a skipped/pending test with exit 0; the pending marker now defers until the framework's teardown chain has run and yields to any failure. Known residual: an RSpec `config.append_after` registered after this gem still runs later than the gem's hook — require the gem last if you use appended after-hooks ([#203](https://github.com/snap-diff/snap_diff-capybara/pull/203))
+- **`BacktraceFilter` path-boundary matching** — a custom `lib_directory` of `/app/lib` no longer also filters locations under `/app/library` ([#202](https://github.com/snap-diff/snap_diff-capybara/pull/202))
+
+### Internal
+- Failure-masking guard tests for the `pending_if_new` teardown paths via subprocess RSpec runs ([#199](https://github.com/snap-diff/snap_diff-capybara/pull/199))
+- Hygiene pass — skip-area/VCS-baseline and `BacktraceFilter` guard tests, entry-point forwarder dedupe, `Comparison` and `BacktraceFilter` merged into their sole consumers (−2 files, constant paths preserved) ([#201](https://github.com/snap-diff/snap_diff-capybara/pull/201))
+
+---
+
+## [v1.14.0] - 2026-08-22
+
+### Added
+- **`SnapDiff` namespace aliases** — `SnapDiff::Comparison`, `SnapDiff.compare`, and `SnapDiff.start` provide a forward-looking entry point onto the existing `Capybara::Screenshot::Diff` API, no behavior changes ([#166](https://github.com/snap-diff/snap_diff-capybara/issues/166))
+
+### Fixed
+- **Standalone require path** — `require "capybara_screenshot_diff"` (or `require "snap_diff"`) followed by `Diff.compare` no longer raises `NameError` for the missing drivers require ([#194](https://github.com/snap-diff/snap_diff-capybara/pull/194))
+
+### Internal
+- Merged `DifferenceFinder` into `ImageCompare` (ADR-004 step) ([#192](https://github.com/snap-diff/snap_diff-capybara/pull/192))
+- Extracted `AnnotationService` from `Reporters::Default`; full public surface preserved via delegation ([#193](https://github.com/snap-diff/snap_diff-capybara/pull/193))
+- Consolidated `pending_if_new` teardown logic into one shared helper across Minitest/RSpec/Cucumber adapters ([#197](https://github.com/snap-diff/snap_diff-capybara/pull/197))
+- Test-suite driver-coverage banner and CI guard against silently missing drivers ([#198](https://github.com/snap-diff/snap_diff-capybara/pull/198))
+
+---
+
+## [v1.13.0] - 2026-08-22
+
+### Added
+- **`capture_screenshot` DSL method** — take a screenshot without ever comparing or asserting ([#191](https://github.com/snap-diff/snap_diff-capybara/issues/191))
+- **`compare:` option on `screenshot`** — pass `compare: true` (default) to assert, or `compare: false` to capture only ([#191](https://github.com/snap-diff/snap_diff-capybara/issues/191))
+- **`Capybara::Screenshot::Diff.pending_if_new` config** — mark tests as skipped in teardown when a baseline does not exist, complementing `fail_if_new` ([#191](https://github.com/snap-diff/snap_diff-capybara/issues/191))
+
+### Changed
+- **`assert_matches_screenshot` is now the primary assertion method** — captures a screenshot and compares against baseline ([#191](https://github.com/snap-diff/snap_diff-capybara/issues/191))
+- **`screenshot` is now a convenience wrapper** — safe to override in user test classes; the gem no longer calls it internally ([#191](https://github.com/snap-diff/snap_diff-capybara/issues/191))
+
+---
+
+## [v1.12.0] - 2026-04-12
+
+### Added
+- **HTML reporter** — interactive dashboard with 4 comparison modes (both/base/new/heatmap), per-image zoom, keyboard navigation, and search ([#170](https://github.com/snap-diff/snap_diff-capybara/pull/170))
+- **GitHub Actions integration** — inline HTML preview with base64 embedded images + reusable composite action ([#171](https://github.com/snap-diff/snap_diff-capybara/pull/171))
+- **`disable_animations` helper** — inject CSS to stop all animations/transitions during screenshots ([#174](https://github.com/snap-diff/snap_diff-capybara/pull/174))
+- **`snap_diff:clean` rake task** — remove diff artifacts while keeping baselines ([#177](https://github.com/snap-diff/snap_diff-capybara/pull/177))
+- `Diff.compare` for standalone image comparison without Capybara or browser
+- Perceptual color distance (dE00) for anti-aliasing tolerance in VipsDriver
+- `assert_no_screenshot_changes` DSL assertion
+- `Diff.configure` block helper for simplified configuration
+- Ruby 3.5 and 4.0 support
+
+### Changed
+- `blur_active_element` now defaults to `true` — prevents cursor blinking artifacts
+- `hide_caret` now defaults to `true` — stable screenshots without caret
+- `fail_if_new` now defaults to `true` in CI (when `ENV['CI']` is set)
+- Thread-safe reporter notification with mutex ([#175](https://github.com/snap-diff/snap_diff-capybara/pull/175))
+
+### Removed
+- **SVN support** — Git only
+- **ActiveSupport runtime dependency** — pure Ruby, lighter installations
+
+### Fixed
+- VCS path resolution rewritten for thread safety (Open3 + array-form system)
+- Reporter diff artifacts cleaned up properly on `Snap#delete!` ([#173](https://github.com/snap-diff/snap_diff-capybara/pull/173))
+- RSpec matcher now provides `failure_message` and description
+- Missing baseline error includes recording instructions
+- Ruby 4.0 DSLStub ordering compatibility
+- ChunkyPNG `filter_image_with_median` incorrect behavior
+- Tolerance calculation no longer skips large changes
+
+### Performance
+- ChunkyPNG shift-detection: eliminated array allocations (~30% faster for large images)
+- VIPS: cached computations at construction (~15% faster)
+- Memoized region area size, replaced closures with blocks
+
+### Documentation
+- README restructured from 970 to 149 lines with 7 dedicated `docs/` files ([#171](https://github.com/snap-diff/snap_diff-capybara/pull/171))
+- CI integration guide with artifact upload and PR commenting ([docs/ci-integration.md](docs/ci-integration.md))
+- Upgrade guide ([docs/UPGRADING.md](docs/UPGRADING.md))
+- Color comparison guide — tolerance vs perceptual_threshold vs color_distance_limit ([#176](https://github.com/snap-diff/snap_diff-capybara/pull/176))
+
+### Internal
+- Simplified internals: inlined CaptureStrategy, ComparisonLoader, ScreenshotNamerDSL, VipsUtil
+- Unified Screenshoter constructors, consolidated skip_area accessor
+- Upgraded CI dependencies (actions/checkout v5, upload-artifact v7)
+
+---
+
+## [v1.11.0] - Previous Release
+
+[Unreleased]: https://github.com/snap-diff/snap_diff-capybara/compare/v1.12.0...HEAD
+[v1.12.0]: https://github.com/snap-diff/snap_diff-capybara/releases/tag/v1.12.0
+[v1.11.0]: https://github.com/snap-diff/snap_diff-capybara/releases/tag/v1.11.0
+
+**Upgrade Guide:** See [docs/UPGRADING.md](docs/UPGRADING.md) for detailed migration instructions.

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,129 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement by
+[opening a GitHub Issue](https://github.com/snap-diff/snap_diff-capybara/issues).
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact:** Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence:** A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact:** A violation through a single incident or series
+of actions.
+
+**Consequence:** A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact:** A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence:** A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact:** Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence:** A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016 Uwe Kubosch
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/Rakefile

@@ -0,0 +1,65 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rake/testtask"
+
+task default: :test
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/**/*_test.rb"]
+end
+
+Rake::TestTask.new("test:unit") do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/unit/**/*_test.rb"]
+end
+
+Rake::TestTask.new("test:integration") do |t|
+  t.libs << "test"
+  t.libs << "lib"
+  t.test_files = FileList["test/integration/**/*_test.rb"]
+end
+
+desc "Run all tests with coverage"
+task :coverage do
+  ENV["COVERAGE"] = "true"
+  Rake::Task["test"].invoke
+end
+
+desc "Generate sample HTML report. Use bin/rake 'report:sample[embed]' for base64 images"
+task "report:sample", [:embed] do |_t, args|
+  embed_arg = args[:embed] ? "--embed" : ""
+  ruby "scripts/generate_sample_report.rb #{embed_arg}"
+end
+
+desc "Remove screenshot diff artifacts (keeps baselines)"
+task "snap_diff:clean" do
+  patterns = ["**/*.diff.png", "**/*.base.png", "**/*.base.diff.png", "**/*.heatmap.diff.png",
+    "**/*.diff.webp", "**/*.base.webp", "**/*.base.diff.webp", "**/*.heatmap.diff.webp",
+    "**/snap_diff_report.html"]
+  removed = patterns.flat_map { |p| Dir.glob("tmp/#{p}") + Dir.glob("doc/screenshots/#{p}") }.uniq
+  removed.each { |f| FileUtils.rm_f(f) }
+  puts "Removed #{removed.size} diff artifacts"
+end
+
+task "clobber" do
+  puts "Cleanup tmp/"
+  FileUtils.rm_rf(Dir["./tmp/*"])
+end
+
+task "test:benchmark" do
+  require_relative "scripts/benchmark/find_region_benchmark"
+  benchmark = Capybara::Screenshot::Diff::Drivers::FindRegionBenchmark.new
+
+  puts "For Medium Screen Size: 800x600"
+  benchmark.for_medium_size_screens
+
+  puts ""
+  puts "*" * 100
+
+  puts "For Small Screen Size: 80x60"
+  benchmark.for_small_images
+end

data/capybara-screenshot-diff.gemspec

@@ -0,0 +1,29 @@
+# frozen_string_literal: true
+
+lib = File.expand_path("lib", __dir__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "capybara/screenshot/diff/version"
+
+Gem::Specification.new do |spec|
+  spec.name = "capybara-screenshot-diff"
+  spec.version = Capybara::Screenshot::Diff::VERSION
+  spec.authors = ["Uwe Kubosch"]
+  spec.email = ["uwe@kubosch.no"]
+  spec.summary = "Track your GUI changes with diff assertions"
+  spec.description = "Save screen shots and track changes with graphical diff"
+  spec.homepage = "https://github.com/snap-diff/snap_diff-capybara"
+  spec.required_ruby_version = ">= 3.2"
+  spec.license = "MIT"
+  spec.metadata["allowed_push_host"] = "https://rubygems.org/"
+  spec.files = `git ls-files -z`.split("\x0").reject do |f|
+    f.match(%r{(^(\.|tmp|bin|test|spec|features|gemfiles|scripts|foo)/)|(^(\.|Dockerfile|CONTRIBUTING|README))})
+  end
+
+  spec.bindir = "exe"
+  spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "actionpack", ">= 7.1", "< 9"
+  spec.add_development_dependency "activesupport", ">= 7.1", "< 9"
+  spec.add_runtime_dependency "capybara", ">= 2", "< 4"
+end

data/docs/RELEASE_PREP.md

@@ -0,0 +1,44 @@
+# Release Preparation — v1.15.1
+
+## Summary
+
+HIGH-severity VipsDriver resize fix (retina halving could enlarge screenshots
+and corrupt baselines) plus the driver contract tests that caught it.
+
+## Release Checklist
+
+### Pre-Release
+
+- [x] Update version to `1.15.1`
+- [x] Run tests: `bundle exec rake test:unit` (376 runs, 0 failures)
+- [x] Update CHANGELOG.md
+
+### Release (One Click)
+
+1. Push to GitHub
+2. Go to [Actions → Release](https://github.com/snap-diff/snap_diff-capybara/actions/workflows/release.yml)
+3. Click **Run workflow**, enter `1.15.1`
+4. Workflow will: test → tag → publish to RubyGems → create GitHub Release
+
+### Post-Release
+
+- [ ] Verify on [RubyGems](https://rubygems.org/gems/capybara-screenshot-diff)
+- [ ] Verify GitHub Release created
+
+## What Changed
+
+### Added
+- `SnapDiff::Config` — flat, additive consolidation of all 27 settings
+  (`SnapDiff.config` / `SnapDiff.configure`); old accessors stay canonical
+
+### Fixed
+- `pending_if_new` no longer converts real teardown/after-hook failures into
+  pending tests (Minitest defers to `after_teardown`; RSpec uses `append_after`;
+  known residual for consumer `append_after` hooks documented)
+- `BacktraceFilter` custom `lib_directory` matches on a path boundary
+
+### Internal
+- Guard tests for failure masking and skip-area/VCS-baseline regressions;
+  two files merged into sole consumers (constant paths preserved)
+
+See [CHANGELOG.md](../CHANGELOG.md) for full details.