fix(kernel): Opentrons evidence uses the closed vocabulary and reports the robot's outcome

[LamaSu]

What

The TypeScript Opentrons adapter (packages/kernel/src/opentrons/adapter.ts) now emits evidence only from the closed vocabulary (EVIDENCE_EVENT_TYPES), and it reports the robot's own outcome.

When	Before	Now
Protocol upload	protocol_uploaded	method_loaded {opentronsProtocolId, name, protocolHash}. The hash is sha256 of the protocol source, i.e. what the robot was told to run
First play of a run	run_action	execution_started {opentronsRunId}
Pause, resume	run_action	execution_progress {opentronsRunId, action}
Stop	run_action	execution_failed {opentronsRunId, reason}
The robot reports the run succeeded	(nothing in real mode)	execution_completed {status, commandsSucceeded, commandsTotal}
The robot reports failed or stopped	(nothing; the runner waited 120 s for its timeout)	execution_failed {status, errors}; the runner sees idle and fails at once
Mock mode	run_started / run_progress / run_completed	execution_*, still marked mock: true and source.simulated

Why

In real mode, no Opentrons bundle could prove a run finished: it held protocol_uploaded and run_action and nothing else. adk limited the opentrons manifest to tier 0 until this mapping lands (#418, bus #3309), and evidence took the mapping.

Details

• Reserved-field rule (#3219). Robot-local ids are opentronsRunId and opentronsProtocolId. payload.jobId and the unit fields are reserved for the PCC binding, which the kernel's EvidenceEmitter stamps on every event (feat(evidence): LO-EV-9 bind device evidence to the accepted job and kernel before settlement #341). The tests assert that no reserved key appears in any payload.
• The robot's outcome is read when the runner polls getProgress(). A terminal status releases the run. Before this change, a finished run stayed current, so the next job's start replayed it.
• emitEvidence now takes an EvidenceEventType, not string cast to any, so the compiler enforces the vocabulary.

Tests (DGX Spark)

• kernel 867/867 on master, including 4 new tests in opentrons-evidence-vocabulary.test.ts, run against a fake Opentrons HTTP API. adapter-honesty.test.ts is updated to the new types. tsc is clean.
• Test-merged into feat(evidence): LO-EV-9 bind device evidence to the accepted job and kernel before settlement #341 (feat/evidence-subject-binding @799cea1d): kernel 873/873.
• Mutation check. Each of these mutants is killed:
  • the outcome is not read;
  • the run is not released on success, or on failure;
  • the first play is reported as progress;
  • a stop is reported as a completion;
  • runId is used in place of opentronsRunId.

Draft. Merging is the operator's call.

🤖 Generated with Claude Code

https://claude.ai/code/session_0117ows6894R3n6YQXBCRahS