@conarium-ai/core 0.2.24 → 0.2.25

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.
Files changed (3) hide show
  1. package/CHANGELOG.md +47 -0
  2. package/README.md +31 -8
  3. package/package.json +2 -1
package/CHANGELOG.md CHANGED
@@ -1,5 +1,52 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.2.25 — 2026-08-17
4
+
5
+ A documented command was never installed. It was found by running the README on a
6
+ machine that had never seen this package — the one path no test had walked, because
7
+ every test walks it from the repository, where the paths resolve.
8
+
9
+ - **`npx conarium-anchor-service` resolves.** The countersigning endpoint was
10
+ documented in the README, shipped in the tarball as
11
+ `bin/conarium-anchor-service.mjs`, correctly shebanged, and fail-closed on
12
+ missing configuration. It was never listed in package.json `bin`, so npm looked
13
+ for a package by that name in the registry and answered E404 — for as long as
14
+ the file had existed. It is registered now; starting it without a token file or
15
+ a signing key exits 2 and names what is missing, as the README says it does.
16
+
17
+ - **Documented commands are checked against installed commands, both ways.**
18
+ `test/bin_claims.mjs` reads the `npx conarium-*` invocations out of README,
19
+ SECURITY, LIMITATIONS and `docs/` and fails when one of them is absent from
20
+ package.json `bin`; it also asserts every registered bin exists and carries a
21
+ shebang. Neither list is restated in the test. A `stranger-install` CI job
22
+ installs the packed tarball into an empty directory and checks the opposite
23
+ direction — that every registered command resolves without asking the registry.
24
+ A loop over `bin` cannot catch an unregistered name, and an offline test cannot
25
+ see how npm resolves after install, so both directions are needed.
26
+
27
+ - **The README's commands run where the README puts them.** Four blocks were
28
+ command references written as if they were sequences. `conarium-init` writes keys
29
+ and config, not receipts, so three `conarium-verify` lines answered 20 on a file
30
+ that does not exist yet; `declaration.json` and the `pg_stat_statements`
31
+ snapshots are not generated either; the repository ships a
32
+ `conarium.config.json`, so `node bin/conarium-init.mjs` correctly refused to
33
+ overwrite it and exited 1; and `conarium-doctor` was placed before the step that
34
+ points the config at a DSN, so it reported the placeholder host unreachable. The
35
+ runnable commands now use the demo chain the reader downloaded in the section
36
+ above, and the exit codes are stated — including `--anchor-check` answering 14 on
37
+ a chain that ships without a sidecar, which is the intended answer, since an
38
+ absent anchor is not a verified one. The rest name their prerequisites instead
39
+ of implying they have none.
40
+
41
+ - **Policy pages no longer assert past their own inventory.** `privacy.html` said
42
+ "We never receive, see, or store your data or your customers' data" and then
43
+ itemised the waitlist email it stores, the chat it forwards to a third-party
44
+ model, and the host logs it keeps; `terms.html` made the same claim with no
45
+ itemisation at all. The self-hosted claim is true and kept, now scoped to what
46
+ it covers: the data Conarium governs never reaches us. `test/claim_discipline.mjs`
47
+ had been reading both files and could not see this, because it only knows
48
+ phrasings already caught — the phrasing is in it now.
49
+
3
50
  ## 0.2.24 — 2026-08-17
4
51
 
5
52
  Documentation that shipped with 0.2.23 still carried claims this project had
package/README.md CHANGED
@@ -110,14 +110,21 @@ npx conarium-init
110
110
 
111
111
  export CONARIUM_AUDIT_SIGNING_KEY=./audit-ed25519.pem
112
112
 
113
+ # init writes keys and config, not receipts: your own audit file does not exist
114
+ # until the gateway has served a query. The three commands below therefore run
115
+ # against the demo chain downloaded above, so they work as written — swap in
116
+ # your own sink (conarium.config.json → audit.sink) once it has records.
117
+
113
118
  # Verify a receipt chain (exit 0 = the records *in the file* are intact)
114
- npx conarium-verify ./receipts.jsonl --pubkey ./audit-ed25519.pub.pem
119
+ npx conarium-verify chain.jsonl --pubkey key.pem
115
120
 
116
121
  # Pin length / last hash if you need to catch records dropped from the end
117
- npx conarium-verify ./receipts.jsonl --pubkey ./audit-ed25519.pub.pem --expect-count 3
122
+ npx conarium-verify chain.jsonl --pubkey key.pem --expect-count 3
118
123
 
119
- # Optional: check OpenTimestamps sidecar (pending → exit 0 + warning; missing → 14)
120
- npx conarium-verify ./receipts.jsonl --pubkey ./audit-ed25519.pub.pem --anchor-check
124
+ # Check the OpenTimestamps sidecar. The demo chain ships without one, so this
125
+ # answers 14, deliberately not 0: an absent anchor is not a verified anchor.
126
+ # A sidecar that exists but is not yet confirmed → exit 0 with a warning.
127
+ npx conarium-verify chain.jsonl --pubkey key.pem --anchor-check
121
128
  ```
122
129
 
123
130
  A second verifier, Go and the standard library only, is in [`verifiers/go`](verifiers/go). `go build -o conarium-verify .` then the same arguments as `conarium-verify`; `test-vectors/` is the contract.
@@ -248,6 +255,12 @@ everywhere and would shred the output) and matches on Unicode word boundaries, s
248
255
  Receipts prove what went **through** the gateway. Reconciliation asks the database
249
256
  what it saw, and compares:
250
257
 
258
+ Neither command invents its inputs and `conarium-init` does not create them, so
259
+ both answer **20 (input missing)** until you have produced them: `declaration.json`
260
+ is your own period-and-scope statement ([`docs/RECEIPT-SPEC.md`](docs/RECEIPT-SPEC.md)
261
+ names the fields), and the two snapshots come from
262
+ [`scripts/pg-snapshot.sql`](scripts/pg-snapshot.sql).
263
+
251
264
  ```bash
252
265
  # One-sided: signed coverage declaration over a period + declared scope
253
266
  npx conarium-coverage ./declaration.json --pubkey ./audit-ed25519.pub.pem --receipts ./receipts.jsonl
@@ -286,13 +299,17 @@ The service is in this package, so you can run your own and sign your own heads
286
299
  above. What makes it worth anything is that the signer is not you.
287
300
 
288
301
  ```bash
289
- # Run the endpoint (refuses to start without a signing key or a token file)
302
+ # Run the endpoint. It refuses to start without a signing key or a token file:
303
+ # with neither present the three lines below exit 2 and name what is missing,
304
+ # which is the intended answer, not a failed install. Generating both is in
305
+ # deploy/anchor-service/.
290
306
  CONARIUM_ANCHOR_TOKENS=./anchor.tokens.json \
291
307
  CONARIUM_ANCHOR_SIGNING_KEY=./anchor.pem \
292
308
  CONARIUM_ANCHOR_BASE_URL=https://anchor.example.com \
293
309
  npx conarium-anchor-service
294
310
 
295
- # Verify a countersignature you were given — offline, no network, no package
311
+ # Verify a countersignature you were given — offline, no network, no package.
312
+ # record.json is what the endpoint returned to you; without it, exit 20.
296
313
  npx conarium-countersign-verify ./record.json --pubkey ./anchor.pub.pem
297
314
  # exit 0 = signature valid (and inclusion valid if a proof or --log-url was given)
298
315
  # exit 13 = signature invalid / unknown keyId
@@ -438,7 +455,11 @@ npm i @conarium-ai/core
438
455
  npx conarium-init
439
456
  export CONARIUM_AUDIT_SIGNING_KEY="$PWD/audit-ed25519.pem"
440
457
 
441
- # 3. Check the install before trusting it
458
+ # 3. Check the install before trusting it. Until step 4 points the config at a
459
+ # reachable DSN, doctor reports the placeholder host unreachable and exits 1.
460
+ # That FAIL is the check working, not the install being broken — it is the one
461
+ # thing a gateway must not be quiet about, because it keeps running with zero
462
+ # connectors and looks healthy while serving nothing.
442
463
  npx conarium-doctor
443
464
 
444
465
  # 4. Point the generated conarium.config.json at your read-only DSN,
@@ -459,7 +480,9 @@ its output is safe to paste into an issue.
459
480
  git clone https://github.com/dogrucanemek-alt/conarium.git
460
481
  cd conarium
461
482
  npm install && npm run build
462
- node bin/conarium-init.mjs
483
+ # The repository already ships a conarium.config.json, so init refuses rather
484
+ # than overwrite it (exit 1). Pass --force only if you want it regenerated.
485
+ node bin/conarium-init.mjs --force
463
486
  node bin/conarium-doctor.mjs --no-net
464
487
  npm start
465
488
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@conarium-ai/core",
3
- "version": "0.2.24",
3
+ "version": "0.2.25",
4
4
  "mcpName": "io.github.dogrucanemek-alt/conarium",
5
5
  "//files-artefakt": "examples/ altindaki uretilmis dosyalar (ozel anahtar, makbuz/denetim JSONL) ELENIR. .gitignore npm'i baglamaz: izin listesinde 'examples' oldugu icin demoyu kosturmus bir makinede 'npm publish' _keys/audit-ed25519.pem'i (OZEL ANAHTAR) ve makbuzlari yayinliyordu. test/pack_artefakt.mjs bunu kilitler. Elemeler examples/ ile SINIRLI: test-vectors/ altindaki receipts.jsonl ve .pub.pem YAYINLANMAK ZORUNDA, yoksa ucuncu taraf konformans vektorlerini kosturamaz.",
6
6
  "//files": "Pakete NE gireceginin izin listesi. Liste olmadan npm her seyi gonderiyordu: 296 dosya / 1.5 MB — CI workflowlari, gitleaks ayari, 137 KB pazarlama gorseli, sitenin api/chat.js dosyasi. Bir bankanin guvenlik ekibi tarball'i acip bunlari gorur. scripts/ BILEREK var: conarium-reconcile calisirken scripts/pg-snapshot.sql'e atif yapiyor, olmazsa kullanici destek maili yazar.",
@@ -75,6 +75,7 @@
75
75
  "conarium-coverage": "bin/conarium-coverage.mjs",
76
76
  "conarium-reconcile": "bin/conarium-reconcile.mjs",
77
77
  "conarium-stamp": "bin/conarium-stamp.mjs",
78
+ "conarium-anchor-service": "bin/conarium-anchor-service.mjs",
78
79
  "conarium-anchor-upgrade": "bin/conarium-anchor-upgrade.mjs",
79
80
  "conarium-console": "bin/conarium-console.mjs",
80
81
  "conarium-suggest-policy": "bin/conarium-suggest-policy.mjs"