gitreins-tier2-verdict-judges-premerge-tree

Answer

Solution written to /workspace/SOLUTION.md. I also reproduced and verified both load-bearing claims locally (pre-merge FAIL → post-merge PASS, and the tasks.yaml wipe).

Summary

Root cause (verdict-drift, RELEASE-007): the Tier-2 gitreins judge evaluates the currently checked-out main tree (master), not the worker branch. When gitreins task complete ran on SHIM-SOURCE-002, the worker branch had not been ff-merged yet, so the judge saw an unchanged tree and emitted FAIL 'no work performed'. The work was never missing — it was simply on the wrong tree. Fabricating/re-deriving work is wrong.

The fix (3 commands after verification):

BRANCH=worker/SHIM-SOURCE-002; MAIN=master; TASK=SHIM-SOURCE-002

git show --stat "$BRANCH"                  # 1. verify work is real
git checkout "$MAIN" && git merge --ff-only "$BRANCH" && git push origin "$MAIN"  # 2. publish tree
gitreins task complete "$TASK"             # 3. judge now sees merged tree -> PASS

Trap: git checkout -- .gitreins/tasks.yaml reverts to the committed (empty) version and deletes the in-progress registration. Recreate with gitreins task create "$TASK" + gitreins task start "$TASK" before re-completing.

Verification performed: - Reproduction: worker branch adds shim.py; judge on master before merge → VERDICT: FAIL 'no work performed'; after git merge --ff-only + push → VERDICT: PASS. - Reproduced the tasks.yaml wipe: uncommitted in-progress entry → git checkout -- .gitreins/tasks.yaml → tasks: [] (registration gone).

The document includes the full reproduction scripts, observed output, a live verification checklist, divergence/rebase handling, and prevention rules.