Commander v0.3.0

What's Changed

Prepare intelligent agents for distributed missions with shared credentials,
interactive questions, execution progress and operator-controlled completion.

Missions and execution

• Create and edit mission objectives, actions, rules and schemas through Admin,
  HTTP API, MCP or Admin CLI. Names stay unchanged; running operations retain
  their original mission definition.
• Set completion.decision_by to operator to require explicit completion.
  Model submissions save completion_draft; operators review or edit it in
  Admin before completing through the existing API. Omitted/model policy keeps
  immediate completion.
• Actions can ask durable questions with action.Question. Operators answer
  first; the model may answer after fallback_at. Passing the waiting deadline
  never supplies an answer or completion approval.
• Record execution progress with action.Log, query it through HTTP/MCP and
  follow it in Admin, filtering by task, agent or action.
• Reconcile late execution outcomes after interrupted waits. The default initial
  task-result wait is now 15m, configurable with TASK_TIMEOUT; a timeout does
  not prove the underlying work stopped.
• Inspect and manage agent-owned runtime resources in Admin's Sessions page.

Secrets and deployment

• Save a credential once by name for all requesting agents, including agents
  started later. The controller decrypts requested values for delivery; agents
  and spawner no longer need SECRETS_ENCRYPTION_KEY.
• Playground shares the selected provider key through the API under its canonical
  environment-variable name, preserving any existing saved value.
• Spawner can launch Kubernetes Pods using in-cluster authentication and configured
  namespace, ServiceAccount and child configuration references.
• API, MCP and Admin UI honor platform PORT, with component-specific listener
  settings and explicit flags taking precedence.

Playground and Admin

• Playground retains settings, chat history and locally encrypted provider keys
  in ~/.commander, including remote sessions. --temporary opts out; Docker
  sessions retain state through their mounted volume.
• Provider and connection status stay fixed above the scrolling conversation.
  Completed tool calls replace their pending row, and the operation summary shows
  up to three recent operations.
• Admin opens on Operations, provides shared Secrets in the sidebar and exposes
  connection health through the current connection's Status page.