fix(skills): /merge — prefer fixture logs in candidate signal intake (line 63)

[OriginalGary]

Problem

claude-code/.claude/skills/merge/SKILL.md line 63 selects the latest orchestrator log via:

LATEST=$(ls -t ~/.claude/orchestrator-log/run-*.md 2>/dev/null | head -1)

This bypasses fixture-log precedence: when a fixture log exists for deterministic test verification, a newer non-fixture log can shadow it and skew confidence calibration. Breaks the campaign contract for /merge testing.

Evidence

CodeRabbit has flagged this on every push to PR #33 since 5a906790 (4 reviews running):

• feat(skills): /merge — ranked merge queue with honest confidence scoring #33 (review) (12:06Z)
• feat(skills): /merge — ranked merge queue with honest confidence scoring #33 (review) (12:12Z)
• feat(skills): /merge — ranked merge queue with honest confidence scoring #33 (review) (09:15Z)
• Latest in PR feat(skills): /merge — ranked merge queue with honest confidence scoring #33's bb59fd9 re-review at 03:21Z (today)

Spec

Update the LATEST selection to prefer fixture logs first, fall back to general:

-LATEST=$(ls -t ~/.claude/orchestrator-log/run-*.md 2>/dev/null | head -1)
+LATEST=$(ls -t ~/.claude/orchestrator-log/run-*-fixture.md 2>/dev/null | head -1)
+if [ -z "$LATEST" ]; then
+  LATEST=$(ls -t ~/.claude/orchestrator-log/run-*.md 2>/dev/null | head -1)
+fi

Why this is a separate issue from #36

#36 is scoped to adding the BLOCKED MED-cap bullet only. The line-63 fixture-log concern pre-dates that work — folding it into PR #33 violates the no-scope-creep rule per ~/.claude/rules/pipeline-nevers.md. Filed separately so the line-63 fix can land in its own commit on its own branch.

Sensitivity

sensitivity:staff-ok — pure technical fix, no PII, no funder dynamics, no campaign intel.

Filed by

OpenGaryBot from /run orchestrator at operator request after the 03:35Z fire surfaced the recurring CodeRabbit finding.

[OriginalGary]

STAGE 2 — Triage

Classification confirmed: auto:auto-fixable

• Verifiable end state — exact diff in issue body, single file, single line block
• Bounded blast — claude-code/.claude/skills/merge/SKILL.md only; no consumers of the existing glob outside this skill
• CI-verifiable / locally-reproducible — fixture log can be staged in ~/.claude/orchestrator-log/ and /merge re-run to confirm precedence
• No information-access gap — Gary owns the file, the test harness, and the fixture
• No decision conflict — fixture-log selection is mechanical; nothing in $OP_CONTEXT_REPO/decisions.md or proposals/ touches it
• Sensitivity — staff-ok correct; only public PR review URLs referenced

Labels applied:

• +component:pipeline-config (matches related feat(skills): /merge — add mergeStateStatus calibration to flag BLOCKED / DIRTY PRs #36, same skill doc surface)
• +stage:ready-for-plan
• -stage:triaged

Note for next stage: existing status:done label appears stale (likely sticky from a prior batch operation). Plan stage may want to verify or strip it — out of triage scope.

Advancing to STAGE 3 (plan).