Documentation
¶
Overview ¶
Package registry maps sandbox.HarnessType to a HarnessAdapter implementation.
adapters/ is the interface package and each adapters/<harness>/ package imports it for Usage / Result / RunContext / HarnessAdapter — so adapters/ itself cannot import the sub-packages without an import cycle. The registry lives one level out (it imports the sub-packages and the interface package) and is consumed by callers that need a harness → adapter mapping in one place: the dispatcher (for Bindings()) and the runner-inner-child (for Run()).
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func For ¶
func For(harness sandbox.HarnessType) adapters.HarnessAdapter
For returns the HarnessAdapter that owns the given HarnessType, or nil if the harness is unknown.
Phase 3-d made the three built-in harnesses (shell / claude / opencode) authoritative; the runner-inner-child rejects an empty / unknown HarnessType because the planner now resolves every job to one of these. The nil return path is kept for forward compatibility (a future harness the caller has not yet wired) but is no longer expected on any live path.
Types ¶
This section is empty.
Source Files