cuke-dedup 0.5.0 → 0.7.0

package/CHANGELOG.md

@@ -5,6 +5,67 @@ All notable changes to CukeDedup are documented in this file. The project follow
 
 ## [Unreleased]
 
+## [0.7.0] - 2026-09-21
+
+### Changed
+
+- **Breaking (reports and baselines):** semantic fingerprints now use the first 128 bits of SHA-256 instead of FNV-1a-64. JSON and JSONL reports use schema version `3`, SARIF publishes `cukeDedupFingerprint/v3`, and semantic baselines use version `3`. Existing version `1` or `2` baselines are rejected for comparison and can be regenerated in place with `--update-baseline`.
+- Matcher compilation now runs in bounded windows instead of retaining every compiled matcher at once, substantially reducing peak memory on large definition corpora. Complete, untruncated runs retain the same findings; a run that exhausts its matcher-scan budget may become incomplete or retain a different bounded subset than v0.6.0.
+
+## [0.6.0] - 2026-09-18
+
+### Added
+
+- `assertionModules` names module specifiers whose `expect` export is a trusted assertion factory.
+  Use it for a local module that re-exports `expect`, or for a runner this build does not recognise
+  by name. Both `import` and `require` spellings honour the setting, including
+  `import * as fixtures from "./fixtures"` and `import fixtures = require("./fixtures")`. An
+  undeclared module stays untrusted, and a facade inferred from registration re-exports is not
+  trusted for assertions.
+
+### Changed
+
+- `vitest`, `chai` and `bun:test` join the recognised assertion factories. Importing `expect` from
+  one of them was previously *less* trusted than relying on an injected global, so explicit imports
+  were penalised: expected values did not count as behaviour and two steps asserting different
+  values could be offered as a `parameterization-candidate`. Chain recognition is shape-based, so
+  Chai's `expect(x).to.equal(y)` is read exactly as `expect(x).toBe(y)` is. **Reports can lose those
+  spurious findings on upgrade.**
+- A module-scoped constant now reaches the handler fingerprint, so two handlers reading the same
+  value through differently named constants are recognised as the same handler. A mutable `let`
+  stays unproven, a handler-local binding of the same name shadows the module constant, and a
+  constant declared inside another declaration's initializer is out of scope and never substituted.
+  A name captured from an enclosing scope is nearer than the module's, so a module constant never
+  substitutes over it. **Reports can gain findings on upgrade.**
+
+### Fixed
+
+- A function declared in a handler and then called contributes its assertions to that handler, so
+  conflicting expected values inside it keep the handlers apart instead of surfacing as a
+  `parameterization-candidate`. Expansion is single level and terminates on recursion. It is
+  declined when the name is bound by anything else in the handler — another declaration, a variable,
+  a parameter, a catch binding, a `class`, an `enum`, or a reassignment — because a name-keyed lookup
+  cannot tell which body a shadowed call reaches, and expanding the wrong one would attribute
+  assertions the handler never runs. A transparent wrapper such as `(check)()` resolves the same
+  declaration a bare call does.
+
+### Known limitations
+
+- A module-scoped constant reaches the handler fingerprint only when it is declared **before** the
+  registrations that read it. Two handlers reading the same value through constants declared after
+  the `Given`/`When`/`Then` calls are not recognised as the same handler, so the duplicate is
+  missed. Moving the declarations above the registrations restores the finding.
+- A handler passed as a call expression, such as `Given("...", makeHandler())`, cannot be resolved
+  to a body and takes no part in the handler rules; it is reported as `dynamic or unsupported step
+  handler cannot be compared statically`. A handler reached through a member expression, such as
+  `Given("...", steps.run)`, is not compared either, and that case is silent. Inline functions —
+  arrow, `async`, `function` and generator — and a reference to a local function declaration are
+  all compared normally.
+- Step definitions registered through a default import or TypeScript's `import x = require(...)`
+  and called as a member, such as `cucumber.Given("...")`, are not discovered, so those files
+  contribute no definitions to any rule. Named imports, namespace imports (`import * as cucumber`),
+  renamed named imports and `require` destructuring are all recognised.
+
 ## [0.5.0] - 2026-09-16
 
 ### Added
@@ -223,6 +284,8 @@ Initial public release.
 - Native Cargo and npm distributions for eight supported targets.
 - A checksum-verified GitHub Action and an agent-oriented CukeDedup skill.
 
+[0.7.0]: https://github.com/figueiredoluiz/cuke-dedup/compare/v0.6.0...v0.7.0
+[0.6.0]: https://github.com/figueiredoluiz/cuke-dedup/compare/v0.5.0...v0.6.0
 [0.5.0]: https://github.com/figueiredoluiz/cuke-dedup/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/figueiredoluiz/cuke-dedup/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/figueiredoluiz/cuke-dedup/compare/v0.2.1...v0.3.0

package/README.md

@@ -136,7 +136,7 @@ steps:
     with:
       fetch-depth: 0
       persist-credentials: false
-  - uses: figueiredoluiz/cuke-dedup@v0.5.0
+  - uses: figueiredoluiz/cuke-dedup@v0.7.0
     with:
       path: .
       threshold: 5

package/SECURITY.md

@@ -5,11 +5,6 @@
 Security fixes are released for the latest published minor version. Before the first
 stable release, only the latest `0.x` release is supported.
 
-| Version | Supported |
-| --- | --- |
-| 0.2.x | Yes |
-| Older versions | No |
-
 ## Reporting a vulnerability
 
 Please do not open a public issue for a suspected vulnerability. Use

package/docs/ci-and-baselines.md

@@ -18,7 +18,7 @@ steps:
       fetch-depth: 0
       persist-credentials: false
 
-  - uses: figueiredoluiz/cuke-dedup@v0.5.0
+  - uses: figueiredoluiz/cuke-dedup@v0.7.0
     id: cuke-dedup
     with:
       path: .
@@ -101,8 +101,7 @@ cuke-dedup . --baseline .cuke-dedup-baseline.json --fail-on-new 3
 
 Baselines store sorted semantic fingerprints with multiplicity counts. Renames and unrelated line
 changes do not make a finding new, while an additional occurrence beyond the recorded count does.
-Version `1` baselines from CukeDedup 0.1 can be replaced by running the version `2` tool with
-`--update-baseline`; comparison rejects mismatched schemas.
+Version `1` and `2` baselines can be replaced by running the version `3` tool with `--update-baseline`; comparison rejects mismatched schemas and names the regeneration command.
 
 Updates reject `--changed-since` and are skipped after incomplete analysis or an operational error,
 preventing a partial scan from erasing accepted findings.

package/docs/configuration.md

@@ -134,6 +134,39 @@ Nested, asynchronous, generator, conditional, multi-statement, reordered, rewrit
 dynamically constructed wrappers cannot be inferred safely. Declare those names when they still
 take the matcher first and handler second.
 
+## Trusted assertion modules
+
+`assertionModules` names module specifiers whose `expect` export is a real assertion factory.
+
+CukeDedup recognizes `@playwright/test`, `playwright/test`, `@jest/globals`, `expect`, `vitest`,
+`chai`, and `bun:test` without configuration, and it also trusts the ambient `expect` that Jest,
+Vitest, and Playwright inject. Chain recognition is shape-based, so Chai's `expect(x).to.equal(y)`
+is understood exactly as Jest's `expect(x).toBe(y)` is; only the origin of the factory is listed.
+
+Declare a module when the factory reaches your steps another way:
+
+```json
+{
+  "assertionModules": ["./support/fixtures"]
+}
+```
+
+A local module that re-exports `expect` is the common case:
+
+```ts
+// support/fixtures.ts
+export { expect } from "@playwright/test";
+```
+
+Without the declaration, `expect` is untrusted, because the analyzer does not follow a local
+re-export back to its origin. An untrusted factory is not an error: its expected values simply stop
+counting as behaviour, so two steps asserting genuinely different values can be offered as a
+`parameterization-candidate`. Declaring the module restores the distinction. Both `import` and
+`require` spellings honour the setting.
+
+Trust only modules that really do expose an assertion factory. Declaring an unrelated module makes
+its call arguments semantically load-bearing and can manufacture similarity evidence.
+
 ## Custom parameter types
 
 `parameterTypes` maps a project-defined Cucumber Expression parameter type to the regular

package/docs/reports.md

@@ -23,7 +23,7 @@ Rule headings are bold cyan, paths are blue, error/warning labels are red/yellow
 
 ## JSON and HTML
 
-JSON schema version `2` contains:
+JSON schema version `3` contains:
 
 - Relative Unicode-aware source spans and severity.
 - Suppressions and semantic fingerprints.
@@ -43,7 +43,7 @@ byte-reproducible artifacts matter. The deterministic corpus census remains pres
 
 ## JSON Lines
 
-JSONL schema version `2` emits one compact record per finding and a final summary:
+JSONL schema version `3` emits one compact record per finding and a final summary:
 
 ```sh
 cuke-dedup . --reporters jsonl \

package/docs/safety-and-limitations.md

@@ -25,6 +25,16 @@ resource limits keep failures visible and bound the work performed.
   overlap witnesses.
 - Bounded fuzzy indexes preserve a deterministic sample in highly repetitive vocabularies but do
   not promise every possible pair after a work limit is reached.
+- A module-scoped constant declared *after* the registrations that read it is not resolved, even
+  though the handler body runs later and the value is initialized by then. Declaration order is the
+  conservative rule shared with handler-local constants, where a reference before the declaration is
+  a temporal-dead-zone error. The effect is a missed duplicate, never an invented one.
+- A handler produced by calling a generator function, such as
+  `Given('a step', (function* () { … })())`, is not compared. Calling a generator returns a
+  suspended object and never runs the body, so the registered handler is that object rather than a
+  function and its assertions never execute. Treating the suspended body as the handler's behaviour
+  would invent meaning the code does not have, so each such registration warns that the handler
+  cannot be compared statically and is excluded from handler rules.
 
 When analysis is incomplete, existing findings remain valid but the absence of a finding proves
 nothing. Machine reports expose the incomplete or truncated status. Pass `--fail-on-incomplete`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cuke-dedup",
-  "version": "0.5.0",
+  "version": "0.7.0",
   "description": "Static analysis for duplicate and reusable Cucumber step definitions",
   "type": "module",
   "bin": {
@@ -24,6 +24,8 @@
     "bump:version": "node scripts/release/bump-version.mjs",
     "pack:check": "npm pack --dry-run",
     "corpus:check": "node scripts/check/check-corpus.mjs",
+    "memory:check": "node scripts/check/check-memory.mjs target/release/cuke-dedup",
+    "duplication:check": "node scripts/check/check-duplication.mjs",
     "benchmark": "node scripts/benchmark/benchmark-analysis.mjs"
   },
   "engines": {
@@ -47,13 +49,13 @@
     "npm/platforms/*"
   ],
   "optionalDependencies": {
-    "cuke-dedup-darwin-arm64": "0.5.0",
-    "cuke-dedup-darwin-x64": "0.5.0",
-    "cuke-dedup-linux-arm64-gnu": "0.5.0",
-    "cuke-dedup-linux-arm64-musl": "0.5.0",
-    "cuke-dedup-linux-x64-gnu": "0.5.0",
-    "cuke-dedup-linux-x64-musl": "0.5.0",
-    "cuke-dedup-windows-arm64-msvc": "0.5.0",
-    "cuke-dedup-windows-x64-msvc": "0.5.0"
+    "cuke-dedup-darwin-arm64": "0.7.0",
+    "cuke-dedup-darwin-x64": "0.7.0",
+    "cuke-dedup-linux-arm64-gnu": "0.7.0",
+    "cuke-dedup-linux-arm64-musl": "0.7.0",
+    "cuke-dedup-linux-x64-gnu": "0.7.0",
+    "cuke-dedup-linux-x64-musl": "0.7.0",
+    "cuke-dedup-windows-arm64-msvc": "0.7.0",
+    "cuke-dedup-windows-x64-msvc": "0.7.0"
   }
 }