Bare go test ./... times out before the e2e suite finishes #143

go test defaults to a 10-minute timeout. The e2e suite alone takes ~394s on bay1's CI runner and ~660-870s on a laptop, so go test ./... typed directly panics part way through:

panic: test timed out after 10m0s
	running tests:
		TestOwnerProfiles (4s)

The named test is whatever happened to be in flight when the alarm fired, not the cause, so the output points at an innocent test and reads like a hang. It cost this session two full 11-minute runs and a wrong report that a branch was failing.

make test passes -timeout 30m and .gitbay/ci.yml passes -timeout 20m, so neither hits it. The bare command is what CONTRIBUTING.org:27 asks a contributor to run ("go build ./... and go test ./... must be green"), and what Users.org:386 and Roadmap.org:232 both repeat.

Remedy: point CONTRIBUTING and the wiki at make test, and say in the e2e package why a bare go test needs -timeout. A TestMain that fails fast with that explanation when the deadline is under, say, 15 minutes would turn the confusing panic into a sentence.