Build Eurocopter Tiger style attack helicopter: slim fuselage, tandem cockpit, mast-mounted sight, stub wings with rocket pods and missiles, chin gun turret, fixed wheels (the one on sheet.jpg) as a production, REALISTIC 3D game asset in Blender, for Forge's asset library. Look at the reference
images in this directory with your image tool first: sheet.jpg, previous_final.png, previous_side.png. It must look like a real object from a modern
third-person game up close: never blocky, never toy-like, never flat colours.

The operator reviewed the previous version (previous.glb / previous renders here) and asked for this. Fix it first, keep what was good:
  "Art direction critique of v1 (previous_final.png, previous_side.png): it is an Apache clone (the sheet was too). Make it unmistakably a Eurocopter TIGER, ignore the sheet where it looks like an Apache: a SLIMMER, smoother, more rounded composite fuselage with few rivets; tandem cockpit with a long sloping two-step canopy; the two engines side by side on top of the fuselage behind the cockpit inside ONE smooth faired cowl (no separate pod nacelles on the sides); a mast-mounted sight ball on top of the 4-blade compact rotor hub; short straight stub wings with two pylons each; a tall swept vertical fin with a 3-blade tail rotor on the RIGHT side; a horizontal tailplane at the base of the fin with small vertical endplate fins at both tips (the Tiger's signature); fixed main wheels on short struts and a tailwheel; chin gun turret. It is smaller and lighter-looking than an Apache: 14.1 m fuselage, 13 m rotor. Keep the contract of the previous version (node names, pivots, Paint material factor, paints in nodes.json, game weight). Start from the previous build script and change what the critique names; deliver the same files."

Blender 5.2 is headless on another machine. Write bpy scripts here and run them with:
  ssh gex44 /root/blender-spike/blender-5.2.0-linux-x64/blender -b --python-exit-code 1 --python /root/fal-author/tiger-helicopter-v2/<script>.py
(first `ssh gex44 mkdir -p /root/fal-author/tiger-helicopter-v2`, scp scripts and any textures to gex44:/root/fal-author/tiger-helicopter-v2/, scp renders back here, then
LOOK at them with your image tool). Iterate until the renders match the references: silhouette, proportions, every
named part, materials. Only one Blender job on the GPU box at a time from you.

Quality bar:
- Real dimensions in metres: 14.1 m fuselage, main rotor 13.0 m diameter, 3.8 m high.
- Construction detail as geometry where it shapes the silhouette or catches light: bevelled edges everywhere (no razor
  box edges), real thickness, frames around openings, trims, rails, fittings, bolts, ropes, cables, small parts. No
  z-fighting, no gaps, nothing floating, smooth shading on round parts.
- Photographic materials: use CC0 Poly Haven textures (download 1k or 2k jpg maps from https://dl.polyhaven.org/file/
  ph-assets/Textures/jpg/<res>/<id>/<id>_<map>_<res>.jpg, maps diff, nor_gl, arm; pick ids by browsing
  https://api.polyhaven.com/assets?t=textures) mixed with node detail (rust streaks, grime, moss, edge wear, salt), then
  BAKE each material's result with Cycles to image textures (base colour, normal, ORM) so it survives glTF export.
  List every Poly Haven id you used in NOTES.md (licence evidence). No other image sources.
- Budget: 60k to 140k triangles, at most 8 materials, texture images at most 2048 px, GLB at most 12 MB.

Export contract (glTF binary .glb, Y up, metres): Nose toward +Z, up = +Y, +X = the aircraft's LEFT side, centred on X = 0; origin (0,0,0) on the ground plane directly below the main rotor mast (the front rotor mast for a tandem), wheels or skids resting on y = 0. Apply transforms and modifiers. No cameras, lights or
helpers in the GLB. GAME WEIGHT overrides the budget above: every texture image at most 1024 px, ORM / occlusion maps at most 512 px; share baked texture sets between parts and use tiling materials + trim textures on big surfaces (a 1024 bake cannot hold a 40 m fuselage). Separate named mesh nodes: Fuselage (everything fixed), MainRotor (hub + blades, origin ON the mast axis at the hub, spins about Y; for a tandem: Rotor_Front and Rotor_Rear, no tail rotor), TailRotor (origin at its hub, spins about its shaft; write the axis in nodes.json), Door_L, Door_R where doors open (origin on the hinge or slide line), Gun (chin or nose turret, origin at its pivot) where the type has one. Rotor blades are real twisted airfoils, not planks. Empty nodes: Seat_Pilot, Seat_Copilot (or Seat_Gunner), Troop_1..Troop_n (cabin seat hip points) for troop carriers, Hardpoint_L1, Hardpoint_R1... (pylon attach points), Light_Nav_L, Light_Nav_R, Light_Beacon, Exhaust_L, Exhaust_R. Cockpit glazing: material "Glass" (alpha BLEND) with a visible cockpit (seats, panels, sticks) behind it. Lamps: "Lamps". PAINT CONTRACT (how games get variants of one model): the main paint lives in ONE material named exactly "Paint". Its base colour TEXTURE holds only light neutral detail (near white, with grey grime, mud, dust, soot, rain streaks, panel lines, chipped edges baked in) and its baseColorFactor holds the paint colour; default factor = [0.20, 0.22, 0.20] (grey green). A game changes that factor, so nothing else (rubber, metal, tracks, glass, lamps, weapons, interior) may use Paint. Matte military paint: no clearcoat. In nodes.json add "paints": six real paints for this model as linear RGB triples with names, the default first, chosen from: air-superiority light grey, dark grey, navy blue-grey, desert sand, olive, black, two-tone grey; and render paints.png: a 3x2 grid of the same 3/4 view in those six paints (EEVEE or low-sample Cycles) to prove the recolour works. No national insignia, roundels, flags, unit badges, serial numbers or any text: games give these to their own factions. No manufacturer logos. Keep this directory clean: put any helper tools you install (node_modules, vendored three.js, browser checks) under /tmp, never here. Pace: deliver a first complete GLB within about 25 minutes, then use what is left of about 45 minutes to improve what the renders show is weakest. Use Cycles with the GPU (OptiX/CUDA) and modest samples for bakes and renders. 
Deliver in this directory: tiger-helicopter.glb; build_tiger-helicopter.py (ONE script that builds the whole asset from an empty scene,
downloads/loads its textures, bakes and exports: the GLB you deliver must come from a clean run of it); final.png
(1920x1080 Cycles render, 3/4 front view, soft daylight); side.png (orthographic side); clay.png (same view as final,
plain grey material); nodes.json (every node name with world position + overall bounding box); NOTES.md (6 lines:
what you made, triangle count, materials, texture sizes, Poly Haven ids, what still differs from the references).
Stop when you judge it matches the references and would not look out of place in a modern realistic game.