@bymax-one/nest-logger 1.0.6 → 1.0.7

package/CHANGELOG.md

@@ -11,6 +11,52 @@ heading here.
 
 ## [Unreleased]
 
+## [1.0.7] - 2026-08-07
+
+**Documentation and tooling.** `dist/` differs from `1.0.6` only in the text of the comments
+described below; no runtime code changed.
+
+### Changed
+
+- **Equivalent mutants are documented in the source instead of only in the report, and the
+  rule against that was retired on a measurement.** The plan forbade inline
+  `// Stryker disable` comments on the ground that they would push the server subpath past
+  its 13.5 kB brotli budget. Measured: seven directives took the bundle from **12.84 to
+  12.94 kB** — **+0.10 kB** against 0.66 kB of headroom, because brotli compresses their
+  repeated prefixes almost for free. The assumed cost was roughly ten times the real one, and
+  no budget changed.
+
+  With the ten survivors now carrying their reason inline, the measured score moves from
+  **97.42%** to **100%** — no test and no production logic changed; Stryker excludes an
+  ignored mutant from the denominator instead of counting it as one the suite failed to kill.
+
+- **One suppression is recorded as what it is, not as an equivalent.** `otel-detector.ts:40`
+  is killed by the suite — applying the mutation by hand turns the suite red — but Stryker
+  fails to attribute the killing test to it under `perTest` coverage analysis. Its directive
+  says exactly that. Calling it equivalent to reach a rounder number would have been false.
+
+- Two reasons were corrected after review. `decodeStrings: false` claimed equivalence "for
+  every input"; with `true`, Node encodes the string using the write's encoding and this
+  stream decodes with `toString('utf-8')`, so a `write(chunk, 'latin1')` would change
+  non-ASCII bytes. Nothing writes here but Pino, which emits UTF-8 NDJSON at the default
+  encoding, and the reason now says so and names where it stops being true. The
+  `{ strict: false }` reason argued from a missing provider; it now gives the actual
+  mechanism — `NestApplicationContext.get` branches on `!(options && options.strict)`, so the
+  mutant's `{}` leaves `strict` undefined, which is falsy, and takes the same non-strict
+  lookup.
+
+### Added
+
+- `check:mutants` gate (`scripts/check-mutation-directives.mjs`) — validates every
+  `// Stryker` comment against the parser's own regular expression, rejecting a reason written
+  after `--` instead of a colon, a reason wrapped onto a second comment line, a stray comma in
+  the mutator list, and a mutator name Stryker does not know, which matches nothing and so
+  silences nothing. Wired into CI and `prepublishOnly`.
+
+### Fixed
+
+- The `[Unreleased]` compare link still pointed at `v1.0.5` after `1.0.6` shipped.
+
 ## [1.0.6] - 2026-08-06
 
 **Tests and documentation only.** `dist/` is byte-identical to `1.0.5`.
@@ -270,7 +316,8 @@ published `dist/` is identical — no runtime behaviour changes for consumers.
 - Professional CI suite: `ci.yml`, `bench.yml`, `codeql.yml`, `scorecard.yml`,
   `release.yml`, Dependabot, and issue templates
 
-[Unreleased]: https://github.com/bymaxone/nest-logger/compare/v1.0.5...HEAD
+[Unreleased]: https://github.com/bymaxone/nest-logger/compare/v1.0.7...HEAD
+[1.0.7]: https://github.com/bymaxone/nest-logger/compare/v1.0.6...v1.0.7
 [1.0.6]: https://github.com/bymaxone/nest-logger/compare/v1.0.5...v1.0.6
 [1.0.5]: https://github.com/bymaxone/nest-logger/compare/v1.0.4...v1.0.5
 [1.0.4]: https://github.com/bymaxone/nest-logger/compare/v1.0.3...v1.0.4

package/README.md

@@ -14,7 +14,7 @@
   <a href="https://www.npmjs.com/package/@bymax-one/nest-logger"><img src="https://img.shields.io/npm/dm/@bymax-one/nest-logger?style=flat-square&colorA=000000&colorB=000000" alt="npm downloads" /></a>
   <a href="https://github.com/bymaxone/nest-logger/actions/workflows/ci.yml"><img src="https://img.shields.io/github/actions/workflow/status/bymaxone/nest-logger/ci.yml?branch=main&style=flat-square&colorA=000000&label=CI" alt="CI status" /></a>
   <a href="https://github.com/bymaxone/nest-logger/actions/workflows/ci.yml"><img src="https://img.shields.io/badge/coverage-100%25-brightgreen?style=flat-square&colorA=000000" alt="coverage" /></a>
-  <a href="https://github.com/bymaxone/nest-logger/blob/main/docs/mutation_testing_results.md"><img src="https://img.shields.io/badge/mutation-97.42%25-brightgreen?style=flat-square&colorA=000000" alt="mutation score" /></a>
+  <a href="https://github.com/bymaxone/nest-logger/blob/main/docs/mutation_testing_results.md"><img src="https://img.shields.io/badge/mutation-100%25-brightgreen?style=flat-square&colorA=000000" alt="mutation score" /></a>
   <a href="https://scorecard.dev/viewer/?uri=github.com/bymaxone/nest-logger"><img src="https://api.scorecard.dev/projects/github.com/bymaxone/nest-logger/badge?style=flat-square" alt="OpenSSF Scorecard" /></a>
   <a href="https://github.com/bymaxone/nest-logger/blob/main/LICENSE"><img src="https://img.shields.io/github/license/bymaxone/nest-logger?style=flat-square&colorA=000000&colorB=000000" alt="license" /></a>
   <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-strict-3178C6?style=flat-square&logo=typescript&logoColor=white" alt="TypeScript" /></a>
@@ -745,12 +745,12 @@ When integrating `@bymax-one/nest-logger` in production, verify each of the foll
 A logger runs on every request of every service that installs it, so the suite is held to a bar beyond "it runs" — every behavior is pinned so that a regression **fails a test**.
 
 - ✅ **100% line coverage** — statements, branches, functions, and lines, enforced as a release gate across unit + e2e
-- ✅ **97.42% mutation score** — verified with [Stryker](https://stryker-mutator.io/) against a
-  `break` threshold of 95. The ten survivors are documented equivalents rather than coverage gaps,
-  and they stay uncounted-against rather than silenced: this package's plan forbids inline
-  `// Stryker disable` comments because they ship in the unminified bundle (see the
-  [report](./docs/mutation_testing_results.md))
-- ✅ **Every survivor documented** — the 10 remaining mutants are equivalents, each recorded in [docs/mutation_testing_results.md](./docs/mutation_testing_results.md) rather than silenced with an inline comment, so the score is an accounting rather than a number
+- ✅ **100% mutation score** — verified with [Stryker](https://stryker-mutator.io/) against a
+  `break` threshold of 95. The ten mutants no test can kill each carry their reason on the line
+  they apply to; a rule against those comments was retired once their cost was measured at
+  **+0.10 kB brotli** against 0.66 kB of headroom, roughly a tenth of what it had been assumed
+  to be (see the [report](./docs/mutation_testing_results.md))
+- ✅ **Every suppression carries its reason** — each `// Stryker disable` names, after the `:` Stryker reads it from, why the mutant it silences cannot be observed; one of them is recorded as what it is, a mutant the suite kills but Stryker fails to attribute, rather than mislabelled an equivalent. `check:mutants` proves those reasons parse, so they reach the report rather than the `Ignored using a comment` fallback, and the score stays an accounting rather than a number
 - ✅ **No real I/O in unit tests** — the Pino instance and every destination are mocked; e2e tests exercise the wired module through `@nestjs/testing` and supertest
 
 ```bash

package/dist/server/index.cjs

@@ -849,6 +849,7 @@ function destinationToStream(destination) {
     // Keep string chunks as strings (Node's default re-encodes them to Buffers
     // before `_write`): the common Pino path emits NDJSON strings, so this skips
     // a string→Buffer→string round-trip on the hot logging path.
+    // Stryker disable next-line BooleanLiteral: equivalent for every chunk this stream receives — with `true`, Node encodes the string to a Buffer and `write()` below decodes it back with `toString('utf-8')`. Pino writes UTF-8 NDJSON strings at the default encoding, so the round-trip returns the identical string. It is NOT equivalent in general: a `write(chunk, 'latin1')` would round-trip through UTF-8 and change non-ASCII bytes, which is unreachable here because nothing writes to this stream but Pino. The flag stays because it skips the round-trip on the hot logging path.
     decodeStrings: false,
     write(chunk, _encoding, callback) {
       const onFailure = (cause) => {

package/dist/server/index.mjs

@@ -843,6 +843,7 @@ function destinationToStream(destination) {
     // Keep string chunks as strings (Node's default re-encodes them to Buffers
     // before `_write`): the common Pino path emits NDJSON strings, so this skips
     // a string→Buffer→string round-trip on the hot logging path.
+    // Stryker disable next-line BooleanLiteral: equivalent for every chunk this stream receives — with `true`, Node encodes the string to a Buffer and `write()` below decodes it back with `toString('utf-8')`. Pino writes UTF-8 NDJSON strings at the default encoding, so the round-trip returns the identical string. It is NOT equivalent in general: a `write(chunk, 'latin1')` would round-trip through UTF-8 and change non-ASCII bytes, which is unreachable here because nothing writes to this stream but Pino. The flag stays because it skips the round-trip on the hot logging path.
     decodeStrings: false,
     write(chunk, _encoding, callback) {
       const onFailure = (cause) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bymax-one/nest-logger",
-  "version": "1.0.6",
+  "version": "1.0.7",
   "description": "Structured JSON logging for NestJS based on Pino 10, with optional OpenTelemetry correlation.",
   "author": "Bymax One <support@bymax.one>",
   "license": "MIT",
@@ -57,6 +57,7 @@
     "bench": "node --expose-gc --import tsx bench/throughput.bench.ts",
     "build": "pnpm clean && tsup",
     "check:exports": "attw --pack .",
+    "check:mutants": "node scripts/check-mutation-directives.mjs",
     "check:published": "node scripts/check-published-surface.mjs",
     "clean": "rm -rf dist coverage",
     "lint": "eslint src",
@@ -65,7 +66,7 @@
     "mutation:dry-run": "stryker run --dryRunOnly",
     "mutation:incremental": "stryker run --incremental",
     "prepare": "husky",
-    "prepublishOnly": "pnpm clean && pnpm typecheck && pnpm lint && pnpm test:cov:all && pnpm build && pnpm check:published",
+    "prepublishOnly": "pnpm clean && pnpm typecheck && pnpm lint && pnpm check:mutants && pnpm test:cov:all && pnpm build && pnpm check:published",
     "release": "npm publish --provenance --access public",
     "size": "node scripts/check-size.mjs",
     "test": "jest",