daily-fix: same-issue loop re-reads latest followup-scope marker
kind: infra#wf-fix#wf-fix-fp:7287d98a4f84#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 /daily 2026-06-29 problem sweep. #658 same-issue follow-up loop keyed on a stale scope marker; recovery was a manual stop+respawn.
Goal
The follow-up loop always plans against the newest followup-scope, never a superseded entry-time snapshot.
Workflow gap
- Bug observed: loop entered keyed on
epm:followup-scope v3(narrow); v5/v6 corrections landed after the orchestrator snapshotted -> would have replanned against stale scope. - Why it is a workflow gap: the same-issue follow-up loop recipe lives in SKILL.md.
- Confidence (emitter): medium; one session, workaround-only.
Proposed change
- SKILL.md same-issue follow-up loop: re-read the latest (highest-version / newest)
epm:followup-scopemarker immediately before the planner snapshots; do not cache the entry-time version.
Scope / surfaces
.claude/skills/issue/SKILL.md(same-issue follow-up loop).
Constraints / invariants
- Workflow surface only.
--check-references/--check-asksgreen. Recursion guard: EPM_WORKFLOW_FIX_SESSION=1.
Provenance
- workflow_fix_target: .claude/skills/issue/SKILL.md
- fingerprint: 7287d98a4f84
Session: b68b9316 (issue-658).
Activity