Small. Fast. Reliable.
Choose any three.
*** 8,14 ****
  
  So, we could encode nPrefix<16 and nSuffix<8 in a single byte.  If either is exceeded, we could fallback to no prefix and encode 128+nTerm (or, we could encode 0, then nPrefix and nSuffix).
  
! This is only of moderate value, because we'll only save a maximum of a byte per term.  But it's a free byte, and not too complicated at all to implement.
  
  ----
  
--- 8,14 ----
  
  So, we could encode nPrefix<16 and nSuffix<8 in a single byte.  If either is exceeded, we could fallback to no prefix and encode 128+nTerm (or, we could encode 0, then nPrefix and nSuffix).
  
! This is only of moderate value, because we'll only save a maximum of a byte per term.  But it's a free byte, and not too complicated at all to implement.  Additionally, awhile back I tested delta-encoding for interior nodes, and for most nodes it *increased* the space needed, because adjacent terms tended to have no shared prefix.  It did save about 2% for the 64kdoc segment's height-1 interior nodes.  This encoding might counter that.
  
  ----