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
refactor(bugs): move the .claude/bugs.md settings to docs/conventions/bugs.yaml #9730
The bugs, harness-ops settings this repository keeps in .claude/bugs.md (its fenced YAML block) resolve from docs/conventions/bugs.yaml,
validated by a schema the plugin ships. The old location is read only when the YAML is absent, for one release.
The setup skill, if the plugin has one, writes the YAML.
Decisions
ADR 0064 Decision 1: a plugin's team settings live in one docs/conventions/<concern>.yaml, validated by a
JSON Schema at plugins/<plugin>/schemas/<concern>.schema.json (Decision 6), checked in CI by scripts/check-convention-yaml.sh (Decision 7). Script readers use the shared reader lib/parse-concern-value.sh.
ADR 0075: layers are plugin default < userConfig < team <home>/<concern>.yaml < personal <home>/<concern>.local.<ext>; every resolver reports the layer that supplied each value.
/bugs:scan's lane and filing-posture reader, plugins/bugs/reference/config.md, harness-ops' mention. The prose stays as docs/conventions/bugs.md (ADR 0075: prose in <concern>.md).
Done when
docs/conventions/bugs.yaml carries every value of .claude/bugs.md (its fenced YAML block) and scripts/check-convention-yaml.sh --check exits 0 against plugins/bugs/schemas/bugs.schema.json.
The skill bodies that read the settings name docs/conventions/bugs.yaml first and the old location only as the one-release fallback (git grep -n "docs/conventions/bugs.yaml" -- plugins/bugs/skills prints each).
No skill body tells an agent to read or write the old location: git grep -n for it under plugins/bugs, plugins/harness-ops prints only compatibility-read code, its tests and changelog lines.
The PR body lists each migrated setting with its new home and schema.
The work-resolve-issue run that agent-ready started failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and added agent-ready back to start a fresh run on main's workflow files. It does this once per version of those files, so if this run fails the same way, a person looks at it.
The work-resolve-issue lane stopped on its usage limit, not on this issue. It keeps agent-ready, and work-unblock starts it again after 2026-10-25T16:00:00Z.
Activity
melodic-automation-lanes commentedon Oct 24, 2026
The work-resolve-issue run that
agent-readystarted failed or was cancelled before it reported, or it stopped or the token broker refused it because its workflow files differ from main's. work-unblock removed and addedagent-readyback to start a fresh run on main's workflow files. It does this once per version of those files, so if this run fails the same way, a person looks at it.melodic-automation-lanes commentedon Oct 24, 2026
The work-resolve-issue lane stopped on its usage limit, not on this issue. It keeps
agent-ready, and work-unblock starts it again after 2026-10-25T16:00:00Z.Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/40140300709