NAME

init - private built-in command wrapper for Developer Dashboard

SYNOPSIS

dashboard init

DESCRIPTION

This private helper is staged under ~/.developer-dashboard/cli/dd/ so the public dashboard entrypoint can stay a thin switchboard.

PURPOSE

This staged helper exposes dashboard init, the command that creates or refreshes the runtime tree, stages dashboard-managed helpers, and seeds starter pages when they are missing or safely refreshable.

WHY IT EXISTS

It exists because runtime bootstrap is a first-run command with non-destructive rules around existing config, helper staging, and managed seed refresh. That behavior needs a dedicated built-in entrypoint instead of ad hoc shell setup.

WHEN TO USE

Use this file when changing init CLI behavior or the handoff into the runtime bootstrap and seed-refresh implementation.

HOW TO USE

Users run dashboard init in a project or from home. The staged helper forwards that request into the private runtime, which creates the runtime directories, preserves existing config, stages helpers, and writes starter pages as needed.

WHAT USES IT

It is used for first-run setup, by integration smoke that builds fresh runtimes, and by tests that guard non-destructive init reruns and seed refresh behavior.

EXAMPLES

Example 1:

dashboard init

Run the public built-in command path that stages or re-enters this helper.

Example 2:

~/.developer-dashboard/cli/dd/init --help

Inspect the staged helper directly after dashboard init or helper extraction has populated the home runtime.

Example 3:

prove -lv t/05-cli-smoke.t t/30-dashboard-loader.t

Rerun the focused staged-helper and thin-loader tests after changing helper dispatch behavior.

Example 4:

prove -lr t

Verify that the helper still behaves correctly inside the complete repository suite.