fix(enable): default repo-init and GitHub-create prompts to No

entire enable in a non-git directory offered to git init, create a GitHub repo, and push — but the interactive confirms defaulted to Yes, so reflexively pressing Enter blew through the whole cascade and published the directory's contents on the user's behalf (issue #1717).

Flip both confirms to default No so a bare Enter declines: the init prompt halts the cascade before git init, and the GitHub prompt never creates or pushes a remote unless the user explicitly opts in. Both prompts now show the absolute path in the title so a wrong-directory mistake is obvious in interactive and accessible modes. Non-interactive behavior is unchanged: without -y/--init-repo it already declines; those flags still bypass the prompts.