mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-08 00:02:20 +03:00
9f7d0ffd93
`check:agent-skills-sync` fails on the tip of release/v3.8.50: the generator
reports `Generated: 3 · Unchanged: 42`, exit 2. Three agent-skill documents are
behind the route catalog they are generated from.
Measured, not assumed — the same generator on three refs:
release/v3.8.50 @ ed2db6cb19 (pre sync-back) Generated: 0 ✅
main Generated: 3 ❌
release/v3.8.50 @ d61798fb31 (post sync-back) Generated: 3 ❌
So the drift came from main — the v3.8.49 release itself — and the sync-back
faithfully propagated it. Nothing was deleted: all three files exist in all
three refs, and the regeneration is purely additive (139 insertions, zero
deletions) covering routes that landed during the cycle:
omni-auth GET /api/auth/oidc/login, GET /api/auth/oidc/callback
omni-inference +81 lines
omni-usage-logs +27 lines
Why CI never caught it at the source: the gate lives in the PR-only
"Merge integrity" job (its changelog half needs a base to diff against), and
this cycle's merge trains landed in batches with `--admin`, which bypasses
required checks. A gate that only runs on PRs and can be bypassed at merge
lets the violation reach main, where it becomes a base-red blocking every PR
into the next cycle's branch.
Generated with `node scripts/skills/generate-agent-skills.mjs --apply` — the
files are outputs, not hand-edited. `check:agent-skills-sync` now exits 0
(`Generated: 0 · Unchanged: 45`) and the 19 tests in
tests/integration/agent-skills-content.test.ts pass.
Co-authored-by: diegosouzapw <diegosouzapw@users.noreply.github.com>