@oss-autopilot/core - v3.7.0
    Preparing search index...

    Interface StartupOutput

    Output of the startup command (combines auth, setup, daily, dashboard, issue list).

    Three valid shapes:

    1. Setup incomplete: { version, setupComplete: false }
    2. Auth failure: { version, setupComplete: true, authError: "..." }
    3. Success: { version, setupComplete: true, daily, dashboardUrl?, issueList? }
    interface StartupOutput {
        authError?: string;
        autoDetected?: boolean;
        daily?: DailyOutput;
        dashboardBuildErrorTail?: string;
        dashboardBuildStatus?: "failed" | "fresh" | "rebuilt" | "missing-pnpm";
        dashboardError?: string;
        dashboardUrl?: string;
        issueList?: IssueListInfo;
        setupComplete: boolean;
        version: string;
    }
    Index

    Properties

    authError?: string
    autoDetected?: boolean

    True when username was auto-detected on first run (zero-config).

    daily?: DailyOutput
    dashboardBuildErrorTail?: string

    Last few lines of the dashboard build log when dashboardBuildStatus is 'failed' or 'missing-pnpm'. Surfaced by the workflow as a one-line warning so the user sees what broke without leaving /oss.

    dashboardBuildStatus?: "failed" | "fresh" | "rebuilt" | "missing-pnpm"

    Status of the dashboard SPA build that ran (or didn't) before this startup invocation (#1293). Populated by the workflow shell via OSS_DASHBOARD_BUILD_STATUS; absent when the CLI is invoked outside the plugin workflow:

    • 'fresh' — built artifact was up-to-date, no rebuild attempted.
    • 'rebuilt' — rebuild ran and succeeded.
    • 'failed' — rebuild ran and failed; dashboardUrl may serve stale or missing assets until the build is fixed.
    • 'missing-pnpm' — rebuild was needed but pnpm (required for the workspace dependency) was unavailable.
    dashboardError?: string

    Set when the dashboard launch or refresh failed (assets missing, port conflict, spawn error, etc.). The dashboard is always attempted, so JSON consumers — which previously saw only a missing dashboardUrl — now have a structured signal to surface or recover from the failure.

    dashboardUrl?: string

    URL of the interactive SPA dashboard server, when running (e.g., "http://localhost:3000")

    issueList?: IssueListInfo
    setupComplete: boolean
    version: string