Release v2.4.1

What does this MR do and why?

Cuts v2.4.1. VERSION moves to v2.4.1 and the changelog section is retitled; just sync carries the new version into every .reference.yaml pin and every design bundle URL the templates publish. standards/design/check.sh's illustrative pin is hand-edited, because the sync script's glob covers markup and config but not shell.

The release carries one fix: just check honours the exemptions: a project declares in .reference.yaml, already merged. It is a patch because no assertion, tier or schema field changes.

Merge without squash, so the release commit survives as the merge's second parent and the tag goes on the merge commit.

References

• The fix: !136 (merged)

Standards affected

standards/design/check.sh changes one comment, the illustrative version pin. No assertion changes. standards/design/SKILL.md's pinned bundle URL moves to v2.4.1 with the rest.

Exemption implications

None added or modified. A consumer's declared exemptions are honoured once its reference_version: reaches v2.4.1.

Test plan

• just ship: all gates green at reference v2.4.1 / catalog 6, including validate-versions (v2.4.1 consistent across all pinned files), validate-release-notes and validate-exemptions; self-conformance 21 standard(s) passed, 0 exempt, 0 failed
• scripts/release-notes.sh v2.4.1 extracts the section as the tag body, headed reference v2.4.1
• Templates not lifted into a consumer: the bumped URLs name design/v2.4.1/, which publishes on the first main pipeline after the tag. Same ordering as every prior release.