WORLD1 BLOOM MAINTENANCE
- world1/composite.fsh is preserved unchanged (known-good working composite).
- world1/composite2.fsh is preserved as the working stage and only gets an isolated End bloom section.
- obsolete world1 composite1/deferred variants removed if present.
- no world0/world-1 composite files were changed.
- bloom is present only in world1/composite2.fsh, so it is End-only.

ADDENDUM — Aura Pillar / Volumetric fog (blue-white, 4-layer, ring-anchored):
- world1/lib/Volumetric_fog.glsl was rewritten. It used to hold an ambient
  purple/pink void fog (8 layers) that was never actually #included from
  anywhere (dead code). It now holds "Aura Pillar": a 4-layer, blue-white
  volumetric energy that spirals up from the foot of The End's obsidian
  pillars, fading to transparent higher up. Still 100% local to
  world1/lib/, still no noisetex/shadow-map dependency.
- It is #included from world1/composite2.fsh (not composite.fsh), since
  composite2.fsh is the only "normal" active composite stage in world1 and
  is already where the isolated End bloom section lives.
- world1/composite.fsh was NOT touched for this addition either — still
  preserved unchanged, per the rule above.
- No gbuffer/MRT changes were made (per WORLD1_MAINTENANCE.txt's warning
  about the custom MRT chain that previously broke the frame). Pillars are
  not detected per-block; the aura is anchored to an approximate 10-point
  world-space ring (AURA_RING_RADIUS/AURA_CENTER_X/AURA_CENTER_Z in
  Volumetric_fog.glsl) matching vanilla The End's pillar layout. Nudge
  those values if a specific world/build's pillars sit noticeably off that
  ring.
- endBloomSample()/endBloom() in composite2.fsh were widened (thin+wide
  dual-ring kernel + soft-knee compression) and now also sample the Aura
  Pillar function, so the aura's brightest strands bloom the same way any
  other bright End pixel does. KEKUATAN_BLOOM_END / JARAK_BLOOM_END /
  JARAK_BLOOM_END_WIDE / SUHU_BLOOM_END remain End-only and independent
  from Overworld's own bloom (which lives entirely under world0/, untouched).
- no world0/world-1 files were touched for this addendum either.
