Skip .copier-answers.yml in the scaffolded typos hook

[MattFisher]

Overview

Fixes the red Render and validate both variants job on main (run 31150433393):

error: `ba` should be `by`, `be`
  ╭▸ .copier-answers.yml:3:10
  │
3 │ _commit: ba338ef

Why it happens

Template CI renders each variant with --vcs-ref=HEAD and runs the rendered scaffold's own pre-commit stack. _commit is whatever git describe returns for that ref — a plain tag only when HEAD is exactly a release commit, otherwise a describe string carrying raw hex, or a bare short SHA.

A short hex run is a coin flip away from spelling something typos treats as a misspelled word. ba338ef tokenises to ba, which typos wants to correct to by/be. Nothing in the file is prose, so checking it can only ever produce false positives — and which commits trigger one is pure chance, so this recurs unpredictably.

Consumers are exposed too, though less often: their _commit is normally a tag, but any project updated with --vcs-ref pointing at a branch or SHA carries the same landmine.

What changed

• template/.pre-commit-config.yaml.jinja: exclude: ^\.copier-answers\.yml$ on the typos hook.
• CHANGELOG.md: entry under [Unreleased] → Fixed.

Verification

• Rendered both app and library variants at HEAD and ran each scaffold's complete pre-commit stack — all 14 hooks pass in both.
• Decisive test, since the current describe string happens not to contain a trigger: on a rendered app with _commit forced back to the exact value that broke CI, typos passes with the exclude and fails without it (removed the line and re-ran as a control).

Notes

• The comment on the new line deliberately doesn't quote a real example. My first draft did, and it failed the same hook — .pre-commit-config.yaml itself isn't excluded, so a SHA quoted there gets spell-checked. Worth preserving that constraint if anyone edits the comment.
• Rendering at ba338ef today produces _commit: v1.8.1, because the annotated tag now sits on that commit. The original failure was transient in that sense — but it recurs for any merge to main that lands before the next release is tagged, which is most of them.
• Separately confirmed the downgrade fix is working in production: copier update --defaults --trust --vcs-ref v1 against the real remote, in a consumer checkout at _commit: v1.7.0, now reports Updating to template version 1.8.1. git describe --tags at main's tip answers v1.8.1, so the annotate step did its job on the 1.8.1 release.

---

Generated by Claude Code