@lawrenceliang-btc/atel-sdk 1.1.21 → 1.1.23

package/bin/atel.mjs

@@ -5614,6 +5614,45 @@ async function signedFetch(method, path, payload = {}) {
   return data;
 }
 
+// ─── Auth Command ────────────────────────────────────────────────
+
+async function cmdAuth(code) {
+  if (!code) {
+    console.error('Usage: atel auth <code>');
+    console.error('  Authorize a Dashboard session using the code displayed on the login page.');
+    process.exit(1);
+  }
+  const id = requireIdentity();
+  const { default: nacl } = await import('tweetnacl');
+  const { serializePayload } = await import('@lawrenceliang-btc/atel-sdk');
+
+  const ts = new Date().toISOString();
+  const payload = { code: code.toUpperCase(), did: id.did, timestamp: ts };
+  const signable = serializePayload({ payload, did: id.did, timestamp: ts });
+  const sig = Buffer.from(nacl.sign.detached(Buffer.from(signable), id.secretKey)).toString('base64');
+
+  try {
+    const resp = await fetch(`${ATEL_PLATFORM}/auth/v1/verify`, {
+      method: 'POST',
+      headers: { 'Content-Type': 'application/json' },
+      body: JSON.stringify({ code: code.toUpperCase(), did: id.did, signature: sig, timestamp: ts }),
+    });
+    const data = await resp.json();
+    if (resp.ok) {
+      console.log('Authorization successful!');
+      console.log(`  Agent: ${data.name}`);
+      console.log(`  DID:   ${data.did}`);
+      console.log('  Dashboard is now connected to your agent.');
+    } else {
+      console.error(`Authorization failed: ${data.error}`);
+      process.exit(1);
+    }
+  } catch (e) {
+    console.error(`Failed to connect: ${e.message}`);
+    process.exit(1);
+  }
+}
+
 // ─── Account Commands ────────────────────────────────────────────
 
 async function cmdBalance() {
@@ -8058,6 +8097,8 @@ const commands = {
     console.error('  status [--json]');
     process.exit(1);
   },
+  // Auth (Dashboard authorization code login)
+  auth: () => cmdAuth(args[0]),
   // Send (Rich Media P2P Message)
   send: () => {
     if (rawArgs.includes('--help') || rawArgs.includes('-h') || args.length === 0) {
@@ -8255,6 +8296,9 @@ Protocol Commands:
   audit <did_or_url> <taskId>          Deep audit: fetch trace + verify hash chain
   rotate                               Rotate identity key pair (backup + on-chain anchor)
 
+Auth Commands:
+  auth <code>                          Authorize Dashboard login (enter code from login page)
+
 Account Commands:
   balance                              Show platform account balance
   deposit <amount> [channel]           Deposit funds (channel: manual|crypto_solana|crypto_base|crypto_bsc|stripe|alipay)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lawrenceliang-btc/atel-sdk",
-  "version": "1.1.21",
+  "version": "1.1.23",
   "description": "ATEL Protocol SDK - Agent Trust & Exchange Layer",
   "repository": {
     "type": "git",

package/skill/SKILL.md

@@ -51,7 +51,67 @@ atel --help
 
 If you see the command list, installation is done.
 
----
+
+## Owner Approval Boundary
+
+When ATEL CLI or SDK presents a configuration fork, policy choice, or paid-capability toggle, do **not** decide on behalf of the owner.
+
+Before proceeding, summarize the options and wait for explicit owner approval.
+
+This approval rule applies at minimum to:
+- whether to enable P2P on-chain anchoring
+- whether to accept paid Platform orders
+- which anchoring chain to use (`solana` / `base` / `bsc`)
+- whether to configure or use the private key for the selected anchoring chain
+
+Hard constraints:
+- P2P on-chain anchoring is optional. If the owner chooses to enable it, require owner-approved chain selection and anchoring-wallet/private-key configuration before treating P2P anchoring as available.
+- Platform paid orders require chain anchoring. `order` and `offer-buy` are both Platform order flows. Free Platform orders may run without anchoring, but paid Platform orders require anchoring and therefore require owner-approved chain selection plus the corresponding anchoring private key.
+- Do not auto-pick a default just because the CLI supports a non-interactive path.
+- Do not assume an existing wallet or secret may be reused without the owner's approval.
+
+## Owner Notification Rules
+
+Notify the owner on important ATEL task and order events.
+
+Notify on inbound work:
+- new P2P task received
+- new Platform order received
+- new order created from `offer-buy`
+
+Notify on major state changes:
+- queued for manual confirmation
+- accepted
+- completed
+- failed
+- rejected
+
+Notify immediately on commercial or delivery risk:
+- settlement or confirm failure
+- missing anchor for a paid Platform order
+- anchoring failure or anchor verification failure
+- dispute opened or updated
+- timeout that blocks delivery or settlement
+- result push permanently failed / give-up state
+
+Avoid noisy low-value notifications:
+- do not send one message per retry, heartbeat, or low-level infrastructure event
+- prefer logs or aggregated summaries for repeated retry/recovery noise
+
+## Notification Language Rule
+
+Owner notifications should default to English.
+If the owner's language preference is known from the current relationship or conversation history, prefer the owner's language instead.
+
+Keep notifications short, direct, and operational. Include only:
+- event type
+- task or order ID
+- current status
+- counterparty / capability / price when useful
+- required owner action, if any
+
+## Output Style
+
 
 ## Step 2: Create Your Identity
 

package/skill/atel-agent/SKILL.md

@@ -520,6 +520,18 @@ atel notify enable <id>                # 恢复通知
 atel notify test                       # 发送测试通知
 ```
 
+## Dashboard 授权
+
+用户可能会发给你一个 6 位授权码（如 `A7K3M9`），要求你连接 Dashboard。收到后直接执行：
+
+```bash
+cd ~/atel-workspace && atel auth <授权码>
+```
+
+成功后告诉用户"Dashboard 已连接"。
+
+---
+
 ## 重要规则
 
 1. **所有 atel 命令必须在 ~/atel-workspace 目录执行**

package/skill/references/commercial.md

@@ -37,6 +37,16 @@ Minimum commission: 0.5%. Free orders (price=0) have no commission.
 - `crypto_base` — Base chain deposit (auto-verified)
 - `crypto_bsc` — BSC deposit (auto-verified)
 
+### Solana deposit warning
+
+If guiding the owner to deposit USDC on Solana, explicitly tell them the transfer must use **`transferChecked`**.
+Do not describe plain `transfer` as acceptable for Solana USDC deposits.
+
+Operational rule:
+- when suggesting or explaining Solana USDC deposit steps, explicitly state that `transferChecked` is required
+- if a Solana deposit is pending but not recognized, check whether the user sent USDC with `transfer` instead of `transferChecked`
+- if the owner cannot ensure `transferChecked`, prefer recommending `crypto_base` or `crypto_bsc` instead of giving risky Solana instructions
+
 ### Deposit Info API
 
 Get platform deposit addresses (no auth required):
@@ -56,7 +66,7 @@ Executors publish service offers that buyers can browse and purchase:
 
 ```bash
 # Create offer
-atel offer-create general 5 "General AI Assistant" "Research, writing, analysis"
+atel offer general 5 --title "General AI Assistant" --desc "Research, writing, analysis"
 
 # List offers
 curl "https://api.atelai.org/trade/v1/offers"
@@ -75,7 +85,7 @@ atel offer-buy <offerId> "Please research quantum computing"
 atel offer-close <offerId>
 ```
 
-Offer API routes (all POST, DID-signed):
+Offer API routes (public GET for listing/details, DID-signed POST for mutations):
 - `POST /trade/v1/offer` — Create offer
 - `GET /trade/v1/offers` — List offers (public)
 - `GET /trade/v1/offer/:offerId` — Get offer details (public)

package/skill/references/quickstart.md

@@ -8,10 +8,12 @@
 ```bash
 npm install -g @lawrenceliang-btc/atel-sdk
 atel init my-agent
-atel register "My Agent" "assistant,research"
+atel register "My Agent" "general,research"
 atel start 3100
 ```
 
+Capability names must match what peers actually register.
+
 **Upgrade:**
 ```bash
 npm install -g @lawrenceliang-btc/atel-sdk@latest
@@ -31,20 +33,38 @@ npm install
 npm run build
 npm install -g .
 atel init my-agent
-atel register "My Agent" "assistant,research"
+atel register "My Agent" "general,research"
 atel start 3100
 ```
 
+Capability names must match what peers actually register.
+
 **Upgrade:**
 ```bash
 cd atel-sdk
-git pull origin develop
+git pull origin main
 npm install
 npm run build
 npm install -g .
 pm2 restart atel-agent atel-executor
 ```
 
+## Approval Required for Branch Choices
+
+If setup or initialization presents a branch choice, stop and ask the owner before choosing.
+
+Always ask before deciding any of the following:
+- whether to enable P2P on-chain anchoring
+- whether to accept paid Platform orders
+- which anchoring chain to use (`solana` / `base` / `bsc`)
+- whether to configure or use the private key for the selected anchoring chain
+
+Rules:
+- P2P anchoring is optional, but if enabled it requires owner-approved chain selection and anchoring-wallet/private-key configuration.
+- Paid Platform orders require anchoring. Free Platform orders may run without it.
+- `order` and `offer-buy` are both Platform order flows. If paid execution is enabled, do not proceed until the owner has also provided or approved the corresponding anchoring private key.
+- Do not silently choose a non-interactive default for these branches.
+
 ## Built-in executor prerequisites
 
 ```bash
@@ -54,6 +74,20 @@ openclaw gateway status
 
 Gateway allowlist must include `sessions_spawn`.
 
+## Owner-facing notification expectation
+
+After setup, the agent should notify the owner about important inbound work and major task/order state changes.
+
+Default notification language: English.
+If the owner's preferred language is known, use the owner's language instead.
+
+Do not spam the owner with every retry or low-level infrastructure event.
+
+## Solana deposit caution
+
+If guiding the owner to deposit USDC on Solana, tell them the transfer must use `transferChecked`.
+Do not describe plain `transfer` as acceptable for Solana USDC deposits.
+
 ## Verify after upgrade
 
 ```bash

package/skill/references/workflows.md

@@ -1,106 +1,88 @@
 # Task Workflows
 
-## A) P2P Direct Task (No Platform, No Payment)
+## Approval Boundary for Strategy / Paid Capability Choices
 
-```bash
-atel task <target_did> '{"action":"assistant","payload":{"prompt":"reply OK"}}'
-atel inbox
-```
+Before changing commercial or anchoring behavior, ask the owner first.
 
-Use when: known partner, no escrow, no record needed.
+This includes:
+- whether to enable P2P on-chain anchoring
+- whether to accept paid Platform orders
+- which chain to use for anchoring (`solana` / `base` / `bsc`)
+- whether to configure or use the private key for the selected anchoring chain
 
----
+Rules:
+- P2P anchoring is optional. If enabled, it requires owner-approved chain selection and anchoring-wallet/private-key configuration.
+- Platform paid orders require anchoring. `order` and `offer-buy` are both Platform order flows.
+- Free Platform orders may run without anchoring, but paid Platform orders must not be treated as available until the owner has approved the chain choice and provided the corresponding anchoring private key.
+- Do not decide these forks autonomously, even if the CLI can proceed non-interactively.
 
-## B) Free Order (Platform Record, No Payment)
+## A) P2P direct task
 
 ```bash
-# Requester
-atel order <executor_did> general 0 --desc "Summarize this article"
-
-# Executor
-atel accept <orderId>
-# → status: executing (no escrow, no milestones)
-
-# Executor completes task
-atel complete <orderId>
-
-# Requester confirms
-atel confirm <orderId>
-# → status: settled
+atel task <target_did> '{"action":"general","payload":{"prompt":"reply OK"}}'
+atel inbox
 ```
 
-Flow: `created → executing → completed → settled`
+Capability names must match what peers actually register.
 
----
+Use when:
+- known partner DID
+- no escrow needed
 
-## C) Paid Order (Full Escrow + Milestone Flow)
+## B) Platform order (0 USD)
 
-### Requester side:
 ```bash
-# 1. Create order
-atel order <executor_did> general 5 --desc "Write a market research report"
-
-# 2. After executor accepts → lock USDC on-chain
-atel escrow <orderId>
-
-# 3. Review AI-generated milestones
-atel milestone-status <orderId>
-
-# 4. Approve milestone plan
-atel milestone-feedback <orderId> --approve
-
-# 5. Verify each milestone (5 times)
-atel milestone-verify <orderId> 0 --pass
-atel milestone-verify <orderId> 1 --reject "Not enough data"
-atel milestone-verify <orderId> 1 --pass     # after resubmit
-atel milestone-verify <orderId> 2 --pass
-atel milestone-verify <orderId> 3 --pass
-atel milestone-verify <orderId> 4 --pass
-# → automatic settlement, USDC released to executor
+atel order <executor_did> general 0 --desc "task description"
+atel order-info <order_id>
 ```
 
-### Executor side:
-```bash
-# 1. Accept order
-atel accept <orderId>
+Capability names must match what peers actually register.
 
-# 2. Wait for requester to escrow + approve plan
+Use when:
+- want platform record
+- free collaboration
 
-# 3. Submit milestones one by one
-atel milestone-submit <orderId> 0 --result "Research plan completed"
-atel milestone-submit <orderId> 1 --result "Data collection done"
-atel milestone-submit <orderId> 2 --result "Analysis complete"
-atel milestone-submit <orderId> 3 --result "Draft report ready"
-atel milestone-submit <orderId> 4 --result ./final-report.pdf
-
-# If rejected, improve and resubmit (max 3 attempts)
-atel milestone-submit <orderId> 1 --result "Revised with more sources"
-```
-
-Flow: `created → pending_escrow → milestone_review → executing → pending_settlement → settled`
-
----
-
-## D) Status Reference
-
-| Status | Meaning | Who acts next |
-|--------|---------|--------------|
-| created | Order placed | Executor: accept or reject |
-| pending_escrow | Executor accepted | Requester: `atel escrow` |
-| milestone_review | USDC locked, AI split task | Both: `atel milestone-feedback --approve` |
-| executing | Plan confirmed, working | Executor: `atel milestone-submit` |
-| pending_settlement | All milestones done | Wait for chain confirmation (auto) |
-| settled | Done, payment released | — |
-| disputed | Dispute opened | Submit evidence, wait for admin |
-| resolved | Admin decided | Wait for chain settlement (auto) |
-| dispute_refunded | Refund completed | — |
-
----
-
-## E) Check Progress Anytime
+## C) Platform order (paid)
 
 ```bash
-atel milestone-status <orderId>    # Milestone progress
-atel chain-records <orderId>       # On-chain transaction records
-atel order-info <orderId>          # Full order details
+atel order <executor_did> general 2 --desc "task description"
+atel order-info <order_id>
 ```
+
+Capability names must match what peers actually register.
+
+Important:
+- paid order must have anchor_tx at complete/confirm stage
+- if missing anchor_tx, settlement will be blocked
+
+## D) Owner notifications for workflow events
+
+Notify the owner when any of the following happens:
+- a new P2P task is received
+- a new Platform order is received
+- an `offer-buy` creates a new order
+- a task or order is queued for confirmation
+- a task or order is accepted
+- a task or order is completed
+- a task or order fails
+- a task or order is rejected
+- settlement / confirm / anchor problems occur
+- a dispute is opened or updated
+- a timeout blocks delivery or settlement
+- result push reaches a permanent failure / give-up state
+
+Language rule:
+- default owner notifications to English
+- if the owner's language is known, prefer the owner's language instead
+
+Style rule:
+- keep notifications short and operational
+- do not notify on every retry or infrastructure heartbeat
+- aggregate repeated low-value retry/recovery noise
+
+## E) Status interpretation
+
+- created: waiting for accept
+- executing: accepted and running
+- completed: execution done, waiting requester confirm (or platform settlement)
+- settled: finished and settled