mnemospark 0.3.0 → 0.4.0

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.
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "id": "mnemospark",
3
3
  "name": "mnemospark",
4
- "version": "0.3.0",
4
+ "version": "0.4.0",
5
5
  "description": "mnemospark is an OpenClaw plugin that gives agentic systems instant, secure access to cloud storage, compute, and proprietary datasets paid via x402 with USDC on Base. Wallet and go.",
6
6
  "configSchema": {
7
7
  "type": "object",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mnemospark",
3
- "version": "0.3.0",
3
+ "version": "0.4.0",
4
4
  "description": "mnemospark is an OpenClaw plugin that gives agentic systems instant, secure access to cloud storage, compute, and proprietary datasets paid via x402 with USDC on Base. Wallet and go.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -6,7 +6,7 @@ Use this skill for mnemospark cloud backup/storage workflows, async operation tr
6
6
 
7
7
  ## Inputs expected
8
8
 
9
- - User intent: backup, price-storage, upload, ls, download, delete, op-status
9
+ - User intent: backup, price-storage, upload, payment-settle, ls, download, delete, op-status
10
10
  - Wallet context (`--wallet-address`) where required
11
11
  - Optional selector context (`--object-key` or `--name`, plus `--latest` / `--at`)
12
12
  - Optional async orchestration context for long-running work:
@@ -32,6 +32,7 @@ Use this skill for mnemospark cloud backup/storage workflows, async operation tr
32
32
  - `/mnemospark_cloud backup <file|directory> [--name <friendly-name>] [--async] [--orchestrator <inline|subagent>] [--timeout-seconds <n>]`
33
33
  - `/mnemospark_cloud price-storage --wallet-address <addr> --object-id <id> --object-id-hash <hash> --gb <gb> --provider <provider> --region <region>`
34
34
  - `/mnemospark_cloud upload --quote-id <quote-id> --wallet-address <addr> --object-id <id> --object-id-hash <hash> [--name <friendly-name>] [--async] [--orchestrator <inline|subagent>] [--timeout-seconds <n>]`
35
+ - `/mnemospark_cloud payment-settle --quote-id <quote-id> --wallet-address <addr> [--object-id <id>] [--object-key <key>] [--storage-price <n>]`
35
36
  - `/mnemospark_cloud ls --wallet-address <addr> [--object-key <object-key> | --name <friendly-name>] [--latest|--at <timestamp>]`
36
37
  - `/mnemospark_cloud download --wallet-address <addr> [--object-key <object-key> | --name <friendly-name>] [--latest|--at <timestamp>] [--async] [--orchestrator <inline|subagent>] [--timeout-seconds <n>]`
37
38
  - `/mnemospark_cloud delete --wallet-address <addr> [--object-key <object-key> | --name <friendly-name>] [--latest|--at <timestamp>]`
@@ -20,6 +20,13 @@
20
20
  - Purpose: upload encrypted object for a valid quote.
21
21
  - `--timeout-seconds <n>` only applies when `--async --orchestrator subagent`.
22
22
 
23
+ ### Payment settle (scheduled / manual)
24
+
25
+ `payment-settle --quote-id <quote-id> --wallet-address <addr> [--object-id <id>] [--object-key <key>] [--storage-price <n>]`
26
+
27
+ - Purpose: call the same proxy + x402 payment settlement path as upload (for monthly cron lines stored after upload).
28
+ - Required: `--quote-id`, `--wallet-address` (configured private key must match the address).
29
+
23
30
  ### List
24
31
 
25
32
  `ls --wallet-address <addr> [--object-key <object-key> | --name <friendly-name>] [--latest|--at <timestamp>]`
@@ -62,6 +62,14 @@ For async runs, `operations` may include:
62
62
  - `timeout_seconds`
63
63
  - `cancel_requested_at`
64
64
 
65
+ ## Payment settle (client) JSONL events
66
+
67
+ Emitted to `events.jsonl` and `proxy-events.jsonl` when `/mnemospark_cloud payment-settle` runs (dual-write for operator grep parity with proxy `payment.settle` lines):
68
+
69
+ - `payment-settle.started` → `events.jsonl` (status `running`)
70
+ - `payment-settle.completed` → `events.jsonl` (status `succeeded` or `failed`, includes `http_status` when known)
71
+ - `payment.settle` with `status` `start` / `result` → `proxy-events.jsonl` (`details.source`: `client`)
72
+
65
73
  ## Operation lifecycle JSONL events
66
74
 
67
75
  Operation lifecycle events emitted to `events.jsonl` and `proxy-events.jsonl`: