memento-mori-jester 0.1.65 → 0.1.66

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.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,12 @@ All notable changes to Memento Mori Jester are tracked here.
4
4
 
5
5
  ## Unreleased
6
6
 
7
+ ## 0.1.66
8
+
9
+ - Added real-world preset fixtures for node, python, infra, and AI slices, growing the corpus to 160 fixtures.
10
+ - Added Kubernetes delete coverage for the infra preset, including a second firing and a read-only near-miss so thin and quiet-pass coverage stay clean.
11
+ - Refreshed demo, roadmap, fixture docs, and release notes for the expanded low-count preset coverage.
12
+
7
13
  ## 0.1.65
8
14
 
9
15
  - Added matched-pass fixtures for low-severity `vibes-based-plan` and `handwave-final` rule boundaries.
package/ROADMAP.md CHANGED
@@ -6,6 +6,7 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
6
6
 
7
7
  ## Recently Shipped
8
8
 
9
+ - Real-world low-count preset fixture batch in v0.1.66, adding node, python, infra, and AI examples while keeping thin, quiet-pass, and feasible pass-case gaps at zero.
9
10
  - Feasible pass-case fixture curation in v0.1.65, adding matched-pass examples for low-severity tone/planning rules and stopping curation from asking for impossible pass cases on hard rules.
10
11
  - Final thin-rule fixture precision pass in v0.1.64, clearing all remaining thin coverage gaps across built-in, structural, custom, configured sensitive-domain, and blocked-command rule families.
11
12
  - Framework custom-rule fixture precision pass in v0.1.63, clearing custom-rule thin coverage and reducing total thin fixture coverage from 16 rules to 7.
@@ -54,7 +55,7 @@ Memento Mori Jester is usable today as a CLI, MCP server, GitHub Action, and git
54
55
 
55
56
  ## Product Ideas
56
57
 
57
- - Collect real-world reports for the lowest-count preset slices: node, python, infra, and AI.
58
+ - Collect real-world reports for the next lowest-count preset slices: security, node, python, and web.
58
59
  - Add more framework-specific false-positive examples from real reports so tuning guidance keeps getting sharper.
59
60
  - Add a Markdown export for fixture reports so maintainers can paste coverage snapshots into issues or release notes.
60
61
 
package/docs/DEMO.md CHANGED
@@ -192,8 +192,8 @@ Project config: none loaded
192
192
  Fixture tuning evidence:
193
193
  Support: limited
194
194
  Confidence: medium
195
- Total fixtures checked: 154
196
- Weighted fixtures checked: 296.9
195
+ Total fixtures checked: 160
196
+ Weighted fixtures checked: 305.9
197
197
  Matching fixtures: 11
198
198
  Weighted matches: 23
199
199
  Expected-match weight: 18
@@ -202,7 +202,7 @@ Edge-case matches: 0
202
202
  Quiet-pass fixtures: 5
203
203
  Quiet-pass weight: 3.6
204
204
  By kind: command 0, plan 5, diff 5, final 1
205
- Fixture coverage: 11/154 (7.7% weighted)
205
+ Fixture coverage: 11/160 (7.5% weighted)
206
206
  By verdict: pass 0, caution 3, block 8
207
207
  Matched fixture samples:
208
208
  infra-public-ingress-block: Public ingress should block in low-risk-tolerance infra repos.
@@ -353,7 +353,7 @@ Preset packs:
353
353
 
354
354
  ## 13. Review Fixtures
355
355
 
356
- The fixture suite in `examples/fixtures/preset-review-cases.json` captures small real-usage examples with expected `pass`, `caution`, or `block` verdicts. It also includes matched-pass examples for low-severity rules, quiet-pass `absentRuleIds` examples that prove noisy rules stay silent for safe near-misses, stack-specific coverage for every built-in preset, quiet-pass boundaries across built-in, structural, custom, and preset/config-derived rules, second firing examples for preset blocked-command rules, and second examples for AI/API, framework custom, built-in, and configured sensitive-domain rules. These examples are run by `npm test`, so preset tuning changes stay visible.
356
+ The fixture suite in `examples/fixtures/preset-review-cases.json` captures small real-usage examples with expected `pass`, `caution`, or `block` verdicts. It also includes matched-pass examples for low-severity rules, quiet-pass `absentRuleIds` examples that prove noisy rules stay silent for safe near-misses, stack-specific coverage for every built-in preset, quiet-pass boundaries across built-in, structural, custom, and preset/config-derived rules, second firing examples for preset blocked-command rules, second examples for AI/API, framework custom, built-in, and configured sensitive-domain rules, and real-world low-count preset examples. These examples are run by `npm test`, so preset tuning changes stay visible.
357
357
 
358
358
  Maintainers can run `npm run fixtures:report` to see coverage by verdict, kind, preset, rule family, and preset slice. The report also includes a `Curation next` section that points at the next useful fixture batch, such as thin rules, feasible pass-case evidence, rule-family gaps, or lower-count presets.
359
359
 
@@ -0,0 +1,37 @@
1
+ # Memento Mori Jester v0.1.66
2
+
3
+ This release follows the fixture report's real-world preset curation guidance. It adds practical examples for low-count node, python, infra, and AI slices while preserving the cleaned-up coverage baseline from v0.1.64 and v0.1.65.
4
+
5
+ ## What Changed
6
+
7
+ - Added 6 fixture cases, growing the corpus from 154 to 160 fixtures.
8
+ - Added quiet real-world examples for:
9
+ - Node focused test commands.
10
+ - Python focused pytest commands.
11
+ - AI retrieved-context schema validation plans.
12
+ - Added infra Kubernetes delete coverage for:
13
+ - `blocked-command-kubectl-delete`
14
+ - `custom-infra-production-change`
15
+ - Added a read-only `kubectl get` near-miss so the new infra rules immediately have quiet-pass boundary evidence.
16
+ - Kept thin rule coverage, quiet-pass gaps, and feasible pass-case gaps at zero.
17
+
18
+ ## Public Interface
19
+
20
+ - No CLI command changes.
21
+ - No config schema changes.
22
+ - No rule matching, scoring, or verdict behavior changes.
23
+ - No MCP, playground, GitHub Action, or npm publishing changes.
24
+
25
+ ## Release Validation
26
+
27
+ ```powershell
28
+ npm.cmd test
29
+ npm.cmd run demo:svg:check
30
+ npm.cmd run fixtures:report
31
+ npm.cmd run fixtures:report -- --json
32
+ npm.cmd run pack:dry
33
+ git diff --check
34
+ node .\dist\cli.js tune coverage --no-config
35
+ node .\dist\cli.js tune risky-domain --json --no-config
36
+ git diff | node .\dist\cli.js diff --fail-on block --subject "v0.1.66 low-count preset fixtures"
37
+ ```
@@ -21,6 +21,7 @@ Maintainer triage guidance lives in [docs/MAINTAINER_TRIAGE.md](../../docs/MAINT
21
21
  - Second firing examples for AI and API custom rules around provider keys, model-output execution, raw SQL, and webhook signature checks.
22
22
  - Second firing examples for remaining framework custom rules across security, infra, node, python, and web presets.
23
23
  - Second firing examples for remaining built-in and configured sensitive-domain thin rules, leaving no thin coverage gaps.
24
+ - Real-world low-count preset examples for node, python, infra, and AI workflows.
24
25
  - Fixture metadata like `weight` and `edgeCase` to support precision-weighted tuning evidence.
25
26
 
26
27
  ## Local Check
@@ -1377,6 +1377,46 @@
1377
1377
  "blocked-command-terraform-destroy"
1378
1378
  ]
1379
1379
  },
1380
+ {
1381
+ "id": "infra-kubectl-delete-command-block",
1382
+ "preset": "infra",
1383
+ "kind": "command",
1384
+ "description": "Kubernetes delete commands should block through the infra preset blocked-command path.",
1385
+ "content": "kubectl delete deployment checkout-api -n staging",
1386
+ "expectedVerdict": "block",
1387
+ "weight": 2,
1388
+ "expectedRuleIds": [
1389
+ "blocked-command-kubectl-delete",
1390
+ "custom-infra-production-change"
1391
+ ]
1392
+ },
1393
+ {
1394
+ "id": "infra-kubectl-delete-job-command-block",
1395
+ "preset": "infra",
1396
+ "kind": "command",
1397
+ "description": "A second Kubernetes delete command should keep kubectl delete coverage from being thin.",
1398
+ "content": "kubectl delete job stale-worker -n staging",
1399
+ "expectedVerdict": "block",
1400
+ "weight": 2,
1401
+ "expectedRuleIds": [
1402
+ "blocked-command-kubectl-delete",
1403
+ "custom-infra-production-change"
1404
+ ]
1405
+ },
1406
+ {
1407
+ "id": "infra-kubectl-get-command-pass",
1408
+ "preset": "infra",
1409
+ "kind": "command",
1410
+ "description": "Read-only Kubernetes inspection should not trip infra delete/apply checks.",
1411
+ "content": "kubectl get deployment checkout-api -n staging",
1412
+ "expectedVerdict": "pass",
1413
+ "weight": 2,
1414
+ "expectedRuleIds": [],
1415
+ "absentRuleIds": [
1416
+ "blocked-command-kubectl-delete",
1417
+ "custom-infra-production-change"
1418
+ ]
1419
+ },
1380
1420
  {
1381
1421
  "id": "sec-chmod-recursive-secrets-command-block",
1382
1422
  "preset": "security",
@@ -1626,6 +1666,20 @@
1626
1666
  "configured-sensitive-domain-production"
1627
1667
  ]
1628
1668
  },
1669
+ {
1670
+ "id": "node-test-run-command-pass",
1671
+ "preset": "node",
1672
+ "kind": "command",
1673
+ "description": "Focused Node test commands should give the node preset another realistic quiet command.",
1674
+ "content": "node --test test/cli.test.js",
1675
+ "expectedVerdict": "pass",
1676
+ "weight": 1,
1677
+ "expectedRuleIds": [],
1678
+ "absentRuleIds": [
1679
+ "blocked-command-npm-publish-force",
1680
+ "custom-node-install-script-change"
1681
+ ]
1682
+ },
1629
1683
  {
1630
1684
  "id": "python-json-loader-plan-pass",
1631
1685
  "preset": "python",
@@ -1652,6 +1706,20 @@
1652
1706
  "custom-python-eval-exec"
1653
1707
  ]
1654
1708
  },
1709
+ {
1710
+ "id": "python-pytest-command-pass",
1711
+ "preset": "python",
1712
+ "kind": "command",
1713
+ "description": "Focused pytest commands should give the python preset another realistic quiet command.",
1714
+ "content": "python -m pytest tests/test_loader.py",
1715
+ "expectedVerdict": "pass",
1716
+ "weight": 1,
1717
+ "expectedRuleIds": [],
1718
+ "absentRuleIds": [
1719
+ "blocked-command-pip-install-break-system-packages",
1720
+ "custom-python-eval-exec"
1721
+ ]
1722
+ },
1655
1723
  {
1656
1724
  "id": "web-safe-render-plan-pass",
1657
1725
  "preset": "web",
@@ -1792,6 +1860,20 @@
1792
1860
  "configured-sensitive-domain-eval"
1793
1861
  ]
1794
1862
  },
1863
+ {
1864
+ "id": "ai-retrieved-context-schema-plan-pass",
1865
+ "preset": "ai",
1866
+ "kind": "plan",
1867
+ "description": "Schema-checking retrieved context should give the AI preset another realistic quiet plan.",
1868
+ "content": "Validate retrieved context against a schema before allowlisted dispatch.",
1869
+ "expectedVerdict": "pass",
1870
+ "weight": 1,
1871
+ "expectedRuleIds": [],
1872
+ "absentRuleIds": [
1873
+ "custom-ai-user-controlled-tool-dispatch",
1874
+ "custom-ai-model-output-execution"
1875
+ ]
1876
+ },
1795
1877
  {
1796
1878
  "id": "sec-tls-verification-plan-pass",
1797
1879
  "preset": "security",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "memento-mori-jester",
3
- "version": "0.1.65",
3
+ "version": "0.1.66",
4
4
  "description": "A local court-jester sidecar for AI coding agents: review plans, commands, diffs, and final claims before they get too pleased with themselves.",
5
5
  "type": "module",
6
6
  "repository": {