@agent-blueprint-protocol/verifier 0.7.0 → 0.7.1
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 +44 -0
- package/README.md +11 -4
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,50 @@
|
|
|
2
2
|
|
|
3
3
|
All notable public changes to `agent_blueprint_protocol` are documented here.
|
|
4
4
|
|
|
5
|
+
## [0.7.1] — 2026-09-16
|
|
6
|
+
|
|
7
|
+
### Changed — the toolchain enforces itself (hygiene release)
|
|
8
|
+
|
|
9
|
+
- The declared Elixir requirement is a supported range (`~> 1.19`: the
|
|
10
|
+
1.19 and 1.20 lines are admitted, and Mix refuses anything outside
|
|
11
|
+
the range at compile), and `config/config.exs` refuses any Erlang/OTP
|
|
12
|
+
major outside the supported set (27/28/29) before anything compiles.
|
|
13
|
+
The set was probed from the official precompiled build lists, not
|
|
14
|
+
assumed; the decision record ships as
|
|
15
|
+
`docs/adr/supported-otp-set.md`. The assert governs development and
|
|
16
|
+
CI only — the Hex archive does not ship `config/`, so package
|
|
17
|
+
consumers see no new requirement.
|
|
18
|
+
- CI exercises every lane of the supported matrix: Elixir 1.19 on
|
|
19
|
+
OTP 28, and Elixir 1.20 on OTP 27, 28, and 29 (the dev pin, mirrored
|
|
20
|
+
in the new `.tool-versions`). The four toolchain declarations — the
|
|
21
|
+
Elixir range, the supported-OTP set, the dev pin, and the CI lanes —
|
|
22
|
+
move together in one commit.
|
|
23
|
+
- A dependency-currency gate (`mix deps.currency`; decision record at
|
|
24
|
+
`docs/adr/dependency-currency-gate.md`) reds the battery on any
|
|
25
|
+
resolvable drift and never passes an unverified registry state.
|
|
26
|
+
dialyxir rides at its latest resolvable release.
|
|
27
|
+
- Clones are byte-identical on every platform: `.gitattributes`
|
|
28
|
+
disables line-ending conversion regardless of a machine's autocrlf
|
|
29
|
+
settings (Git for Windows defaults to rewriting LF to CRLF, which
|
|
30
|
+
would shift the byte-frozen digests). The repository tree was probed
|
|
31
|
+
for Windows checkout obstacles (reserved device names, forbidden
|
|
32
|
+
characters, case collisions, symlinks, path length): none found.
|
|
33
|
+
- Development documentation re-trued to the enforced-range story
|
|
34
|
+
(README, CONTRIBUTING, quickstart). No Livebooks ship in this
|
|
35
|
+
repository (probed — no notebook files and no `Mix.install`
|
|
36
|
+
anywhere), so no notebook cells were in scope. The npm kit version
|
|
37
|
+
moves with the Hex line under the version-sync gate; no kit behavior
|
|
38
|
+
changed.
|
|
39
|
+
|
|
40
|
+
For consumers nothing reachable changed: the library surface, the
|
|
41
|
+
conformance corpus, the registry, and the specification are
|
|
42
|
+
byte-identical to 0.7.0, and the Elixir floor widened (1.20 to 1.19),
|
|
43
|
+
never narrowed. The test suite is 917 tests (59 properties) at 100%
|
|
44
|
+
coverage. Corpus: 96 cases, digest
|
|
45
|
+
`sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry
|
|
46
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
|
|
47
|
+
digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
|
|
48
|
+
|
|
5
49
|
## [0.7.0] — 2026-09-14
|
|
6
50
|
|
|
7
51
|
### Changed — the npm kit moves to `@agent-blueprint-protocol/verifier`
|
package/README.md
CHANGED
|
@@ -26,7 +26,7 @@ and evidence retention.
|
|
|
26
26
|
```elixir
|
|
27
27
|
def deps do
|
|
28
28
|
[
|
|
29
|
-
{:agent_blueprint_protocol, "~> 0.7.
|
|
29
|
+
{:agent_blueprint_protocol, "~> 0.7.1"}
|
|
30
30
|
]
|
|
31
31
|
end
|
|
32
32
|
```
|
|
@@ -128,9 +128,16 @@ lands with a red-capable test.
|
|
|
128
128
|
|
|
129
129
|
## Development
|
|
130
130
|
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
131
|
+
The toolchain enforces itself: the declared Elixir range in `mix.exs`
|
|
132
|
+
(`~> 1.19` — Mix refuses anything outside it at compile) and the
|
|
133
|
+
supported-OTP set in `config/config.exs` (27/28/29 — the build refuses
|
|
134
|
+
any other OTP major before anything compiles; see the
|
|
135
|
+
[supported-OTP-set decision record](docs/adr/supported-otp-set.md)). CI
|
|
136
|
+
exercises every lane of that matrix: Elixir 1.19 on OTP 28, and Elixir
|
|
137
|
+
1.20 on OTP 27, 28, and 29 (the dev pin, mirrored in `.tool-versions`);
|
|
138
|
+
the full battery runs on the dev lane and tests plus the conformance
|
|
139
|
+
corpus on every lane. The four declarations — Elixir range, supported-OTP
|
|
140
|
+
set, dev pin, and CI lanes — move together in one commit.
|
|
134
141
|
|
|
135
142
|
```bash
|
|
136
143
|
mix deps.get
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@agent-blueprint-protocol/verifier",
|
|
3
|
-
"version": "0.7.
|
|
3
|
+
"version": "0.7.1",
|
|
4
4
|
"description": "Installable verifier for the Agent Blueprint Protocol: canonical-bytes, digest, signature, bounds, and conformance-corpus verification. Non-authorizing \u2014 evidence, never a decision.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|