chore: validate schema generation in CI

[sakinaroufid]

Description

Adds a pre-commit hook to catch schema sync issues before commit, plus keeps CI validation as a safety net.

Right now you can edit source schemas, forget to run generate_schemas.py, and CI will pass. Then downstream tools break because spec/ is out of sync.

The pre-commit hook gives instant feedback (seconds instead of waiting for CI). But kept the CI check too in case someone bypasses pre-commit or doesn't have it installed.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected, including removal of schema files or fields)
• Documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[nearlyforget]

Thank you for this contribution. We are evaluating the changes and will provide a formal response within 1 - 2 weeks.

[nearlyforget]

To help us review this more effectively, could you please break this CI update down into multiple logical pieces?

Handling these as distinct logical units (e.g., separate commits or steps) allows us to validate the logic for each component independently and ensures our CI pipeline is modular.

Thanks for your help!

[sakinaroufid]

To help us review this more effectively, could you please break this CI update down into multiple logical pieces?

Handling these as distinct logical units (e.g., separate commits or steps) allows us to validate the logic for each component independently and ensures our CI pipeline is modular.

Thanks for your help!

Thanks for the feedback! @nearlyforget

Currently, this PR includes:

1. A new schema-validation.yml workflow file (schema generation, validation, and sync checks)
2. A pre-commit hook for local validation
3. Updates to workflow path triggers

I can split this into separate PRs if that works better for review. Just to clarify the process - are you a maintainer on this project? I want to make sure I'm following the right review workflow.

Cheers,
S

[nearlyforget]

Apologies for the late reply @sakinaroufid. There has been some changes on CI workflow, and yes, I'm a maintainer.
Would you be able to break it down into 3 parts you described and resolve the conflicts?

[sakinaroufid]

Hi @nearlyforget, I've split this into 3 separate PRs as requested!

1. chore(ci): add schema validation workflow #230 — Schema validation CI workflow + generator bug fix
2. chore(pre-commit): add local schema generation sync check #231 — Pre-commit hook for local schema sync check (depends on chore(ci): add schema validation workflow #230)
3. chore(ci): update workflow path triggers and improve docs build #232 — Workflow path triggers + docs build improvements

All three pass CI and have no conflicts with main. Happy to address any feedback on the individual PRs.