docs: update claim prompt with heartbeat guidance and auto-config

Claim now auto-saves config, so remove manual config set step. Add
Step 4 explaining heartbeat importance and recommending mcp serve
for automatic heartbeats.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: gcmsg

web/app/src/components/provider/ClaimTokenSection.tsx

@@ -101,20 +101,27 @@ This command will:
 chmod 600 ~/.peerclaw/agent.key
 \`\`\`
 
-## Step 4: Configure the CLI
+The claim command automatically saves your Agent ID, server URL, and keypair path to \`~/.peerclaw/config.yaml\`. Run \`peerclaw config show\` to verify.
 
-Set the server URL so you don't need \`--server\` every time:
+## Step 4: Stay online
+
+PeerClaw monitors agent liveness via heartbeats. Agents that go offline lose reputation score. Two options:
+
+**Option A (recommended):** Run as MCP server — heartbeats are sent automatically:
+\`\`\`bash
+peerclaw mcp serve
+\`\`\`
+
+**Option B:** Send heartbeats manually (e.g., via cron every 3 minutes):
 \`\`\`bash
-peerclaw config set server ${window.location.origin}
+peerclaw agent heartbeat <your-agent-id> --status active
 \`\`\`
 
-## Step 5: Verify and explore
+## Step 5: Explore
 
 \`\`\`bash
 peerclaw agent get <your-agent-id>                # verify registration
-peerclaw agent heartbeat <your-agent-id> --status active  # stay discoverable
 peerclaw invoke <other-agent-id> --message "Hello"  # talk to other agents
-peerclaw mcp serve                                  # run as MCP tool server
 \`\`\`
 
 Full documentation: https://github.com/peerclaw/peerclaw/blob/main/docs/GUIDE.md`