tick.md's issue-filing section names `tang` in 13 places and two skills repeat it, but the CLI is now `tg` per Cameron. `tg` is not on PATH on this machine and the local tangled-cli checkout still declares only a `tang` bin, so the correct binary is unconfirmed — the sweep needs verification rather than a rename guess. tick.md:81's stated symlink path is wrong independently of that. Defense: documentation-only. Records a corpus-versus-machine mismatch in the findings queue so it is not lost; no workflow text is changed, because pointing a binding process page at a command that is not installed would be worse than the current staleness.