Skip to content

fix: make scan coverage explicit and clarify usage - #58

Merged
lbb00 merged 1 commit into
mainfrom
fix/native-scan-integrity
Sep 17, 2026
Merged

lbb00 merged 1 commit into
mainfrom
fix/native-scan-integrity

Conversation

@lbb00

@lbb00 lbb00 commented Sep 15, 2026 •

Copy link
Copy Markdown
Member

Native file primitives could report zero when their globs matched no files, making a misplaced config or stale include path indistinguishable from a clean scan. This adds an optional min_files floor to file-length, file-bytes, and pattern-count. Successful non-quiet runs report the scanned file count and config root on stderr; that runtime metadata stays out of measurement documents and snapshots.

The CLI now accepts pawl measure --format json as the explicit spelling of its existing JSON document output, while continuing to reject --format text. pawl init links to the public recipe cookbook instead of naming a file that may not exist in an installed user's project. The pending Chinese README rewrite is included as requested; it clarifies measurement sources, gate modes, exit codes, and CI integration without adding language detection, presets, tool installation, or new adapters.

Pawl's passing-tests metric improved from 689 to 709 after adding the regression coverage. pawl record --only passing-tests advances that one baseline while preserving every other snapshot metric.

Test plan

  • gofmt -l .
  • go vet ./...
  • go test -v ./...
  • node --test npm/cli/test/*.test.js
  • node --test scripts/*.test.mjs
  • node scripts/demo-repro-check.mjs
  • node scripts/docs-version-check.mjs
  • python3 demo/scripts/test_eval_scripts.py
  • pawl check --format json

@github-actions

github-actions Bot commented Sep 15, 2026 •

Copy link
Copy Markdown

pawl CI · 28945be

Quality gate (pawl on pawl)

metric               baseline    current       Δ  status
------------------------------------------------------
file-length                 0          0      ±0  ✅ same
file-length-growth          0          0      ±0  ✅ same
file-bytes                  0          0      ±0  ✅ same
panics                      1          1      ±0  ✅ same
todo-markers                0          0      ±0  ✅ same
stray-prints                0          0      ±0  ✅ same
passing-tests             709        709      ±0  ✅ same
test-failures               0          0      ±0  ✅ same

✅ npm release packages validated (build + dry-run pack)

@lbb00
lbb00 force-pushed the fix/native-scan-integrity branch from d0fc025 to e92458b Compare September 16, 2026 02:43
@lbb00
lbb00 merged commit a4eb059 into main Sep 17, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant