THE REPLY MODEL WAS WRONG.  This is the most consequential correction of the
session and it explains the ERR8/ERR10/ERR14 inconsistencies and several
retractions.

1) SUCCESSFUL create AND arm SEND NO PACKET AT ALL.
   Measured with a strict one-request-per-read probe on valid ids:
     create -> (no packet)     and the resource really is created
     arm    -> (no packet)     when it succeeds
     put    -> BadMatch packet when it fails
   Only ERRORS produce a packet.  So "no-reply" in earlier runs meant SUCCESS,
   not a lost reply, and my reader was silently consuming nothing.

2) HARDCODED IDS ARE INVALID.  The client id base differs per connection
   (0x004xxxxx, 0x005xxxxx, 0x006xxxxx were all observed).  Every request using
   a literal id such as 0x0047xxxx or 0x0048xxxx was rejected:
     create id=0x00470001 -> BadIDChoice
     create id=0x00470002 -> BadIDChoice
     create id=0x00470100 -> BadIDChoice
     create id=0x00480002 -> BadIDChoice   (also has bit 19 set)
   while c.new_id(...) works.  Consequences: many sequences in earlier turns
   created NOTHING and then "measured" arm/put against a non-existent resource;
   the ERR14 results and several contradictions come from this.

3) ERROR PACKET LAYOUT (from a raw hexdump, no parsing assumptions):
     type=0 | error_code | sequence | bad_value | minor | major=0x81
   e.g. 00 0e 03 00 | 02 10 47 00 | 08 00 81 00  -> code 14, minor 8 (create)
   So the error vocabulary in the tooling was correct; the ATTRIBUTION was not,
   because with several requests outstanding the first packet read may belong to
   an earlier request.

RE-VERIFIED WITH THE CORRECT MODEL (valid ids, one request per read):

  w9=0x100 (byte8=1):  create silent OK, arm silent OK, put = BadMatch
  w9=0x300 (byte8=3):  create silent OK, arm = BadMatch,    put = BadMatch

and on the arm path the shared lookup still SUCCEEDS in both cases:

  w9=0x100 : H_STORE -> K -> L(a7=FFFFFFFF) -> N(jrlt) -> P_6BBE2_SUCCESS
  w9=0x300 : H_STORE -> K -> L(a7=FFFFFFFF) -> N(jrlt) -> P_6BBE2_SUCCESS

So for arm the lookup returns 0 in both cases and the BadMatch with byte8=3 is
produced later, in slot 20's body.  Instrumenting slot 20's four MOVK 0x8 sites
(0x6ABD2, 0x6AC5C, 0x6AC96, 0x6ACD4) with valid ids: NONE of them fires.

NEXT: find the callee in slot 20's post-lookup body that returns 8 -- candidates
are the DD dispatcher 0x7E80008 and the per-element helpers -- now that valid ids
and the no-reply model are in place.  Every earlier measurement that used a
literal id must be considered void until re-run.
