daily-fix: bake self-pid exclusion into single-flight probe
kind: infra#wf-fix#wf-fix-fp:b31a9cd2b342#daily-auto-filed
track:Highlight text on any card (body, plan, or an event) to anchor a comment, or leave a whole-task comment here. Mention @claude to summon a reply.
No comments yet.
Overview / Motivation
Auto-filed by the /daily 2026-07-28 problem sweep (transcript miners over the day's 55 session transcripts). Source: group-I P6 (rule anchor miner-probed; re-verified).
Goal
Replace the remembered single-flight probe-placement rule with a mechanical self-pid-excluding probe.
Workflow gap
- Bug observed: #1742's session folded the Step 9c single-flight probe inside the launch call; the probe matched its own wrapper (the documented #1606 trap) despite SKILL.md line 7329's explicit 'in a separate FOREGROUND call — never inside' rule. One more re-hit of a rule that exists precisely because it keeps being forgotten.
- Why it is a workflow gap: the defense is prose placement discipline; a self-pid-excluding probe (helper or entrypoint-internal) removes the failure mode regardless of placement.
- Confidence (emitter): medium-high
- verified-at-filing:
grep -n 'separate FOREGROUND call' .claude/skills/issue/SKILL.md→ line 7329 (rule present, trap still re-hit) (2026-07-29 UTC).
Proposed change (candidate diff sketch — refine in planning)
A helper (or step9c_baseline.py entry-internal probe) with -P $$/pgid exclusion + bracket pattern; SKILL.md snippet updated to call it.
Scope / surfaces
- Primary targets:
scripts/step9c_baseline.py,.claude/skills/issue/SKILL.md(Step 9c 1b snippet)
Constraints / invariants
- Workflow-surface only — never experiment code,
configs/, ortasks/. scripts/workflow_lint.py --check-askspasses; ruff on touched files passes.- The spawned session runs under a
workflow_fix_target:Provenance line — recursion guard applies (it parks, never auto-routes, its own subagents' workflow-fix candidates).
Provenance
-
fingerprint: b31a9cd2b342
-
workflow_fix_target: scripts/step9c_baseline.py
Activity