HUNT FOR THE ELEMENT-LIST HANDLER: NO VARIABLE-LENGTH ELEMENT REQUEST EXISTS
IN THE IMPLEMENTED SURFACE.

A) STATIC: every handler's length gate was extracted and classified
     slot 0   EXACT(4)     slot 1  EXACT(2)   slot 3  EXACT(2)   slot 4  EXACT(2)
     slot 5   EXACT(5)     slot 7  EXACT(4)   slot 8  MIN(>=3)   slot 9  EXACT(3)
     slot 10  EXACT(3)     slot 11 EXACT(3)   slot 12 EXACT(2)   slot 13 EXACT(2)
     slot 14  EXACT(4)     slot 15 EXACT(3)   slot 18 MIN(>=4)   slot 19 MIN(>=8)
     slot 20  EXACT(35)    slot 21 EXACT(16)  slot 22 EXACT(2)   slot 24 EXACT(4)
     slot 33  EXACT(4)     slot 40 EXACT(4)   slot 43 EXACT(10)  slot 44 EXACT(5)
   Only slots 8, 18, 19 accept a variable length.  A photoflo-create request
   carrying "the supplied list of elements" (xieSIarch.txt 8.3.3.1 / 8.3.4.1)
   would have to be variable length or a very large fixed layout.

B) SLOT 20 IS THE ONLY LARGE FIXED REQUEST: length must be EXACTLY 35 words
     0x6AA6E MOVE *A9(0x10),A7,0x0   ; request length
     0x6AA72 CMPI 0x23,A7            ; 0x23 = 35
     0x6AA76 JREQ 0x6AA7E  else MOVK 0x10 (BadLength)
   It then does the generic resource lookup (0x7EAB966) on w0 with byte13 as a
   class argument, and loops over up to 3 band-array elements (*A5(0xd8)).

   Measured (photoflo + image both registered, 35-word payload, 32 data words):
     w0=FLO w2hi=0     -> err2 (BadValue)   renderer trace: (none)
     w0=FLO w2hi=1     -> err8 (BadMatch)   renderer trace: (none)
     w0=FLO w2hi=2     -> err8 (BadMatch)   renderer trace: (none)
     w0=FLO w2hi=3     -> err8 (BadMatch)   renderer trace: (none)
     w0=IMA w2hi=2     -> err8 (BadMatch)   renderer trace: (none)
   No TYPE1..TYPE5 store fired, the RP (0x1B296) breakpoint never fired, and the
   GATE never ran.  So slot 20 rejects before building anything.

C) THE TWO VARIABLE-LENGTH HANDLERS DO NOT FIT EITHER
   slot 8  MIN(>=3): parses 4 request words, has NO element loop, and an
           over-long payload simply fails to register (length sweep 11..27).
   slot 18 MIN(>=4): the only handler that touches *A7(0xd8) and writes
           element+0x20, but it returns BadAccess(10) with the resource id for
           BOTH a class-2 resource and a class-1 photoflo.

D) CONSEQUENCE
   Within the request surface this server implements and that I can drive, there
   is no request that accepts a list of elements with phototags, no request that
   writes the element record, and no request that makes the renderer produce a
   non-zero source (src_base = rp+0x610 has been 00000000 in every run).

STATUS.  No client-chosen XIE image.  The window has never differed from the
no-export baseline; solid-white and solid-black readbacks are identical; xshow
(core X) is the only viewer that has displayed an image.

WHAT IS STILL MISSING, precisely: the WIRE ENCODING of the photoflo element list
(phototag / element type / parameter field order and the DAG connection fields)
plus the minor opcode of the request that carries it.  xieSIarch.txt documents
the semantics (7.3 Photo Element Definition; 8.3.4.1 Create) but is a server
architecture document and does not specify the protocol encoding.
