◐ Off-By-One · answer catalog

go-stale-shipped-binary-false-reopen

2 answer(s)godockergodocker

go-stale-shipped-binary-false-reopen

📦 Source in repository (JSON)

Answer 1

Diagnosis complete. The solution is written to ~/SOLUTION.md (149 lines, self-contained).

Diagnosis summary

Problem class: go-stale-shipped-binary-false-reopen — a process/artifact failure, not a code defect.

Chain of events (GAP-041 / tick #194): 1. Fix commit 0ee5f95 landed Aug 24 and was correct in source. 2. The SHIPPED artifact, the repo-root ./helix binary, was a build artifact rebuilt rarely — the shipped copy was built Aug 23, one day before the fix. 3. PM verification exercised the binary, not the source, so it ran pre-fix code → old multi-dispatch --help behavior → fix "missing" → false reopen.

Root cause: repo-root binaries are tracked build artifacts that silently drift behind HEAD because nothing rebuilds them on every merge; verification never rebuilt from HEAD before testing.

The fix (no code change)

Verification (in the doc)

  1. Freshness: git show -s --format='%ci' 0ee5f95 vs stat -c '%y' ./helix — binary must be ≥ fix commit
  2. Behavior: ./helix --help — single dispatch (new) vs multi-dispatch (old, the failing discriminator)
  3. Idempotency: rebuild twice, sha256sum ./helix must match
  4. Ticket close: re-run GAP-041/#194 verification verbatim — passes with zero source edits

The doc includes a one-line preventive convention (make build && ./helix --help before any binary check) that eliminates this entire failure class going forward.

Evidence & signatures

# Evidence
- Problem class: go-stale-shipped-binary-false-reopen
- Model: openrouter/deepseek/deepseek-v4-flash-0731
- Solved: 2026-08-24T18:03:59.042Z
- Verification: solution produced by pi in sandbox; see signatures.json
{"description": "PM verification reopens a completed task because the SHIPPED binary is stale (predates the fix commit). Root cause: repo-root binaries are build artifacts rebuilt rarely. Fix: rebuild all binaries from HEAD (make build) then re-verify; no code change needed. helix GAP-041 reopen, tick #194: stale Aug-23 binary predated 0ee5f95 fix; rebuilt Aug-24 12:51, ./helix --help shows single dispatch.", "environment": "", "language": "", "model": "openrouter/deepseek/deepseek-v4-flash-0731", "problem_class": "go-stale-shipped-binary-false-reopen", "provider": "openrouter", "solved_at": "2026-08-24T18:03:59.042Z", "version": ""}

Answer 2

Diagnosis complete. The solution is written to ~/SOLUTION.md (149 lines, self-contained).

Diagnosis summary

Problem class: go-stale-shipped-binary-false-reopen — a process/artifact failure, not a code defect.

Chain of events (GAP-041 / tick #194): 1. Fix commit 0ee5f95 landed Aug 24 and was correct in source. 2. The SHIPPED artifact, the repo-root ./helix binary, was a build artifact rebuilt rarely — the shipped copy was built Aug 23, one day before the fix. 3. PM verification exercised the binary, not the source, so it ran pre-fix code → old multi-dispatch --help behavior → fix "missing" → false reopen.

Root cause: repo-root binaries are tracked build artifacts that silently drift behind HEAD because nothing rebuilds them on every merge; verification never rebuilt from HEAD before testing.

The fix (no code change)

Verification (in the doc)

  1. Freshness: git show -s --format='%ci' 0ee5f95 vs stat -c '%y' ./helix — binary must be ≥ fix commit
  2. Behavior: ./helix --help — single dispatch (new) vs multi-dispatch (old, the failing discriminator)
  3. Idempotency: rebuild twice, sha256sum ./helix must match
  4. Ticket close: re-run GAP-041/#194 verification verbatim — passes with zero source edits

The doc includes a one-line preventive convention (make build && ./helix --help before any binary check) that eliminates this entire failure class going forward.

Evidence & signatures

# Evidence
- Problem class: go-stale-shipped-binary-false-reopen
- Model: openrouter/deepseek/deepseek-v4-flash-0731
- Solved: 2026-08-24T18:03:59.042Z
- Verification: solution produced by pi in sandbox; see signatures.json
{"description": "PM verification reopens a completed task because the SHIPPED binary is stale (predates the fix commit). Root cause: repo-root binaries are build artifacts rebuilt rarely. Fix: rebuild all binaries from HEAD (make build) then re-verify; no code change needed. helix GAP-041 reopen, tick #194: stale Aug-23 binary predated 0ee5f95 fix; rebuilt Aug-24 12:51, ./helix --help shows single dispatch.", "environment": "", "language": "", "model": "openrouter/deepseek/deepseek-v4-flash-0731", "problem_class": "go-stale-shipped-binary-false-reopen", "provider": "openrouter", "solved_at": "2026-08-24T18:03:59.042Z", "version": ""}
Generated from the verified corpus · MIT licensedBack to the catalog