sonicop 26.8.108 → 26.8.110

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: bbee17a19e72bf5b5dad03303c42be9905e5dfeef68faf8f1155b5f9910f3fac
-  data.tar.gz: d756a00e368f91dcf8c3ca4d2e0e9df85c0315638d1aaa0d653e6cfbb4d68648
+  metadata.gz: a00a7d0dc817fde927c8f9a5eb24db975f85aa2f4dda36ae1f7de548aa6557f6
+  data.tar.gz: 2c09e86e186f680c8f31cf5fd0e979fb974bc23ad173fa14e4f100f98dc95ce3
 SHA512:
-  metadata.gz: cdbfc78cb9c5f22948032627bd4dbcb6f28f9b044c69d2ee139cb16b598e928113e64d3d0267505d58160b000a9a66193456cd6943fb1f95b86f8c7d1699061d
-  data.tar.gz: 6d7cf795e8e02782a81c4f16a9e2805cbd93dc88daf25d175944aefeb3b1a06af405b64c1c720129bf8945a8eee7873882968d5649efa43670d0029094e991ae
+  metadata.gz: 786c6eb994b2d5020f9f035623ec0f54ab95ad3f0359f747efd0bf97fd1bd4cca00d21b7a652b483861aef2af80dabb18dea4185bf9320a214307c4ea8780a8a
+  data.tar.gz: 8c0b93e14e6e7a56f497cc55aad95ce730c681515f9e2f8d67efcfe3c8ae44d98dc8f5ab1bf9c25b60f6de0791b0ed077bc3df0b4a679d3c07416a731426c66d

data/CONFORMANCE.md

@@ -1,6 +1,6 @@
 # RuboCop conformance
 
-Snapshot date: 2026-08-14
+Snapshot date: per row — see the `Measured` column of *Results*
 Reference: RuboCop 1.89.0 on Ruby 4.0.6
 Configuration: RuboCop 1.89.0 built-in defaults (`--force-default-config`) on both sides
 
@@ -30,7 +30,11 @@ sequence in UTF-8` on it — and `test/ruby/test_file_exhaustive.rb` holds an of
 not valid UTF-8, which stops the JSON formatter from emitting a document. The comparison for that
 corpus therefore covers 7,464 of its 7,466 files.
 
-The **target file lists match exactly** on all five — not just the counts but the paths. That is
+The **target file lists match exactly** on all five — not just the counts but the paths, compared as
+sets: rubocop/rubocop (1,765), rails/rails (3,551), mastodon/mastodon (3,290), Homebrew/brew (2,179)
+and ruby/ruby (7,466), with nothing on either side of any of the five. Counts alone would not settle
+it — a set that loses one file and gains another keeps its count — so the check compares the sorted
+lists and reports what only one side holds. That is
 worth stating separately because file discovery is where a port silently diverges first: RuboCop
 never reads `.gitignore`, applies a shebang test only to extensionless files, descends through
 directory symlinks, and treats a hidden path by its *first* component rather than by any dot in it.
@@ -51,19 +55,47 @@ sonicop --force-default-config --format json
 
 ## Results
 
-| Corpus | Excess | Missing | Field differences |
-|---|---:|---:|---|
-| rubocop/rubocop | 0 | 0 | none |
-| rails/rails | 0 | 0 | none |
-| mastodon/mastodon | 0 | 0 | none |
-| Homebrew/brew | 263 | 997 | none |
-| ruby/ruby | 142 | 585 | 5 |
-
-Three of the five agree offense for offense — RuboCop's own tree, Rails and Mastodon — with no
-excess, no shortfall and no metadata differences anywhere.
-
-Homebrew's remaining difference is entirely `Lint/Syntax`; every other cop matches exactly. Much of
-ruby/ruby's is too, with 117 of the 585 missing and 44 of the 142 excess being `Lint/Syntax` itself,
+The two kinds of difference are counted separately because they mean different things. A
+`Lint/Syntax` difference says the two disagree about whether a file parses, and everything else in
+that file follows from it; a difference in any other cop says the port reads the same tree and
+draws a different conclusion. Only the second is a defect in a cop.
+
+| Corpus | Excess | Missing | of which `Lint/Syntax` | Other cops | Field differences | Measured |
+|---|---:|---:|---|---:|---|---|
+| rubocop/rubocop | 0 | 0 | — | 0 | correctable ×1 | 2026-08-17 |
+| rails/rails | 0 | 0 | — | 0 | none | 2026-08-17 |
+| mastodon/mastodon | 0 | 0 | — | 0 | none | 2026-08-17 |
+| Homebrew/brew | 263 | 997 | **all of them** | **0** | none | 2026-08-17 |
+| ruby/ruby | 142 | 585 | 117 missing, 44 excess | 92 | 5 | 2026-08-16 |
+
+The last column is per row on purpose. A single date at the top of the file would say the five were
+measured together, and they were not: the first four are re-measured on every release, ruby/ruby is
+not — it is the one corpus whose reference cannot be produced in a single run (see above), so it is
+re-measured deliberately rather than routinely. Its row is the older of the two and should be read
+as such.
+
+**No cop other than `Lint/Syntax` differs on four of the five corpora**, Homebrew included: across
+its 2,179 files and 49,920 offenses the two agree on every position, message, severity and
+correctability that is not a syntax diagnostic.
+
+Homebrew's 1,260 differences — 997 missing and 263 excess — share one cause, and it is not a parser
+bug on either side. Homebrew is a Ruby 4.0
+codebase — `Library/Homebrew/.ruby-version` says `4.0.6` — but that file sits below the directory the
+run starts from, and `TargetRubyVersion` is only inferred from the working directory's ancestors. Both
+tools therefore fall back to the default of 2.7 (RuboCop says so itself: `Using Ruby 2.7 parser`) and
+both call `dry_run:,` — a hash value omission, valid since 3.1 — a syntax error. **Run the same corpus
+at 3.1 and both report zero `Lint/Syntax`.** What is left is not disagreement about which files parse:
+the file sets are identical, 569 on each side, and the first diagnostic in each file lands at the same
+position. Only the second and later diagnostics diverge, because the two parsers recover from the
+error differently — which is what puts offenses on both sides of the ledger rather than only on
+RuboCop's. Those are not chased; see *Known divergences*.
+
+What is checked here is that every one of the 1,260 is a `Lint/Syntax` offense, in both directions.
+What is not checked is which recovery produced which diagnostic: the 263 Sonicop reports and RuboCop
+does not have not been read one by one. They are accounted for as a class, not individually.
+
+Much of ruby/ruby's difference is the same shape,
+with 117 of the 585 missing and 44 of the 142 excess being `Lint/Syntax` itself,
 and the rest follows from it: a file the two disagree about is inspected by one tool and skipped by
 the other, so every offense in it lands on one side of the ledger. Counting that through, 635 of the
 727 differences sit in files one tool or the other calls a syntax error, and they are spread thinly
@@ -271,6 +303,14 @@ current list of what these corpora never exercise; the main ones are non-default
 values, extension plugins, and Windows line endings. Cops that never fire contribute nothing to a
 match count, and their silence is indistinguishable from agreement.
 
+That limit is not hypothetical, and one instance is now measured. `Style/HashSyntax` defaults
+`EnforcedShorthandSyntax` to `either`, under which neither tool reports anything; the port
+implements none of the other four values, so half the cop is missing. Both the corpus runs and a
+sweep of RuboCop's own specs report agreement for it, because both run at the default. A cop can be
+half absent and still match everywhere the default reaches. Where a cop's behaviour is selected by
+configuration, this document covers the default branch only — the others are neither measured nor
+claimed.
+
 The 215 cops RuboCop ships switched off are a limit of a different kind. They are implemented, but a
 default run never reaches them, so the corpus numbers above say nothing about them. What stands
 behind those is a separate measurement: the same corpora linted with all 609 cops switched on, on

data/Cargo.lock

@@ -742,7 +742,7 @@ checksum = "f8fadd59c855ef2080decdef8ff161eb6661b86933c9d82e5ba29dc602a55aba"
 
 [[package]]
 name = "sonicop"
-version = "26.8.108"
+version = "26.8.110"
 dependencies = [
  "anyhow",
  "assert_cmd",

data/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "sonicop"
-version = "26.8.108"
+version = "26.8.110"
 edition = "2024"
 rust-version = "1.85"
 description = "A fast, native RuboCop-compatible Ruby linter and formatter"

data/NOTICE

@@ -1,7 +1,153 @@
-Sonicop includes and adapts configuration data from RuboCop 1.89.0.
-RuboCop is Copyright (c) 2012-26 Bozhidar Batsov and contributors,
-licensed under the MIT License. See licenses/RUBOCOP.txt.
+NOTICE
 
-Sonicop links to owayo/tree-sitter-ruby, derived from tree-sitter-ruby.
-tree-sitter-ruby is Copyright (c) 2016 Rob Rix and contributors,
-licensed under the MIT License. See licenses/TREE_SITTER_RUBY.txt.
+sonicop is distributed under the MIT License (see LICENSE). It also carries
+material generated from, or copied verbatim out of, the projects listed below.
+Each is redistributed under its own licence, reproduced in full at the end of
+this file.
+
+This file is an inventory as much as an attribution: it records **what is taken,
+from where, and how to regenerate it**. Keeping it current is what makes the
+licence position checkable rather than remembered.
+
+  **Adding anything derived from another project means adding it here in the
+  same change.** This file was written only after a routine attempt to list what
+  we vendor turned up a corpus nobody had recorded -- the inventory found it,
+  not the attribution. An entry that is added late is an entry that was, for a
+  while, undocumented in a public repository.
+
+  Known to be coming: tests/fixtures/upstream_spec_cases.jsonl, which will hold
+  input text from RuboCop's specs. It is deliberately **not** listed yet -- this
+  file describes what is here now, not what is planned.
+
+================================================================================
+WHAT IS TAKEN
+================================================================================
+
+RuboCop -- https://github.com/rubocop/rubocop -- MIT
+  Copyright (c) 2012-26 Bozhidar Batsov
+
+  config/default.yml
+      The upstream configuration, taken verbatim at v1.89.0. It is the sole
+      source of truth for which cops exist and what their defaults are.
+      Regenerate: scripts/sync_default_yml.sh 1.89.0
+      Full text also kept at licenses/RUBOCOP.txt
+
+Ruby on Rails -- https://github.com/rails/rails -- MIT
+  Copyright (c) David Heinemeier Hansson
+
+Ruby -- https://github.com/ruby/ruby -- 2-clause BSDL
+  Copyright (C) 1993-2013 Yukihiro Matsumoto
+
+  Ruby is dual-licensed. Its COPYING offers a choice:
+
+      "You can redistribute it and/or modify it under either the terms of the
+       2-clause BSDL (see the file BSDL), or the conditions below"
+
+  **sonicop takes the 2-clause BSDL**, reproduced below. This is written down
+  because the alternative -- saying nothing -- leaves the next reader to work
+  out why the longer Ruby License is absent.
+
+Homebrew -- https://github.com/Homebrew/brew -- BSD 2-Clause
+  Copyright (c) 2009-present, Homebrew contributors
+
+  Rails, Ruby and Homebrew contribute to one file, together with RuboCop:
+
+  tests/fixtures/regexp_trees.jsonl
+      Every distinct regular-expression literal appearing in those projects'
+      Ruby sources, paired with the tree the `regexp_parser` gem builds for it.
+      It is the differential check for this port's own regexp scanner.
+      Corpora, commit hashes and the regeneration command are recorded in
+      tests/fixtures/regexp_trees.PROVENANCE.
+
+      Note: mastodon is **not** among the corpora. It is AGPL-3.0, and this
+      repository is MIT; the two are not obviously compatible, so it is left
+      out rather than reasoned about. Only permissively licensed corpora are
+      used, and dropping mastodon cost 218 of 10,966 patterns.
+
+tree-sitter-ruby -- https://github.com/owayo/tree-sitter-ruby -- MIT
+  Copyright (c) 2016 Rob Rix and contributors
+
+  Linked as a dependency (see Cargo.toml). sonicop uses a fork; the grammar
+  itself is derived from the original. Full text: licenses/TREE_SITTER_RUBY.txt
+
+================================================================================
+MIT License -- applies to RuboCop and to Ruby on Rails
+================================================================================
+
+Copyright (c) 2012-26 Bozhidar Batsov
+Copyright (c) David Heinemeier Hansson
+
+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.
+================================================================================
+2-clause BSDL -- applies to Ruby
+================================================================================
+
+Copyright (C) 1993-2013 Yukihiro Matsumoto. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+   notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+   notice, this list of conditions and the following disclaimer in the
+   documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.
+
+================================================================================
+BSD 2-Clause License -- applies to Homebrew
+================================================================================
+
+BSD 2-Clause License
+
+Copyright (c) 2009-present, Homebrew contributors
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+* Redistributions of source code must retain the above copyright notice, this
+  list of conditions and the following disclaimer.
+
+* Redistributions in binary form must reproduce the above copyright notice,
+  this list of conditions and the following disclaimer in the documentation
+  and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

data/README.ja.md

@@ -41,6 +41,10 @@ sonicop --show-cops
 ```
 
 **RuboCop 1.89 の全 609 Cop を実装しています。** 本家のレジストリと名前まで一致しており、
+ただしこれは**レジストリについての主張**であって、すべての設定についての主張ではありません。
+`Style/HashSyntax` は存在し既定の届く範囲では一致しますが、`EnforcedShorthandSyntax` の
+既定以外の 4 つの値はいずれも未実装です。**Cop は半分欠けたまま、既定の届く範囲では
+一致し続けられます** — [CONFORMANCE.md](CONFORMANCE.md) の *Limits* を参照してください。
 `Enabled: pending` の 159 個と `Enabled: false` の 56 個も含みます。この 215 個は本家でも
 既定の実行では走らないので、`--only` で名指しするか設定で有効にしてください。本家にも
 存在しない Cop 名だけをエラーにし、必要なら `--ignore-unrecognized-cops` で続行できます。
@@ -103,8 +107,26 @@ Style/StringLiterals:
 ```
 
 既存コマンドとの互換性を保つため、server/LSP/MCP、plugin、cache 系の引数も受理します。
-未対応の機能を要求する引数は互換 no-op として stderr に明示します。現在、サーバートランスポート、
-Ruby プラグイン実行、キャッシュ再利用、カスタム Cop、実装済み以外の Cop は実行しません。
+サーバートランスポート、Ruby プラグイン実行、キャッシュ再利用、カスタム Cop、実装済み以外の
+Cop は実行しません。
+
+そのうち大半は、その旨を出力します。`--server` / `--no-server` / `--lsp` / `--mcp` /
+`--plugin` は stderr に 1 行の注記を出します。cache 系は何も出しませんが、
+無言でよいのは片方だけです。
+
+- `--cache=false` はキャッシュを使わないことを求めるもので、sonicop はそれを満たしているため、
+  無言が正しい応答です。
+- `--cache=true` はキャッシュ再利用を求めるものですが、sonicop はこれを提供しておらず、
+  それでも無言です。
+
+Cop の設定値も後者と同じ挙動です。sonicop が実装していない設定値 — たとえば
+`Style/HashSyntax` の `EnforcedShorthandSyntax` — は**警告なしに無視されます**。
+名前を綴り間違えた設定値も同様に無視されます。つまり
+**offense が 0 件であることは、その設定が効いた証拠にはなりません**。
+無視された設定値と、違反の無いファイルが、同じ出力になるためです。
+
+Cop の*名前*は検査されます。設定ファイルに未知の Cop 名があれば、実行はエラーで止まります。
+素通りするのは、既知の Cop の中の設定値です。
 
 ### 適合性
 
@@ -114,8 +136,12 @@ Ruby プラグイン実行、キャッシュ再利用、カスタム Cop、実
 
 5 つのうち 3 つが**完全一致**です。RuboCop 自身のツリー（5,766 件）、Rails（167,760 件）、
 Mastodon（15,286 件）で、過剰も不足もメタデータ差もありません。対象ファイル一覧は 5 つすべてで
-一致します。残る差分は `Lint/Syntax` に集中しており、本家の LALR パーサが構文エラーから回復して
-出す追加診断を tree-sitter では再現できないことによるものです。autocorrect は RuboCop 自身のツリーと
+**件数だけでなくパスまで**一致します（集合として比較。どの側にも余りはありません）。
+残る差分は `Lint/Syntax` に集中しています。その大半は、本家の LALR パーサが
+構文エラーから回復して出す追加診断を tree-sitter では再現できないことによるもので、
+**これが説明するのは不足の向きだけ**です。**過剰の向きは別の問題で、未調査です** —
+Homebrew の 263 件はすべて `Lint/Syntax` であることまでは確認していますが、
+移植版だけが構文エラーと呼ぶその中身は調べていません。autocorrect は RuboCop 自身のツリーと
 Mastodon でバイト単位に一致します。この 2 つは死守ラインとして扱い、バイト一致が崩れた場合は
 既知差分ではなく退行として直します。
 
@@ -126,10 +152,15 @@ Mastodon でバイト単位に一致します。この 2 つは死守ライン
 
 適合性検証に使う 5 コーパスすべてで測定しました。両者とも同梱の既定設定
 （`--force-default-config`）で走らせているためプロジェクト側の `.rubocop.yml` は読まず、
-どのコーパスでも**対象ファイル一覧は完全に一致**しています。
+どのコーパスでも**対象ファイル数は一致**しています。この計測に必要なのはそこまでで、
+どちらの側も少なく検査してはいない、と言えます。パス単位の一致はより強い主張で、
+上の*適合性*の節で 5 つすべてについて示していますが、それは固定したリビジョンでの測定であって
+この速度計測の run そのものではありません。
 
 両者とも既定の全 Cop で走らせています。**同じ 394 Cop** が名前まで一致しているため、
 どちらも絞る必要がなく、素の実行がそのまま対等な比較になります。
+（394 は 609 から `Enabled: pending` の 159 個と `Enabled: false` の 56 個を除いた残りで、
+既定の実行はどちらの群にも届きません。）
 各値は暖機後 2 回の最速値です。
 
 | コーパス | ファイル | RuboCop 並列 | Sonicop 並列 | RuboCop 単一 | Sonicop 単一 |
@@ -147,8 +178,9 @@ Mastodon でバイト単位に一致します。この 2 つは死守ライン
 エンジンを測っていますが、並列はエンジンに加えて「その実行でスケジューリングがそのツリーに
 どれだけ噛み合ったか」を測っています。
 
-仕事を省いて速いわけではありません。この同じ 394 Cop について、RuboCop 自身のツリーと
-Mastodon では**すべての offense が一致**し、autocorrect もバイト単位で一致します。
+仕事を省いて速いわけではありません。この同じ 394 Cop について、RuboCop 自身のツリー・
+Rails・Mastodon の 3 つで**すべての offense が一致**します（計 188,812 件、どちらの側にも
+残りません）。autocorrect は前者と後者でバイト単位に一致します。
 
 再現時に注意が必要な点が 2 つあります。RuboCop は **`--cache false` と併用すると
 `--parallel` を黙って無効化します**。そのためここでの並列実行はキャッシュを有効にしたうえで

data/README.md

@@ -41,6 +41,10 @@ sonicop --show-cops
 ```
 
 **All 609 RuboCop 1.89 cops are implemented**, matched name for name against the upstream registry.
+That is a claim about the registry, not about every configuration: `Style/HashSyntax` is present and
+matches everywhere its default reaches, yet none of the four non-default values of its
+`EnforcedShorthandSyntax` are implemented. **A cop can be half absent and still match everywhere the
+default reaches** — see *Limits* in [CONFORMANCE.md](CONFORMANCE.md).
 That includes the 159 shipped as `Enabled: pending` and the 56 shipped as `Enabled: false`, which a
 default run does not reach on either side — name them with `--only` or switch them on in a
 configuration, exactly as with RuboCop. Unknown cop names still fail validation unless
@@ -111,9 +115,24 @@ Style/StringLiterals:
 ```
 
 The CLI accepts RuboCop's server/LSP/MCP, plugin, and cache flags to keep existing command lines
-parse-compatible. These flags are reported as compatibility no-ops when they request unsupported
-functionality. Sonicop does not currently provide server transports, Ruby plugin execution, cache
-reuse, custom Ruby cops, or cops outside the implemented set.
+parse-compatible. Sonicop does not provide server transports, Ruby plugin execution, cache reuse,
+custom Ruby cops, or cops outside the implemented set.
+
+Most of those flags say so. `--server`, `--no-server`, `--lsp`, `--mcp`, and `--plugin` each print
+a one-line notice on stderr. The cache flags print nothing, and only one of them is silent for a
+good reason:
+
+- `--cache=false` asks for no caching, which sonicop already satisfies, so silence is the correct
+  answer.
+- `--cache=true` asks for cache reuse, which sonicop does not provide, and it is silent anyway.
+
+Cop settings behave like the second case. A setting sonicop does not implement — for example
+`EnforcedShorthandSyntax` under `Style/HashSyntax` — is ignored without any warning, and so is a
+setting whose name is simply misspelled. **A run that reports no offenses is therefore not evidence
+that a setting took effect**, because an ignored setting and a clean file produce the same output.
+
+Cop *names* are checked: an unrecognised cop in a configuration file stops the run with an error.
+It is the settings inside a recognised cop that pass unvalidated.
 
 ### Conformance
 
@@ -124,8 +143,12 @@ column, length, message, severity and correctability.
 
 Three of the five match **exactly**: RuboCop's own tree (5,766 offenses), Rails (167,760) and
 Mastodon (15,286), with no excess, no shortfall and no metadata differences. The target file lists
-match exactly on all five. What remains is concentrated in `Lint/Syntax`, where RuboCop's LALR
-parser recovers from an error and emits diagnostics a tree-sitter parse cannot reconstruct.
+match exactly on all five — paths, not just counts, compared as sets. What remains is concentrated in
+`Lint/Syntax`. Most of it is RuboCop's
+LALR parser recovering from an error and emitting diagnostics a tree-sitter parse cannot
+reconstruct — that direction accounts for the shortfall. **The excess is a separate question and has
+not been investigated**; on Homebrew all 263 of it is `Lint/Syntax` too, but what Sonicop calls a
+syntax error there and RuboCop does not is unexamined.
 Autocorrect is byte-identical on RuboCop's own tree and on Mastodon, the two corpora held as a hard
 line: a change that breaks byte equality there is a regression, not a new known divergence.
 
@@ -136,10 +159,14 @@ measured at, and the two ways a measurement of this kind can mislead you.
 
 Measured over all five conformance corpora. Both tools were given their own bundled default
 configuration (`--force-default-config`), so neither reads the project's `.rubocop.yml`, and on every
-corpus the two resolve **the same file list**.
+corpus the two resolve **the same number of files** — which is what these timings need, since it
+means neither side is inspecting less. Path-by-path equality is a stronger claim, established under
+*Conformance* above for all five, but on the pinned corpus revisions rather than on these timing runs.
 
 Both tools run their full default set — **the same 394 cops**, matched name for name — so neither
-side is restricted and the comparison is like-for-like as it stands. Times are the fastest of two
+side is restricted and the comparison is like-for-like as it stands. (394 is what is left of the 609
+once the 159 RuboCop ships as `Enabled: pending` and the 56 it ships as `Enabled: false` are set
+aside; a default run reaches neither group on either side.) Times are the fastest of two
 warmed runs.
 
 | Corpus | Files | RuboCop parallel | Sonicop parallel | RuboCop single | Sonicop single |
@@ -158,7 +185,8 @@ else the machine was doing. Single-process measures the engines; parallel measur
 how well each one's scheduling happens to fit that tree on that run.
 
 The speed is not bought by skipping work: over those same 394 cops the two agree on **every offense**
-on RuboCop's own tree and on Mastodon, and autocorrect there is byte-identical.
+on RuboCop's own tree, on Rails and on Mastodon — 188,812 offenses with nothing on either side of the
+ledger — and autocorrect is byte-identical on the first and the last.
 
 Two details matter for reproducing this. RuboCop **silently turns `--parallel` off when combined
 with `--cache false`**, so its parallel runs here use a cache directory that is deleted before each

data/lib/sonicop/version.rb

@@ -2,5 +2,5 @@
 
 # Generated from Cargo.toml by `rake version:sync`. Do not edit by hand.
 module Sonicop
-  VERSION = '26.8.108'
+  VERSION = '26.8.110'
 end

data/src/config/loader.rs

@@ -11,7 +11,17 @@ pub(super) fn find_config(start: &Path) -> Option<PathBuf> {
         if candidate.is_file() {
             return fs::canonicalize(candidate).ok();
         }
-        if project_root.as_deref().is_none_or(|root| directory == root) {
+        // `break if dir == stop_dir || dir == FileFinder.root_level`
+        //
+        // **`stop_dir` が無いことは「止まらない」であって「止まる」ではない。**
+        // 上流の `find_project_dotfile` は `find_file_upwards(DOTFILE, target_dir, project_root)`
+        // で、`project_root` が nil のときは何とも一致しないので**ファイルシステムの根まで
+        // 昇る**。ここを `is_none_or` で書いていたため、Gemfile の無い木では最初の 1 段で
+        // 止まり、**`.rubocop.yml` がリポジトリ直下・コードが `lib/` という標準の配置で
+        // 設定が 1 つも効かなかった。**
+        //
+        // `ancestors()` は根で終わるので、`root_level` の側は自然に満たされる。
+        if project_root.as_deref() == Some(directory) {
             break;
         }
     }