traderclaw-v1 1.0.2 → 1.0.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "traderclaw-v1",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "TraderClaw V1 — autonomous Solana memecoin trading agent plugin for OpenClaw",
   "type": "module",
   "main": "./dist/index.js",

package/skills/solana-trader/SKILL.md

@@ -62,6 +62,77 @@ Full processing instructions are in Step 1.5b below.
 
 ---
 
+## ⚠️ MANDATORY STARTUP SEQUENCE — Run This EVERY Session
+
+**You MUST execute these steps in order at the start of EVERY session before entering the trading loop.** Do not skip any step. Do not jump to scanning or trading until all steps complete. If any step fails, STOP and report the error — do not proceed with a broken setup.
+
+**Exception:** If the incoming message starts with `CRON_JOB:`, skip this startup sequence entirely and go directly to the "CRON_JOB Recognition" section.
+
+### Startup Step 1: Verify System Connectivity
+
+```
+Call solana_status()
+```
+
+This confirms the orchestrator is reachable and your session is authenticated. If this fails, STOP. Nothing else will work. Tell the user to run `traderclaw status` from their terminal to diagnose the issue.
+
+**IF THIS FAILS → DO NOT PROCEED. Report the error and stop.**
+
+### Startup Step 2: Gateway Registration Check
+
+```
+Call solana_gateway_credentials_get()
+```
+
+- **If credentials are returned with `active: true`** → Gateway is registered. Proceed to Step 3.
+- **If credentials are empty or missing** → This is your first run (or credentials were deleted). You MUST register now:
+
+```
+Call solana_gateway_credentials_set({
+  gatewayBaseUrl: "<your OpenClaw Gateway's public HTTPS URL>",
+  gatewayToken: "<your Gateway bearer token>"
+})
+```
+
+The Gateway URL and token come from the user's OpenClaw Gateway configuration. If you don't know them, ask the user. Without Gateway registration, the orchestrator cannot push high-priority signals to wake you up — you will miss critical alpha and subscription events between sessions.
+
+After setting, verify with `solana_gateway_credentials_get()` — confirm `active: true`.
+
+**IF THIS FAILS → DO NOT PROCEED. The agent cannot receive event-driven wake-ups without gateway credentials. Report the error.**
+
+### Startup Step 3: Alpha Stream Subscription
+
+```
+Call solana_alpha_subscribe({ agentId: "main" })
+```
+
+This subscribes you to the SpyFly alpha signal stream via WebSocket. The `agentId: "main"` parameter enables Gateway forwarding — the orchestrator will push high-priority signals to your Gateway even when your WS session closes.
+
+You only need to call this once per session. The subscription persists across heartbeat cycles within the same session.
+
+**IF THIS FAILS → DO NOT PROCEED. Without an active alpha subscription, you will miss real-time signals and Gateway-forwarded events. Report the error and stop.**
+
+### Startup Step 4: Portfolio Health Check
+
+```
+Call solana_capital_status()
+Call solana_positions()
+Call solana_killswitch_status()
+```
+
+Know your portfolio state before making any decisions:
+- Current capital and daily usage
+- Open positions and unrealized PnL
+- Kill switch status
+
+If the kill switch is active, enter Position Defense Mode immediately (see Step 0: INTERRUPT CHECK below).
+
+**IF THIS FAILS → DO NOT PROCEED. You cannot make safe trading decisions without knowing your portfolio state. Report the error and stop.**
+
+**After all 4 startup steps complete → proceed to the trading loop (Step 0: INTERRUPT CHECK).**
+
+---
+
 ## Mode System
 
 You operate in exactly one mode at a time. If not explicitly set, default to `HARDENED`.
@@ -173,25 +244,6 @@ There is no context loss from this separation. Cron outputs flow into the persis
 
 ---
 
-### Step 0 Pre-Requisite: GATEWAY REGISTRATION (First Run Only)
-
-On your **very first session**, before doing anything else, register your Gateway credentials with the orchestrator so event-to-agent forwarding works:
-
-```
-Call solana_gateway_credentials_set({
-  gatewayBaseUrl: "<your OpenClaw Gateway's public HTTPS URL>",
-  gatewayToken: "<your Gateway bearer token>"
-})
-```
-
-This tells the orchestrator WHERE to forward subscription events when you include `agentId` in subscribe calls. Without this, subscriptions still work but events only arrive on the WS connection (which closes when your session ends — events between sessions would be lost).
-
-**Verify with** `solana_gateway_credentials_get` — should return your registered URL and `active: true`.
-
-You only need to do this once. The credentials persist across sessions. If your Gateway URL or token changes, call `solana_gateway_credentials_set` again to update.
-
----
-
 ### Step 0: INTERRUPT CHECK (Before Every Cycle)
 
 **How you wake up determines your path:**