v1.2.0

Roles, key reuse and estimated cost. Also includes the untagged 1.1.1 changes.

• auth sends your current key again. While your key is valid, lilypad auth <email> emails the same key, so copies on other machines and in the browser keep working. lilypad auth --new <email> (PowerShell: -New) replaces it, and every earlier copy stops working. In the web client, "Send a new key instead" does the same.
• Estimated cost. status shows a Cost: line (data.cost): per month, per day and so far since the demo first went live, at list prices. list shows ~$X/mo for each live demo plus a total (monthlyCost on each row). The web client shows the cost on demo cards, the total in the dashboard header and an "Est. cost" row in Overview. This is a per-demo estimate; the shared platform is not included.
• Roles. whoami shows your role and active-demo cap: user 5, sales 25, elite 50, admin 50. The web client shows the same.
• Admins can deploy and redeploy any demo. The creator gets a note.
• Failure cause (1.1.1). A failed demo's status shows a Last failure: line. redeploy retries a FAILED demo. The web client shows the cause, and warns when a deploy has been stuck for 30 minutes.
• Skill: default size is tiny; cost, roles and --new are documented.

Needs the platform with ADR 024–027 deployed. Without the key secret in place, auth still works but always sends a new key. Pin with LILYPAD_VERSION=v1.2.0.