@cejel/cejel 0.6.3 → 0.6.5

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/README.md CHANGED
@@ -92,7 +92,7 @@ if (-not $expected -or $actual -ne $expected.ToLowerInvariant()) {
92
92
  ```
93
93
 
94
94
  > **Windows signing status:** `cejel-Windows-x86_64.exe` is intentionally unsigned in
95
- > 0.6.3 and may trigger Microsoft SmartScreen. The release build removes Node's inherited
95
+ > 0.6.5 and may trigger Microsoft SmartScreen. The release build removes Node's inherited
96
96
  > signature before SEA injection and fails unless Windows reports the result as `NotSigned`;
97
97
  > it does not ship an invalid signature. Before running it, verify `SHA256SUMS` and the
98
98
  > GitHub build-provenance attestation. Each binary also has an attached SPDX SBOM (the packages
@@ -116,7 +116,7 @@ docker run --rm --network=none -v "$PWD:/w" -w /w -v "$PWD/cejel:/cejel:ro" debi
116
116
  npx @cejel/cejel@latest .
117
117
  ```
118
118
 
119
- > **Distribution note:** Cejel `0.6.3` is the coordinated release version for npm,
119
+ > **Distribution note:** Cejel `0.6.5` is the coordinated release version for npm,
120
120
  > standalone binaries, Docker/OCI, GitHub Action, Homebrew, and MCP Registry. A GitLab CI
121
121
  > template and Code Quality export live in [`docs/gitlab-ci.md`](./docs/gitlab-ci.md).
122
122
 
@@ -187,16 +187,16 @@ gh attestation verify ./cejel-Windows-x86_64.exe -R BargLabs/cejel
187
187
  This is cryptographically signed provenance. It is distinct from Apple Developer ID or
188
188
  Microsoft Authenticode code-signing.
189
189
 
190
- **Docker / OCI.** The current container release is `0.6.3`:
190
+ **Docker / OCI.** The current container release is `0.6.5`:
191
191
 
192
192
  ```bash
193
- docker run --rm -i -v "$PWD:/workspace:ro" ghcr.io/barglabs/cejel:0.6.3
193
+ docker run --rm -i -v "$PWD:/workspace:ro" ghcr.io/barglabs/cejel:0.6.5
194
194
  ```
195
195
 
196
196
  The image defaults to `cejel-mcp` over stdio. To use the CLI instead:
197
197
 
198
198
  ```bash
199
- docker run --rm -v "$PWD:/workspace:ro" --entrypoint cejel ghcr.io/barglabs/cejel:0.6.3 .
199
+ docker run --rm -v "$PWD:/workspace:ro" --entrypoint cejel ghcr.io/barglabs/cejel:0.6.5 .
200
200
  ```
201
201
 
202
202
  The OCI image carries an SBOM of its base-image packages, maximum-mode build provenance, and a
@@ -299,8 +299,12 @@ prints that boundary on every successful verification.
299
299
  - `--rubric-pin <version>` — Explicit opt-in only: pin an alternate rubric instead of the
300
300
  calibrated public default. It
301
301
  accepts the calibrated version or any published prospective rubric
302
- (`witan-rubric-v18-prospective-*` through `v23`) and fails closed, naming what was accepted, on
303
- anything else. `v23` is prospective and uncalibrated, like every rubric after v17: the public
302
+ (`witan-rubric-v18-prospective-*` through `v26`) and fails closed, naming what was accepted, on
303
+ anything else. `v26` (`witan-rubric-v26-prospective-2026-10-14`) is prospective and uncalibrated:
304
+ it is the next calibration candidate, inherits v25 complete, inherits neither v23 nor v24, and
305
+ today scores exactly as v25 does. `v25` is prospective and uncalibrated: it inherits v22 and adds only credit for a
306
+ health or readiness route declared inline in an application file (see "What counts as a health or
307
+ readiness signal" below). `v23` is prospective and uncalibrated, like every rubric after v17: the public
304
308
  default (`WITAN_LAST_CALIBRATED_RUBRIC_VERSION`) is still `witan-rubric-v17-2026-07-24`, and v23
305
309
  inherits none of v17's precision, recall, or false-positive-rate figures. It inherits v22
306
310
  detector/scoring behavior and adds bounded A1 coverage-flag recognition (#276) plus per-signal
@@ -567,7 +571,7 @@ The OCI image is an alternative when Docker is the preferred execution boundary.
567
571
  the host path with the repository OpenClaw should allow Cejel to read:
568
572
 
569
573
  ```bash
570
- npx -y openclaw@latest mcp set cejel-oci '{"command":"docker","args":["run","--rm","-i","-v","/absolute/path/to/repo:/workspace:ro","ghcr.io/barglabs/cejel:0.6.3"]}'
574
+ npx -y openclaw@latest mcp set cejel-oci '{"command":"docker","args":["run","--rm","-i","-v","/absolute/path/to/repo:/workspace:ro","ghcr.io/barglabs/cejel:0.6.5"]}'
571
575
  npx -y openclaw@latest mcp doctor cejel-oci --probe
572
576
  ```
573
577
 
@@ -635,6 +639,27 @@ belongs to:
635
639
  `test` script's content against known test-runner invocations rather than crediting it by key
636
640
  presence alone, so no separate disclosure line is needed for it.
637
641
 
642
+ ### What counts as a health or readiness signal
643
+
644
+ The "health or readiness signal" component of A3's production-readiness checks is filename-based
645
+ by design under the calibrated rubric (and every prospective rubric before `v25`). It is credited
646
+ for exactly these forms:
647
+
648
+ - a dedicated health or readiness file, such as `health.ts`, `healthcheck.js`, `readiness.py`
649
+ (the file must mention health or readiness);
650
+ - a `HEALTHCHECK` instruction in a root `Dockerfile`;
651
+ - Kubernetes liveness or readiness probes in a `k8s/`, `kubernetes/` or `helm/` manifest.
652
+
653
+ **A route declared inline in an application file does not count under the calibrated rubric**,
654
+ whatever its content: `app.get("/health", ...)` in `server.ts` or `app.ts` earns nothing there,
655
+ because the component never reads route text. The certificate states this next to the component.
656
+ Prospective `witan-rubric-v25-prospective-2026-10-12`, and `witan-rubric-v26-prospective-2026-10-14`
657
+ which inherits it, are the only rubrics that also credit an inline route, in the files the separate info-level "no health or readiness route" finding already reads
658
+ (under `src/`, `app/`, `lib/`, `packages/`, `functions/`, a repo-root `server`/`index`/`app`/`main`
659
+ file, or a `server/`, `backend/` or `api/` tree), with comments stripped and tests, docs, examples
660
+ and scripts excluded. Both are explicit opt-in (`--rubric-pin`), carry no precision or recall
661
+ claim, and have had no public paired rescore.
662
+
638
663
  ## Help validate Cejel
639
664
 
640
665
  Cejel does not collect telemetry. External validation is therefore opt-in and inspectable:
@@ -5,7 +5,7 @@ import {
5
5
  deriveProductIdentity,
6
6
  runCejelScan,
7
7
  serializeWitanReport
8
- } from "../chunk-FA72HEWJ.js";
8
+ } from "../chunk-7XQVE76B.js";
9
9
  import {
10
10
  listCejelLlmPackFiles
11
11
  } from "../chunk-M6YYPJSN.js";
@@ -5,7 +5,7 @@ import {
5
5
  renderWitanBadgeSvg,
6
6
  renderWitanHtmlReport,
7
7
  runCejelScan
8
- } from "./chunk-FA72HEWJ.js";
8
+ } from "./chunk-7XQVE76B.js";
9
9
  import {
10
10
  ZodFirstPartyTypeKind,
11
11
  ZodOptional,