@jinn-network/client 0.1.3-canary.e1853100 → 0.1.4-canary.1dcd368f

package/CHANGELOG.md

@@ -2,14 +2,117 @@
 
 ## Unreleased
 
-- Operator-app first-run polish (jinn-mono-mc24): a brand-new operator can run `jinn run` with no env var, no setup, no input.
-  - `jinn run` now auto-generates a keystore password if `JINN_PASSWORD` isn't set and `~/.jinn-client/keystore-password` doesn't already exist (mode 0600). Replaces the previous fatal-exit on missing env var.
-  - Daemon API server now starts BEFORE init/bootstrap; the operator panel auto-opens immediately and shows progress while init/bootstrap runs.
-  - New top-level loading screen in the SPA renders during init / `mode: 'uninitialized'`, with spinner + latest event status line + collapsible event log; transitions to the four-region App once `/v1/bootstrap` is ready.
-  - `ClaudeAuthCard` is now a "Sign in with Claude" button (in `bare` runtime mode); the daemon spawns `claude /login` server-side via the existing `buildLoginCommand` helper. Docker / container modes still surface the appropriate CLI command since the daemon can't reach the operator's host browser.
-  - Keystore password change is now a `SettingsCard` in the panel (`POST /v1/setup/change-password`). The existing `jinn keys change-password` CLI continues to work for scripted use.
-  - Removed the unreachable `KeystoreCreateCard` and `POST /v1/setup/keystore` endpoint (daemon now owns keystore creation; the panel observes).
-- Removed the `jinn quickstart` verb; `jinn run` now subsumes its zero-to-running flow (resolve/generate password, init wallet, bootstrap fleet, then start the daemon in the foreground). The corresponding MCP tool was renamed `jinn_run`. Existing scripts using `jinn quickstart` should switch to `jinn run`. (jinn-mono-zqm2)
+## v0.1.4 — Shipping Machine
+
+_Released 2026-05-12_
+
+2026-05-12 · Suggested bump: patch (Captain: override to vX.Y+1.0 if an epic closed in this window)
+
+### Highlights
+- Operator onboarding: `jinn run` now owns first-run setup, including keystore-password generation and app-driven Claude sign-in for bare-host operators.
+- Discovery API and hosted-subgraph removal: the client now follows the on-chain-first path from the merged 280n stack.
+- Engineering handbook v1: the shipping-machine SOP, release-note scaffold, cadence correction, and Run-mode chore conventions are now exercised by a real cut.
+- SWE-rebench v2 donation prep: package and gate work for donated execution-data consumption is included, with release gates run before publish.
+
+### Changes
+
+#### feat
+- (#63) feat(client): Phase A.2 plug-in surface — @jinn-network/restorer-sdk + Path 1 slot registry + 9 worked examples — @ritsuKai2000
+- (#139) feat(2cl.16): auto-close bd issues referenced in merged PR body — @ritsuKai2000
+
+#### fix
+- (#131) fix: purge canonical-plugin traces from operator surfaces (jinn-mono-l2zl.15.4.2) — @ritsuKai2000
+- (#132) fix(2cl.13): correct bd JSON field references in bd-mirror — @ritsuKai2000
+- (#147) fix: friday-triage.yml YAML parse error (embedded python dedent) — @ritsuKai2000
+- (#149) fix(2cl.19): Monday scaffold — squash-merge enumeration + stats line + closed-bd list — @ritsuKai2000
+
+#### refactor
+- (#153) refactor(280n): land #138/#150 hosted-subgraph removal stack — @ritsuKai2000
+
+#### chore
+- (#133) chore(2cl.6): dual-tag releases with v2026.MM.DD alongside v<semver> — @ritsuKai2000
+- (#135) chore(2cl.7): harden release gates without slowing canary — @ritsuKai2000
+- (#136) chore(2cl.15): allow .claude/skills/ to be tracked in git — @ritsuKai2000
+- (#137) chore(2cl.17): document Run-mode declaration convention — @ritsuKai2000
+- (#148) chore: drop bd-close-on-merge workflow (manual bd close suffices) — @ritsuKai2000
+- (#152) chore: prep v0.1.4 release — @ritsuKai2000
+
+#### docs
+- (#66) docs: reconcile Phase 1b roadmap under Phase A umbrella — @ritsuKai2000
+- (#128) docs: engineering handbook v1 design + engineering-substrate DR — @ritsuKai2000
+- (#146) docs: spec — realign GROWTH §3 around ecosystem builders on the leading open agentic harness + ERC-8004 — @oaksprout
+
+#### test
+- (#89) test(engine): cross-impl artifact-row invariant (jinn-mono-6ig7) — @ritsuKai2000
+
+#### other
+- (#61) Fix npm publish workflow Foundry setup — @ritsuKai2000
+- (#64) Phase A.1: corpus library + gating fix + manifest hygiene + sha256 cache + MCP rewiring — @ritsuKai2000
+- (#65) Automatic Base Sepolia earning setup migration — @ritsuKai2000
+- (#70) Growth skill stack: cluster-model, growth-watcher, twitter-strategy, growth-day, plus canon promotions — @oaksprout
+- (#71) [codex] Improve operator onboarding dashboard flow — @ritsuKai2000
+- (#72) [codex] Complete Task and SolverNet migration — @ritsuKai2000
+- (#73) growth-day auto-invokes stale feed routines + freshness stamps — @oaksprout
+- (#74) Glossary: JINN/veJINN casing rules; ignore growth recruitment docs — @oaksprout
+- (#75) [codex] Add one-click Claude Code install — @ritsuKai2000
+- (#76) [codex] Implement task-native SolverNet lifecycle — @ritsuKai2000
+- (#77) [codex] Implement prediction SolverNet v1 SDK surface — @ritsuKai2000
+- (#78) [codex] Deliver Prediction SolverNet task lifecycle phase — @ritsuKai2000
+- (#79) [codex] Add Prediction SolverNet Brier scoreboard — @ritsuKai2000
+- (#80) Prediction SolverNet operator UX diagnostics — @ritsuKai2000
+- (#81) [codex] Surface Prediction dashboard status — @ritsuKai2000
+- (#82) [codex] Add Network Tools prediction learner plugins — @ritsuKai2000
+- (#83) growth: 2026-05-04 recruit log + Tier A/B/C ranking for growth-day — @oaksprout
+- (#88) Operator app: Overview + Configuration page split (operator-shakedown) — @ritsuKai2000
+- (#90) growth-day: enforce active-sprint precondition + warm-contacts ladder — @oaksprout
+- (#91) Add jinn-adjacent cluster frame and Sprint #1 recruitment learnings — @oaksprout
+- (#93) SPEC: tokenomics; canonical-doc process via GitHub Discussions — @oaksprout
+- (#94) plugin: simplify claude-code-learner + decouple from Jinn vocabulary — @ritsuKai2000
+- (#95) growth: canonical restructure — populate §3, add GTM/channel/sprint sections, cluster-aware skills — @oaksprout
+- (#101) [codex] add jinn activity tabs — @ritsuKai2000
+- (#102) Agent-harness SolverNet: freeze-mode + SWE-rebench v2 + train/frozen leaderboard — @ritsuKai2000
+- (#104) growth: §3 niche+pitch+bridge rewrite, §6.1 token-tolerance rule (PMF-search refinement) — @oaksprout
+- (#106) growth: pin §7 currently-testing to swe-rebench v2 (follow-up to #104) — @oaksprout
+- (#107) growth: §3 tighten to OSS coding agent contributors + pin swe-rebench v2 + skill hardening — @oaksprout
+- (#108) growth + decision: lock swe-rebench v2 as the operational launch SolverNet (DR-2026-05-07-h) — @ritsuKai2000
+- (#109) Plan 4 Phase 0+1: capture envelope schema + OTLP receiver + scrub processors — @ritsuKai2000
+- (#111) growth: §5 Engage — three ways in → four ways in (contributor) — @oaksprout
+- (#112) Revise README for clarity and additional instructions — @oaksprout
+- (#121) brand: canonical introduction + stake-claiming voice rule — @oaksprout
+- (#123) [codex] Implement telemetry capture publish and readable donation path — @ritsuKai2000
+- (#124) Prepare SWE-rebench v2 donation flow for public testnet — @ritsuKai2000
+- (#125) Fix canary packaging and daemon liveness blockers — @ritsuKai2000
+- (#126) Prepare SWE donation flow for public testnet release — @ritsuKai2000
+- (#127) Fix SWE typed payload fallback validation — @ritsuKai2000
+- (#134) discovery: DiscoveryAPI interface + OnchainDiscoveryAPI floor + callsite migration — @ritsuKai2000
+- (#172) Fix Docker acceptance build context — @ritsuKai2000
+- (#184) Fix Docker testnet acceptance gate — @ritsuKai2000
+
+### Closed this week
+- jinn-mono-280n.1
+- jinn-mono-2cl.13
+- jinn-mono-2cl.15
+- jinn-mono-2cl.16
+- jinn-mono-2cl.17
+- jinn-mono-2cl.19
+- jinn-mono-2cl.6
+- jinn-mono-2cl.7
+- jinn-mono-9a4d
+- jinn-mono-pgjj
+- jinn-mono-uy6v.7
+
+### Stats
+- Window: client-v0.1.3 → HEAD (2026-05-12)
+- 122 commits · 1278 files changed, 189811 insertions(+), 37079 deletions(-) · 58 PRs · 2 contributors
+
+### Operator-facing notes
+- A brand-new operator can run `jinn run` with no env var, no setup, and no input; the daemon now generates a local keystore password when needed and opens the app while bootstrap continues.
+- Host operators sign in through the app with `Sign in with Claude`; Docker/container modes still surface the appropriate CLI command because the daemon cannot reach the operator's host browser.
+- The old `jinn quickstart` verb has been removed; `jinn run` is the supported zero-to-running path.
+
+### Known issues
+- The v1 public-testnet milestone (`jinn-mono-uy6v`) is not included in this cut; it remains the next major waypoint, with open P0 work still tracked separately.
+- This is a weekly patch Build Notes release, not a v1 graduation or the `jinn-mono-uy6v` milestone.
 
 ## 0.1.3
 

package/CONTRIBUTING.md

@@ -74,7 +74,7 @@ The `files` field in `package.json` ensures only `dist/`, `deployments/`, `READM
 
 ## Releases
 
-Use [RELEASING.md](./RELEASING.md) for the package bootstrap publish, npm trusted-publishing setup, canary/stable release flow, the fork-based operator gate (`yarn release:operator-gate`), the contracts release gate (`cd ../contracts && yarn test && forge install foundry-rs/forge-std --no-git && forge test --match-contract Invariant`), and the manual Docker-first real testnet acceptance gate (`yarn release:testnet-acceptance`) that must pass on the exact stable release commit. The dedicated Docker acceptance environment and evidence expectations are documented in [TESTNET_ACCEPTANCE.md](./TESTNET_ACCEPTANCE.md).
+Use [RELEASING.md](./RELEASING.md) for the package bootstrap publish, npm trusted-publishing setup, canary/stable release flow, the fork-based operator gate (`yarn release:operator-gate`), the cross-operator donation consumption gate (`yarn release:donation-consumption`), the contracts release gate (`cd ../contracts && yarn test && forge install foundry-rs/forge-std --no-git && forge test --match-contract Invariant`), and the manual Docker-first real testnet acceptance gate (`yarn release:testnet-acceptance`) that must pass on the exact stable release commit. The dedicated Docker acceptance environment and evidence expectations are documented in [TESTNET_ACCEPTANCE.md](./TESTNET_ACCEPTANCE.md).
 
 ## Updating deployment artifacts
 
@@ -98,6 +98,7 @@ This copies the 4 deployment JSON files from `contracts/` into `client/deploymen
 | `yarn staking` | Earning bootstrap validation on Anvil fork |
 | `yarn pack:smoke` | Pack tarball and run smoke tests |
 | `yarn release:operator-gate` | Run the stable-release operator gate (`staking` then `e2e`) |
+| `yarn release:donation-consumption` | Prove two isolated operators can consume donated SWE execution data through real testnet on-chain/IPFS/MCP paths |
 | `cd ../contracts && yarn test && forge install foundry-rs/forge-std --no-git && forge test --match-contract Invariant` | Run the contracts release gate |
 | `yarn release:testnet-acceptance` | Run the manual Docker-first real testnet acceptance harness |
 | `yarn setup:testnet-acceptance-operator` | First-time Docker acceptance setup + bootstrap/funding helper (`TESTNET_ACCEPTANCE.md`) |

package/README.md

@@ -7,7 +7,7 @@ Jinn protocol client. Runs a headless daemon that participates in the Jinn train
 
 ## Operator panel (local web UI)
 
-Running `jinn run` (or `yarn start`) opens a browser to `http://127.0.0.1:7331`
+Running `jinn run` opens a browser to `http://127.0.0.1:7331`
 with the operator panel — Status, Visibility (live event stream), Setup
 (bootstrap state machine), and an embedded Claude Code session in Auto Mode
 (when available).
@@ -45,10 +45,7 @@ yarn global add @jinn-network/client@latest
 The fast path for a new operator on Base Sepolia:
 
 ```bash
-# One-time: pick runtime mode + authenticate Claude Code (interactive).
-jinn auth
-
-# Zero-to-running (wallet + funding check + bootstrap + run).
+# Zero-to-running: opens the app, then wallet + funding check + bootstrap + run.
 jinn run
 ```
 
@@ -57,6 +54,8 @@ it to `~/.jinn-client/keystore-password` (mode 0600), and prints a summary
 with the master address and a pointer to back up your mnemonic. Subsequent
 verbs (`jinn run`, `jinn bootstrap`, `jinn claim-rewards`, …) pick up the
 password from that file automatically — no env var needed.
+If Claude Code authentication or runtime setup is needed, complete it in the
+operator app that `jinn run` opens.
 
 **Back up your mnemonic before you fund anything:**
 
@@ -152,7 +151,7 @@ Then open your agent and paste:
 > running. Keep me in the loop if anything needs my input.
 
 The `jinn-operator` skill activates on mentions of "jinn", "jinn network", and
-"jinn run", then walks your agent through install, auth, bootstrap, and
+"jinn run", then walks your agent through install, app-guided setup, bootstrap, and
 daemon lifecycle. You stay in the loop for funding decisions.
 
 ## Opting in to SolverNets
@@ -388,13 +387,7 @@ Quick answers to the things that typically surprise new operators:
 
 ## How it works
 
-The daemon runs three concurrent loops:
-
-1. **CreatorLoop** — posts Tasks via the deployed restoration-job contract boundary
-2. **TaskEngine** — claims requests, runs the selected Harness, submits Solutions
-3. **DeliveryWatcherLoop** — claims deliveries, creates evaluation jobs
-
-Each loop call increments on-chain activity counters. Staking contracts read these at checkpoints to determine reward eligibility.
+See [`client/ARCHITECTURE.md`](https://github.com/Jinn-Network/mono/blob/main/client/ARCHITECTURE.md) for the integrating narrative — operator app, CLI, daemon loops, task lifecycle, and extension points — with code pointers for each layer.
 
 ## Development
 

package/dist/adapters/adapter.d.ts

@@ -1,5 +1,6 @@
 import type { Task, RequestId, PostedTask, TaskAnnouncement, TaskRequest, TaskResult, DeliveredResult } from '../types/index.js';
 import type { Hex } from 'viem';
+import type { VerdictCode } from './mech/verdict-code.js';
 export interface ExecutionAdapter {
     readonly name: string;
     initialize(): Promise<void>;
@@ -23,7 +24,7 @@ export interface ExecutionAdapter {
         blockNumber?: number;
     }>;
     submitSolutionDelivery?(requestId: RequestId, solutionDigest: Hex): Promise<void>;
-    submitVerdictDelivery?(requestId: RequestId, verdictDigest: Hex, verdictCode?: number): Promise<void>;
+    submitVerdictDelivery?(requestId: RequestId, verdictDigest: Hex, verdictCode: VerdictCode): Promise<void>;
     watchForDeliveries(): AsyncIterable<DeliveredResult>;
     stop(): Promise<void>;
 }

package/dist/adapters/mech/adapter.d.ts

@@ -2,6 +2,7 @@ import { type Hex } from 'viem';
 import type { ExecutionAdapter } from '../adapter.js';
 import type { Task, RequestId, PostedTask, TaskAnnouncement, TaskRequest, TaskResult, DeliveredResult } from '../../types/index.js';
 import { type MechAdapterConfig } from './types.js';
+import { VerdictCode } from './verdict-code.js';
 import type { Store } from '../../store/store.js';
 export declare class MechAdapter implements ExecutionAdapter {
     readonly name = "mech";
@@ -14,6 +15,7 @@ export declare class MechAdapter implements ExecutionAdapter {
     private pendingEvaluations;
     private observedTasks;
     private requestKinds;
+    private claimedRestorationTaskIds;
     private evaluationOpportunities;
     private pendingEvaluationSolutions;
     private originalStates;
@@ -21,6 +23,11 @@ export declare class MechAdapter implements ExecutionAdapter {
     constructor(config: MechAdapterConfig, store?: Store);
     initialize(): Promise<void>;
     private recoverPendingState;
+    private onchainTaskDiscoveryFromBlock;
+    private joinedManifestDigestSet;
+    private allowedDiscoveryTaskIds;
+    private isDiscoveryTaskAllowed;
+    private getRouterLogsInChunks;
     private loadPendingEvaluationSolutions;
     private persistPendingEvaluationSolutions;
     private rememberPendingEvaluationSolution;
@@ -30,6 +37,8 @@ export declare class MechAdapter implements ExecutionAdapter {
     private contractPolicyForTask;
     private buildEvaluationTask;
     private restorationAnnouncementForTaskId;
+    private restorationAnnouncementFromDigest;
+    private discoverSubgraphRestorationTasks;
     private deliveryEnvelopeCidForSolution;
     private evaluationAnnouncementForSolution;
     private retryPendingEvaluationSolutions;
@@ -45,7 +54,7 @@ export declare class MechAdapter implements ExecutionAdapter {
         blockNumber?: number;
     }>;
     submitSolutionDelivery(requestId: RequestId, solutionDigest: Hex): Promise<void>;
-    submitVerdictDelivery(requestId: RequestId, verdictDigest: Hex, verdictCode?: number): Promise<void>;
+    submitVerdictDelivery(requestId: RequestId, verdictDigest: Hex, verdictCode: VerdictCode): Promise<void>;
     private evidenceHashForDelivery;
     private ensureDeliveryClaimed;
     watchForDeliveries(): AsyncIterable<DeliveredResult>;