docs(kiloclaw): clarify Stop Instance behavior and cron job handling

[ScuttleBot]

Context

User in Discord was confused about KiloClaw instance behavior:

I stopped the instance via the KiloClaw dashboard and disabled all cron jobs. The machine restarted on its own overnight. When I asked the agent why, it said it was triggered by a heartbeat check.

Is there a way to fully stop a KiloClaw instance so it stays stopped?

The docs weren't clear that "stopped" means fully off — no cron jobs, no heartbeats, no self-wake capability.

Changes

dashboard.md

• Added new section Understanding Stop Instance that explains:
  • What "stopped" actually means (machine fully off)
  • Cron jobs and heartbeats do NOT run while stopped
  • How to disable cron jobs without stopping the whole instance
  • When to stop vs destroy
• Updated Instance Lifecycle table with cron/heartbeat note
• Added cross-reference link from Stop Instance bullet

troubleshooting.md

• Added FAQ: My instance restarted after I stopped it — explains that stopped instances cannot self-wake
• Added FAQ: How do I disable cron jobs without stopping the instance — points to Control UI

Preview

The new "Understanding Stop Instance" section:

When you click Stop Instance, the machine is fully shut down — no code runs, no CPU cycles are consumed, and billing for compute time stops.

What "Stopped" Means:

• The machine is completely off — not sleeping, not paused
• No cron jobs will execute
• No heartbeat checks will run
• No messages will be processed

[vercel]

@olearycrew is attempting to deploy a commit to the Kilo Code Team on Vercel.

A member of the Team first needs to authorize it.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• packages/kilo-docs/pages/automate/kiloclaw/dashboard.md
• packages/kilo-docs/pages/automate/kiloclaw/troubleshooting.md