# vendormark's path rule refuses a tracked filename that carries a site-generator
# vendor's name, on the reasoning that there is no honest reason to have one. This
# repo is the exception that rule documents: a brand-mark catalog, forked from
# lobe-icons, whose whole job is to draw and name other people's logos. It ships
# 323 of them — Anthropic, OpenAI, Cursor, Replit, V0, Vercel, Windsurf — each a
# directory named after its vendor with static assets named to match. Lovable is
# one row in that table. It cannot be drawn without being spelled, any more than
# the history-scrubber rules can strip a string they are not allowed to write.
#
# What the gate hunts is a site the generator BUILT, and that mark is absent here:
# no vendor-named upload folder, no tagger plugin in the dependencies, no injected
# third-party script, no generator meta tag, no bot in the commit identities. Only
# the path rule fires, and only on the catalog entry. So the exemption is that
# entry and nothing else — the icon's own two folders, and the shared asset
# directories narrowed by extension. A vendor-named upload folder added tomorrow
# matches none of these and still reds. The content and identity rules, which are
# what actually distinguish a generated site, stay armed everywhere.

src/Lovable/*
packages/react-native/src/icons/Lovable/*
packages/static-avatar/avatars/lovable.webp
packages/static-svg/icons/lovable*.svg
packages/static-png/dark/lovable*.png
packages/static-png/light/lovable*.png
packages/static-webp/dark/lovable*.webp
packages/static-webp/light/lovable*.webp
