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
harness-config: read audit-pass config from the config-cascade layers, not ~/.claude #18007
harness-config (audit-pass) still reads its user-global and personal config from a user directory and .claude/. Move both to the config-cascade layers.
The engine reads the contract layers; a file at an old path keeps being read during a dual-read window (see the acceptance criteria) and is reported with a warning. The canonical location list (docs/contracts/config-cascade/locations.md) lands in the docs/config-locations pull request.
Key interfaces
load_markdown_layer calls and the layer names the audit pass reports
Acceptance criteria
The resolver reads the config-cascade layers (the layers).
Dual-read window: while an old-path file exists, it is still read and its values still apply where no new-layer file supplies that layer; each run prints one warning naming the old file and the new location to move it to. No setting in an old file is silently dropped.
The plugin's setup (check/apply), where it has one, names each old file it finds and after a preview and a yes, moves its settings to the new location, checks the new location resolves the same values, then deletes the old file, so migration ends in one home, never two (owner 2026-11-21: "we don't have dual approaches, and that stuff gets cleaned up"); the dual-read warning names that setup command, so normal skill use leads to the migration.
Removing the old-path read is a separate later change, made only once no old file is reported.
Tests cover: new layer only; old file only (values apply, warning printed); both present (new wins, warning names both).
Placement rule (owner decisions 2026-11-21, #18000 Q1 and #18009 Q2)
For each key in the old user-global file, choose the new home by what the key is:
a per-repo convention (what a repository's commits, PRs or files must look like): the team file <home>/<concern>.yaml, with the personal override for one person in one repo; no new userConfig option;
a per-user value userConfig can hold (string, number, boolean, directory, file, list of strings): a userConfig option;
a per-user structure userConfig cannot hold (a list of objects, a nested map): one file-typed userConfig option naming the user's file, which keeps the structure as it is.
If a key fits none of these, stop as design-change and name the key.
Out of scope
Other plugins' resolvers (one issue each), and the audit-pass lane logic.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the harness-config audit engine script, its setup (check/apply) and tests; anyone running the audit pass with an old-path config file.
Reversible: yes; revert the change, and the dual-read window keeps old files working until the setup migration deletes them.
Open questions: none
I understood this as moving the audit-pass user-global and personal config reads to the config-cascade layers. Old-path files stay readable during a dual-read window, with a warning. Setup migrates them and removes the old file. The acceptance criteria and placement rule are exact, so no owner decision is needed. Related per-plugin issues such as #18000 to #18014 cover other plugins' resolvers and are not duplicates.
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44960301577, 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-21T23:27:01Z. 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: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Blocked by: none
Blast radius: the harness-config audit engine script, its setup (check/apply) and tests; anyone running the audit pass with an old-path config file.
Reversible: yes; revert the change, and the dual-read window keeps old files working until the setup migration deletes them.
Open questions: none
I understood this as moving the audit-pass user-global and personal config reads to the config-cascade layers. Old-path files stay readable during a dual-read window, with a warning. Setup migrates them and removes the old file. The acceptance criteria and placement rule are exact, so no owner decision is needed. Related per-plugin issues such as #18000 to #18014 cover other plugins' resolvers and are not duplicates.
Automated triage. A maintainer reviews it.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"86850edcf89c03c9134dae1f3b770030cfeda3f976c6a9ff04acc6c21a24b7dd","body_sha256":"95dfb42cc734023cbb9885228831bd1b18cdb763144c7486e89c0ebd90464415"}
melodic-automation-lanes commentedon Nov 21, 2026
Not admitted to the issue lane yet: its body was edited after it was deferred, so the admission it was deferred from judged an older body.
Intake triages this issue again, against its body as it stands now.
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"86850edcf89c03c9134dae1f3b770030cfeda3f976c6a9ff04acc6c21a24b7dd","body_sha256":"180f16f68e6dca37af24a3c23c125b34e9974345637a89a5fdeeab9d3e0dfbd2"}
melodic-automation-lanes commentedon Nov 21, 2026
{"v":1,"actor_id":337595936,"title_sha256":"86850edcf89c03c9134dae1f3b770030cfeda3f976c6a9ff04acc6c21a24b7dd","body_sha256":"ed76df990a6d01cfd4cdf743bf61377af1aa0686a353dc655e59be7a5c8700b4"}
melodic-automation-lanes commentedon Nov 22, 2026
This records a re-fire of an earlier stop, not a new one. The start gate stopped run 44960301577, 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-21T23:27:01Z. 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 22, 2026