Member Junction
    Preparing search index...

    Shared accumulator fixture for the entity-graph-client bundle (client transport, mutating).

    Setup creates nothing — it only resolves the two ids the checks need to reference, so a deterministic-only run writes no rows at all. Each mutating check appends what it created, and Teardown sweeps FK-safe: AgentPromptIds before AgentIds, since a prompt row references its agent.

    interface EntityGraphClientFixture {
        AgentIds: string[];
        AgentPromptIds: string[];
        AgentTypeID?: string;
        Prefix: string;
        PromptIDs: string[];
    }
    Index

    Properties

    AgentIds: string[]

    Every MJ: AI Agents row the bundle created, in creation order.

    AgentPromptIds: string[]

    Every MJ: AI Agent Prompts row the bundle created, in creation order.

    AgentTypeID?: string

    An existing MJ: AI Agent Types id, when one exists. Optional on the schema, and leaving it unset also skips the server subclass's TypeConfiguration validation, which is not under test.

    Prefix: string

    Unique per-run name prefix stamped on every fixture agent.

    PromptIDs: string[]

    Two DISTINCT existing MJ: AI Prompts ids — the required FK on every child row the bundle stages. Two, not one, because UQ_AIAgentPrompt_Agent_Prompt_Config is unique on (AgentID, PromptID, ConfigurationID): staging the same prompt twice on one agent would fail the constraint rather than the behavior under test.