nightpay 0.3.11 → 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.

Potentially problematic release.

This version of nightpay might be problematic. Click here for more details.

Files changed (26) hide show
  1. package/LICENSE +666 -666
  2. package/README.md +456 -408
  3. package/bin/cli.js +558 -558
  4. package/nightpay_sdk.py +398 -398
  5. package/openclaw.plugin.json +10 -10
  6. package/package.json +50 -51
  7. package/plugin.js +712 -379
  8. package/skills/nightpay/AGENTS.md +302 -302
  9. package/skills/nightpay/HEARTBEAT.md +55 -55
  10. package/skills/nightpay/SKILL.md +471 -447
  11. package/skills/nightpay/contracts/receipt.compact +456 -390
  12. package/skills/nightpay/ontology/ontology.jsonld +395 -395
  13. package/skills/nightpay/ontology/ontology.md +243 -224
  14. package/skills/nightpay/openclaw-fragment.json +21 -21
  15. package/skills/nightpay/rules/content-safety.md +187 -187
  16. package/skills/nightpay/rules/escrow-safety.md +194 -194
  17. package/skills/nightpay/rules/privacy-first.md +51 -51
  18. package/skills/nightpay/rules/receipt-format.md +45 -45
  19. package/skills/nightpay/scripts/bounty-board.sh +325 -325
  20. package/skills/nightpay/scripts/gateway.sh +1474 -1474
  21. package/skills/nightpay/scripts/mip003-server.sh +4820 -4625
  22. package/skills/nightpay/scripts/update-blocklist.sh +194 -194
  23. package/bin/deploy-hetzner-ci.sh +0 -428
  24. package/scripts/agent-playground-setup.sh +0 -384
  25. package/scripts/load-sim.sh +0 -1324
  26. package/scripts/server-sync-start.sh +0 -237
package/skills/nightpay/HEARTBEAT.md CHANGED
@@ -1,55 +1,55 @@
1
- # NightPay heartbeat checklist
2
-
3
- Use this file for OpenClaw heartbeat runs.
4
-
5
- If nothing needs attention, reply exactly: `HEARTBEAT_OK`
6
-
7
- ## Objective
8
-
9
- Keep NightPay operator and agent flows healthy without spamming.
10
- Only report new or actionable changes.
11
-
12
- ## Rules
13
-
14
- - Do not repeat old alerts from earlier heartbeats.
15
- - Do not invent tasks from stale chat context.
16
- - If a check fails once, retry next heartbeat before escalating.
17
- - If all checks are green and no new action exists, return `HEARTBEAT_OK`.
18
-
19
- ## Checks (in order)
20
-
21
- 1) API availability
22
- - Check `GET ${NIGHTPAY_API_URL:-https://api.nightpay.dev}/availability`
23
- - If status is not available or endpoint is down for 2 consecutive heartbeats, alert.
24
-
25
- 2) Ontology & Knowledge Graph health
26
- - Check `GET ${NIGHTPAY_API_URL:-https://api.nightpay.dev}/ontology`
27
- - If the JSON-LD context is unreachable, agents lose navigation capabilities. Alert if down.
28
-
29
- 3) Bridge health (when bridge is configured)
30
- - If `BRIDGE_URL` is set, check `GET ${BRIDGE_URL%/}/health`
31
- - Alert on non-200, `initError`, or unexpected network switch.
32
- - If `stub: true`, send info-level notice only (not urgent).
33
-
34
- 4) Work queue signal
35
- - Compare `active_jobs` from `/availability` to previous heartbeat state.
36
- - Alert only when:
37
- - `active_jobs` increases from 0 to >0, or
38
- - `active_jobs` jumps significantly (>= +5 since last check).
39
-
40
- 5) Daily skill freshness (once per 24h)
41
- - Check `https://raw.githubusercontent.com/nightpay/nightpay/master/skills/nightpay/SKILL.md`
42
- - If `metadata.version` differs from local skill version, notify that an update is available.
43
-
44
- ## Alert format
45
-
46
- When alerting, keep it short:
47
- - What changed
48
- - Why it matters
49
- - Suggested next action
50
-
51
- If multiple alerts exist, order by severity:
52
- 1. service down
53
- 2. bridge/init issues
54
- 3. new work spikes
55
- 4. version update
1
+ # NightPay heartbeat checklist
2
+
3
+ Use this file for OpenClaw heartbeat runs.
4
+
5
+ If nothing needs attention, reply exactly: `HEARTBEAT_OK`
6
+
7
+ ## Objective
8
+
9
+ Keep NightPay operator and agent flows healthy without spamming.
10
+ Only report new or actionable changes.
11
+
12
+ ## Rules
13
+
14
+ - Do not repeat old alerts from earlier heartbeats.
15
+ - Do not invent tasks from stale chat context.
16
+ - If a check fails once, retry next heartbeat before escalating.
17
+ - If all checks are green and no new action exists, return `HEARTBEAT_OK`.
18
+
19
+ ## Checks (in order)
20
+
21
+ 1) API availability
22
+ - Check `GET ${NIGHTPAY_API_URL:-https://api.nightpay.dev}/availability`
23
+ - If status is not available or endpoint is down for 2 consecutive heartbeats, alert.
24
+
25
+ 2) Ontology & Knowledge Graph health
26
+ - Check `GET ${NIGHTPAY_API_URL:-https://api.nightpay.dev}/ontology`
27
+ - If the JSON-LD context is unreachable, agents lose navigation capabilities. Alert if down.
28
+
29
+ 3) Bridge health (when bridge is configured)
30
+ - If `BRIDGE_URL` is set, check `GET ${BRIDGE_URL%/}/health`
31
+ - Alert on non-200, `initError`, or unexpected network switch.
32
+ - If `stub: true`, send info-level notice only (not urgent).
33
+
34
+ 4) Work queue signal
35
+ - Compare `active_jobs` from `/availability` to previous heartbeat state.
36
+ - Alert only when:
37
+ - `active_jobs` increases from 0 to >0, or
38
+ - `active_jobs` jumps significantly (>= +5 since last check).
39
+
40
+ 5) Daily skill freshness (once per 24h)
41
+ - Check `https://raw.githubusercontent.com/nightpay/nightpay/master/skills/nightpay/SKILL.md`
42
+ - If `metadata.version` differs from local skill version, notify that an update is available.
43
+
44
+ ## Alert format
45
+
46
+ When alerting, keep it short:
47
+ - What changed
48
+ - Why it matters
49
+ - Suggested next action
50
+
51
+ If multiple alerts exist, order by severity:
52
+ 1. service down
53
+ 2. bridge/init issues
54
+ 3. new work spikes
55
+ 4. version update