Module testing 

Test-only constructors, seed helpers and dispatch interception for Workspace, so tests here and cross-crate tests can drive a workspace without a real subprocess.

Re-exports

use std::collections::HashMap; 🔒

use std::collections::HashSet; 🔒

use std::path::PathBuf; 🔒

use std::sync::Arc; 🔒

use parking_lot::Mutex; 🔒

use tokio::sync::mpsc; 🔒

use crate::config::LoadedConfig; 🔒

use crate::domain_session::PendingInteractions; 🔒

use crate::protocol::SessionUpdate; 🔒

use crate::target::ProjectKey; 🔒

use crate::target::SessionSlot; 🔒

use crate::update_fanout::SeatUpdate; 🔒

use crate::update_fanout::SubscriberRole; 🔒

use crate::update_fanout::UpdateFanout; 🔒

use crate::workspace::KickRequest; 🔒

use crate::workspace::PendingInteractionKind; 🔒

use crate::workspace::PooledAgent; 🔒

use crate::workspace::Workspace; 🔒

use forge_gateway::AccountKey; 🔒

use forge_primitives::SessionId; 🔒

Constants

TEST_DOCUMENT_PATH 🔒

The path a seeded document hand-off parks at. The registration IS the state a seeder produces - nothing reads the file - so the fixture names one rather than touching disk.

TEST_TOOL_ID

The tool id a parked test prompt answers to, so a test addresses the one it seeded rather than a key it has to know how the fixture built.

Functions

set_seat_ring_cap

Drive a seat’s frame window down, so a fixture reaches the transcript fallback without emitting a window’s worth of frames. The window is otherwise the constant it ships as, and the module this sits in is the gate that keeps it out of production.

test_permission 🔒

A permission prompt for a fixture to park on a seat: the smallest one a dock can draw, carrying the id TEST_TOOL_ID answers to. A fixture is the only place a prompt is invented, so it says what it invents.

test_prompt 🔒

test_permission or test_question with a receiver nobody keeps.

test_question 🔒

The same, for a question.

test_tool_call 🔒

The tool call a fixture’s prompt is about.