v0.4.0 — warden-lite

[0.4.0] - 2026-05-12

Partner-readiness release. Closes the gap between "partner says yes"
and "partner is running warden-lite in front of their agent." Single
binary now covers server + operator ops; yellow-tier parks alert
Slack with a one-click-ready decide command line; the SDK demo
demonstrates the canonical operator flow end-to-end.

Added

• GET /pending — operator list endpoint. Query params:
  ?status=parked|decided|all (default parked), ?limit=N (default
  50, server hard-cap 500). Returns array of pending views, newest
  requested first. Requires --decide-token if configured.
• warden-lite pending {list,get,decide} CLI subcommands. Talks
  to a running warden-lite over HTTP; same wire contract as the
  endpoints. pending list prints a table by default, --json for
  scripting. pending decide takes --allow or --deny (mutually
  exclusive) + optional --note. Falls back to WARDEN_LITE_URL,
  WARDEN_LITE_DECIDE_TOKEN, WARDEN_LITE_TOKEN envs.
• Slack-webhook park alerts via --slack-webhook-url (or
  WARDEN_LITE_SLACK_WEBHOOK_URL). Every yellow-tier park spawns a
  fire-and-forget POST with the correlation id, agent, tool, review
  reasons, and the exact warden-lite pending decide command line
  for the approver. One-way — operators decide via the CLI or curl
  (no Slack→warden return path; that lives in the full edition's HIL
  service). Failed webhooks log at warn and never block the
  agent's 202.