ADR 0627 §1: node-engine's client holds the checks of compose-candidate's ask and answer

The checks the node-engine, the checker and the assigner share over the verb (ADR 0593 §7, §9) leave mesh-sdk's delivery
package, where they sat over aliases of the seat's types, for go/clients/nodeengineclient, a Go module and package
artifact of its own over the seat's generated contract: the verdicts, the module states, the asker's bound, the no-answer
words, Encode/DecodeAsk, Encode/DecodeAnswer and CheckAnswer. Its test holds the cases mesh-sdk's held, and that an
open input's number keeps its digits; each fails without the code. seatgen -check finds nothing out of step.

Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig

README.md

@@ -21,8 +21,8 @@ implements its contract, and no holder's code lives here.
   counts the npm package a lock resolves, so here too a module is rebuilt only for the seats it uses.
 - **A seat's client**, written by hand: `go/clients/<seat without hyphens>client`, a Go module of its own, only where
   two or more callers share logic over the seat (ADR 0625 §4, ADR 0627 §1): operator-channel's (checking an ask,
-  its digest, a warrant's, and an asking module's keeping of its asks) and the four registry seats' (publishing a file
-  in parts). A client imports its own seat's contract and mesh-sdk's runtime, never another seat's client, and names
+  its digest, a warrant's, and an asking module's keeping of its asks), node-engine's (checking compose-candidate's ask
+  and answer) and the four registry seats' (publishing a file in parts). A client imports its own seat's contract and mesh-sdk's runtime, never another seat's client, and names
   no module's subject or tool.
 - **Not here**: the value layouts of seats not yet defined whole (they stay in mesh-sdk until their domain moves,
   ADR 0625 §9), and a role only one module could ever play (that module's own tools and events, ADR 0625 §8).