@conarium-ai/core 0.2.47 → 0.2.49
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 +33 -0
- package/docs/claims/reviews/0.2.48.md +86 -0
- package/docs/claims/reviews/0.2.49.md +19 -0
- package/docs/claims/surfaces.json +5 -0
- package/package.json +3 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,38 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.49 - the registry entry carries a name and an address
|
|
4
|
+
|
|
5
|
+
Nothing in the tool changed. The MCP registry entry for this package carried
|
|
6
|
+
neither a display title nor a website, so directories and assistants reading
|
|
7
|
+
the registry showed the bare package name and never pointed anyone at
|
|
8
|
+
conarium.dev. `server.json` now sets both.
|
|
9
|
+
|
|
10
|
+
The correction needed a version of its own: the registry refuses to accept a
|
|
11
|
+
version number it already holds, and 0.2.48 was published. The claims review
|
|
12
|
+
for this release records an empty surface diff — the surface hash matches
|
|
13
|
+
0.2.48 byte for byte.
|
|
14
|
+
|
|
15
|
+
## 0.2.48 - the preprint is a claim surface
|
|
16
|
+
|
|
17
|
+
`paper/two-ledgers-one-window.md` joined `docs/claims/surfaces.json`. That
|
|
18
|
+
file ships in the tarball, so the number moves even though `paper/` does
|
|
19
|
+
not; v0.2.47 already holds the previous copy, and a tree that differs in
|
|
20
|
+
a shipped file from the tag it names is what `version_claim` refuses.
|
|
21
|
+
|
|
22
|
+
The preprint's text is CC BY 4.0 (`paper/LICENSE`); the software stays
|
|
23
|
+
MIT. The Zenodo record carries that licence. Nothing here changes a
|
|
24
|
+
tool.
|
|
25
|
+
|
|
26
|
+
**The Go verifier now exits like the Node verifier everywhere, not just
|
|
27
|
+
on the vectors.** Outside the thirteen frozen vectors, seven invocation
|
|
28
|
+
cases diverged: three usage exits (`--help`, no arguments, an unknown
|
|
29
|
+
flag), two missing targets (with and without an unrelated key flag),
|
|
30
|
+
valid JSON that is not JSONL, and directory mode beside a named
|
|
31
|
+
non-receipt JSON file. The finding, the differential guard that pins all
|
|
32
|
+
seven, and the fix are Iman Schrock's (EMILIA Protocol), PR #72. The
|
|
33
|
+
guard landed first and failed 7/7 against the unpatched tree; the fix
|
|
34
|
+
landed second and the same guard passes.
|
|
35
|
+
|
|
3
36
|
## 0.2.47 - a number for the paper and the kit
|
|
4
37
|
|
|
5
38
|
v0.2.46 is on npm. Two things that are not that package now exist in
|
|
@@ -0,0 +1,86 @@
|
|
|
1
|
+
# Claims review — 0.2.48
|
|
2
|
+
|
|
3
|
+
- base: v0.2.47
|
|
4
|
+
- head: 1375041
|
|
5
|
+
- surface: sha256:46439a314e3f75c085c3df6e910adf0ac4f8d1dce42c0c2a9b9f9f33600dd382
|
|
6
|
+
- verdict: pass
|
|
7
|
+
- reviewer: Claude. The only surface that changed is the one that joined:
|
|
8
|
+
`paper/two-ledgers-one-window.md` (229 lines), read in full against the
|
|
9
|
+
question the gate asks. Its claim-to-source table (`paper/CLAIMS.md`,
|
|
10
|
+
66 rows, 61 carrying `file:line`) was re-checked at the R2 gate on
|
|
11
|
+
23 August 2026; this review re-read the prose, not the table.
|
|
12
|
+
|
|
13
|
+
The number moved for one file: `docs/claims/surfaces.json` ships in the
|
|
14
|
+
tarball and now lists the preprint. `paper/` itself is outside the
|
|
15
|
+
tarball. No tool changed.
|
|
16
|
+
|
|
17
|
+
## Findings
|
|
18
|
+
|
|
19
|
+
### 1. paper/two-ledgers-one-window.md:221 — the package version was pinned to the wrong mechanism
|
|
20
|
+
|
|
21
|
+
- Claim: "version `0.2.46` (declared, from the repository `package.json` at the commit that carries this preprint)."
|
|
22
|
+
- Mechanism: `package.json` at the carrying commit.
|
|
23
|
+
- Why it falls short: at the carrying commit `package.json` says `0.2.48`. The sentence would have been false the moment the branch merged. `0.2.46` is right as the release the preprint describes and the archived snapshot covers; the provenance given for it was wrong.
|
|
24
|
+
- Disposition: reworded in `c555243` — "the release this preprint describes and the snapshot below covers; the repository at the commit that carries this preprint names a later number". `CLAIMS.md` row updated to the npm registry as the mechanism.
|
|
25
|
+
|
|
26
|
+
### 2. paper/two-ledgers-one-window.md:222 — the draft revision named was superseded on the day of merge
|
|
27
|
+
|
|
28
|
+
- Claim: "Individual Internet-Draft `draft-dogru-scitt-disclosure-evidence-06`".
|
|
29
|
+
- Mechanism: the datatracker.
|
|
30
|
+
- Why it falls short: `-07` was posted on 23 August 2026 (archive copy HTTP 200). Not false — `-06` exists — but a reader following the reference lands on `-07`, and the bib entry's note said the datatracker fetch had timed out.
|
|
31
|
+
- Disposition: `-07` in the markdown, the tex, the bib key and note, and `CLAIMS.md`, in `c555243`. The bib URL now points at the archive copy that was fetched.
|
|
32
|
+
|
|
33
|
+
### 3. paper/BUILD.md — "the PDF was not compiled here" was about to become a stale denial
|
|
34
|
+
|
|
35
|
+
- Claim: "The PDF was **not compiled** here. Do not read `paper/arxiv/main.tex` as a file that has been shown to build."
|
|
36
|
+
- Mechanism: a build.
|
|
37
|
+
- Why it falls short: true until today; a denial left standing after the fact is the pattern `standards/README.md` carried for two days after -04 posted. The tex was compiled on 23 August 2026 in a TeX Live container (pdflatex, bibtex, pdflatex x2): exit 0, 15 pages, 0 undefined references or citations.
|
|
38
|
+
- Disposition: `BUILD.md` records the build and the command in `c555243`. `paper/build/` stays ignored.
|
|
39
|
+
|
|
40
|
+
### 4. paper/two-ledgers-one-window.md:44 — the proposition pointed the reader the wrong way
|
|
41
|
+
|
|
42
|
+
- Claim: "Under assumptions A1–A7 below" — in the statement of Proposition 1.
|
|
43
|
+
- Mechanism: the assumptions section.
|
|
44
|
+
- Why it falls short: A1–A7 are stated in Section 3, above the proposition. "Below" sends a reader looking for text that is not there. Found on the pre-submission read of the compiled PDF.
|
|
45
|
+
- Disposition: "above", in the markdown and the tex. The same pass removed the ORCID placeholder from the title block, turned the bibliography's working notes ("opened", "confirmed on the abs page") into access dates, and removed every line that overflowed the margin (seven in the first build, none now).
|
|
46
|
+
|
|
47
|
+
## Second pass — the surface moved after the record was written
|
|
48
|
+
|
|
49
|
+
The record above was written at `1c92b89`. Four commits then touched the
|
|
50
|
+
surface (`1084309`, `2a2b63e`, `edf0bf7`, `b187859`) and the gate refused the
|
|
51
|
+
release, correctly: the review described a text that was no longer the one
|
|
52
|
+
about to ship. The head and hash above are the re-read. Nothing was published
|
|
53
|
+
in between.
|
|
54
|
+
|
|
55
|
+
### 5. standards/ADOPTION-EVIDENCE.md:20 — a list of figures was written as a ratio
|
|
56
|
+
|
|
57
|
+
- Claim: "at commit `a209864e`: 45 passed, 0 failed, 1 skipped over 75 cases."
|
|
58
|
+
- Mechanism: the Vaara conformance page, row #3.
|
|
59
|
+
- Why it falls short: the page writes the four figures as a list — "45 passed,
|
|
60
|
+
0 failed, 1 skipped, 75 cases" — and the three outcome counts sum to 46, not
|
|
61
|
+
75. "over 75 cases" invites a 45/75 reading the page does not state, and the
|
|
62
|
+
reading runs in our favour on a page another project maintains. Same class as
|
|
63
|
+
the prior-art row that was scored twice: the source's own units were replaced
|
|
64
|
+
with a stronger shape.
|
|
65
|
+
- Disposition: the page's phrasing restored, with the units named, in `1375041`.
|
|
66
|
+
|
|
67
|
+
### Read and not a finding
|
|
68
|
+
|
|
69
|
+
- **`paper` sections renumbered** (unnumbered abstract, 1–10). The one internal
|
|
70
|
+
cross-reference moved with them: "the artefacts of Section 9" resolves to
|
|
71
|
+
`## 9. Artefacts`. No stale pointer left.
|
|
72
|
+
- **"two propositions" → "one conditional impossibility result and two
|
|
73
|
+
normative principles"**, and 2a/2b relabelled Principles throughout. The
|
|
74
|
+
change narrows what the paper claims: 2a and 2b are MUST-shaped rules, and
|
|
75
|
+
calling them propositions asserted a standing no proof in the paper carries.
|
|
76
|
+
- **A5 and the proof sketch now hold `G`'s internal randomness and state equal
|
|
77
|
+
across the two worlds.** Without it the construction leaks: a randomised
|
|
78
|
+
signature would differ between worlds that agree on every row. The assumption
|
|
79
|
+
is now stated rather than used silently, which is a narrowing, not a claim.
|
|
80
|
+
- **"a conditional impossibility result under seven explicit assumptions, not
|
|
81
|
+
an unconditional completeness theorem"** replaces "a proposition, not a
|
|
82
|
+
theorem". Considered as a possible upgrade of standing, since the argument
|
|
83
|
+
below it is labelled a proof sketch. Not recorded as a finding: every step of
|
|
84
|
+
the sketch cites the assumption it uses, the label carries "conditional" and
|
|
85
|
+
names the assumption count, and the sentence exists to deny the stronger
|
|
86
|
+
reading rather than to invite it.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
# Claims review — 0.2.49
|
|
2
|
+
|
|
3
|
+
- base: v0.2.48
|
|
4
|
+
- head: 0a51b0c
|
|
5
|
+
- surface: sha256:46439a314e3f75c085c3df6e910adf0ac4f8d1dce42c0c2a9b9f9f33600dd382
|
|
6
|
+
- verdict: pass
|
|
7
|
+
- reviewer: Claude. No claim surface changed between v0.2.48 and this commit —
|
|
8
|
+
the surface hash is byte-identical to the one recorded for 0.2.48, and the
|
|
9
|
+
diff over the 24 surfaces is empty. The release carries version fields only
|
|
10
|
+
(`package.json`, `server.json`, `package-lock.json`); no source, no prose.
|
|
11
|
+
|
|
12
|
+
It exists for one reason: the registry entry fixed in #91 — a display title and
|
|
13
|
+
`websiteUrl: https://conarium.dev`, neither of which the entry carried — cannot
|
|
14
|
+
reach the MCP registry under an already-published version number. The registry
|
|
15
|
+
refuses a duplicate version, so the correction needs a version of its own.
|
|
16
|
+
|
|
17
|
+
## Findings
|
|
18
|
+
|
|
19
|
+
none
|
|
@@ -115,6 +115,11 @@
|
|
|
115
115
|
"path": "standards/ADOPTION-EVIDENCE.md",
|
|
116
116
|
"why": "Public on GitHub and linked from standards/README.md. Every row asserts what an outside party did with this draft; a row that overstates a citation as an adoption is the same overclaim the kind labels exist to prevent. Its first version carried one.",
|
|
117
117
|
"phrasing": true
|
|
118
|
+
},
|
|
119
|
+
{
|
|
120
|
+
"path": "paper/two-ledgers-one-window.md",
|
|
121
|
+
"why": "A preprint is read as the project's claim about what the method shows; it is the one surface that outlives the package.",
|
|
122
|
+
"phrasing": true
|
|
118
123
|
}
|
|
119
124
|
]
|
|
120
125
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@conarium-ai/core",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.49",
|
|
4
4
|
"mcpName": "io.github.dogrucanemek-alt/conarium",
|
|
5
5
|
"//files-artefakt": "Generated files under examples/ (private key, receipt/audit JSONL) are EXCLUDED. .gitignore does not bind npm: because the allow-list contained 'examples', `npm publish` on a machine that had run the demo was shipping _keys/audit-ed25519.pem (PRIVATE KEY) and the receipts. test/pack_artefakt.mjs locks this. The exclusions are LIMITED to examples/: receipts.jsonl and .pub.pem under test-vectors/ MUST ship, or a third party cannot run the conformance vectors.",
|
|
6
6
|
"//files": "Allow-list of what enters the package. Without it npm sent everything: 296 files / 1.5 MB — CI workflows, gitleaks config, a 137 KB marketing image, the site's api/chat.js. A bank security team opens the tarball and sees those. scripts/ is here ON PURPOSE: conarium-reconcile references scripts/pg-snapshot.sql at runtime; without it the user files a support mail.",
|
|
@@ -30,6 +30,8 @@
|
|
|
30
30
|
"!examples/**/conarium.tokens.json",
|
|
31
31
|
"!examples/starter-kit",
|
|
32
32
|
"!examples/starter-kit/**",
|
|
33
|
+
"!examples/missing-record-demo",
|
|
34
|
+
"!examples/missing-record-demo/**",
|
|
33
35
|
"conformance",
|
|
34
36
|
"test-vectors",
|
|
35
37
|
"!test-vectors/jcs/rfc8785",
|