#275 Add 'swamp auth status' as alias for 'swamp auth whoami'

Problem

When AI coding agents (Claude Code, Cursor, etc.) try to programmatically check whether swamp is authenticated, they reach for swamp auth status by analogy with the dominant convention in the CLI ecosystem:

• gh auth status
• aws sts get-caller-identity / aws configure list
• gcloud auth print-access-token
• kubectl auth whoami (added in 1.28 alongside the older kubectl config view)
• docker login / docker info (status-check pattern)
• op signin --account / op whoami

status is the term agents — and most humans — try first. swamp uses whoami, which works but produces a hard error on first attempt:

$ swamp auth status --json
"status" is not a subcommand of "auth".

The agent then has to re-plan, retry with whoami, and (if it's persistent) save a memory note to remember the swamp-specific spelling next time.

Proposed solution

Add status as an alias for whoami under swamp auth. Both should work; the help text can list whoami as the canonical name and status as an alias, or vice versa — whichever the maintainers prefer for branding. Output shape unchanged.

Alternatives considered

• Document the difference: doesn't help agents that don't read docs before reaching for a CLI.
• Rename whoami → status: backwards-incompatible. Aliasing avoids this.

Why this matters

Small ergonomics issues like this compound across the agentic workflows swamp explicitly targets. Every "wrong subcommand" error costs an LLM round-trip and pollutes its memory. Matching the dominant CLI convention reduces friction for both humans coming from gh/aws/gcloud and for agents driving swamp programmatically.

Environment

• swamp version: 20260506.233640.0-sha.5729ac50