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
Tell existing users to install plugin-diagnostics after the hook split #16591
#16519 moved harness-ops' session hooks into session-telemetry (off by default) and plugin-diagnostics (on by default). A marketplace update does not install a default-on plugin for a user who already has the marketplace: ADR 0109's probe row default-on-existing-users reads "a plugin added to the marketplace with defaultEnabled: true was not installed by marketplace update". So an existing user who updates gets harness-ops 10.0.0 with no hooks and no plugin-diagnostics, and nothing reports a hook that fails to launch.
plugins/harness-ops/CHANGELOG.md (the 10.0.0 entry) tells that user to enable session-telemetry and calls plugin-diagnostics "on by default", which reads as nothing to do.
Owner decision
2026-11-16, "go w/ recommendations" (control-hub#11): correct the wording only. No plugin dependency (the Q75 decision stands: a disabled dependency stops its dependent loading).
Done when
The harness-ops README and the plugin-diagnostics README say that an existing install must run claude plugin install plugin-diagnostics@melodic-software, and that "on by default" applies to a new install.
The same is said where a user upgrading harness-ops reads it: a changelog fragment for harness-ops and one for plugin-diagnostics (released entries are not rewritten unless the repository's changelog rule allows it).
Each statement points at the ADR 0109 probe row and does not restate it.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: after the hook split in #16519, existing users who update the marketplace don't get plugin-diagnostics installed automatically. The harness-ops and plugin-diagnostics READMEs and changelog fragments should say that existing installs must run claude plugin install plugin-diagnostics@melodic-software, that "on by default" applies to new installs, and point at the ADR 0109 probe row. This is a wording-only change with no behavior change. Nothing is missing, and I found no duplicate or merged fix.
Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 1 (a live Claude Code CLI run: "The harness-ops README and the plugin-diagnostics README say that an existing..."); recommended split: keep the other items here as the admissible issue and move these to a child issue for the host queue (host-run); it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
Activity
github-actions commentedon Nov 16, 2026
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood: after the hook split in #16519, existing users who update the marketplace don't get
plugin-diagnosticsinstalled automatically. The harness-ops and plugin-diagnostics READMEs and changelog fragments should say that existing installs must runclaude plugin install plugin-diagnostics@melodic-software, that "on by default" applies to new installs, and point at the ADR 0109 probe row. This is a wording-only change with no behavior change. Nothing is missing, and I found no duplicate or merged fix.Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 16, 2026
Not admitted to the issue lane: its done-when asks for what an unattended lane run cannot perform: item 1 (a live Claude Code CLI run: "The harness-ops README and the plugin-diagnostics README say that an existing..."); recommended split: keep the other items here as the admissible issue and move these to a child issue for the host queue (
host-run); it carries host-run. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).