Everything you need to deploy with confidence.

CURRENT · EE 0.33.1 · 2026-08-07 EE 0.33.1 · CE 0.2.38 · agent-skill 0.2.36

The wiring release — eleven compliance options that nothing shipped could populate now receive values. They were reachable only in theory: the option existed, the engine read it, and no entry point ever wrote to it. The new entry points live in Community Edition, so EE 0.33.0 requires CE ≥ 0.2.37 — on an older CE the options stay unfed. Alongside it, the Zero-Data-Exfiltration claim was rebuilt as a positive register of 17 enumerated outbound paths rather than a blanket denial, so a reviewer can read what the process does contact instead of taking “nothing” on faith; and signature records now carry algorithm and backend frozen at the moment of signing, not re-derived later from whatever the current configuration happens to be. RFC 3161 trusted timestamping is now opt-in via NSAUDITOR_TSA_URL and was verified against a real timestamp authority on 2026-08-07 — it is opt-in, not a default, and it is an outbound call. Ed25519 suppression signing is still not reachable — no shipped entry point signs a suppression record. Matrix-neutral — all seven coverage matrices UNCHANGED and the plugin count UNCHANGED at 28 Enterprise plugins (27 of them cloud auditors), 55 overall. Paired CE 0.2.37 + agent-skill 0.2.35.

Previously — EE 0.32.11 (2026-08-05). The dependency-advisory gate was auditing the wrong tree. It ran its audit inside the maintainer’s development checkout and called the result the production closure. It now packs the tarball, installs it the way a customer does, and audits that. With both readings taken side by side: the development tree carried 25 advisories, 8 of them HIGH; the closure a customer installs carried 6, none HIGH. The two lists share 5 of 26 packages and zero high-severity ones — every one of the eight highs was development-only. A matching total is exactly what makes a wrong list read as right, so the gate now reconciles the two as sets and prints the package-for-package divergence on every run.

And it refuses to report clean until an advisory database has answered. With the audit taken offline the gate produced a well-formed zero — dependency counts non-zero, the summary reconciling against its own list — and printed a pass over a closure that really carried six. It now installs a pinned canary carrying a permanently published advisory and requires that advisory back; silence is an untrustworthy run, not a pass. It also prints which registry answered, because a canary proves liveness, not freshness.

SOC 2, enumerated in full — 10 covered / 4 partial / 37 out of scope = 51. Four AICPA criteria (CC7.4, CC7.5, A1.1, A1.3) appeared nowhere in the mapping data: silently non-enumerated, which is not the same thing as out-of-scope-with-a-reason. Each is now enumerated with an architectural reason and the operator-side evidence that closes it. No control changed status and no routing changed — this is enumeration completeness, not a coverage bump — and the other six matrices are unchanged. Separately, the Type II tables now state which mechanisms are reachable from a shipped entry point instead of presenting all of them as supported. 28 Enterprise plugins — 27 of them cloud auditors — 55 in total, the same seven frameworks — unchanged. Live-verified on the published bytes: 28 of 28 Enterprise plugins active, and a three-cloud scan wrote a 76-file evidence pack per cloud.

Previously — EE 0.32.9 (2026-07-29). An internal-provenance strip: a compliance report is a document a customer hands their auditor, and ours carried internal engineering identifiers — roadmap ids, internal release stamps, the name of an internal audit review — in finding titles, on the attestation cover page and in the chain-of-custody record; measured on a rebuilt three-cloud evidence pack, 686 unexplained internal-marker occurrences → 0 across 105 files, with a positive control in the same run (3,572 benign matches still detected). And a false-clean closure: when a cloud plugin could not start — optional SDK absent, credentials unusable — it refused to report, and that refusal evaporated one layer up, so the report came out byte-identical to one where the scanner ran and found nothing and ten controls read PASS. Every in-scope control of a cloud that could not be scanned now carries a fail-closed evidence gap, and an archived scan re-processed by a newer build WARNS instead of failing clean. Community Edition 0.2.34 fixed --out <dir> writing to the parent directory when the directory name contains a dot, made the MCP scan_cloud summary handle both spellings of the evidence-gap prefix, and stopped validate misreporting where plugins came from.

Upgrading — three things to know. (1) Coming from a build older than 0.32.9: the evidence-gap finding title changed, so suppression rules written against the old text stop matching. The direction is safe — findings resurface rather than hide — but it is silent, so re-check your suppression list against the new titles. (2) Re-scan rather than re-processing scans captured before 0.32.9; the engine warns when it is handed an older archive. (3) Your next SOC 2 report carries four additional out-of-scope rows — CC7.4, CC7.5, A1.1 and A1.3, each with its reason. Nothing you were passing has moved.