Both were found by running paths that had never executed. Neither was visible to any test: one needs a laptop whose DNS cannot complete a MagicDNS name, the other needs a real terminal behind a wrapper that pipes stdin. Rule 15 covers name resolution being mistaken for reachability, which appeared at three sites at once. Rule 16 covers a prompt opening its own reader on the terminal and racing the wrapper that feeds its stdin. Also notes in CLAUDE.md that tailscale-api-token belongs in the operator vault rather than the deployment vault, since moving it for symmetry with the two Tailscale auth keys would hand a full-access credential to the server. The remark that confirm()'s interactive branch is unexercised is narrowed to the restic-key removal it was written about: confirm() itself has since run interactively, which is what surfaced rule 16.