ANSWERING THE ASSIGNED QUESTION: the class-3 object is NOT reachable through any
client id, because nothing ever registers an id on it.

1) Registration audit (breakpoints on file 0x67B04 ID-store and 0x67B34 table
   register), one connection:

     create op=2 (image)    id=0040C000 -> REGIDSTORE obj=003FDA10   (class 2)
     create op=1 (photoflo) id=0040D000 -> REGIDSTORE obj=00385890   (class 1)

     arm1 / put / arm2 / slot43 / export / arm1(photoflo) / put(photoflo)
       -> 0 registration hits each

   Registration happens ONLY inside create, and only these two objects are ever
   given an id.  The class-3 object produced by the allocator (file 0x6CA82,
   class = 3 when the flag is 0) never appears in a REGIDSTORE.

2) Walking the photoflo's +0x160 chain the way export does
   (0x1B230 MOVE *A5(0x160),A5), from the registered photoflo 0x00385890:

     lvl0 obj 00385890  id@0=0040D000  class=1    w=3692048  h=9948    p44=00386010
     lvl1 obj 00386010  id@0=003859D0  class=80   w=0 h=0x55555555      p44=00386290
     lvl2 obj 00386290  id@0=00386150  class=144  w=0 h=0x55555555      p44=003C7150
     lvl3 obj 003C7150  id@0=003863D0  class=144  w=0 h=1               p44=00000000
          +0x160 -> 00000000 (chain ends)

   Only lvl0 has a resource-like layout.  From lvl1 onward the first word is a
   POINTER (0x003859D0, 0x00386150, 0x003863D0) and the "class" byte is 0x50 /
   0x90, so these are not resource structs and carry no client id.  The chain
   therefore does not lead to an addressable class-3 resource; it leads to
   internal blocks.

   (Honest caveat: the garbage-looking w/h and rotated-looking pointers at
   lvl1+ mean I cannot claim what those blocks ARE -- only that they are not
   resource structs and have no id field holding a client id.)

3) Reachability probes with the two ids we do have:

     query image    0040C000 -> REPLY     (addressable)
     query photoflo 0040D000 -> BadAccess (registered but not a resource)

   and from the earlier runs: PUT_TILE with the photoflo armed gives
   BadAccess(10); with the image armed gives BadMatch(8); with an unregistered
   id gives BadIDChoice(14).

CONCLUSION: there is no client-visible id whose registered object is class 3.
The import's typed lookup wants class 3; the two ids the client can obtain are
registered to class 2 (resource) and class 1 (photoflo).  Whatever EXPORT needs
for src_base lives behind an id-less internal object, so it cannot be driven
from the client request surface using any id obtainable through slot 8.
