From 62c18cfddb0bd398cabae1a8a041b6d4107536f4 Mon Sep 17 00:00:00 2001 From: "Ioannis L." <44038245+blitzcrieg1@users.noreply.github.com> Date: Wed, 18 Nov 2026 16:31:06 +0200 Subject: [PATCH 1/2] release: prepare 0.13.0 Package the detection pass and both offline preflight scanners. Update the recorded CI counts and document the fingerprint change for recorder rollout. --- .github/ISSUE_TEMPLATE/bug_report.yml | 2 +- CHANGELOG.md | 13 +++++++++--- CLAUDE.md | 22 ++++++++------------ README.md | 8 +++---- apps/orchestrator/agentmetry/core/version.py | 2 +- 5 files changed, 25 insertions(+), 22 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 13869d7..e13e1d1 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -16,7 +16,7 @@ body: attributes: label: Agentmetry version description: 'Run: python -c "import agentmetry; print(agentmetry.__version__)"' - placeholder: "0.12.2" + placeholder: "0.13.0" validations: required: true - type: input diff --git a/CHANGELOG.md b/CHANGELOG.md index 1e68d9c..a5535c1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,11 @@ separately (currently `1.2.0`) and changes additively. ## [Unreleased] +## [0.13.0] + +This release improves how detection rules use successful tool outcomes and +adds offline preflight checks for repositories and Python wheels. + ### Added - **Repository execution preflight.** `agentmetry scan --preflight PATH` @@ -68,8 +73,9 @@ separately (currently `1.2.0`) and changes additively. executable (#51). - Credential-path patterns avoid repeated scans of hostile long input tokens. -This pass changes the ruleset fingerprint and requires a new dogfood period when -it ships. The provider-token redaction fixes shipped separately in 0.12.2. +The ruleset fingerprint is `01e0a0c3339f6d80`. Start a new dogfood period +when the recorder adopts this ruleset. The provider-token redaction fixes +shipped separately in 0.12.2. ## [0.12.2] - 2026-11-16 @@ -3064,7 +3070,8 @@ tamper-evident JSONL trail you own. - Agentmetry records the agents you wire in. It is not a CASB and does not see unmanaged ChatGPT or an IDE with hooks disabled. -[Unreleased]: https://github.com/blitzcrieg1/agentmetry/compare/v0.9.9...HEAD +[Unreleased]: https://github.com/blitzcrieg1/agentmetry/compare/v0.13.0...HEAD +[0.13.0]: https://github.com/blitzcrieg1/agentmetry/compare/v0.12.2...v0.13.0 [0.9.9]: https://github.com/blitzcrieg1/agentmetry/compare/v0.9.8...v0.9.9 [0.9.8]: https://github.com/blitzcrieg1/agentmetry/compare/v0.9.7...v0.9.8 [0.9.7]: https://github.com/blitzcrieg1/agentmetry/compare/v0.9.6...v0.9.7 diff --git a/CLAUDE.md b/CLAUDE.md index a83d1dd..cf78caa 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -58,16 +58,13 @@ also scored RED, on one and three untriaged `session-tool-burst` detections, and turned GREEN when those were triaged that day. The fingerprint did not move during the run. -**Decided by the maintainer on 2026-11-15: the freeze ends after the r/netsec -post on 2026-11-17.** By then the gate reads 11 of 4. The trigger is outside +**The maintainer ended this freeze after confirming the r/netsec post.** +The trigger was outside reports saying which rules matter: #431 (a Hugging Face forum critique of the token rule), #425 (an outside test of copied agent logins), and #433, where context-mode, a plugin with about 34k stars, routes shell commands through MCP -inputs the command detections cannot read. **Until then the list above stays -frozen**, because the post leans on the unchanged-ruleset line. Work may start -in a worktree before then; nothing merges to master, and the live recorder is -not updated, until the post is out. See "The detection pass" below for what -lands and how. +inputs the command detections could not read. The detection pass merged in +[#435](https://github.com/blitzcrieg1/agentmetry/pull/435) on 2026-11-18. That flip is worth knowing about. **A week scored red on untriaged detections can be rescued at any time**, because `assess` reads the disposition store @@ -101,7 +98,7 @@ fingerprint has not moved before opening any PR that touches ```bash apps/orchestrator/.venv/Scripts/python.exe -c "from agentmetry.core.audit.dogfood import ruleset_fingerprint; print(ruleset_fingerprint()[:16])" -# expect 15846a0915769d4a +# expect 01e0a0c3339f6d80 for the 0.13.0 source ``` Four of the five parked detection-precision bugs were fixed in 0.7.0 and are @@ -128,11 +125,10 @@ dogfood trail through the new rules and compare against the dispositions, so the false-positive drop on real traffic is measured rather than claimed. That figure replaces the green-week streak as the number worth quoting. -On the day it merges: record the new fingerprint in place of the one above, -restart the clock with `agentmetry dogfood --start --restart`, update the -recorder checkout, and change everything that quotes `15846a0915769d4a` or the -streak (the site's `DOGFOOD` constant and copy, the README, the skills). Then -release it as its own minor version. +When rolling out 0.13.0, update the recorder and verify its active fingerprint. +Restart the clock with `agentmetry dogfood --start --restart` after the new +ruleset is running. Update the site and skills after publication. Historical +results for fingerprint `15846a0915769d4a` belong to the previous ruleset. Files in `detection/` that are **not** frozen and are safe to edit: `disposition.py`, `live.py`, `live_store.py`, `benchmark.py`, `yaml_rules.py`, diff --git a/README.md b/README.md index bd3ed24..f5be9ca 100644 --- a/README.md +++ b/README.md @@ -158,10 +158,10 @@ These are the numbers from commands, not from a slide. Run `agentmetry benchmark` to check these expectations. The 14 rule IDs in the corpus include 13 published rules and the experimental rule. The Sigma generator also covers `host-subagent-swarm-burst` and `off-hours-activity`. -Expected collection: 2904 tests collected (`pytest --collect-only -q` from `apps/orchestrator`). The -[0.12.1 release PR's CI run](https://github.com/blitzcrieg1/agentmetry/actions/runs/43610018759) -on Python 3.12 reported 2443 passed and 19 skipped on Linux and macOS, -2456 passed and 6 skipped on Windows, and 83% line coverage on Linux +2904 tests collected (`pytest --collect-only -q` from `apps/orchestrator`). The +[detection pass CI run](https://github.com/blitzcrieg1/agentmetry/actions/runs/44312544675) +reported 2885 passed and 19 skipped on Linux, 2898 passed and 6 skipped on Windows, +and 84% line coverage on Linux (`pytest -q --cov=agentmetry --cov-report=term`). CI fails the coverage job under 78%. The corpus and the expectations live in [`apps/orchestrator/agentmetry/core/audit/detection/corpus/`](apps/orchestrator/agentmetry/core/audit/detection/corpus/). diff --git a/apps/orchestrator/agentmetry/core/version.py b/apps/orchestrator/agentmetry/core/version.py index 44c35ce..08bfe4f 100644 --- a/apps/orchestrator/agentmetry/core/version.py +++ b/apps/orchestrator/agentmetry/core/version.py @@ -10,4 +10,4 @@ from __future__ import annotations -__version__ = "0.12.2" +__version__ = "0.13.0" From fe967a4996877edff4e0c2520bec7914447a89c6 Mon Sep 17 00:00:00 2001 From: "Ioannis L." <44038245+blitzcrieg1@users.noreply.github.com> Date: Wed, 18 Nov 2026 16:33:08 +0200 Subject: [PATCH 2/2] release: sync the funding manifest with 0.13.0 --- funding.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/funding.json b/funding.json index e639b41..16ac797 100644 --- a/funding.json +++ b/funding.json @@ -15,7 +15,7 @@ { "guid": "agentmetry", "name": "Agentmetry", - "description": "AI coding agents run shell commands, edit files and call third-party tools hundreds of times an hour, largely unattended. What they actually did is recorded nowhere by default. The agent transcript is a conversation rather than a record of effects, the editor keeps no durable log, and endpoint security sees only that one process spawned another, which is what a coding agent looks like when it is working correctly.\n\nAgentmetry records what an agent did at the tool boundary, correlates sequences into detections, and writes a hash-chained JSONL trail the operator owns, forwarding into whatever SIEM they already run. It is local-first: there is no vendor cloud, and no telemetry reaches the maintainer. Tool arguments are hashed inside the hook process, so plaintext never crosses the wire.\n\nVerifiable as of 2026-11-16: version 0.12.2 on PyPI, Apache-2.0, a detection benchmark that runs at zero misses and zero false positives, MITRE ATT&CK and ATLAS mappings, and five SIEM adapters. Case and test counts are deliberately not quoted here, because they move every time somebody contributes. The README prints the current ones and a test checks that it still prints them correctly.\n\nFunding would go to making the format underneath it common rather than ours: a standalone agent session record specification, mappings into Elastic Common Schema, OCSF, Splunk CIM and Google SecOps UDM, and a conformance suite so a third party can verify their own mapping without reading our Python. The success condition is other vendors adopting the fields, including ones who compete with us.", + "description": "AI coding agents run shell commands, edit files and call third-party tools hundreds of times an hour, largely unattended. What they actually did is recorded nowhere by default. The agent transcript is a conversation rather than a record of effects, the editor keeps no durable log, and endpoint security sees only that one process spawned another, which is what a coding agent looks like when it is working correctly.\n\nAgentmetry records what an agent did at the tool boundary, correlates sequences into detections, and writes a hash-chained JSONL trail the operator owns, forwarding into whatever SIEM they already run. It is local-first: there is no vendor cloud, and no telemetry reaches the maintainer. Tool arguments are hashed inside the hook process, so plaintext never crosses the wire.\n\nVerifiable as of 2026-11-18: version 0.13.0 in source, Apache-2.0, a detection benchmark that runs at zero misses and zero false positives, MITRE ATT&CK and ATLAS mappings, and five SIEM adapters. Case and test counts are deliberately not quoted here, because they move every time somebody contributes. The README prints the current ones and a test checks that it still prints them correctly.\n\nFunding would go to making the format underneath it common rather than ours: a standalone agent session record specification, mappings into Elastic Common Schema, OCSF, Splunk CIM and Google SecOps UDM, and a conformance suite so a third party can verify their own mapping without reading our Python. The success condition is other vendors adopting the fields, including ones who compete with us.", "webpageUrl": { "url": "https://agentmetry.ai", "wellKnown": "https://agentmetry.ai/.well-known/funding-manifest-urls"