shaonlisted

# Shaon Use the MCP tool when it covers the requested operation. Use the `shaon` CLI for unsupported operations, diagnosis, or when the user asks for the CLI. Inspect `shaon --help` or the relevant subcommand help for exact flags. ## Choose the task - Month status, missing days, and errors: start with `shaon attendance overview`. - Daily or monthly attendance details: use `shaon attendance` read commands. - Corrections: preview the relevant `attendance report` or `attendance resolve` command first. - Payslips and salary: use `shaon payroll` commands. - Authentication or account setup: use `shaon auth` commands. Prefer structured output when another tool will consume the result. Do not request credentials or a browser login for a read until the command reports that authentication is required. ## Human-attested writes Attendance submissions are claims about real work performed. The user must attest the facts; neither inferred calendar events nor an agent's judgment is enough. - Reporting commands preview by default. Show the employee, date or range, times, report type, and resulting action. - Run with `--execute` (or MCP `execute: true`) only after the user explicitly authorizes that concrete submission. - Never autonomously rerun a write with `--execute`. - After an ambiguous timeout or transport error, read back attendance state before proposing another submission. - CAPTCHA and attended login steps must be completed by the user. Example safe flow: ```bash shao