/ 
Developer-Dashboard-2.17
/ _dashboard-core

NAME

_dashboard-core - internal staged built-in command runtime for Developer Dashboard

SYNOPSIS

_dashboard-core <built-in-command> [args...]

DESCRIPTION

This internal helper runs the heavier built-in Developer Dashboard commands after the public dashboard entrypoint has already handled hook execution and switchboard dispatch. It is staged under ~/.developer-dashboard/cli/dd/ as _dashboard-core and is not meant to be called by users directly. It also generates the shared shell bootstrap snippets that expose cdr, dd_cdr, which_dir, and prompt wiring across bash, zsh, POSIX sh, and PowerShell.

__END__

NAME

_dashboard-core - contains the shared private built-in command runtime that the staged helper scripts hand off into.

PURPOSE

This private staged runtime owns the heavier built-in command implementations after bin/dashboard has already done hook execution and helper dispatch. It is also where the generated shell bootstrap snippets come from, including cdr, which_dir, and prompt wiring across bash, zsh, POSIX sh, and PowerShell.

WHY IT EXISTS

It exists so the public entrypoint stays thin while dashboard-managed built-ins still share one internal command runtime. The staged helper wrappers can all hand off into this file instead of each carrying their own copy of command logic.

WHEN TO USE

Use this file when changing built-in command dispatch after helper staging, shell bootstrap generation, or behavior shared across multiple staged helper wrappers.

HOW TO USE

Users do not call this file directly. dashboard init or on-demand staging writes wrappers under ~/.developer-dashboard/cli/dd/, and those wrappers invoke _dashboard-core with the built-in command name they represent.

WHAT USES IT

It is used by every staged dashboard-managed helper under ~/.developer-dashboard/cli/dd/, by shell bootstrap generation, and by tests that verify the private-helper runtime contract.

EXAMPLES

Example 1:

dashboard paths

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

Example 2:

~/.developer-dashboard/cli/dd/_dashboard-core --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.