THE XIE PROTOCOL SPECIFICATION WAS FOUND, WITH THE PHOTOFLO ELEMENT ENCODING.

Source (the same FTP mirror that yielded xieSIarch.txt):
  https://ftp5.gwdg.de/pub/xfree86/XFree86/4.2.0/doc/
    XIEProto.TXT   291988 bytes  "X Image Extension Protocol", Version 5.02,
                   X11R6.3, Dec 1996, (c) DEC/X Consortium/AGE Logic
                   photoflo=343  photomap=132
    xielib.TXT     297381 bytes  photoflo=267  photomap=110
    overview_xie.TXT  26659 bytes
  Saved to xie/docs/dec/ (XIEProto.TXT, xielib.TXT, overview_xie.TXT).
  NOTE: this is the document whose vocabulary matches the VT1200 (photoflo /
  photomap).  The X11R4 "contrib" specs already in xie/docs/x11r4/ have ZERO
  photoflo hits -- they are a different lineage.

WHAT IT DEFINES (verbatim structures)

1. PhotoElement subpacket (a subpacket INSIDE a photoflo request, not a request):
     2 bytes  CARD16  Element type
     2 bytes  CARD16  Element length (bytes divided by 4)
     multiple of 2  XieTyp(Phototag|Tile)  element's data source(s), if required
     N               parameters as required by element type
     < 4             pad to a multiple of 4
   "A photo element consists of four (4) bytes of header followed by zero (0) or
    more bytes of element input connection definitions and by ... additional data."

2. Element list / phototag rules (chapter 5):
   - the protocol representation of a Photoflo IS a list of elements, sent as ONE
     request; its total length must fit in maximum-request-length;
   - each element is identified by its POSITION in the list = Phototag; the first
     element is index ONE (1); phototag 0 is reserved;
   - "the order of elements in the list does not have to match the Photoflo
     topology ... the source for each element's input connections are explicitly
     specified using the Phototags of upstream elements";
   - three element kinds: Import (no inputs, 1 output), Process (>=1 input, 1
     output), Export (1 input, no output).  A useful Photoflo has >=1 import and
     >=1 export.

3. Request encodings (v5.02 minor numbers):
     CreatePhotoflo   minor 17  length 3+n/4
        photoflo(4) | CARD16 #elements | 2 unused | element-list
     ExecuteImmediate minor 16  length 4+n/4
        Executable(8) | CARD16 #elements | BOOL notify | 1 unused | element-list
     ExecutePhotoflo  minor 19  length 3
        photoflo(4) | BOOL notify | 3 unused
     ModifyPhotoflo   minor 20 ; RedefinePhotoflo minor 21 ;
     DestroyPhotoflo  minor 18
     PutClientData    minor 22  (client -> ImportClient element; phototag + band)
     GetClientData    minor 23
   And: "CreatePhotoflo ... no action is taken to validate them at that time.
   CreatePhotoflo will only STORE the Photoflo's definition; parameter validation
   is delayed until an execute request is received."

4. Photomap (7.2.3 / XieTypPhotomap): the resource that stores image data;
   ImportPhotomap brings it into a flo, ExportPhotomap re-populates it.

MEASURED AGAINST THE VT1200 THIS TURN

  slot 18 is the only handler whose length gate is a MINIMUM (>=4) and it reads
  w0 (0x20) plus request BYTE 13 (0x68) -- that is exactly the shape of
  CreatePhotoflo (photoflo id in w0; the element-type CARD16 of the first
  element straddles bytes 12-13).  But the v5.02 numbering does not hold:
     slot18 with a NEW id + 3 header-only elements
        [FLO, 3, 0x00010001, 0x00010002, 0x00010003]   (len = 6 words)
        -> err14 (BadIDChoice) bad = the new id, and NOTHING registers
  So on this server slot 18 operates on an EXISTING resource, i.e. it is a
  modify/execute-family request, not CreatePhotoflo.  (Earlier: an existing
  class-2 resource and an existing class-1 photoflo both gave BadAccess(10).)

  The shared lookup's BadAccess site was also read exactly:
     6BAB2 A7 = *A13(0xff20) ; JRLT 0x6BABC
     6BAB8 A7 = *A11         ; JRNE 0x6BAEA        ; value != 0 -> gate path
     6BABC A7 = *A13(0xff20) ; JRLT 0x6BBCE        ; < 0 -> skip
     6BAC6 MOVK 0xa -> BadAccess                   ; only when >=0 AND *A11 == 0
  i.e. BadAccess requires the caller-supplied signed local at frame 0xff20 to be
  >= 0 while the dereferenced caller pointer holds 0.

STATUS.  No client-chosen XIE image.  src_base (rp+0x610) 0 in every run, the
window never differs from the no-export baseline, and xshow (core X) is still the
only viewer that has displayed an image.  What changed: the element wire format is
now READ rather than guessed.
