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
Split from the changelog release issue(s) above under the owner's decision of 2026-11-21 (melodic-software/architecture#148): one issue per handoff row, rows that edit the same file grouped.
Route: lane work. Basis: adopt: drafted rules rest on real denials instead of interview recall; the skill's users are the consumer, and it reads a native surface.
Problem
The skill has no denial-history input and routes only the environment section to the native
/auto-mode-setup; the native command now scans recent auto mode denials and can offer allow rules
from them, reviewed one by one before saving, which could supply the allow-rule input the interview
lacks. auto-mode-config does not yet document
the denial scan.
Repo evidence: plugins/harness-config/skills/draft-auto-mode-rules/SKILL.md:56-59 (routing) and SKILL.md:81 (no history input).
Done when
the Routing section offers /auto-mode-setup's
denial-based allow rules as input to the allow section, and reference/native-auto-mode-setup.md
records what the command now reads and writes, with its version.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: one skill's SKILL.md routing section and one reference file in the harness-config plugin; read by users of the draft-auto-mode-rules skill.
Reversible: yes; revert the doc edits.
Open questions: none
Understood: update the Routing section to offer /auto-mode-setup's denial-based allow rules as input to the allow section, and record in reference/native-auto-mode-setup.md what the command reads and writes, with its version (2.1.329). Related open issue #17555 is the parent changelog issue; #17886-era merges do not already cover this.
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44938445030, the work-resolve-issue run that agent-ready started, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T19:18:57Z. work-unblock has now removed and added agent-ready back to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or the kill-switch wait.
Activity
github-actions commentedon Nov 21, 2026
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: one skill's SKILL.md routing section and one reference file in the harness-config plugin; read by users of the draft-auto-mode-rules skill.
Reversible: yes; revert the doc edits.
Open questions: none
Understood: update the Routing section to offer /auto-mode-setup's denial-based allow rules as input to the allow section, and record in reference/native-auto-mode-setup.md what the command reads and writes, with its version (2.1.329). Related open issue #17555 is the parent changelog issue; #17886-era merges do not already cover this.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"b816fe2bbd1847a597eb3336dc37ae3ec75e12f4366fa853943ffda911b22cea","body_sha256":"6ebc1ce5c4c07abf09f834feaed791918949a36954f2cd221ae886744a0df2c5"}
melodic-automation-lanes commentedon Nov 21, 2026
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44938445030, the work-resolve-issue run that
agent-readystarted, before any model turn, because the GITHUB_TOKEN budget was under its start-gate share, or the window was projected to have under its start-project share of the header's limit left by the run's expected end (github-token start-gate, start-project and start-run-minutes in rate-limits.json; the run's start-gate notice names which); that run ended at 2026-11-21T19:18:57Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A budget stop is the lanes' load, not a fault in this issue: it never counts toward limits.limit-stops-per-issue or thekill-switchwait.github-actions commentedon Nov 21, 2026