CLI E2E Testcase Writer

Work on one domain per run. Produce exactly two artifacts for that domain:

• workflow testcase files under tests/cli_e2e/{domain}/
• tests/cli_e2e/{domain}/coverage.md

Focus on domain testcase files. Do not change shared E2E support code such as tests/cli_e2e/core.go unless the user explicitly asks. Treat tests/cli_e2e/demo/ as reference only.

Core standard

• Make the testcase scenario-based and self-contained.
• Prove one workflow end to end: create plus follow-up read, or mutate plus teardown.
• Prefer one file per workflow or one closely related feature.
• For mutable flows, prove persisted state with read-after-write assertions, not just exit code.
• Leave prerequisite-heavy paths uncovered when they cannot be proven, and explain why in coverage.md.

Workflow

1. Explore the live CLI before writing code