pub const ISSUE_TIMER: &str = "\
Start, stop or drop a timer.
```
ytcli issue timer start PROJ-1
ytcli issue timer stop PROJ-1 -m \"pairing on the migration\"
ytcli issue timer cancel PROJ-1
```
`stop` is the only verb here that reaches Tracker: it records the elapsed time as
a worklog, rounded to the minute and never to zero. The timer is only forgotten
once Tracker has accepted the worklog, so a failed write leaves the clock
running rather than losing the time.
`cancel` drops it and records nothing, saying how long it had been running so
the number is not simply gone.
Timers are kept per organisation, not per profile: two profiles onto the same
Tracker are two ways of naming one issue, and a timer started through either
stops through the other. A timer running in a *different* organisation is
reported as such rather than as \"no timer running\", which would be true and
useless.
The whole group writes, even the two verbs that only touch a local file: a host
allowlists by prefix. Reading is `issue timers`.";