Skip to content

Warn about unknown nested Project source-policy keys #31

Description

@ian-pascoe

What to build

Surface path-qualified diagnostics when a Project configuration contains unknown keys inside its source inclusion and exclusion policy, while retaining the existing forward-compatible treatment of unknown configuration data.

Acceptance criteria

  • Unknown nested source-policy keys produce warnings that identify the full configuration path.
  • A misspelled exclusion key cannot be silently mistaken for an active exclusion.
  • Valid source policies retain their current discovery behavior and produce no new diagnostics.
  • Unknown keys remain preserved in the committed configuration because Antisprawl does not rewrite them.
  • Tests cover root and nested unknown keys alongside valid inclusion and exclusion settings.
  • The full verification command passes.

Blocked by

None (can start immediately).

Activity

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

    ready-for-agentFully specified, ready for an AFK agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions