Struct ApprovalGatedResolver 

pub struct ApprovalGatedResolver<R, F>
where
    R: SecretResolver,
    F: Fn(&str) -> ApproveOnUsePolicy + Send + Sync,
{ /* private fields */ }

Type-safe wrapper that enforces the approve-on-use policy before dispatching to an inner SecretResolver. This is what closes the loop on the P25 protocol — a resolver that is not gated through this wrapper makes the approve_on_use field a metadata-only theatrical control.

Construction takes three values:

1. An inner SecretResolver (keychain, local-vault, 1Password, …).
2. An Arc<SessionApprovalCache> — shared across every gated resolver in the process so the user only sees one prompt per session per path.
3. A policy_for_path closure — typically reads the path’s approve_on_use field from the merged manifest. The closure shape avoids a hard dependency on devboy-storage in this crate.

On every resolve() call:

• ApproveOnUsePolicy::Never → straight to the inner resolver.
• ApproveOnUsePolicy::Session with a cache hit → straight to the inner resolver.
• ApproveOnUsePolicy::Session without a cache hit, or ApproveOnUsePolicy::PerCall → return AliasResolverError::Backend with a message that names the path and the policy, so the caller can surface the approval dialog and retry.

Implementations

impl<R, F> ApprovalGatedResolver<R, F>

where R: SecretResolver, F: Fn(&str) -> ApproveOnUsePolicy + Send + Sync,

pub fn new( inner: R, cache: Arc<SessionApprovalCache>, policy_for_path: F, ) -> Self

pub fn cache(&self) -> &Arc<SessionApprovalCache>

Underlying cache handle — exposed so the orchestration layer (which drives the approval dialog) can call record_session after the user clicks “Allow always (this session)”.

Trait Implementations

impl<R, F> SecretResolver for ApprovalGatedResolver<R, F>

where R: SecretResolver, F: Fn(&str) -> ApproveOnUsePolicy + Send + Sync,

fn resolve(&self, path: &str) -> Result<SecretString, AliasResolverError>

Resolve path (the portion after @secret:) to its current value. Implementations consume the path verbatim; path validation belongs in the credential layer per ADR-020.