spec-koh Document or standardise specs' version-stamping mechanism in its APKBUILD Lined Up

What is wrong: specs' APKBUILD passes no `VERSION=` to `make build` and relies entirely on Go's automatic VCS stamp (`debug.ReadBuildInfo`) for its version string, with no comment explaining that this is the chosen mechanism.

Why it matters: `artifacts`, `coverage` and `tokens` instead define `_version="${SRHT_VERSION:-$pkgver}"` and inject it via `-ldflags -X`, which is strictly more explicit — it does not depend on the build having been run inside a git checkout. `phoebe-lab/srht/CLAUDE.md` documents `docker logs srht-<svc>-1 | grep version=` as the universal way to verify a deploy, implying both mechanisms are expected to produce a usable startup log line, but nothing states that specs made a deliberate choice rather than just defaulting.

Sibling that does it correctly: neither is wrong on its own; the gap is that the choice isn't recorded anywhere. `sourcehut-artifacts`/`sourcehut-coverage`/`sourcehut-tokens` show the explicit ldflags form if that's preferred instead.

Fix: add a one-line comment to specs' APKBUILD stating it relies on the Go VCS stamp and why (or switch to the ldflags form to match the other convention), so the split reads as a decision rather than an accident.

Note: confidence unverified — whether the two mechanisms are truly equivalent for specs' actual startup log line was not traced into `cmd/specsrht/main.go`; verify before treating this as more than a documentation gap.

Audit: D43 (cross-repo audit, 2026-08-17)