Gazelle SA341 / SA342 corresponding source — GTLA, September 12, 2026

Upstream: Emmanuel BARANGER / helijah and credited FlightGear contributors.
https://svn.code.sf.net/p/flightgear/fgaddon/trunk/Aircraft/Sud-Aviation-SA342/
GPL v2. See COPYING and the original Read-Me.txt/source headers. GTLA geometry,
paint and animation modifications are also distributed under GPL v2. No warranty.

Includes the complete downloaded upstream source tree, mesh parser, conversion
and animation scripts, modified texture maps, build configs and FAA identity
inputs required by the reproducible-build checks. The minimal roster fixture
contains only the two public registration/hex pairs needed by those checks.
No reference photographs or proprietary font files are included.

Rebuild from this extracted root with Blender 5.2, Python 3 + numpy/Pillow,
Node 22, and npm install. Using the included final editable textures:
  blender --background --factory-startup --disable-autoexec --python outputs/Gazelle-family/build.py -- N888GZ
  node outputs/Gazelle-family/finalize.mjs N888GZ
Repeat both commands for N342MR and shared-sa341. Outputs appear in each
package's exports directory. Optional repaint scripts use macOS fonts; install
substitute fonts if desired. Repainting is not needed to rebuild included art.
Production stamping changes JSON provenance only, never geometry or animation.
The six production GLBs are served separately from /models/ and /models/mobile/.
Whole-file checksums of those published copies are in SHA256SUMS-published.txt.
MODEL-BIN-CHUNK-SHA256.txt lists the checksum of each file's BIN chunk (geometry,
textures and animation), which stamping never changes, for checking a rebuild.

FAA records: by GTLA owner decision on September 26, 2026, the owner's street,
city, county and ZIP lines were taken out of the three references/faa-*.txt
files in this archive and replaced with a one-line note. The registered
owner's name and every other line are unchanged. The full record is public at
the FAA registry URL at the top of each file. The build scripts check each
record against faaSha256 in its package's config.json; in this archive those
values are the checksums of the edited files, so the checks pass. The
published N888GZ and N342MR models still carry the checksum of the unedited
record in their JSON chunk, so a rebuild differs from them there as well.
