@eir-labs/coltrane 0.24.33 → 0.24.35

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.
@@ -0,0 +1,59 @@
1
+ {
2
+ "slug": "release-notes-v0",
3
+ "domain": "release",
4
+ "agent_slugs": [
5
+ "release-writer",
6
+ "release-note-verifier"
7
+ ],
8
+ "phases": [
9
+ {
10
+ "name": "write",
11
+ "chairs": [
12
+ {
13
+ "role": "write-note",
14
+ "agent_slug": "release-writer",
15
+ "depends_on": [],
16
+ "input_contract": [
17
+ "release-record"
18
+ ],
19
+ "output_contract": [
20
+ "release-note"
21
+ ],
22
+ "required_skills": [],
23
+ "turn_reserve": 4
24
+ }
25
+ ]
26
+ },
27
+ {
28
+ "name": "check",
29
+ "chairs": [
30
+ {
31
+ "role": "check-note",
32
+ "agent_slug": "release-note-verifier",
33
+ "depends_on": [
34
+ "write-note"
35
+ ],
36
+ "input_contract": [
37
+ "release-record",
38
+ "release-note"
39
+ ],
40
+ "output_contract": [
41
+ "release-note-verdict"
42
+ ],
43
+ "required_skills": [],
44
+ "turn_reserve": 4
45
+ }
46
+ ]
47
+ }
48
+ ],
49
+ "status": "draft",
50
+ "input_types": [
51
+ "release-record"
52
+ ],
53
+ "output_types": [
54
+ "release-note",
55
+ "release-note-verdict"
56
+ ],
57
+ "max_examine_rounds": 2,
58
+ "description": "Two registers of one release, written from a record compiled out of git and refused when the prose outruns it. The input is a release-record (src/releases.ts, compileReleases): the commits a tag carries, the law counts at both ends, and the surface that changed — tool slugs and arguments, CLI flags, environment variables, domain types as slug@version — with any surface it could not read named rather than silently empty. The writer seals a plain register for someone using coltrane and a formal one for someone auditing it, plus `claims`: every factual statement paired with the record path that supports it. The verify seat resolves each path against the record, adds any assertion that carries no evidence entry, names any surface change neither register mentions, and fails the note rather than letting it publish. A failing verdict re-runs the writer with the verdict fed back, up to max_examine_rounds. Both seats are TOOL-LESS by construction: everything true about a release is already in the record, which is what lets this standard run on a cheap chat-completions seat. It publishes nothing — the note is sealed to the ledger and the changelog reads it from there."
59
+ }