CI: a pull request that edits only the MCP server's SKILL.md renderer skips the Console test that pins its download mirror #31017

domain:ui#2 · os-tesla · session_01L9qibw7DekEe3wx5f3zphf

Filing gate: ① a named location. This is an out-of-scope finding from PR #31015 (card #30865), raised by the card thread (os-dev-report 6691357143, carrier: seat). ⛔ Not a claim. Triage sets the grade and the lane.
class: b · reach: every future edit to packages/mcp/src/skill-md.ts that lands without the Console mirror; NOT MEASURED in CI (read from .github/workflows/ci.yml on the PR branch 828224c8).

Business reason

#30865 happened because the Console's "Download skill" SKILL.md drifted from the one the MCP server serves. After #30861 the download taught a delete_record call the server refuses, so an agent following it failed every delete. PR #31015 makes the mirror byte-identical and adds a drift pin: ui/apps/console/src/pages/developer/objectstack-skill.test.ts compares the download with renderSkillMarkdown from packages/mcp/src/skill-md.ts. That pin only runs when Test UI runs. A pull request that edits only skill-md.ts matches neither the ui nor the ui_consumers filter, so Test UI skips. The ui filter is ui/** plus root build files; ui_consumers is spec, client, core, formula, lint, sdui-parser and types, and not packages/mcp. Per the filter's own comments, the queue reads the same diff, so its entry skips too. The drift lands, and the same broken download can ship again until some later run of the full ui suite reds on main.

Where

• .github/workflows/ci.yml, job filter: the ui / ui_consumers path lists, around lines 547–598 on 828224c8.
• The pin: ui/apps/console/src/pages/developer/objectstack-skill.test.ts (describe('renderObjectStackSkill mirrors renderSkillMarkdown')). It lands with PR fix(console): the skill download teaches delete_record confirm: true and mirrors the served SKILL.md #31015.

Wanted

A change to packages/mcp/src/skill-md.ts runs the Console test that pins its mirror, on the PR and in the queue. One possible fix is a ui-filter row for that one file, with a comment naming the pin. Another is an equivalent pin on the packages/mcp side that Test Core runs. Whichever is chosen, check:ci-filter-parity and check:cross-package-test-inputs must stay green.