mesh-sdk's node-engine names are the seat's generated contract, kept deprecated for their importers, with their checks

The seat is defined whole in mesh-contracts (ADR 0613 §3), so mesh-sdk takes its names from there (ADR 0613 §5):
EngineSeat and EngineEvents are nodeengine's, EngineComposeCandidateVerb is nodeengine.VerbComposeCandidate, and
ComposeCandidateAsk, ComposeCandidateAnswer and ModuleComposed are aliases of nodeengine's ComposeCandidateInput,
ComposeCandidateAnswer and Module. The encode and decode checks stay here over those types until the seat has a client
package (ADR 0625 §4). For importers: a module's fingerprint is Fp, and the answer's Input is a JSON object
(map[string]any), not raw bytes. compose-candidate's input is the boolean the engine and the checker read; the seat
set's test takes that correction, and the whole seat's added verbs as da653ce reads them. EngineSeat leaves
testdata/seat-names.txt.

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

go/testdata/seat-names.txt

@@ -7,7 +7,6 @@ catalogue/checker_seat.go: CheckerSeat
 catalogue/control_records_seats.go: HandActsSeat
 catalogue/control_records_seats.go: WantsSeat
 catalogue/delivery_seat.go: DeliverySeat
-catalogue/engine_seat.go: EngineSeat
 catalogue/enrolment_seat.go: EnrolmentSeat
 catalogue/environment_into.go: EnvironmentSeat
 catalogue/environment_into.go: LoginShellSeat