CI builds and vets but never runs the tests #63

.gitbay/ci.yml is:

jobs:
  build:
    steps:
      - go build ./...
      - go vet ./...

So a green check on a merge request means the tree compiles and vets. It does not mean the suite passes. Every merge so far has been gated on a suite run from a laptop, by hand, and remembered — including the one where the runner of that suite reported a truncated log as green (#62).

What it needs, and why it is not a one-line change:

• The e2e package drives real git, ssh, sshd, gpg and a live daemon. The runner host needs all of them installed, not just a go toolchain.
• The suite takes 8-11 minutes. That is a long-held runner slot on a single-runner instance, and it would run on every push.
• A build step runs with the runner account's ambient credentials, which belong to an instance admin (see #28). Widening what CI does widens what a pushed ci.yml can reach.

Also worth deciding alongside: Require green checks is off on krz/gitbay, so even the build job does not currently block a merge.