Fix jsonschema.json ignore not taking effect given positional arguments

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR fixes configuration-defined ignore/extension behavior not taking effect when inputs are provided as positional arguments.

Changes:

• Teach for_each_json() to load a shared jsonschema.json configuration (when a single config is detected) and pass it into parse_extensions so directory traversal honors configured extensions.
• Continue merging configuration-derived ignore paths for each discovered configuration file in positional-argument mode.
• Add a new lint test to ensure a configured extension list filters directory scans correctly.
• Update many existing tests’ verbose output expectations to include the now-emitted “Using extension: …” lines.

Technical Notes: Extension matching for directory recursion now becomes configuration-aware for positional inputs when the configuration file is unambiguous.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

When positional arguments resolve to multiple different jsonschema.json files, merge_configuration_ignore merges ignore rules from all of them but parse_extensions will fall back to std::nullopt (so per-directory configured extension filtering won’t apply for directory traversal). Is that behavior intended, or should extension configuration also be applied when multiple configurations are in play?

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[cubic-dev-ai]

1 issue found across 28 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>