Module settings_ask 

The held configuration write.

A settings edit an agent asks for parks here, in the workspace’s own registry, until the person at a client answers it: the blocked tool call awaits a oneshot this module hands back, and nothing reaches forge.toml 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.

Re-exports

use uuid::Uuid; 🔒

use crate::SessionSlot; 🔒

use crate::protocol::PendingAsk; 🔒

use crate::protocol::SessionUpdate; 🔒

use crate::workspace::Workspace; 🔒

use forge_primitives::settings::SettingsWriteAsk; 🔒

use forge_primitives::settings::SettingsWriteEnding; 🔒

Type Aliases

ParkedSettingsWrite 🔒

One composed write held for a decision: the session that asked, the ask itself, and the sender the blocked tool handler awaits. The sender is taken at the answer: the entry stays until the write is settled, so a second view’s answer is refused while the first one applies, and the resolved update carries the write’s own outcome rather than the click.