Description
When a retrospective (or ordinary session work) surfaces new evidence on a problem that is already reported upstream, or a new upstream-shaped finding, the assistant does not route it upstream on its own — it appends the evidence to the local ticket and stops. The user has to explicitly prompt before the evidence reaches the upstream maintainer.
The behaviour sits at two layers:
-
Tooling gap: run-retro Step 2b surfaces pipeline instability and can append evidence to a local ticket, but there is no step that routes NEW evidence on an already-upstream-reported ticket to an upstream comment. update-upstream exists for lifecycle transitions (root-cause-confirmed / fix-released / closed) but not for evidence-appends on a still-open ticket. So the retro has no channel to push new evidence upstream even when the local ticket already carries a ## Reported Upstream back-link.
-
Assistant-discipline gap: the assistant treats "append evidence locally" as done and leaves the outward propagation for the user to request.
Symptoms
- New evidence on an upstream-reported ticket lands only in the local problem body; the upstream issue is not updated until the user prompts.
- Newly-surfaced upstream-shaped findings from a retro are recorded in the local Pipeline Instability section but not filed/commented upstream without a prompt.
Affected plugin / component
@windyroad/retrospective (run-retro Step 2b) + @windyroad/itil (update-upstream skill).
Fix direction
- A run-retro Step 2b sub-step that, for detections that dedup to an already-upstream-reported ticket, drafts an upstream comment (gated through the external-comms + security-self-own review, then queued or auto-posted per appetite).
- And/or an
update-upstream extension covering evidence-appends, not just lifecycle transitions.
Cross-reference
Reported from a downstream adopter; tracked locally as P164.
Versions
- Local plugin:
@windyroad/* (cache: itil 0.57.1, retrospective 0.25.0)
- Claude Code CLI: 2.1.201 (Claude Code)
- Node: v22.17.1
- OS: Darwin 25.3.0 x86_64
Description
When a retrospective (or ordinary session work) surfaces new evidence on a problem that is already reported upstream, or a new upstream-shaped finding, the assistant does not route it upstream on its own — it appends the evidence to the local ticket and stops. The user has to explicitly prompt before the evidence reaches the upstream maintainer.
The behaviour sits at two layers:
Tooling gap:
run-retroStep 2b surfaces pipeline instability and can append evidence to a local ticket, but there is no step that routes NEW evidence on an already-upstream-reported ticket to an upstream comment.update-upstreamexists for lifecycle transitions (root-cause-confirmed / fix-released / closed) but not for evidence-appends on a still-open ticket. So the retro has no channel to push new evidence upstream even when the local ticket already carries a## Reported Upstreamback-link.Assistant-discipline gap: the assistant treats "append evidence locally" as done and leaves the outward propagation for the user to request.
Symptoms
Affected plugin / component
@windyroad/retrospective(run-retro Step 2b) +@windyroad/itil(update-upstream skill).Fix direction
update-upstreamextension covering evidence-appends, not just lifecycle transitions.Cross-reference
Reported from a downstream adopter; tracked locally as P164.
Versions
@windyroad/*(cache: itil 0.57.1, retrospective 0.25.0)