Module vault_ask 

The held vault call.

A vault operation an agent asks for parks here, in the workspace’s own registry, until the person at a client answers it: the blocked MCP handler awaits a oneshot this module hands back, and no operation runs in the vault unless that answer approved it. It sits beside the Slack draft and the hand-offs for the same reason they do - the parking is workspace state, not a session’s pending set, so a seat with no domain can still hold one.

The lock state is not stored here. The draft is parked without it and stamped from the live session on every read, which is what lets a card whose sibling unlocked first re-base to an ordinary approve card.

Re-exports

use uuid::Uuid; 🔒

use crate::SessionSlot; 🔒

use crate::protocol::PendingAsk; 🔒

use crate::protocol::SessionUpdate; 🔒

use crate::workspace::Workspace; 🔒

use forge_primitives::vault::VaultAskAnswer; 🔒

use forge_primitives::vault::VaultAskEnding; 🔒

use forge_primitives::vault::VaultDraft; 🔒

Type Aliases

ParkedVaultAsk 🔒

One vault call held for a decision: the session that asked, the draft the card draws, and the sender the blocked tool handler awaits.