Flisk status

Read the state from the CLI rather than guessing from Docker output.

Workflow

1. Run flisk status --json from the project root. Use --resources to list every discovered resource, or --tilt for Tilt resource state.
2. Summarize per stack: running, healthy, unhealthy, or stopped, with each service's URL.
3. For an agent resource, list its sessions with flisk agent sessions <resource> (--watch refreshes); add --session-id <id> to read one session's checkpoint.
4. If a service is unhealthy, run flisk networks to confirm its routed URL, then switch to the flisk-troubleshoot skill.

Guardrails

• Report only what the output shows. Say so when a field is missing.
• Do not stop containers by name pattern. Identify the stack first.