# לוגואים של יצרנים

> תיעוד מקור. מקור: docs/data-system/manufacturer-logos.md · 6a466bf.
> בגרסה הציבורית הושמטו מזהים תפעוליים ופרטי חשבון אישיים. קובץ המקור נשמר במאגר.

The shared `ManufacturerLogo` component identifies the vehicle manufacturer beside the model illustration. It is used in registration lookup results, saved driver vehicles, the dashboard vehicle summary, fleet vehicle rows, and the vehicle illustration gallery. Vehicle registration remains the only vehicle entry flow.

## Identity

`lib/reference/manufacturer-logos.json` contains canonical brands, reviewed Hebrew/English aliases, exact Ministry of Transport country-qualified names, local assets, intrinsic dimensions, and the appropriate light/dark backing. `manufacturer-logos.ts` resolves those aliases using Unicode normalization, case folding and whitespace normalization. It does not infer brands from arbitrary substrings or accept external image URLs.

Some catalog entries are registered under a parent manufacturer. Reviewed **exact model** overrides resolve MINI under BMW, Genesis under Hyundai, Hongqi under FAW, AION under GAC, and selected Rover/General Motors models. Older Hyundai Genesis/Genesis Coupe and Rover passenger cars retain their own manufacturer marks. Do not turn these mappings into fuzzy model matching.

Unknown identities or failed assets render an accessible neutral car icon with an unavailable-logo label. No guessed, AI-generated, or first-letter brand marks are substituted.

## Assets and provenance

Assets are stored in `public/manufacturer-logos/`. Names include the first 12 characters of the original bytes' SHA-256. Files are served from the application origin with immutable caching. They do not depend on third-party requests at runtime.

`lib/reference/manufacturer-logo-sources.json` records source pages, source URLs, full SHA-256 and byte length. Sources include the [VehicleSpecs logo collection](https://github.com/vehiclespecs/brand-logos/tree/3f0929e70e0a9a2a502063edc4b3e5c0146cba74), [car-logos-dataset](https://github.com/filippofilip95/car-logos-dataset), Simple Icons, and manufacturer/importer websites. The bytes are preserved, with no recoloring, stretching or tracing. Light logos use a dark backing; all other logos keep a white backing in both application themes. Some original marks represent historical brand versions. Trademarks remain the property of their owners and are used for vehicle identification; their presence does not indicate partnership or endorsement. Repository licenses do not transfer trademark rights.

## Coverage and unresolved records

`lib/reference/manufacturer-logo-coverage.json` records coverage against the 2026-11-08 catalog snapshot, including its SHA-256 and unresolved source names. The initial collection contains 120 brand assets, covers all 43 brands in the illustration library, 130 of 140 source manufacturer labels, and 102,319 of 102,365 catalog rows. These are catalog records, not a count of registered vehicles.

The remaining labels are `צ'אנג יאנג`, `טי אי סי`, `מובימטיק`, `בורג`, `סנטרו`, `לינקסיס`, `מודרן`, `גמס`, `ג'יוואן`, and `נטע`. Some are coachbuilders or ambiguous source identities; others still need an accessible, verified original logo. They intentionally use the neutral fallback. Do not mark coverage complete until those records are verified.

## Maintenance and verification

1. Verify the manufacturer identity and original logo source. Download the original SVG/PNG/WebP, inspect the mark, and reject active SVG content or external references.
2. Add the content-hashed file, dimensions and backing to the manifest; record provenance and SHA-256. Review aliases for collisions. For group overrides, add exact verified catalog models only.
3. Remove any superseded asset, update coverage, and run `pnpm test`, `pnpm typecheck`, `pnpm lint`, and the registration/manufacturer browser suites.
4. Run `node scripts/audit-manufacturer-coverage.mjs /path/to/catalog.json` against the current public catalog snapshot. The audit reads only the reference catalog and makes no customer or production data changes.
5. Inspect desktop/mobile and light/dark mode. After deployment, check that every original asset decodes from the production origin.

Tests check alias collisions, parent-brand boundaries, unknown identity handling, complete gallery brand coverage, original byte hashes, passive SVGs, browser image decoding, failed-file fallback, registration lookup/save, and fleet display.

## Production acceptance · 2026-11-08

- Runtime commit: `65b71dc21847f88fad04af950a0a9a61ed8fd634`.
- Vercel deployment: `[operational-id-redacted]`, READY, with `product.linknodesenergy.com` assigned and no alias error.
- 161 unit tests, ESLint, TypeScript and the production build passed. Eight local browser scenarios passed, including the fleet editor and parent-manufacturer mapping. Desktop and mobile light/dark screenshots were visually reviewed.
- Six production browser scenarios passed: all original assets decode, themes and failed-file fallback, registration lookup/save, stale lookup response handling, lookup errors, and narrow-screen layout. Two authenticated fleet scenarios were checked locally and intentionally skipped in the live smoke suite.
- Independent HTTPS requests with certificate verification confirmed that all 120 deployed originals match their reviewed SHA-256 and use immutable caching.
- Registration numbers/accounts in browser tests were synthetic fixtures; lookup and save requests were intercepted. No production customer records were changed during acceptance.
- Live product: <https://product.linknodesenergy.com/vehicle>. Gallery: <https://product.linknodesenergy.com/vehicles/gallery>.
