You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(harness-ops): replace the 'session start' auto-update wording with a docs pointer (split from #6055) #6196
This was generated by AI during attend-queue. Split from #6055 (item 7) on 2026-10-04 (operator direction: "go with the recommendations"). Operator-ratified as C3 bug-fix-shaped.
What
The harness-ops plugins skill says plugin auto-update happens at "session start", in three places:
gotchas.md:107-108
render-report.jq:44
golden withheld-downgrade.txt:1
Anthropic's plugins/loading page says auto-update runs in interactive sessions, after the first message, after a random delay.
Fix
Point gotchas.md at that docs section instead of restating the timing, with an as-of date and recheck trigger per .claude/rules/skill-bodies-state-current-rules.md.
Correct the render string and the golden.
CHANGELOG entry and version bump.
Independent of #6055's items 1-6. Conflicts on plugin.json and the CHANGELOG with the #6182-#6187 cluster.
Thanks for the report. I understood this as: the harness-ops plugins skill states plugin auto-update happens "at session start" in three places (gotchas.md, render-report.jq's rendered string, and the withheld-downgrade.txt golden fixture), but the actual behavior per Anthropic's docs is that auto-update runs during interactive sessions after the first message, following a random delay — not strictly at session start. I confirmed all three cited locations currently use the "session start" wording. The proposed fix (pointing gotchas.md at the docs section with an as-of date and recheck trigger, correcting the render string and golden, plus a CHANGELOG entry and version bump) looks well scoped and consistent with this repo's conventions. No duplicates found; this is a split-out item from #6055 and is independent of its other items, though it may conflict with the #6182–#6187 cluster on plugin.json/CHANGELOG as noted.
Classification: work-class: scoped (C3). Intended dispatch: the work-loop worker lane, through /work-items:work, to a draft PR the lane never merges, after its blocked-by edges clear. Harness-ops items run one at a time. The first-drain gate dispatches a C3 item only on a ratification reply to this marker. A decision comment or an operator-ratified note in the body is context, not dispatch authority. So it is queued here, keeping its labels, until /work-items:attend-queue records the reply.
Operator ratification (2026-10-04): ratified as C3, bug-fix-shaped. This replies to the kind=ratify-c3 marker above. The operator's direction was "go with the recommendations, make them agent ready". The brief is in the earlier attend-queue decision comment or in the issue body; follow any blocked-by edge on this item.
Activity
github-actions commentedon Oct 4, 2026
Thanks for the report. I understood this as: the harness-ops
pluginsskill states plugin auto-update happens "at session start" in three places (gotchas.md,render-report.jq's rendered string, and thewithheld-downgrade.txtgolden fixture), but the actual behavior per Anthropic's docs is that auto-update runs during interactive sessions after the first message, following a random delay — not strictly at session start. I confirmed all three cited locations currently use the "session start" wording. The proposed fix (pointinggotchas.mdat the docs section with an as-of date and recheck trigger, correcting the render string and golden, plus a CHANGELOG entry and version bump) looks well scoped and consistent with this repo's conventions. No duplicates found; this is a split-out item from #6055 and is independent of its other items, though it may conflict with the #6182–#6187 cluster onplugin.json/CHANGELOG as noted.Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 4, 2026
This was generated by AI during work-loop.
Ratify autonomous dispatch of this C3 item?
Classification:
work-class: scoped(C3). Intended dispatch: the work-loop worker lane, through/work-items:work, to a draft PR the lane never merges, after its blocked-by edges clear. Harness-ops items run one at a time. The first-drain gate dispatches a C3 item only on a ratification reply to this marker. A decision comment or an operator-ratified note in the body is context, not dispatch authority. So it is queued here, keeping its labels, until/work-items:attend-queuerecords the reply.Lane: work-loop, instance melo-worker-1, cycle 1.
kyle-sexton commentedon Oct 4, 2026
kyle-sexton commentedon Oct 4, 2026
This was generated by AI during attend-queue.
Operator ratification (2026-10-04): ratified as C3, bug-fix-shaped. This replies to the
kind=ratify-c3marker above. The operator's direction was "go with the recommendations, make them agent ready". The brief is in the earlier attend-queue decision comment or in the issue body; follow any blocked-by edge on this item.fix(harness-ops): drop the last session-start auto-update timing claim