TURN RECORD: EXPORT-SIDE STATE AFTER THE IMPORT MILESTONE.

CONFIRMED AGAIN (client-driven, no pokes):
  InitSession -> CreatePhoto(w6=1) -> SetTransport(mode=3, org=1)
    -> PutTile  => element+0x28 buffer holds 0xFF (white) / 0x00 (black)
  Export(21)  => err2 (BadValue); renderer runs with src_base = 00915FD0
                 (non-zero, verified at RP 0x1B296)
  framebuffer  => white and black captures byte-identical (AE = 0)

WHERE THE err2 COMES FROM -- narrowed this turn
  slot21 between the extent check and the render call:
    0x62F7E  CALLA 0x7EA3432          ; drawable resource init/lookup
    0x62F88  A5 = A8 ; JREQ 0x62FBC   ; zero => continue, non-zero => return A5
  and the callee (file 0x63432) returns:
    0x634B0  MOVK 0x9  (BadDrawable)  if *A11(0x160) == 0
  So a failed drawable init would give err9, NOT err2.  The err2 must therefore
  come from a later path (0x62FDC CALLA 0x7EA47B6, or the render driver itself
  returning 2 after 0x1B296).
  Also checked: the target window's geometry is depth=1, 80x64 -- it MATCHES the
  1-bit image, so depth mismatch is ruled out.
  Creating the GC explicitly with function=GXcopy and plane-mask=1 changes
  nothing (still err2, still no paint, AE=0).

STATUS.  NO client-chosen image displayed.  The window never changes.

WHAT IS SOLID
  * The XIE import path is fully client-driven and verified inside the server
    (element+0x28 -> 0xFF for white, 0x00 for black).
  * src_base at rp+0x610 is non-zero (00915FD0 / 002909B0) with org=1.
  * The export request passes every check the handler performs.
  * The window is depth 1 and provably drawable (core-X PutImage control).

WHAT IS STILL UNKNOWN
  The single remaining failure is inside the export/render completion path: the
  renderer has a correct, populated source and still the client receives
  BadValue, and the composited result never reaches the window.
