TURN RECORD: THE PHOTOMAP **IS** POPULATED (QueryResource), AND A CORE-X CONTROL
PROVES THE WINDOW IS DISPLAYABLE -- SO THE EXPORT REALLY IS NOT PAINTING.

A) QueryResource (minor 10) WORKS AND REPORTS THE IMAGE
   Request = {resource_type, resource_id} (12 bytes); photomap reply layout from
   XieProto.h (width@8, height@12, polarity@24, pixel_prog@25, line_prog@26,
   constrained@27, comp_mapping@28, component_count@29, levels[3]@32, photo_id@44).

     after create     -> w=64 h=64 polarity=0 pxprog=0 lnprog=0 constrained=1
                         comp_map=1 comp_COUNT=1 levels=(1, ...) photo_id=00406600
     after transport  -> same, levels=(1,0,0)
     after puttile    -> same, comp_COUNT=1

   So the photomap IS populated: 1 component, 64x64, constrained.  The tile data
   landed.  (levels[0] is always 1 and does not change for w4/w5/w6/w7/w8 or for
   w9 = 0x100/0x102/0x202/0x201/0x101, so it is not settable through those
   words; and w9=0x200+ breaks the transport.)

B) THAT REMOVES "UNPOPULATED PHOTOMAP" AS THE EXPLANATION FOR src_base == 0
   Full client path still reproduces:
     InitSession -> CreatePhoto(w6=1) -> SetTransport(mode=3) -> PutTile = ok
     Export(21, w=64 h=64) -> ok/silent, RP(0x1B296) fires, TYPE5 store fires,
                              src_base (rp+0x610) = 00000000
   Export with w=0,h=0 skips the renderer entirely.

C) CORE-X CONTROL: THE WINDOW IS VISIBLE, SO THE ABSENCE OF CHANGE IS REAL
   On the SAME 64x64 window:
     core-X PutImage (opcode 72, depth 1, 64x64 0xFF) -> a visible white block
     appears in the framebuffer (dwt/screenshot.py).
   So the window is mapped and drawable, and a successful paint IS observable.
   Exporting a black photomap onto that same window then produced err9
   (BadDrawable) x3 followed by err1, and the block did not change.

D) NEW STRUCT FACT THAT CORRECTS AN EARLIER ERROR
   xieBindPhotomapReq = { photoflo_id, photomap_id } -- I had been sending
   [photomap, photoflo], i.e. the operands reversed.

STATUS.  Still NO client-chosen XIE image.  src_base (rp+0x610) 00000000; the
window is unchanged by XIE; solid-white and solid-black captures differ only by
the Terminal Manager's own figures and the cursor; xshow (core X) remains the
only viewer that has displayed an image.

WHERE THIS LEAVES IT: the import half is complete and verified by QueryResource
(data is in the server), and the display half is the only gap.  The renderer is
entered (RP + TYPE5) but reports no source, and exporting onto a window that
demonstrably accepts core-X drawing gives BadDrawable/err1.  The next thing to
read is XieExport.3X's error table plus xieQueryExportReq/Reply, and to bind with
the corrected operand order before executing, since the immediate (unbound) path
is the one that yields src_base 0.
