Capability Map

Use this page to check which first-class capabilities ChatMail currently owns, which ones are verified, and what remains out of scope for this package.

Capability Groups

• CLI Entry

  chatmail --help, --version, --tree, and --tree-brief are the default verification entry points.

• Python API

  Substantive behavior should live in importable Python functions, classes, or service layers rather than only in Click callbacks.

• Config and Environment

  ChatEnv integration is enabled by default; stable, shared configuration belongs in config.py.

Current Boundary

Capability	Status	Notes
CLI base entry	Implemented	The explicit chatmail Click root uses ChatStyle's registered tree and exposes --version, --tree, and --tree-brief.
ChatEnv provider	Implemented	config.py defines a typed sensitive field and registers it through chatenv.configs with ChatEnv-managed storage paths.
Business commands	Not implemented	Add these from the real package domain; do not fake future commands in the template.

Out of Scope

• No plan placeholder page is generated.
• No unimplemented capability should be written as a user operation tutorial.
• No secret, token, cookie, or Authorization header should appear in README, docs, issues, PR comments, or CI logs.