seed: rockit-m4 real recall measurements — Q4/Q8 v1.5, v2-moe (#2) #2

	name: Schema sync check

	# Push-to-main ONLY — deliberately NOT on pull_request. This check compares
	# schema/ against whatever @tpsdev-ai/flair-bench has most recently PUBLISHED
	# to npm, which has nothing to do with any given PR's diff; running it per-PR
	# would just be re-checking the same external state over and over. It runs
	# once per change that lands on main instead.
	on:
	push:
	branches:
	- main

	permissions:
	contents: read

	jobs:
	schema-sync:
	runs-on: ubuntu-latest
	steps:
	- name: Checkout
	uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

	- name: Set up Node
	uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
	with:
	node-version: "22"

	- name: Install dependencies
	run: npm ci

	# ZERO secrets: @tpsdev-ai/flair-bench is a public npm package
	# (publishConfig.access: public); the registry lookup and pack are
	# unauthenticated reads.
	#
	# As of 2026-07, @tpsdev-ai/flair-bench (tpsdev-ai/flair
	# packages/flair-bench) has MERGED to flair's main but no release has
	# been cut — the registry lookup 404s. scripts/check-schema-sync.mjs
	# treats that as a neutral skip (logs plainly, exits 0), NOT a
	# failure — this check arms itself automatically the moment the first
	# version publishes; nobody needs to remember to flip a switch.
	- name: Check schema/ against the published package
	run: node scripts/check-schema-sync.mjs

Provide feedback