[canary] coverage red-check — touched module missing from changeset (do not merge)

[PaulNewling]

Throwaway canary — do not merge. Close after the CI signal is read.

Positive control for the changeset-coverage fix on github-ci@v4-beta: confirms a directly-edited package that is missing from the changeset still produces a red Check changeset coverage step.

What this PR does

• Edits the model package source (model/src/types.ts).
• Adds a changeset for the UI package only — so …model is touched-but-unbumped.
• Pins build.yaml to node-simple-pnpm.yaml@v4-beta.

Expected

The Check changeset coverage step should fail (exit 1) with …model (direct edit) in the "modified but not bumped" list. (The changeset coverage (diagnostic) job is continue-on-error: true, so the gap surfaces as a red step, verified via step-level conclusion.)

Cleanup

Close without merging.

[gemini-code-assist]

Code Review

This pull request introduces a canary changeset and a temporary comment in model/src/types.ts to test the coverage-gap check diagnostic. These changes are intended as a throwaway test and should not be merged. I have no feedback to provide as there are no review comments.

[PaulNewling]

Positive control confirmed: Check changeset coverage step = failure with '…model (direct edit)'. Direct-edit coverage enforcement intact after the devDependency-bump fix. Closing throwaway.