@jinn-network/client 0.1.4-canary.fcbe7ade → 0.1.5-canary.14ebb386

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 CHANGED
@@ -2,6 +2,81 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
+ ## v0.1.5 — Operator App
6
+
7
+ _Released 2026-05-13_
8
+
9
+ # v0.1.5 — "Operator App"
10
+ 2026-05-13 · Suggested bump: patch (first npm `@latest` cut that ships the app-first operator experience)
11
+
12
+ ## Highlights
13
+
14
+ - Release plumbing fixed so the cut can actually ship. `npm-publish.yml` now installs `contracts/` before the operator gate, the Docker/GHCR workflow accepts the new `v<semver>` tag format alongside legacy `client-v*`, and the CHANGELOG mirror writes through a PR (no more failed direct push to protected `main`).
15
+ - SWE-rebench v2 verdict path is structurally correct end-to-end. The eval loop no longer emits verdicts on non-gradeable evals (uy6v.8), the daemon's `verdictCode` default is `Invalid`, not `Pass` (uy6v.7), evaluator-side gating now surfaces a real verdict so the reputation feedback hook fires (uy6v.10), and the `evaluation:<cid>` MetadataSet is published on verdict delivery (n93o).
16
+ - Per-operator disks no longer fill in a couple of weeks. The SWE-rebench v2 eval-image cache is bounded by an in-process LRU (uy6v.11).
17
+ - Operator app feedback on issue 188 addressed across overview / launcher / catalog / configuration / shell, with dashboard tests refreshed.
18
+ - Daemon execution envelope now carries the executor model (`gbut`), giving downstream consumers the model that produced each Solution / Verdict.
19
+ - Discovery API no longer 404s for just-launched manifests when no subgraph is configured (#170) — important for fresh launcher records.
20
+
21
+ ## Recovery context
22
+
23
+ v0.1.4 published as a GitHub Release at `fa8da678` but the npm-publish workflow failed before publish in `release:operator-gate` because contracts dependencies were not installed in the clean Actions checkout. The fix landed as PR #187 *after* the v0.1.4 tag was created, so the v0.1.4 release commit could not retry publish. v0.1.5 cuts from current `main` (`56e84952`) which includes that fix; `@jinn-network/client@latest` becomes `0.1.5` (replacing the stale `0.1.2`). v0.1.4 remains as a Build Notes Release; no `0.1.4` npm artifact exists.
24
+
25
+ ## Changes
26
+
27
+ ### feat
28
+ - (#189) feat(uy6v.11): bound swe-rebench-v2 eval-image cache with in-process LRU — @ritsuKai2000
29
+ - (#194) feat(gbut): publish executor.model in jinn.execution.v1 envelope — @ritsuKai2000
30
+
31
+ ### fix
32
+ - (#170) fix: /v1/solvernets/registry/:cid 404s for just-launched manifests when no subgraph is configured — @ritsuKai2000
33
+ - (#183) fix(uy6v.8): SWE-rebench v2 eval loop — no verdicts on non-gradeable evals; source-only patches — @ritsuKai2000
34
+ - (#185) fix(release): unblock v0.1.4 publish — @ritsuKai2000
35
+ - (#187) fix(release): install contracts before operator gate — @ritsuKai2000
36
+ - (#190) fix(uy6v.10): emit verdict in swe-rebench-v2 gating so reputation hook fires — @ritsuKai2000
37
+ - (#193) fix(uy6v.7): daemon verdictCode default — Invalid not Pass — @ritsuKai2000
38
+ - (#197) fix(n93o): publish evaluation:<cid> MetadataSet on verdict delivery — @ritsuKai2000
39
+
40
+ ### chore
41
+ - (#208) chore(2cl.20): bump client/package.json to 0.1.5 — @ritsuKai2000
42
+
43
+ ### docs
44
+ - (#165) docs: clarify terminal unresolved verdicts — @ritsuKai2000
45
+ - (#195) docs(uy6v.6): DR — keep self-eval bypass on testnet; revert is a mainnet gate — @ritsuKai2000
46
+
47
+ ### test
48
+ - (#168) test: Real-daemon Playwright e2e: lifecycle + operator catalog + empty states + crash recovery (scenarios 2-5) — scenarios 2-4 — @ritsuKai2000
49
+ - (#207) test: align verdict code fallback expectation — @ritsuKai2000
50
+
51
+ ### other
52
+ - (#192) [codex] address operator dashboard issue 188 feedback — @ritsuKai2000
53
+
54
+ ## Closed this week
55
+
56
+ - jinn-mono-uy6v.8 (SWE-rebench v2 eval loop — verdicts on non-gradeable evals)
57
+ - jinn-mono-uy6v.6 (DR — keep self-eval bypass on testnet)
58
+ - jinn-mono-uy6v.9 (Unscorable instances in dataset — quantified)
59
+ - jinn-mono-2cl.20.1 (Discovery-stack scope mismatch before release draft)
60
+
61
+ ## Stats
62
+
63
+ - Window: v0.1.4 → HEAD (2026-05-13)
64
+ - 14 commits · 72 files changed, 4444 insertions(+), 772 deletions(-) · 15 PRs · 1 contributor
65
+
66
+ ## Known issues
67
+
68
+ - jinn-mono-uy6v.7 (Live verdict-success + JINN reward distribution): in_progress. Verdict path is now structurally correct and emitting, but live observation of JINN reward distribution to operator wallets is still gating the v1 public-testnet ship (separate from this Build Notes cut).
69
+ - jinn-mono-uy6v.10 (Reputation-feedback hook): PR #190 makes the feedback hook fire on swe-rebench v2 verdicts; live on-chain registry update observation still pending closure.
70
+ - jinn-mono-uy6v.11 (Eval-image cache): PR #189 bounded the cache via in-process LRU; long-running operator disk validation still pending closure.
71
+
72
+ <!-- jinn-release-evidence:v1
73
+ release-tag=v0.1.5
74
+ release-commit=56e849525ebdbc8efc5a99a8255cead613ef7d80
75
+ release-client-prepare=passed
76
+ donation-consumption=passed
77
+ app-first-testnet-acceptance=passed
78
+ -->
79
+
5
80
  ## v0.1.4 — Shipping Machine
6
81
 
7
82
  _Released 2026-05-12_
@@ -1,6 +1,6 @@
1
1
  {
2
- "clientGitSha": "fcbe7adee1434f9e7ac73a814bb856750410e427",
2
+ "clientGitSha": "14ebb386ba49bc2752ca80f19969d67be6a40860",
3
3
  "codeDigest": "sha256:47a68c455a922bb81c327a1b03a6c74b24f9fdbe9dfff994d2d26007bfc329c3",
4
- "builtAt": "2026-05-13T21:27:46.118Z",
5
- "implVersion": "0.1.4-canary.fcbe7ade"
4
+ "builtAt": "2026-05-14T10:56:30.047Z",
5
+ "implVersion": "0.1.5-canary.14ebb386"
6
6
  }
@@ -1,3 +1,3 @@
1
1
  {
2
- "commit": "fcbe7adee1434f9e7ac73a814bb856750410e427"
2
+ "commit": "14ebb386ba49bc2752ca80f19969d67be6a40860"
3
3
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jinn-network/client",
3
- "version": "0.1.4-canary.fcbe7ade",
3
+ "version": "0.1.5-canary.14ebb386",
4
4
  "description": "Jinn protocol client — headless daemon for the restoration training loop",
5
5
  "type": "module",
6
6
  "packageManager": "yarn@4.13.0",