@bymax-one/nest-ai-tokens 1.0.1 → 1.0.3

package/CHANGELOG.md

@@ -8,6 +8,63 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) and
 
 ## [Unreleased]
 
+## [1.0.3] - 2026-08-06
+
+### Fixed
+
+- **Every suppression reason was dropped from the mutation report.** All 249 `// Stryker
+  disable` directives in the source wrote their justification after `--`. Stryker reads a
+  directive with one regular expression, `/^\s?Stryker (disable|restore)(?: (next-line))?
+  ([a-zA-Z, ]+)(?::(.+)?)?/`, whose mutator list accepts letters, commas and spaces only
+  and which captures the reason exclusively after a colon. A `-` therefore closed the
+  mutator list and left the reason unmatched, so each directive still silenced its mutant
+  but the report recorded Stryker's fallback text, `Ignored using a comment`. The README
+  claimed the opposite — that every suppression carries its reason — and documented the
+  broken separator as the convention. The directives now use `<Mutator>: <reason>`, which
+  is the grammar the parser accepts, and the reasons reach the report.
+
+### 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 `--`, a reason wrapped onto a second comment line (the report keeps only
+  the first fragment), and a mutator name Stryker does not know, which would silence
+  nothing at all. Wired into CI and `prepublishOnly`. Stryker warns about the last case,
+  but only during a mutation run, which on this repo happens post-merge.
+
+### Changed
+
+- No runtime behaviour changed. `dist/` differs only in the text of those comments; the
+  server bundle moved from 38,096 to 38,145 B brotli, well inside its 40,000 B budget.
+
+## [1.0.2] - 2026-08-05
+
+### Fixed
+
+- **The module could not be initialised by a consumer at all.** `MeteringInterceptor` is
+  registered as a plain class provider, so Nest resolves its constructor — but only the
+  third parameter carried a token. Nest reads two separate metadata keys for this:
+  `self:paramtypes`, written by `@Inject()`, and `design:paramtypes`, written by
+  TypeScript. The published bundle is built by tsup/esbuild, and esbuild states it cannot
+  implement `emitDecoratorMetadata` because it does not replicate TypeScript's type
+  system — so the second key was never there. The first two parameters had neither, and
+  the container threw `Nest can't resolve dependencies of the MeteringInterceptor
+  (?, +, Symbol(BYMAX_AI_TOKENS_OPTIONS))` before any provider was created. Both now
+  carry `@Inject`.
+
+### Changed
+
+- `emitDecoratorMetadata` is `false` in `tsconfig.json`. It was `true`, which was never
+  true of the artifact: tsup prints `You have emitDecoratorMetadata enabled but
+  @swc/core was not installed, skipping swc plugin` on every build, and that warning had
+  been printed on every build of this package. Turning it off makes the source compile
+  the way the bundle is built, so a parameter that depends on reflected types now fails
+  where it is cheap to see.
+- The imports that existed only to feed that metadata are `import type` again. The lint
+  rule reported each one the moment the flag went off, which makes it a precise detector
+  for this defect: an import that is value-only because a constructor parameter needs its
+  type is an import that will not survive the bundle.
+
 ## [1.0.1] - 2026-08-04
 
 ### Removed
@@ -135,4 +192,6 @@ have regressed from. They are kept because the reasoning is worth having.
 
 [1.0.0]: https://github.com/bymaxone/nest-ai-tokens/releases/tag/v1.0.0
 [1.0.1]: https://github.com/bymaxone/nest-ai-tokens/compare/v1.0.0...v1.0.1
-[Unreleased]: https://github.com/bymaxone/nest-ai-tokens/compare/v1.0.1...HEAD
+[1.0.2]: https://github.com/bymaxone/nest-ai-tokens/compare/v1.0.1...v1.0.2
+[1.0.3]: https://github.com/bymaxone/nest-ai-tokens/compare/v1.0.2...v1.0.3
+[Unreleased]: https://github.com/bymaxone/nest-ai-tokens/compare/v1.0.3...HEAD

package/README.md

@@ -742,9 +742,11 @@ tests pass".
   system does, `check:runtime` loads every subpath from the packed tarball in ESM and
   CommonJS, and `check:published` compiles this README's snippets against `dist/`
 - ✅ **Every suppression carries its reason** — no coverage directives anywhere; each
-  `// Stryker disable` in the production source states, after `--`, why the mutant it
-  silences is unobservable from a unit test (an internal error context, a provider id
-  reached only through integration)
+  `// Stryker disable` in the production source states, after the `:` Stryker reads it
+  from, why the mutant it silences is unobservable from a unit test (an internal error
+  context, a provider id reached only through integration). `check:mutants` proves the
+  reasons parse, so they reach the mutation report instead of being replaced by
+  Stryker's `Ignored using a comment` fallback
 
 ```bash
 pnpm test          # unit tests

package/dist/prisma/index.cjs

@@ -276,7 +276,7 @@ function computePayloadHash(record) {
 // src/server/utils/hash-chain.ts
 function chainHash(prevHash, record) {
   return deriveIdempotencyKey({
-    // Stryker disable next-line StringLiteral -- empty-string fallback for null prevHash; tests only verify hash determinism and inequality, not the specific hash value for a genesis block
+    // Stryker disable next-line StringLiteral: empty-string fallback for null prevHash; tests only verify hash determinism and inequality, not the specific hash value for a genesis block
     prevHash: prevHash ?? "",
     id: record.id,
     content: computePayloadHash(record)

package/dist/prisma/index.mjs

@@ -274,7 +274,7 @@ function computePayloadHash(record) {
 // src/server/utils/hash-chain.ts
 function chainHash(prevHash, record) {
   return deriveIdempotencyKey({
-    // Stryker disable next-line StringLiteral -- empty-string fallback for null prevHash; tests only verify hash determinism and inequality, not the specific hash value for a genesis block
+    // Stryker disable next-line StringLiteral: empty-string fallback for null prevHash; tests only verify hash determinism and inequality, not the specific hash value for a genesis block
     prevHash: prevHash ?? "",
     id: record.id,
     content: computePayloadHash(record)