branchproof 0.9.0 → 0.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 59c4f3efbd178f68f3137bae18e75de19ebc39e2ffc7873a2d84c9d5ce442b05
-  data.tar.gz: 26247e830fecbf4cdd2dd2c0eb5c50838cbe02de06f919ba7dced1c44252fd2d
+  metadata.gz: 3667120528803b1ceeb8c17313f66391b38633ed452757cb6e532f938d8cfd2a
+  data.tar.gz: ebdab6b41dde4697eff2634fe022c18e7c86e7abf4a317235fc94f24ec6070ad
 SHA512:
-  metadata.gz: e39262ef9fb55f10d3760a1e72cdff4a159f62d199d57729a19cd93b2df2720ceacf1e87317094cab76d3e15427d0e19c6dfe6968f781b7d35ff2f934d0171d5
-  data.tar.gz: f8e73473d13a6c15ba5890e0613848a1fe71d4cd092f8633ce707f1be7d63b566e9cef854bd35551ded41d2e5cd84e753932ce7f2db8e6348e7a1eba34e690e1
+  metadata.gz: 226da6639e0f9aedc3345073e76b8bd78c23921ea0c5664d4230cf1712d25984a8b97168b2d721658e50c552dab54e6ad5cac71ae8bfccf5222c4eb89cf8471e
+  data.tar.gz: 7ff352e0d1ec9aca08a67d0ed9c6246a37f1560f16777a0c89b01ad04ad94fff7af99a2abb3b09135990f1d67b33e58cff3ce4209e0e0a5a808f72ff59a52c07

data/CHANGELOG.md

@@ -1,5 +1,47 @@
 ## [Unreleased]
 
+## [0.11.0] - 2026-09-25
+
+- Add validated coverage policies for Decision, Condition, Condition/Decision,
+  MC/DC, and Decision Table criteria. Repeatable `--minimum criterion=threshold`
+  options override matching project or saved-report policy entries, compare
+  exact counts, and distinguish failed gates from unavailable or incomplete
+  evidence in exit status and JSON.
+- Persist policy decisions in live schema `1.4` reports while keeping saved
+  schemas `1.0` through `1.3` readable; offline policy overrides do not load
+  project configuration or mutate snapshots.
+- Add terminal-only `--focus PATH[:LINE]` and `--top N` selection for analyze
+  and report views. Selection uses captured source spans and deterministic source
+  order while leaving global summaries, gates, diagnostics, and exit status
+  unchanged.
+- Document a GitHub Actions artifact workflow that creates the output directory
+  and uploads reports after gate failures.
+- Preserve setup, body, and teardown phase totals when independent evidence runs
+  are merged, keeping phase attribution complete in combined snapshots.
+- Add declarative `.branchproof.json` project configuration with CLI precedence,
+  source exclusions, and comparison metadata for repeatable coverage runs.
+- Add a pipeline benchmark harness that exposes timing dimensions for future
+  measurements of coverage feedback costs.
+
+## [0.10.0] - 2026-09-21
+
+- Add the first-release RSpec execution path for plain Ruby and Rails projects.
+  It supports RSpec 3.13, including Rails 8.1 with rspec-rails 8.x on CRuby 3.4.
+  Integration is verified against rspec-rails 8.0.4 and native RSpec behavior.
+- Add `--framework auto|minitest|rspec`, native RSpec discovery that respects
+  exclusions and custom patterns, full-description labels, and status mapping for pending,
+  skipped, fixed pending, and failed examples.
+- Keep Rails helper ownership with the application after Branchproof's loader;
+  transaction behavior, in-process specs, and context/suite/unattributed
+  evidence are recorded explicitly.
+- Allow focused pure-Ruby specs inside Rails projects without requiring Rails boot.
+- Match RSpec examples across saved reports only when spec and declaration
+  revisions agree, preventing false matches after examples are inserted or reordered.
+- Stream test progress to stderr, show quoted RSpec rerun commands, and explain
+  unmatched test globs, empty suites, and filters selecting no examples.
+- Document repeated ordinary and shared-example benchmarks with allocations
+  and peak process memory; end-to-end overhead remains substantial.
+
 ## [0.9.0] - 2026-09-18
 
 - Measure contextual predicates, guarded pattern selection, dynamic case splat

data/README.md

@@ -1,7 +1,7 @@
 # Branchproof
 
 Branchproof measures decision, condition, modified condition/decision (MC/DC),
-and decision-table coverage from one serial Minitest run. It discovers Ruby
+and decision-table coverage from one serial Minitest or RSpec run. It discovers Ruby
 decisions through Prism, records their runtime paths, and attributes evidence
 to tests. Boolean decisions receive the coverage ladder; `case`, pattern
 alternatives, safe navigation, and conditional assignments receive alternative
@@ -22,10 +22,13 @@ Or add it to a bundle:
 bundle add branchproof
 ```
 
-Branchproof targets CRuby 3.3 and 3.4, Minitest 5.x, and Prism 1.x. The
-published core runtime matrix is the CI matrix. Rails support is optional and
-has been locally checked against Rails 8.1.3.1 on CRuby 3.4.5; Rails is
-supplied by the application and is not a runtime dependency of this gem.
+Branchproof targets CRuby 3.3 and 3.4, Minitest 5.x, RSpec 3.13, and Prism 1.x. The
+published core runtime matrix is the CI matrix. Rails/RSpec execution is limited
+to Rails 8.1.x, rspec-rails 8.x, RSpec 3.13.x, and CRuby 3.4.x; passing core
+tests on Ruby 4.0 does not imply Rails/RSpec support. Integration has been checked
+with Rails 8.1.3.1, rspec-rails 8.0.4, RSpec Core 3.13.6, and CRuby 3.4.7.
+Rails and RSpec are optional dependencies supplied by the application.
+Minitest 5.x remains a runtime dependency of this gem.
 Unsupported syntax and incomplete observations remain visible in the report
 instead of being counted as coverage.
 
@@ -33,7 +36,7 @@ instead of being counted as coverage.
 
 Run `branchproof analyze` with the source files or globs to inspect, followed by
 options. A second `--` separates Branchproof options from arguments passed to
-Minitest unchanged:
+the selected test framework:
 
 ```sh
 branchproof analyze 'lib/**/*.rb' --test 'test/**/*_test.rb' \
@@ -58,22 +61,126 @@ the application's bundle and Rails version remain in effect:
 bundle exec branchproof analyze 'app/**/*.rb' --project rails --test 'test/**/*_test.rb'
 ```
 
+Choose the test framework independently from project kind:
+
+```sh
+bundle exec branchproof analyze 'app/**/*.rb' --project rails --framework rspec
+```
+
+`--framework auto|minitest|rspec` is explicit about the adapter. Auto mode
+selects RSpec when `.rspec` or `spec/**/*_spec.rb` markers exist and Minitest
+when `test/**/*_test.rb` or `test/**/test_*.rb` markers exist. If both are
+present, specify the framework. RSpec discovery uses `spec/**/*_spec.rb`; an
+explicit `--test` selection remains authoritative. Project roots are resolved
+explicitly, and report paths are relative to that root so reports from
+different checkouts can be compared.
+
+Install `rspec` in the application's test bundle; Rails applications also need
+`rspec-rails`. RSpec reads its usual option files and `SPEC_OPTS`, including
+helper requires, filters, ordering, and file or example-ID selectors. Selectors
+from RSpec configuration replace default discovery. Combining those selectors
+with an explicit Branchproof `--test` is rejected as ambiguous; ordinary filters
+such as `--tag` and `--example` can accompany `--test`.
+
+RSpec before hooks, eager `let!`, and around-hook prefixes own setup evidence.
+The example body and helpers evaluated there own body evidence; after hooks,
+mock cleanup, and around-hook suffixes own teardown evidence. Suite and context
+hooks remain unattributed. Pending and skipped examples do not invent execution;
+an unexpectedly passing pending example remains a failure.
+
+RSpec support is serial: dry-run, bisect, DRb, custom runners, nested runs, and
+repeated example attempts are rejected. Rails/RSpec supports Rails 8.1.x with
+rspec-rails 8.x on CRuby 3.4.x. Feature and system specs use the in-process
+Capybara `rack_test` driver; browser drivers require execution-context support
+outside this release. Capybara is optional for apps that do not use those specs.
+
 For a project rooted at the current directory, `--project auto` is the
 default. It selects Rails only when both `config/application.rb` and
 `config/environment.rb` exist; otherwise it selects a plain Ruby project.
 Use `--project ruby` or `--project rails` to override detection. An explicit
 Rails project without both boot files is a usage error.
 
-Project defaults discover the sorted, de-duplicated union of
+Minitest defaults discover the sorted, de-duplicated union of
 `test/**/*_test.rb` and `test/**/test_*.rb`. Helper, support, and fixture files
 are excluded from that default set. `--test` remains authoritative when test
 files are selected explicitly. The worker prepends the project's `lib` and
-`test` directories to its child load path, so application `require` calls
+`test` directories (`lib` and `spec` for RSpec) to its child load path, so application `require` calls
 resolve without changing the parent process.
 
-Rails analysis boots `config/environment.rb` and `rails/test_help` inside the
-isolated worker after Branchproof's loader and Minitest hooks are installed. The
-child receives `RAILS_ENV=test`, `RACK_ENV=test`, `PARALLEL_WORKERS=1`,
+Project defaults can be checked into `.branchproof.json` at the project root:
+
+```json
+{
+  "schema_version": 1,
+  "project": "rails",
+  "framework": "minitest",
+  "sources": ["app/**/*.rb"],
+  "tests": ["test/**/*_test.rb"],
+  "exclude": ["app/generated/**/*.rb"],
+  "minimum": { "mcdc": 80 }
+}
+```
+
+`project` accepts `auto`, `ruby`, or `rails`; `framework` accepts `auto`,
+`minitest`, or `rspec`. `sources` and `tests` replace their corresponding
+defaults, while `exclude` removes matching source files before inventory. A
+configuration file may live elsewhere when passed with `--config PATH`; its
+patterns are still resolved from the project root. Use `--no-config` to disable
+the default file. Command-line project, framework, source, and test selections
+take precedence over the file. Configured `exclude` patterns are applied
+before source inventory and are recorded in run metadata for comparison.
+`--config` and `--no-config` cannot be used together. RSpec configuration
+selectors continue to conflict with an explicit test selection, including one
+supplied by this file.
+
+The `minimum` values are validated percentages from 0 through 100 for the five
+supported criteria: `decision`, `condition`, `condition_decision`, `mcdc`, and
+`decision_table`. A policy is evaluated against the exact numerator and
+denominator counts in the report, so a value such as `66.67` is not rounded
+before it is compared. The policy is recorded in JSON under
+`coverage_policy`.
+
+The command line can add or replace individual policy entries with repeatable
+`--minimum` options. Use `criterion=threshold`, for example:
+
+```sh
+bundle exec branchproof analyze 'lib/**/*.rb' --minimum mcdc=80 \
+  --minimum decision_table=75
+```
+
+CLI values take precedence over matching `minimum` keys from `.branchproof.json`.
+Specifying the same criterion more than once on the command line is an error.
+The five criteria are evaluated independently. A threshold met exactly passes;
+a result below it fails. A requested gate with a zero denominator, unavailable
+coverage, or incomplete observations or analysis is `unavailable`, and exits
+with status 2. A below-threshold gate exits 1. A failed test run makes
+requested policy gates unavailable and exits 2; without a policy, a failed test
+run retains the existing exit status 1. With no policy, the existing report
+exit behavior remains unchanged.
+
+For a Minitest project, a focused configuration can select the library and
+test trees directly:
+
+```json
+{ "schema_version": 1, "framework": "minitest",
+  "sources": ["lib/**/*.rb"], "tests": ["test/**/*_test.rb"] }
+```
+
+For an RSpec project, use its spec patterns instead:
+
+```json
+{ "schema_version": 1, "framework": "rspec",
+  "sources": ["app/**/*.rb"], "tests": ["spec/**/*_spec.rb"] }
+```
+
+Rails analysis boots the application inside the isolated worker after
+Branchproof's loader and the selected framework hooks are installed. The
+application's `rails_helper` owns requiring and configuring `rspec/rails` after
+the loader; the helper must not require `branchproof` again. Selected specs
+may require only `spec_helper` and run without booting Rails,
+even when project detection selects Rails. Once Rails is loaded, Branchproof
+requires an initialized application and enforces the Rails/RSpec support limits.
+The child receives `RAILS_ENV=test`, `RACK_ENV=test`, `PARALLEL_WORKERS=1`,
 `DISABLE_BOOTSNAP=1`, and `DISABLE_SPRING=1`; the invoking process environment
 is unchanged. The Rails metadata in the report identifies the selected
 project and Rails version.
@@ -93,6 +200,17 @@ the witness pair or missing counterpart constraints beside each condition;
 Level 2 and Level 3 also list named supporting tests. Repeated supporting-set
 rows are collapsed in terminal output only.
 
+RSpec owners use the example's `full_description` and positional `example_id`.
+Terminal views include quoted rerun commands, including selectors for shared
+examples. These selectors apply to the recorded spec revision. Comparisons
+require matching spec and declaration digests before matching example owners;
+changed specs and older reports without digests are treated conservatively.
+Runner output streams to stderr while JSON reports remain on stdout.
+Pending, skipped, fixed-pending, and failed examples map to the corresponding
+baseline statuses; suite and context lifecycle events remain visible, and
+observations without a test owner are counted as unattributed. The same levels
+and terminal views are available for both adapters.
+
 For example, running the contents of the small `decision.rb` /
 `test_decision_test.rb` fixture from a project `lib/` and `test/` directory
 with the terminal format produces a summary like this:
@@ -156,6 +274,15 @@ that did evaluate count toward Condition Coverage even when their value was
 masked by another condition. Here, the two observations prove independence
 for `logged_in?`; `admin?` still needs `[TF] => F`.
 
+This is also a compact test-design walkthrough. A test that records
+`[F-] => F` proves the false branch of `logged_in?`; a test that records
+`[TT] => T` proves the true branch and establishes the current positive path.
+Adding a test that records `[TF] => F` evaluates `admin?` false while
+`logged_in?` stays true, so it supplies the missing independence witness and
+improves the condition, Condition/Decision, MC/DC, and applicable decision-table
+results. The report names the missing vector and its owning test when it is
+observed.
+
 Decision and Condition Coverage are calculated independently from the captured
 evidence. Condition/Decision requires both; MC/DC adds independence evidence.
 Decision Table Coverage is calculated independently of all of them: MC/DC asks
@@ -449,6 +576,34 @@ execution. JSON output always contains the complete evidence document, so an
 explicit view cannot be combined with `--format json`. The `mcdc` executable
 accepts the same arguments for existing scripts.
 
+Terminal reports can be narrowed with `--focus PATH[:LINE]` and bounded with
+`--top N`, where `N` is a positive integer. These options are accepted by
+`analyze` and `report`, and are terminal-only. Focus matches the source spans
+captured in the report; rendering does not reopen or need the original source
+file. `--focus` and `--top` affect displayed detail only: the coverage summary,
+policy gates, diagnostics, exit status, and global counts remain unchanged.
+
+The default view limits decisions. In `--view decision-tables`, the units are
+decision tables; in `--view conditions`, condition and alternative rows; and
+in `--view tests`, test rows. Rows are ordered deterministically by project-
+relative path and source line, with deterministic tie-breakers for each view:
+decisions use column and stable ID; decision tables use decision ID; conditions
+and alternatives use column, decision ID, and condition or alternative index;
+tests use test name and ID. `--top` follows that source order; it does not rank
+rows by risk or coverage. For example:
+
+```sh
+bundle exec branchproof analyze 'lib/**/*.rb' --focus lib/access.rb:12 --top 5
+bundle exec branchproof report .branchproof/current.json --view conditions \
+  --focus lib/access.rb --top 10
+```
+
+Focus and top selections never create a new test run or alter policy scope.
+They also do not generate tests. RSpec rerun labels remain the existing
+recorded selectors and commands. The main finding rows respect the selection;
+supplemental unexecuted, unattributed, and unsupported sections retain their
+run-wide counts rather than expanding into all detail rows.
+
 ### Saved reports and offline comparison
 
 Reports are saved only when requested. Create a local artifact directory and
@@ -466,13 +621,26 @@ The output's parent directory must already exist. Replacing a baseline is an
 explicit `analyze --format json --output` operation; keep CI snapshots as
 artifacts when you need to retain multiple runs.
 
-The `report` command reads the saved document without loading the application
-or running tests. It uses locations and metadata captured in the report, so
-rendering remains useful after the original checkout has moved or been
-removed. New snapshots retain the ladder at every level. Legacy snapshots
-without analysis can still be rendered at Level 1; levels 2 and 3 require
-analysis in the saved report. The repository ignores `.branchproof/`; choose a
-different path and CI artifact policy when a project needs to retain reports.
+The `report` command reads the saved document without loading the application,
+project configuration, or running tests. It uses locations and metadata
+captured in the report, so rendering remains useful after the original
+checkout has moved or been removed. A saved report's policy is inherited by
+default. Repeatable `--minimum criterion=threshold` options override matching
+saved policy entries for that rendering without changing the snapshot file;
+other saved thresholds remain inherited. Offline rendering never consults the
+current `.branchproof.json`.
+
+New live JSON reports use schema `1.4` and include the required
+`coverage_policy` object with the normalized requested minima and recomputed
+gate results. The report validates those results from its exact coverage
+counts rather than trusting a persisted percentage. Readers continue to accept
+schemas `1.0` through `1.3`; an offline policy overlay is optional and
+preserves the input snapshot's schema version, including for legacy reports.
+New snapshots retain the ladder at every level. Legacy snapshots without
+analysis can still be rendered at Level 1; levels 2 and 3 require analysis in
+the saved report.
+The repository ignores `.branchproof/`; choose a different path and CI artifact
+policy when a project needs to retain reports.
 Saved JSON includes existing raw metadata such as test names and expressions;
 relative terminal labels do not mean every legacy JSON field is sanitized.
 
@@ -508,6 +676,29 @@ Invalid input or an incomplete comparison exits 2, which takes
 precedence. Reports are explicit snapshots: comparison never creates history,
 promotes a baseline, or overwrites either input.
 
+### GitHub Actions artifacts
+
+A coverage policy can fail a job while still preserving the report for review.
+Create the output directory before invoking Branchproof and upload the report
+with `if: always()` so failed gates and failed test runs leave an artifact:
+
+```yaml
+- name: Branchproof coverage
+  run: |
+    mkdir -p .branchproof
+    bundle exec branchproof analyze 'lib/**/*.rb' --test 'test/**/*_test.rb' \
+      --format json --output .branchproof/coverage.json \
+      --minimum mcdc=80 --minimum decision_table=75
+
+- name: Upload Branchproof report
+  if: always()
+  uses: actions/upload-artifact@v4
+  with:
+    name: branchproof-coverage
+    path: .branchproof/coverage.json
+    if-no-files-found: warn
+```
+
 MC/DC has two related questions. Evaluation asks whether a condition was
 observed with a value, including short-circuiting. Independent proof asks
 whether the analyzer found a pair of observations where that condition changes
@@ -618,8 +809,8 @@ Ruby-defined custom `!` methods keep their runtime behavior;
 evidence that contradicts Boolean negation is rejected instead of proving
 coverage with an invalid logical model.
 
-New reports use schema `1.3`; saved schema `1.0`, `1.1`, and `1.2` reports
-remain readable. Comparison distinguishes decision-table coverage movement
+New reports use schema `1.4`; saved schema `1.0`, `1.1`, `1.2`, and `1.3`
+reports remain readable. Comparison distinguishes decision-table coverage movement
 (`rule coverage gained`, `rule coverage lost`) from analysis movement
 (`rule reachability changed`), and treats a structurally changed decision as a
 changed decision-table context instead of guessing which old rule a new rule
@@ -654,12 +845,14 @@ the serial Minitest runner. This is useful for seeds and name filters:
 branchproof analyze 'lib/**/*.rb' --level 1 -- --seed 9001 -n /checkout/
 ```
 
-The 0.2 release supports serial Minitest execution in plain Ruby projects and
-Rails applications. Rails lazy and eager loading are supported when the
-application does not enable reloading for the test run. RSpec, parallel or
-forked runners, mutation execution, Rails system/browser tests, custom Rails
-test commands, generated tests, and reloading configurations are outside this
-release and produce diagnostics rather than a passing analysis.
+The first release supports serial Minitest and RSpec execution in plain Ruby
+projects and Rails applications. Rails lazy and eager loading are supported
+when the application does not enable reloading for the test run. Transactions
+and in-process specs are supported within the serial process policy. Parallel
+or forked runners, remote or threaded browser drivers, mutation execution,
+Rails system/browser tests, custom Rails test commands, generated tests, and
+reloading configurations are explicitly unsupported and produce diagnostics
+rather than a passing analysis.
 
 ## Library entry points
 
@@ -672,10 +865,15 @@ Branchproof::Records.id(name: "stable identity")
 
 `require "mcdc"` and `MCDC` are compatibility aliases for the same public
 namespace. The CLI is the supported way to run a complete analysis;
-`Branchproof::Project` exposes project selection and child-environment policy,
+`Branchproof::Project` exposes project and framework selection and
+child-environment policy,
 and `Branchproof::RailsSupport` is the optional Rails boot boundary. The library
 classes expose the source, runtime, evidence, analysis, and report contracts
-for adapters and integrations.
+for adapters and integrations. `Branchproof::CoveragePolicy#call` evaluates a
+normalized `minimum` hash against a report document. `Report#coverage_policy`
+returns the recomputed policy record, and `Report#coverage_policy_lines`
+returns its terminal lines; both are available to integrations that need the
+same gate result as the CLI.
 
 ## Development
 
@@ -705,6 +903,10 @@ Run the commands with the Ruby executable you intend to validate. The checked
 release environments are CRuby 3.3.6 and 3.4.5. Each runtime
 must provide the declared Minitest 5.x and Prism 1.x dependencies.
 
+The repeatable native-versus-instrumented adapter benchmark and its captured
+Ruby 3.4.7 result are in
+[`docs/benchmarks/rspec-adapter.md`](docs/benchmarks/rspec-adapter.md).
+
 ## License
 
 Branchproof is available under the [Apache License, Version 2.0](LICENSE.txt).

data/doc/Branchproof/Configuration.md

@@ -0,0 +1,28 @@
+# Class Branchproof::Configuration <a id="class-Branchproof-Configuration"></a>
+
+|  |  |
+| --- | --- |
+| **Inherits** | Object |
+| **Defined in** | lib/branchproof/configuration.rb |
+
+Loads and validates the project-local .branchproof.json policy.
+
+## Constants
+### `FIELDS` <a id="constant-FIELDS"></a> <a id="FIELDS-constant"></a>
+Not documented.
+
+### `FRAMEWORKS` <a id="constant-FRAMEWORKS"></a> <a id="FRAMEWORKS-constant"></a>
+Not documented.
+
+### `MINIMUM_CRITERIA` <a id="constant-MINIMUM_CRITERIA"></a> <a id="MINIMUM_CRITERIA-constant"></a>
+Not documented.
+
+### `PROJECTS` <a id="constant-PROJECTS"></a> <a id="PROJECTS-constant"></a>
+Not documented.
+
+### `SCHEMA_VERSION` <a id="constant-SCHEMA_VERSION"></a> <a id="SCHEMA_VERSION-constant"></a>
+Not documented.
+
+## Public Class Methods
+### `load(path:, root:, explicit: = false, disabled: = false)` <a id="method-c-load"></a> <a id="load-class_method"></a>
+Not documented.

data/doc/Branchproof/CoveragePolicy.md

@@ -0,0 +1,27 @@
+# Class Branchproof::CoveragePolicy <a id="class-Branchproof-CoveragePolicy"></a>
+
+|  |  |
+| --- | --- |
+| **Inherits** | Object |
+| **Defined in** | lib/branchproof/coverage_policy.rb |
+
+Evaluates configured coverage thresholds against the aggregate Analyzer
+coverage counts without relying on rounded percentage fields.
+
+## Constants
+### `COMPLETENESS_FIELDS` <a id="constant-COMPLETENESS_FIELDS"></a> <a id="COMPLETENESS_FIELDS-constant"></a>
+Not documented.
+
+### `CRITERIA` <a id="constant-CRITERIA"></a> <a id="CRITERIA-constant"></a>
+Not documented.
+
+## Public Class Methods
+### `normalize(minimum)` <a id="method-c-normalize"></a> <a id="normalize-class_method"></a>
+- **@raise** [ArgumentError]
+
+## Public Instance Methods
+### `call(document:)` <a id="method-i-call"></a> <a id="call-instance_method"></a>
+Not documented.
+
+### `initialize(minimum:)` <a id="method-i-initialize"></a> <a id="initialize-instance_method"></a>
+- **@return** [CoveragePolicy] a new instance of CoveragePolicy

data/doc/Branchproof/Evidence.md

@@ -44,3 +44,6 @@ Not documented.
 
 ### `snapshot()` <a id="method-i-snapshot"></a> <a id="snapshot-instance_method"></a>
 Not documented.
+
+### `test_phase_counts()` <a id="method-i-test_phase_counts"></a> <a id="test_phase_counts-instance_method"></a>
+Not documented.

data/doc/Branchproof/FocusedReport.md

@@ -12,7 +12,7 @@ Terminal renderings grouped around conditions or tests.
 Not documented.
 
 ## Public Instance Methods
-### `initialize(document:, view:, level:, missing_only: = false, coordinator: = nil)` <a id="method-i-initialize"></a> <a id="initialize-instance_method"></a>
+### `initialize(document:, view:, level:, missing_only: = false, coordinator: = nil, focus: = nil, top: = nil, selection: = nil)` <a id="method-i-initialize"></a> <a id="initialize-instance_method"></a>
 - **@return** [FocusedReport] a new instance of FocusedReport
 
 ### `render()` <a id="method-i-render"></a> <a id="render-instance_method"></a>

data/doc/Branchproof/Project.md

@@ -8,6 +8,9 @@
 Resolves the project policy used by the isolated analysis worker.
 
 ## Constants
+### `FRAMEWORKS` <a id="constant-FRAMEWORKS"></a> <a id="FRAMEWORKS-constant"></a>
+Not documented.
+
 ### `MODES` <a id="constant-MODES"></a> <a id="MODES-constant"></a>
 Not documented.
 
@@ -15,7 +18,7 @@ Not documented.
 Not documented.
 
 ## Public Instance Methods
-### `initialize(root:, mode: = "auto")` <a id="method-i-initialize"></a> <a id="initialize-instance_method"></a>
+### `initialize(root:, mode: = "auto", framework: = "auto")` <a id="method-i-initialize"></a> <a id="initialize-instance_method"></a>
 - **@raise** [ArgumentError]
 - **@return** [Project] a new instance of Project
 

data/doc/Branchproof/RSpecAdapter/ClassRunnerGuard.md

@@ -0,0 +1,11 @@
+# Module Branchproof::RSpecAdapter::ClassRunnerGuard <a id="module-Branchproof-RSpecAdapter-ClassRunnerGuard"></a>
+
+|  |  |
+| --- | --- |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Rejects additional class-level runner entry points.
+
+## Public Instance Methods
+### `run(*args)` <a id="method-i-run"></a> <a id="run-instance_method"></a>
+Not documented.

data/doc/Branchproof/RSpecAdapter/ContextLifecycle.md

@@ -0,0 +1,14 @@
+# Module Branchproof::RSpecAdapter::ContextLifecycle <a id="module-Branchproof-RSpecAdapter-ContextLifecycle"></a>
+
+|  |  |
+| --- | --- |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Keeps group-level hooks outside individual example ownership.
+
+## Public Instance Methods
+### `run_after_context_hooks(*args)` <a id="method-i-run_after_context_hooks"></a> <a id="run_after_context_hooks-instance_method"></a>
+Not documented.
+
+### `run_before_context_hooks(*args)` <a id="method-i-run_before_context_hooks"></a> <a id="run_before_context_hooks-instance_method"></a>
+Not documented.

data/doc/Branchproof/RSpecAdapter/DefaultDiscovery.md

@@ -0,0 +1,11 @@
+# Module Branchproof::RSpecAdapter::DefaultDiscovery <a id="module-Branchproof-RSpecAdapter-DefaultDiscovery"></a>
+
+|  |  |
+| --- | --- |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Restores CLI directory discovery when RSpec runs inside the worker.
+
+## Public Instance Methods
+### `configure(configuration)` <a id="method-i-configure"></a> <a id="configure-instance_method"></a>
+Not documented.

data/doc/Branchproof/RSpecAdapter/ExampleLifecycle.md

@@ -0,0 +1,11 @@
+# Module Branchproof::RSpecAdapter::ExampleLifecycle <a id="module-Branchproof-RSpecAdapter-ExampleLifecycle"></a>
+
+|  |  |
+| --- | --- |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Assigns observation phases while the reporter owns test registration.
+
+## Public Instance Methods
+### `run(*args)` <a id="method-i-run"></a> <a id="run-instance_method"></a>
+Not documented.

data/doc/Branchproof/RSpecAdapter/RunnerGuard.md

@@ -0,0 +1,11 @@
+# Module Branchproof::RSpecAdapter::RunnerGuard <a id="module-Branchproof-RSpecAdapter-RunnerGuard"></a>
+
+|  |  |
+| --- | --- |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Allows only the worker-owned native runner instance.
+
+## Public Instance Methods
+### `run(*args)` <a id="method-i-run"></a> <a id="run-instance_method"></a>
+Not documented.

data/doc/Branchproof/RSpecAdapter/UnsupportedRunner.md

@@ -0,0 +1,12 @@
+# Class Branchproof::RSpecAdapter::UnsupportedRunner <a id="class-Branchproof-RSpecAdapter-UnsupportedRunner"></a>
+
+|  |  |
+| --- | --- |
+| **Inherits** | ArgumentError |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Identifies runner capabilities that cannot produce supported evidence.
+
+## Public Instance Methods
+### `diagnostic_code()` <a id="method-i-diagnostic_code"></a> <a id="diagnostic_code-instance_method"></a>
+Not documented.

data/doc/Branchproof/RSpecAdapter.md

@@ -0,0 +1,47 @@
+# Class Branchproof::RSpecAdapter <a id="class-Branchproof-RSpecAdapter"></a>
+
+|  |  |
+| --- | --- |
+| **Inherits** | Object |
+| **Defined in** | lib/branchproof/rspec_adapter.rb |
+
+Bridges one serial RSpec run to Runtime lifecycle ownership.
+
+## Constants
+### `FORBIDDEN_OPTIONS` <a id="constant-FORBIDDEN_OPTIONS"></a> <a id="FORBIDDEN_OPTIONS-constant"></a>
+Not documented.
+
+## Attributes
+### `active_adapter` [RW] <a id="attribute-c-active_adapter"></a> <a id="active_adapter-class_method"></a>
+Returns the value of attribute active_adapter.
+
+### `runner_adapter` [RW] <a id="attribute-c-runner_adapter"></a> <a id="runner_adapter-class_method"></a>
+Returns the value of attribute runner_adapter.
+
+### `late_execution_error` [R] <a id="attribute-i-late_execution_error"></a> <a id="late_execution_error-instance_method"></a>
+Returns the value of attribute late_execution_error.
+
+### `tests` [R] <a id="attribute-i-tests"></a> <a id="tests-instance_method"></a>
+Returns the value of attribute tests.
+
+## Public Instance Methods
+### `enter_runner!(runner)` <a id="method-i-enter_runner-21"></a> <a id="enter_runner!-instance_method"></a>
+Not documented.
+
+### `example_finished(notification)` <a id="method-i-example_finished"></a> <a id="example_finished-instance_method"></a>
+Not documented.
+
+### `example_started(notification)` <a id="method-i-example_started"></a> <a id="example_started-instance_method"></a>
+Not documented.
+
+### `initialize(runtime:)` <a id="method-i-initialize"></a> <a id="initialize-instance_method"></a>
+- **@return** [RSpecAdapter] a new instance of RSpecAdapter
+
+### `reject_execution!(message)` <a id="method-i-reject_execution-21"></a> <a id="reject_execution!-instance_method"></a>
+- **@raise** [@run_error]
+
+### `run(test_files:, runner_args:, on_complete:, before_load: = nil, after_load: = nil, test_selection_explicit: = false)` <a id="method-i-run"></a> <a id="run-instance_method"></a>
+rubocop:disable-next Metrics/ParameterLists
+
+### `validate_runner!()` <a id="method-i-validate_runner-21"></a> <a id="validate_runner!-instance_method"></a>
+Not documented.