AutoBE
    Preparing search index...

    Interface AutoBeDebugHistory

    History record generated when the Debug phase validates runtime success.

    interface AutoBeDebugHistory {
        aggregates: AutoBeProcessAggregateCollection<"debug">;
        completed_at: string & Format<"date-time">;
        created_at: string & Format<"date-time">;
        id: string & Format<"uuid">;
        patches: AutoBeDebugPatch[];
        realizeHistoryId: string;
        runtime: IAutoBeDebugRuntimeSummary;
        step: number;
        testHistoryId: string;
        type: "debug";
    }

    Hierarchy

    • AutoBeAgentHistoryBase<"debug">
      • AutoBeDebugHistory
    Index

    Properties

    completed_at: string & Format<"date-time">

    ISO 8601 timestamp indicating when the Debug phase completed.

    created_at: string & Format<"date-time">

    ISO 8601 timestamp indicating when this history record was created.

    Marks the exact moment when this history entry was initiated or when the corresponding agent activity began. This timestamp is fundamental for maintaining chronological order, tracking development progress, and understanding the temporal relationships between different phases of the vibe coding process.

    id: string & Format<"uuid">

    Unique identifier for this history record.

    A UUID that uniquely identifies this specific history entry within the system. This identifier enables precise referencing, cross-linking between related history records, and maintaining referential integrity across the development timeline and different agent activities.

    patches: AutoBeDebugPatch[]

    Realize patches applied during runtime repair.

    realizeHistoryId: string

    Identifier of the Realize history validated by this Debug run.

    Final runtime execution summary after all Debug repair attempts.

    step: number

    Iteration number of the requirements analysis this Debug run validates.

    testHistoryId: string

    Identifier of the Test history executed by this Debug run.

    type: "debug"

    Type discriminator indicating the specific kind of history record.

    Provides type-safe discrimination between different history record types such as "analyze", "database", "interface", "realize", "test", "userMessage", and "assistantMessage". This enables proper type narrowing and ensures that history records are processed according to their specific characteristics and requirements.