Build Russian T-90 style main battle tank: low rounded cast turret covered in explosive reactive armour blocks, 125 mm gun, rubber side skirts, IR dazzlers, log on the back (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 reads as a turretless tank destroyer: the turret is a flat slab that barely rises above the hull. A T-90 turret is low but clearly a TURRET: a rounded cast dome sitting on the hull roof (about 0.8 m tall above the hull deck, 2.2 m across), with explosive reactive armour blocks forming a forward-pointing V (chevron) on its front, the 125 mm gun coming out of a narrow mantlet between them, two IR dazzler boxes beside the gun, smoke launchers on the sides, a commander's cupola with a machine gun and a stowage box on the rear. The hull: steeply sloped upper glacis covered with ERA, rubber side skirts with ERA, six road wheels per side, unditching log and fuel drums on the rear. Overlay your side render on the sheet's side view and match the turret silhouette. 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/t90-tank-v2/<script>.py
(first `ssh gex44 mkdir -p /root/fal-author/t90-tank-v2`, scp scripts and any textures to gex44:/root/fal-author/t90-tank-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: 9.53 m long with the gun forward (hull 6.86 m), 3.78 m wide, 2.23 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: 80k to 160k triangles, at most 8 materials, texture images at most 2048 px, GLB at most 12 MB.

Export contract (glTF binary .glb, Y up, metres): Gun forward toward +Z, up = +Y, +X = the tank's LEFT side, centred on X = 0; origin (0,0,0) on the ground plane at the centre of the hull footprint. Tracks touch y = 0. Turret straight ahead, gun level. 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: Hull (everything fixed to the hull), Turret (origin ON the turret ring's vertical axis, turns about Y), Gun (child of Turret: mantlet + barrel, origin on the trunnion axis, elevates about X), Track_L, Track_R (the track belts: their texture V coordinate runs ALONG the track so a game scrolls it to animate; links modelled where they shape the silhouette), every road wheel, sprocket and idler as its own node Wheel_L1..Wheel_Ln and Wheel_R1..Wheel_Rn (front to back, origin at its hub, spin about X), Hatch_Commander (origin on its hinge), MG (roof machine gun, child of Turret, origin at its pivot) where the type has one. Empty nodes (no mesh): Muzzle (barrel tip, child of Gun), Seat_Commander (head-out hatch point), Seat_Driver, Exhaust, Light_Head_L, Light_Head_R. Lamps: material "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.12, 0.14, 0.08] (Russian 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: olive drab, NATO green, desert tan, field grey, winter white, dark green-black, sand, forest green; 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: t90-tank.glb; build_t90-tank.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.