Support compiling a specific subschema in compile and validate

[jviotti]

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

[augmentcode]

🤖 Augment PR Summary

Summary: Adds support for compiling/validating against a specific subschema via a new --entrypoint/-p option.

Changes:

• Updated CLI docs/usage for compile and validate and added examples for JSON Pointer entrypoints.
• compile can now bundle/analyze the schema and compile starting from a resolved entrypoint URI.
• validate now resolves an entrypoint URI and passes it through to template compilation.
• Introduced resolve_entrypoint helper to normalize pointer/fragment inputs into an absolute entrypoint URI.
• Added error handling for invalid entrypoints with guidance to use inspect to find valid locations.
• Added new unit tests covering pointer, fragment-only, and URI entrypoints plus multiple failure modes.

Technical Notes: Pointer and fragment-only entrypoints are converted into an absolute URI by attaching the pointer as the schema root URI fragment before compilation.

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

[augmentcode]

Review completed. 2 suggestions posted.

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

[cubic-dev-ai]

4 issues found across 22 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="test/validate/pass_entrypoint_pointer_fragment.sh">

<violation number="1" location="test/validate/pass_entrypoint_pointer_fragment.sh:27">
P3: Capture and assert stdout as well as stderr so verbose tests detect unexpected output on either stream.

(Based on your team's feedback about capturing stdout and stderr in verbose tests.) [FEEDBACK_USED]</violation>
</file>

<file name="test/validate/pass_entrypoint_pointer.sh">

<violation number="1" location="test/validate/pass_entrypoint_pointer.sh:27">
P2: Capture and assert stdout as well as stderr in this verbose test; otherwise unexpected stdout output will be missed.

(Based on your team's feedback about capturing stdout and stderr using verbose tests.) [FEEDBACK_USED]</violation>
</file>

<file name="test/validate/pass_entrypoint_uri.sh">

<violation number="1" location="test/validate/pass_entrypoint_uri.sh:28">
P2: Capture stdout as well when running the verbose validate command, and assert it is empty to detect unexpected output.

(Based on your team's feedback about capturing stdout and stderr using verbose tests.) [FEEDBACK_USED]</violation>
</file>

<file name="test/validate/fail_entrypoint_mismatch.sh">

<violation number="1" location="test/validate/fail_entrypoint_mismatch.sh:27">
P3: Capture and assert stdout for the verbose failure case so the test detects unexpected output on either stream.

(Based on your team's feedback about capturing stdout and stderr using verbose tests.) [FEEDBACK_USED]</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}