/**
 * Integration — AgentManager.provisionSpawn compensating rollback.
 *
 * Covers Codex SPAWN-ROLLBACK critique (ses_001-hierarchy-redesign Phase 2
 * adversarial review, 2026-04-18). Without the try/catch wrapper around the
 * createSession → updateSession → createSubSession → workspace.create
 * mutation block, a failure after createSession leaves an `active` child
 * session with no subsession edge — invisible to the parent, but counted
 * against `maxDelegationWidth` and visible to SessionStore.listSessions
 * consumers (archive/delete flows in ThreadManager).
 *
 * Failure modes exercised:
 *   A. Workspace driver throws on create. Subsession exists; must flip to
 *      'failed' for audit. Child session must be hard-deleted.
 *   B. Subsession insert fails (store injection). No subsession recorded.
 *      Child session must be hard-deleted.
 *
 * Assertions in both cases:
 *   - sendMessage rejects with the underlying error.
 *   - SessionStore.listSessions(threadId) returns no row with the child id.
 *   - Parent session remains untouched (status, currentActor).
 *   - Fan-out cap reclaims the slot (next spawn succeeds up to the same
 *     width).
 */
export {};
//# sourceMappingURL=spawn-rollback.test.d.ts.map