pub struct HarnessConfig {
pub source_dir: Option<PathBuf>,
}Expand description
What mecha harness ruminate’s diagnostician is allowed to read.
Global-file only, for [slack]’s reason in its sharpest form. The
diagnostician reads whatever this names and treats it as the authority on
why each mechanism exists — “if the thing you were about to change is
load-bearing for something the documentation explains, propose something
else”. A project file arrives with a cloned repository, so a project layer
able to set this could hand an unattended, privileged nightly a checkout of
its own prose and be believed about which of this harness’s protections are
load-bearing. merge_file strips it from project layers.
None means the diagnostician runs blind, which is what it did until this
existed and is still the default. That case is not silent: the system
prompt says so rather than claiming a capability the run was not given —
see crate::diagnose::diagnose_system.
Fields§
§source_dir: Option<PathBuf>A checkout of this program’s source and docs/. Jailed read-only, and
never the working directory: config is discovered from the cwd, so
standing in a checkout is what would put its mecha.toml in front of
an unattended run. The two are separable and this keeps them separate.
Trait Implementations§
Source§impl Clone for HarnessConfig
impl Clone for HarnessConfig
Source§fn clone(&self) -> HarnessConfig
fn clone(&self) -> HarnessConfig
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more