.gitattributes

# Line endings are CONTENT here, because two of this repository's derivations
# are byte-for-byte copies and one is a compiler's input.
#
# packages/brand copies src/styles/colors_and_type.css and
# src/styles/fonts/fonts.css byte-for-byte and ASSERTS the identity, and
# `npm pack` runs that build — so without this, a tarball published from
# Windows and one published from CI are different bytes for the same version.
# And build-storybook.mjs compiles the .vue sources with esbuild, which is only
# reproducible if its inputs are.
#
# `eol=lf` — not `text=auto` alone — is what makes that hold. `text=auto`
# normalises what is COMMITTED and leaves the checkout platform-native, which is
# exactly the state that produces identical blobs with different bytes on disk.
#
# A third reason stood here until 2026-08-27 and was the sharpest of the three:
# docs/storybook/tw-bridge.css recorded a sha256 of the component roots, read
# from the WORKING TREE, so a CRLF clone and an LF clone of the same commit
# disagreed and the check could only pass on the machine that last generated
# it. That failed the Pages deploy 36 times in a row between 2026-08-20 and
# 2026-08-21 while passing locally every time. The digest is gone — those files
# are generated and gitignored now — but the two reasons above are not, so this
# file stays.

* text=auto eol=lf

# Binaries: never touched. `text=auto` already detects these, but the four
# formats in this repository are worth naming rather than trusting a heuristic
# with 116 PNGs and 33 font files.
*.png  binary
*.ico  binary
*.woff binary
*.woff2 binary