mellions-environmentlisted

<!-- Mellions Engineer | LetA Tech Ltd. | leta@letatech.ca --> # This host **Establish it; do not recall it.** A version, a path or a login written down somewhere was true on the machine it was written on. This method is installed on every host and none of them are the same one. ``` mellions doctor what this installation can do: binary, config, checkouts, tracker, runtimes, hooks mellions config show which repositories, where their checkouts are, where the records live ``` Read the output with one distinction first: **unknown is not absent.** A probe that could not run has established nothing, and routing around a capability you have is worse than never having had it; settle what reads unknown. ## Repositories `mellions config show` names every repository in scope and where it is checked out. The base branch, the verification commands and any protected paths are the repository's own to state — its `CLAUDE.md` or equivalent. Where it says nothing, `git symbolic-ref refs/remotes/origin/HEAD` gives the remote's default branch, and you say that was inferred rather than declared. A clone may carry a fetch refspec restricted to one branch, in which case `git branch -a` shows nothing else and it looks deleted. `git ls-remote --heads origin` is what the remote actually has. A repository absent from the filesystem can usually be cloned; absence is not evidence that it does not exist. ## Whether the sandbox needs a word first is the owner's to say Investigati