Decisions

Why the Claude control probes are built the way they are.

Why use the official SDK for the control proof?

The TypeScript SDK supervises the same native executable as the structured CLI. Its public types expose tool callbacks, dialogs, elicitation, reinitialization and task controls. Consuming those types avoids maintaining a second implementation of the SDK's bidirectional protocol. The direct CLI comparator retains an independently executable create/resume check.

What it leaves open

This is a provisional choice for a bounded control proof. Complete native fidelity, durable owner requests and enforcement by the host are separate requirements. A successful SDK transport fixture does not establish the native runtime semantics of a feature it synthesizes.

Why retain local native records when a transcript mirror exists?

The SDK's mirror can fail while the native subprocess continues. The probe injects append failure and checks both visible degradation and the local transcript. A successful foreground result cannot stand in for a complete capture barrier.