npm - @adbayb/stack - Versions diffs - 3.5.1-next.1792972153066.859e186 → 3.5.1 - Mend

@adbayb/stack 3.5.1-next.1792972153066.859e186 → 3.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (3) hide show

package/dist/index.js +1 -1
package/package.json +1 -1
package/skills/software-audit/references/checklist.md +1 -1

package/dist/index.js CHANGED Viewed

@@ -931,7 +931,7 @@ const createWatchCommand = (program) => {
 //#endregion
 //#region package.json
-var version = "3.5.1-next.1792972153066.859e186";
+var version = "3.5.1";
 //#endregion
 //#region src/index.ts

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@adbayb/stack",
-  "version": "3.5.1-next.1792972153066.859e186",
+  "version": "3.5.1",
   "description": "My opinionated JavaScript-based toolchain",
   "keywords": [
     "development",

package/skills/software-audit/references/checklist.md CHANGED Viewed

@@ -42,7 +42,7 @@ Rules: `software-design` reference `clean-code.md`.
 Rules: `software-design` reference `cohesion-coupling.md`, `software-design` reference `testing-refactoring.md`, and `software-design` reference `clean-code.md`.
 - Evidence: change impact/coupling (cycles, globals, hidden I/O, Demeter, surprise side effects, new third-party dependencies); deterministic tests, adapter contracts, and changed boundary/failure coverage; error convention/boundary mapping/query purity/absence; resource ownership, cancellation, retry/idempotency safety, and bounded workload.
-- Deltas: a diff that omits test files alone does not establish a coverage gap. Report missing changed-behavior coverage only after identifying the changed contract and inspecting the relevant suite to confirm that its boundary or failure behavior is untested; if that evidence is unavailable, record an investigation gap rather than a finding or score deduction. Untouched coverage gaps are not findings. Trace success, rejection, timeout/cancellation, duplicate/concurrent execution, and partial-failure paths when relevant; check final state, effect count, cleanup, and reported errors.
+- Deltas: a diff that omits test files alone does not establish a coverage gap. Before reporting one, identify a behavior contract changed by the reviewed diff; an audit-only finding about existing behavior does not make that contract changed. If no changed contract is in scope, do not report or deduct for absent coverage. For a changed contract, inspect the relevant suite to confirm its boundary or failure behavior is untested; if that evidence is unavailable, record an investigation gap rather than a finding or score deduction. Trace success, rejection, timeout/cancellation, duplicate/concurrent execution, and partial-failure paths when relevant; check final state, effect count, cleanup, and reported errors.
 ## G. Security