v1.0.2: chore(deps): bump checkout/setup-node/github-script for Node 24 runner

GitHub forces all action runners to Node 24 by default starting
2026-06-02. The v4 majors of checkout + setup-node and the v7 major of
github-script still run on Node 20, which triggers the deprecation
warning visible in adopter workflow logs today and will break outright
after the cutover.

Bump to current stable majors — no input/output changes, no adopter
migration required:
  actions/checkout       v4 → v6 (README example only)
  actions/setup-node     v4 → v6
  actions/github-script  v7 → v9

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

v1.0.1 — fix --strict bug

v1.0.0 passed a non-existent --strict flag to meta verify. Action now uses the CLI's actual surface (--prompts <dir>). Surfaced via dogfooding.

v1.0.0 — initial release

First public release of metaobjectsdev/meta-verify-action.

What this does

Catches metadata-vs-code drift in a MetaObjects project at PR time. Composite GitHub Action wrapping meta verify from @metaobjectsdev/cli.

Two-line adopter usage

- uses: actions/checkout@v4
- uses: metaobjectsdev/meta-verify-action@v1

That's the entire adopter surface. The action installs @metaobjectsdev/cli, runs meta verify --strict, and fails the workflow if drift is detected. With comment-on-pr: true (the default), the drift report posts as a PR comment.

With a database

- uses: metaobjectsdev/meta-verify-action@v1
  with:
    database-url: \${{ secrets.DATABASE_URL }}

Catches "added a column to YAML, forgot to commit the migration" before review.

See the README for full input/output reference.

Marketplace

To submit this release to the GitHub Marketplace, edit it via the UI and check "Publish this Action to the GitHub Marketplace."

License

Apache 2.0 — matches the MetaObjects framework.