Module adapters 

The harness adapter layer.

harness defines the HarnessAdapter trait — the single API generic dispatch code uses to reach harness-specific behavior. Each harness’s declarative half lives in its embedded descriptor file (harnesses/<label>.toml, loaded by descriptor and served through the generic descriptor_adapter); the code-backed features a descriptor references by name live in capabilities, backed by the per-harness module trees (claude_code, codex, opencode): transcript parsers, plugin-shadow detection, slug sanitization. The write guard is pure descriptor data rendered by the generic engine in [guard]. The registry loads the descriptors into label-keyed entries and owns harness-identifier resolution; generic code resolves an adapter with adapter_for and calls the trait.

Re-exports

pub use harness::CliDispatchContext;

pub use harness::CliJudgeContext;

pub use harness::CliManifestContext;

pub use harness::HarnessAdapter;

pub use harness::RUNBOOK_TEMPLATE;

pub use harness::ToolVocabulary;

pub use registry::DEFAULT_HARNESS_NAME;

pub use registry::UnknownHarnessError;

pub use registry::adapter_for;

pub use registry::all_config_dir_names;

pub use registry::all_tool_vocabulary;

pub use skill_shadow::PluginShadowReport;

pub use skill_shadow::ShadowSource;

pub use skill_shadow::format_shadow_banner;

pub use skill_shadow::shadow_validity_warnings;

pub use transcript::TranscriptSummary;

Modules

capabilities

Named code capabilities a harness descriptor references.

claude_code

Claude Code harness support — the default harness.

codex

Codex harness support.

descriptor

Harness descriptor files: the data half of a harness adapter.

descriptor_adapter

The generic descriptor-backed HarnessAdapter: one implementation serving every harness, reading declarative values from a validated HarnessDescriptor and dispatching code-backed features through the named capabilities in super::capabilities.

extract

Declarative transcript extraction for flat event streams.

harness

The harness adapter API — the single seam between generic dispatch code and harness-specific behavior.

opencode

OpenCode harness support.

registry

The harness descriptor registry — the resolution authority for harness identifiers.

skill_shadow

Harness-neutral skill-shadow report types and formatters.

transcript

Harness-neutral transcript types.