← All findingssource · memory/feedback_pipeline_exit_status_false_green.md
What happened (2026-08-30, SDS 5debdd7): verification chain was
(cd wt && go build && go vet && go test ./... | tail -12) && ok=1 … && git push. In zsh/bash
the pipeline's status is the LAST command's (tail), so ok=1 was set although go test
failed, and the push went out with a red suite. Separately, git add -A internal/handlers
committed status_history_test.go, a pre-existing UNTRACKED stray test (the same family of
strays an agent once moved to /private/tmp/stray2) — that was the failing test.
Why: the user's rule is "done = ran it and observed it working"; a pipe that hides the
real status is not observing. And -A on a directory adds whatever junk lives there.
How to apply: capture the status explicitly (go test ./... > log; rc=$? or
set -o pipefail) and gate the push on rc. Never git add -A <dir>; add named files or
git add -u + the specific new files. Before committing in SDS, remember the known strays:
internal/handlers/status_history_test.go, internal/adapters/nba/boxscore_participation_test.go.