Skip to content

testing: read config from the config-cascade layers, not ~/.claude - part 1 of 4 #18050

Open

Description

@melodic-automation-lanes

Part 1 of 4 of #17999, split at intake (owner Q93). The done-when below is copied from #17999 as written.

Done when

  • 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.
  • Removing the old-path read is a separate later change, made only once no old file is reported.

Activity

  1. added
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 21, 2026
  2. github-actions commented on Nov 21, 2026

    @github-actions
    Contributor

    Size: Small
    Complexity: Medium
    Uncertainty: Knowable
    Flags: none
    Blocked by: none
    Blast radius: the testing plugin's config resolver and whoever runs it. It reads the config-cascade layers and, for a window, still reads the old ~/.claude file.
    Reversible: yes; revert the resolver change. The old-path read stays in place until a separate later change removes it.
    Open questions: none

    I read this as part 1 of 4 of #17999, split at intake. The testing plugin's config resolver should read the config-cascade layers. While that window lasts, an old-path file is still read. Its values apply wherever no new-layer file supplies that layer, and each run prints one warning naming the old file and the new location. Removing the old-path read is a separate later change.

    The done-when is exact and the design is already chosen, so nothing is needed from the reporter. Parts 2-4 (#18051, #18052, #18053) are siblings from the same split, not duplicates. I found no merged pull request that already covers this.

    Automated triage. A maintainer reviews it.

  3. removed
    needs-triageNot yet classified. Floor until a type and one priority tier are set.
    on Nov 21, 2026
  4. melodic-automation-lanes commented on Nov 21, 2026

    @melodic-automation-lanes
    ContributorAuthor

    {"v":1,"actor_id":337595936,"title_sha256":"b9bb4ae568259fabc0d188f4b6f7df919f3a9b461802e00dd44f6e41e20d31ff","body_sha256":"2ef511c740db2cc735c29a2a01c44c85e4b25af67ac96101e57c28fd515385fd"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    Work status

    agent-ready

    Priority

    medium

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions