The boss-attack e2e test keeps reporting bossHp completely unchanged
(1200, not just short of the timeout) on the CI runner, across two
separate runs, while it passes reliably in ~11s locally. Couldn't get
more signal from the runner itself: test-results/ (screenshots,
trace.zip, error-context.md) was never uploaded anywhere by the
workflow, so it's gone the moment the ephemeral job container is torn
down -- there was nothing left to retrieve.
Two changes to actually get signal on the next failure instead of
guessing blind:
- internal/transport/http.go: a rejected intent (e.g. "boss out of
reach", "attack cooldown") already gets stored on c.Message for the
client to show as a notice, but was never logged server-side. Now it
is, via slog.Warn, so it shows up directly in the [WebServer] console
output already captured in the job log -- no artifact retrieval
needed.
- .gitea/workflows/build.yaml: upload test-results/ as a build artifact
when the verify job fails, so trace.zip etc. survive past the job
container for cases where the console log alone isn't enough.
Verified server still builds/vets clean and the full local e2e suite
(all 7 tests across game.spec.ts + portal.spec.ts, matching CI's count)
still passes.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>