apply-schema-override

name	apply-schema-override
description	Apply a schema override YAML snapshot from a GitHub issue into the correct overrides file, validate with bun run check, and open a PR that closes the issue.

Apply schema override

Use when a GitHub issue was opened from the Tagging Schema Browser with a title starting [missing-inheritance] or [risky-typecombo].

GitHub Actions launches a Cursor cloud agent via the Cloud Agents API when the issue is opened (see .github/workflows/cursor-override-automation.yml). The issue body is included in the agent prompt.

1. Parse the issue

Read the issue body and extract:

• Preset id from Preset: \…``
• Kind from the issue title prefix:
  • [missing-inheritance] → src/data/missing-inheritance-overrides.yaml
  • [risky-typecombo] → src/data/risky-typecombo-overrides.yaml
• YAML snapshot from the fenced ```yaml block under Snapshot (the presets: entry for the preset)

For stale updates, the issue may also include an Existing override (stale) block — the snapshot replaces that stored entry.

2. Commit 1 — apply the issue snapshot

Make one commit for the issue’s primary change:

• Open the target file under src/data/.
• Ensure top-level version: 1 and presets: exist.
• Insert or replace the issue’s preset entry with the snapshot (two-space indent under presets:).
• Keep preset keys sorted alphabetically when practical.
• Do not change unrelated preset entries in this commit.
• fields and moreFields are separate override sections (both are audited). Apply only the lists present in the issue snapshot — do not add the other list unless the snapshot includes it. A partial snapshot is valid; the preset stays unreviewed until every detected list is documented.

Commit message example: Overrides: mark {presetId} missing inheritance as intentional

If the issue is only about removing a stale entry (override exists but live detection is gone), this commit may delete that preset key instead of adding a snapshot.

3. Commit 2 — clean other stale overrides (if any)

Run bun run validate-inheritance-overrides (or bun run check). If validation reports other stale preset ids in the same file, fix them in a second commit:

• Remove override entries that are stale because live detection no longer applies.
• Update entries that are stale because the snapshot drifted only when they are not the issue’s target preset (the issue preset was handled in commit 1).

Do not mix unrelated stale cleanup into commit 1. Aim for one or two commits per PR:

1. Apply / update / remove the issue’s preset.
2. (Optional) Remove or fix any remaining stale entries so validation passes.

Commit message example: Overrides: remove stale entries for {presetA}, {presetB}

4. Validate

bun run check

This runs validate-inheritance-overrides and validate-risky-typecombo-overrides against the published release schema. All stale entries must be resolved before opening the PR.

5. Open a pull request

• Title: [skip netlify] Overrides: mark {presetId} missing inheritance as intentional (adjust wording for typeCombo or stale removal when applicable)
• Body: Start with Written by :robot: <model-name>: then Closes #<issue-number> on the next line, then a short user-facing summary of what was recorded and why (intentional omission or stale cleanup).
• Label: schema-override (required for auto-merge)
• Ready for review: open the PR not as a draft (gh pr create without --draft). If GitHub still opens a draft, run gh pr ready before finishing.
• Only touch the relevant src/data/*-overrides.yaml file.
• Keep the branch to 1–2 commits (issue change, then optional stale cleanup).

6. Auto-merge

CI must pass. Only one schema-override PR is open at a time so parallel agents do not conflict on the same YAML file. When an override PR merges, Cursor override automation launches the next queued issue. The schema-override-auto-merge workflow updates the branch from main, then rebase-merges eligible PRs once checks pass (YAML-only override change; typically 1–2 commits). Netlify deploy previews are skipped for YAML-only override PRs (see scripts/netlify-deploy-preview-ignore.sh).

Attribution

Prefix agent comments and PR descriptions with **[Cursor Agent]** when interacting on GitHub (in addition to the Written by :robot: line in PR bodies per AGENTS.md).